Please ignore this email. Wrong mailing list :)
Sorry!
Praveen
On Thu, Sep 28, 2017 at 9:16 PM Praveen Yalagandula <
yprav...@avinetworks.com> wrote:
> Siva,
> All changes for #1 are not in 17.1.8; there is a pull-request waiting your
> review for last few days.
> Note that
;
>>>> Do we have a way to validate if the tweaks to the Avi controller
>>>> leveraged at EBSCO have also been put in place at LogMeIn?
>>>> The LogMeIn team is asking which Avi software version they should be
>>>> running for Platform9 integration
t;>> This sounds like a bug on the Horizon side. There is/was a patch
>>> regarding a similar issue with LBaaS v2 resources too. It's likely just an
>>> incorrect assumption in the logic processing these names.
>>>
>>> Rob
>>>
>>> On 16 Au
Hi all,
We have developed some heat resources for our custom API server. We
followed the instructions in the development guide at
http://docs.openstack.org/developer/heat/pluginguide.html and got
everything working. However, the Horizon "Resource Types" panel is
returning a 500 error with
d" is the right parameter to define. Why do we need
"immutable"?
Thanks,
Praveen Yalagandula
Avi Networks
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@list
Zane,
Thanks for the reply; this is the information I was looking for.
Cheers,
Praveen
On Thu, Apr 14, 2016 at 10:51 AM Zane Bitter <zbit...@redhat.com> wrote:
> On 11/04/16 14:06, Praveen Yalagandula wrote:
> > Hi,
> >
> > We are developing a custom heat resource plug
We do this for the resources we ship with
> Heat (add new properties while supporting deprecated properties for several
> releases).
>
> On Apr 11, 2016, at 1:06 PM, "Praveen Yalagandula" <
> yprav...@avinetworks.com>
> wrote:
>
> > Hi,
> >
> &g
resources,
whose definitions have been upgraded, need to be updated too. Was there any
discussion on this?
Thanks,
Praveen Yalagandula
Avi Networks
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: ope
if the host has an ip_address of 10.10.1.1 and you want to allow
any ip in 10.10.1.0/24 to pass through the port you can just add a rule
for 10.10.1.0/24 directly without having to break it up.
Aaron
On Tue, May 20, 2014 at 11:20 AM, Praveen Yalagandula
yprav...@avinetworks.com wrote:
Hi Aaron
allowed. What's your
motivation for changing this?
Aaron
On Mon, May 19, 2014 at 4:05 PM, Praveen Yalagandula
yprav...@avinetworks.com wrote:
Hi Aaron,
Thanks for the prompt response.
If the overlap does not have any negative effect, can we please just
remove this check? It creates
Hi Aaron,
In OVS and ML2 plugins, on port-update, there is a check to make sure that
allowed-address-pairs and fixed-ips don't overlap. Can you please explain
why that is needed?
- icehouse final: neutron/plugins/ml2/plugin.py
677 elif changed_fixed_ips:
that traffic through.
Best,
Aaron
On Mon, May 19, 2014 at 12:22 PM, Praveen Yalagandula
yprav...@avinetworks.com wrote:
Hi Aaron,
In OVS and ML2 plugins, on port-update, there is a check to make sure
that allowed-address-pairs and fixed-ips don't overlap. Can you please
explain why
Hi Stephen,
If it is possible, can you please annotate the fields to distinguish the
required ones from the optional ones?
Thanks,
Praveen
On Mon, May 19, 2014 at 4:45 PM, Stephen Balukoff sbaluk...@bluebox.netwrote:
Hi folks,
Ok, I've attached a newly-updated object diagram (and its
13 matches
Mail list logo
