<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Expedition v2 recommended VM sizing on ESXi? in Expedition Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-v2-recommended-vm-sizing-on-esxi/m-p/559844#M4737</link>
    <description>&lt;P&gt;&lt;SPAN&gt;Hello &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/227268"&gt;@Eric_Troldahl&lt;/a&gt;,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I appreciate you reaching out and providing such a comprehensive explanation of your present circumstances and objectives.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I concur with your suggestion that the optimal course of action would be to establish a new, up-to-date OS environment for Expedition2.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You have the option to install the docker engine on a variety of platforms. You can find the relevant information here:&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://docs.docker.com/engine/install/" target="_blank"&gt;https://docs.docker.com/engine/install/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Expedition2 has multi-user support, enabling you to create a singular environment for your entire team. Alternatively, you could install Expedition2 locally for each team member. However, I would advise against having multiple users working on the same project simultaneously due to potential issues with concurrency.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;As for resource requirements, you could use those defined for Expedition1 as a starting point (refer to the document here:&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://live.paloaltonetworks.com/t5/expedition-articles/expedition-documentation/ta-p/215619?attachment-id=11295" target="_blank"&gt;https://live.paloaltonetworks.com/t5/expedition-articles/expedition-documentation/ta-p/215619?attachment-id=11295&lt;/A&gt;&lt;SPAN&gt;). Since Expedition2 operates over containers, you have the flexibility to increase the allocated resources based on the size of your project and the number of concurrent users/automations.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Please take a moment to review the manual attached to the shared Google drive folder and feel free to share your insights to enhance it.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I believe I've addressed all of your queries, but should you have any further questions or suggestions, don't hesitate to email us at&amp;nbsp;&lt;/SPAN&gt;&lt;A href="mailto:fwmigrate@paloaltonetworks.com" target="_blank"&gt;fwmigrate@paloaltonetworks.com&lt;/A&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Best regards,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;David&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 28 Sep 2023 10:42:38 GMT</pubDate>
    <dc:creator>dpuigdomenec</dc:creator>
    <dc:date>2023-09-28T10:42:38Z</dc:date>
    <item>
      <title>Expedition v2 recommended VM sizing on ESXi?</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-v2-recommended-vm-sizing-on-esxi/m-p/559744#M4736</link>
      <description>&lt;UL&gt;
&lt;LI&gt;Summary: &amp;nbsp;I want to spin up Expedition v2 with enough resources to migrate 125+ lsys off of Juniper ScreenOS and JunOS, and also have the ability to use Expedition to "Normalize/Optimize/Eliminate" duplicate objects, unused rules, merge nearly duplicate rules in Panorama, or any other benefits it may offer, so I want to make sure I have enough resources on the new VM. &amp;nbsp;I already have a dozen HA Pairs administered through Panorama, and these new migrations will mostly be to a large chassis (PA-5450) that is replacing 5 Juniper HA Pairs on the interior of our network. &amp;nbsp;I think I read somewhere a suggestion of 8 CPUs, 16GB RAM, and 500GB of Storage for Expedition - does that seem like a good recommendation if it is easier to ask once than expand multiple times in the future? &amp;nbsp;Do I need that much storage? &amp;nbsp;Less/More? &amp;nbsp;I don't really plan to keep all of the projects on Expedition forever, and once I get a script that does most of what I need a lot of these will be "Wash, Rinse, Repeat" - including using shared objects, but with so many migrations to do I will need to have multiple projects in storage at a time.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;The TL;DR:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;I've read througn a LOT of readme, quick start, config PDFs, etc, but... &amp;nbsp;so far no definitive specs for what I should install on that are explicitly stated to be for v2. &amp;nbsp;I am further hampered by the fact that we don't have a Docker expert on the team, so we don't know what we don't know.&lt;/LI&gt;
&lt;LI&gt;I ended up being the lone survivor of a Firewall support team, our documentation on using Expedition usage isn't the best, and I currently have Expedition v1 running with 1 CPU, 2GB RAM, and 40GB of storage, on Ubuntu 16.x LTS. &amp;nbsp;I now have a team that has joined me, soon to be 6 strong, but none of us currently have experience with either version of Expedition.&lt;/LI&gt;
&lt;LI&gt;I have over 130 juniper lsys to migrate to PanOS NGFW on Panorama, and I feel like I'm better off learning the new v2 than dealing with v1 and then having to learn v2 later.&lt;/LI&gt;
&lt;LI&gt;I was originally told by management to just use the current VM to install v2, but I'm thinking I'd be better off spinning up a new VM with reasonable specs and once I get v2 working kill the old VM. &amp;nbsp;Considering the Ubuntu version and the VM specs I can probably sell this concept if I have a solid configuration recommendation.&lt;/LI&gt;
&lt;/UL&gt;</description>
      <pubDate>Wed, 27 Sep 2023 18:11:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-v2-recommended-vm-sizing-on-esxi/m-p/559744#M4736</guid>
      <dc:creator>Eric_Troldahl</dc:creator>
      <dc:date>2023-09-27T18:11:16Z</dc:date>
    </item>
    <item>
      <title>Re: Expedition v2 recommended VM sizing on ESXi?</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-v2-recommended-vm-sizing-on-esxi/m-p/559844#M4737</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hello &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/227268"&gt;@Eric_Troldahl&lt;/a&gt;,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I appreciate you reaching out and providing such a comprehensive explanation of your present circumstances and objectives.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I concur with your suggestion that the optimal course of action would be to establish a new, up-to-date OS environment for Expedition2.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You have the option to install the docker engine on a variety of platforms. You can find the relevant information here:&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://docs.docker.com/engine/install/" target="_blank"&gt;https://docs.docker.com/engine/install/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Expedition2 has multi-user support, enabling you to create a singular environment for your entire team. Alternatively, you could install Expedition2 locally for each team member. However, I would advise against having multiple users working on the same project simultaneously due to potential issues with concurrency.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;As for resource requirements, you could use those defined for Expedition1 as a starting point (refer to the document here:&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://live.paloaltonetworks.com/t5/expedition-articles/expedition-documentation/ta-p/215619?attachment-id=11295" target="_blank"&gt;https://live.paloaltonetworks.com/t5/expedition-articles/expedition-documentation/ta-p/215619?attachment-id=11295&lt;/A&gt;&lt;SPAN&gt;). Since Expedition2 operates over containers, you have the flexibility to increase the allocated resources based on the size of your project and the number of concurrent users/automations.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Please take a moment to review the manual attached to the shared Google drive folder and feel free to share your insights to enhance it.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I believe I've addressed all of your queries, but should you have any further questions or suggestions, don't hesitate to email us at&amp;nbsp;&lt;/SPAN&gt;&lt;A href="mailto:fwmigrate@paloaltonetworks.com" target="_blank"&gt;fwmigrate@paloaltonetworks.com&lt;/A&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Best regards,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;David&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 28 Sep 2023 10:42:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-v2-recommended-vm-sizing-on-esxi/m-p/559844#M4737</guid>
      <dc:creator>dpuigdomenec</dc:creator>
      <dc:date>2023-09-28T10:42:38Z</dc:date>
    </item>
  </channel>
</rss>

