Hi Manan,
Thanks for taking an interest in this project.
1. I am working with the 5.0.0 version of their OS, but I think the APIs I
am implementing are backwards compatible to the 4.1.0 version.
2. I am using the API that is exposed by the Firewall device (or Panorama),
so if you have a Palo Alto
Hi Will,
It is nice to see that you are adding integration with Palo Alto Firewall.
I have read the functional spec and I have a few additional questions.
1. Would this module work with all Palo Alto Firewalls or any specific
firewall models only?
2. Are you using all Publicly available APIs?
3.
Thanks for the information as well as the jira permissions. I have
assigned the issue to myself.
I will keep it in 'nonoss' for now and as I get near the end of the project
I can make a more educated decision on that point. The change is pretty
simple and it won't impact the implementation of th
On Thu, Feb 14, 2013 at 12:24:13PM -0500, Will Stevens wrote:
>- I am currently compiling my code using the 'nonoss' flag similar to
>JuniperSRX, Netscaler, etc... I will not be referencing any code external
>to CloudStack, but I will be integrating with the Palo Alto API. I need to
>
Here is the functional spec:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Palo+Alto+Firewall+Integration
I have most of the wiring in place now for the Palo Alto device to be
visible in the UI as a service provider. Currently my network/element and
network/resource files do not contain
