Getting bug fixes into 4.3

[Will Stevens <ws...@cloudops.com>]

While I was troubleshooting some bugs that appeared in my Palo Alto
Networks firewall integration, I found a bunch of bugs with the way that
the egress firewall rules were handled.

I have created an issue for these bugs:
https://issues.apache.org/jira/browse/CLOUDSTACK-5278

I am not sure how these bugs should be resolved because I am not very
familiar with the underlying implementation of the egress rules.

Should I try to just work around the current issues in the egress rules
implementation for my specific plugin or should I create an issue for the
bugs in my plugin which is dependant on the egress bugs issue and set the
egress rule bugs issue as blocking the issue for my plugin?

Since we need to tie up all the loose ends for the 4.3 code base, I am not
sure the best way to handle this.  I believe the other plugins have
implemented workarounds for these issues, but I don't know that for sure.

Thanks,

Will

Re: Getting bug fixes into 4.3

[Will Stevens <ws...@cloudops.com>]

I have compiled a list of bugs in this issue:
https://issues.apache.org/jira/browse/CLOUDSTACK-5278

Will


On Wed, Nov 27, 2013 at 3:59 PM, Animesh Chaturvedi <
animesh.chaturvedi@citrix.com> wrote:

> It is best to file issues and then we can triage them, once you have
> compiled the list call it out on the mailing list and we can discuss what
> can or cannot be done in 4.3 There is still time for 4.3 so ideally we
> should address as much as possible in 4.3
>
> Animesh
>
> -----Original Message-----
> From: williamstevens@gmail.com [mailto:williamstevens@gmail.com] On
> Behalf Of Will Stevens
> Sent: Wednesday, November 27, 2013 10:57 AM
> To: dev@cloudstack.apache.org
> Subject: Getting bug fixes into 4.3
>
> While I was troubleshooting some bugs that appeared in my Palo Alto
> Networks firewall integration, I found a bunch of bugs with the way that
> the egress firewall rules were handled.
>
> I have created an issue for these bugs:
> https://issues.apache.org/jira/browse/CLOUDSTACK-5278
>
> I am not sure how these bugs should be resolved because I am not very
> familiar with the underlying implementation of the egress rules.
>
> Should I try to just work around the current issues in the egress rules
> implementation for my specific plugin or should I create an issue for the
> bugs in my plugin which is dependant on the egress bugs issue and set the
> egress rule bugs issue as blocking the issue for my plugin?
>
> Since we need to tie up all the loose ends for the 4.3 code base, I am not
> sure the best way to handle this.  I believe the other plugins have
> implemented workarounds for these issues, but I don't know that for sure.
>
> Thanks,
>
> Will
>

RE: Getting bug fixes into 4.3

[Animesh Chaturvedi <an...@citrix.com>]

It is best to file issues and then we can triage them, once you have compiled the list call it out on the mailing list and we can discuss what can or cannot be done in 4.3 There is still time for 4.3 so ideally we should address as much as possible in 4.3

Animesh

-----Original Message-----
From: williamstevens@gmail.com [mailto:williamstevens@gmail.com] On Behalf Of Will Stevens
Sent: Wednesday, November 27, 2013 10:57 AM
To: dev@cloudstack.apache.org
Subject: Getting bug fixes into 4.3

While I was troubleshooting some bugs that appeared in my Palo Alto Networks firewall integration, I found a bunch of bugs with the way that the egress firewall rules were handled.

I have created an issue for these bugs:
https://issues.apache.org/jira/browse/CLOUDSTACK-5278

I am not sure how these bugs should be resolved because I am not very familiar with the underlying implementation of the egress rules.

Should I try to just work around the current issues in the egress rules implementation for my specific plugin or should I create an issue for the bugs in my plugin which is dependant on the egress bugs issue and set the egress rule bugs issue as blocking the issue for my plugin?

Since we need to tie up all the loose ends for the 4.3 code base, I am not sure the best way to handle this.  I believe the other plugins have implemented workarounds for these issues, but I don't know that for sure.

Thanks,

Will