+1 for Mark McClain.
Regards,
Balaji.P
From: Justin Hammond [mailto:justin.hamm...@rackspace.com]
Sent: Saturday, September 21, 2013 9:13 AM
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] [Neutron] PTL Candidacy
I agree. +1. Mark has been nothing but helpful to me and I have
Hi,
Virtio-Serial interface support for Nova - Libvirt is not available now. Some
VMs who wants to access the Host may need like running qemu-guest-agent or any
proprietary software want to use this mode of communication with Host.
Qemu-GA uses virtio-serial communication.
We want to propose a
Hi,
If anyone is already working on the below support for Nova, Please let us know.
Regards,
Balaji.P
-Original Message-
From: P Balaji-B37839
Sent: Tuesday, September 24, 2013 4:10 PM
To: openstack-dev@lists.openstack.org
Cc: Addepalli Srini-B22160; Mannidi Purandhar Sairam-B39209
p 24, 2013 at 8:10 PM, Haomai Wang
mailto:hao...@unitedstack.com>> wrote:
On Sep 24, 2013, at 6:40 PM, P Balaji-B37839
mailto:b37...@freescale.com>> wrote:
> Hi,
>
> Virtio-Serial interface support for Nova - Libvirt is not available now. Some
> VMs who wants to access th
I overcome that?
Thanks,
-Ravi.
On Wed, Sep 25, 2013 at 3:01 AM, P Balaji-B37839
mailto:b37...@freescale.com>> wrote:
Hi Wangpan,
Thanks for Information and suggestions.
We want to have generic virtio-serial interface for Libvirt and applications
can use this irrespective of Qemu Gues
. Berrange [mailto:berra...@redhat.com]
Sent: Thursday, September 26, 2013 1:41 PM
To: P Balaji-B37839
Cc: OpenStack Development Mailing List
Subject: Re: [openstack-dev] [Nova] [Libvirt] Virtio-Serial support for Nova
libvirt driver
On Thu, Sep 26, 2013 at 03:05:16AM +, P Balaji-B37839 wrote:
>
On Mon, Sep 30, 2013 at 08:32:51AM +, P Balaji-B37839 wrote:
> Hi Daniel,
>
> Thanks for comments and examples.
>
> As you already know that for any application running on Host platform
> can communicate with Guest through Virtio-Serial device. What we are
> looki
support for those in Nova at least. There may be UI missing in Horizon
> > to enable though. Any further agents would require some kind of
> > software integration on the host with either qemu, libvirt or Nova
> > itself. So any blueprint should specify what that new agent is,
Agent, But it will add another daemon in
Guest which is not optimal.
Regards,
Balaji.P
> -Original Message-
> From: Daniel P. Berrange [mailto:berra...@redhat.com]
> Sent: Monday, September 30, 2013 5:21 PM
> To: P Balaji-B37839
> Cc: OpenStack Development Mailing Lis
Hi Ravi,
Thanks for giving reference examples.
Though I tried to give very generic use case without referring to Networking
use cases. It is good that you referred to examples so that the community can
understand the need for it.
Regards,
Balaji.P
From: Ravi Chunduru [mailto:ravi...@gmail.com
Hi Ravi and Daniel,
Good that we all converged on the need for this support in Nova Libvirt Driver.
We will collaborate together on this blueprint and make it upstream for
IceHouse.
Regards,
Balaji.P
> -Original Message-
> From: Daniel P. Berrange [mailto:berra...@redhat.com]
> Sent: M
Hi,
Current OVS Agent is creating tunnel with dst_port as the port configured in
INI file on Compute Node. If all the compute nodes on VXLAN network are
configured for DEFAULT port it is fine.
When any of the Compute Nodes are configured for CUSTOM udp port as VXLAN UDP
Port, Then how does the
Any comments on the below from community using OVS will be helpful.
Regards,
Balaji.P
> -Original Message-
> From: P Balaji-B37839
> Sent: Tuesday, October 08, 2013 2:31 PM
> To: OpenStack Development Mailing List; Addepalli Srini-B22160
> Subject: [openstack-dev] [Neutron
n tunnel. But you should
> fill a bug for that, to track this issue.
>
> Thanks for playing with vxlan, and helping us to debug it!
>
>
> On Wed, Oct 9, 2013 at 6:55 AM, P Balaji-B37839
> wrote:
> > Any comments on the below from community using OVS will be helpfu
Agent and VxLan UDP Ports
>
> On Oct 8, 2013, at 4:01 AM, P Balaji-B37839 wrote:
> > Hi,
> >
> > Current OVS Agent is creating tunnel with dst_port as the port
> configured in INI file on Compute Node. If all the compute nodes on VXLAN
> network are configured for DEF
Though we can configure in Nova.conf file, but we have to make sure these
tunnel interface ipaddress of every compute node and nova.conf will have the
same configuration.
But it is still painful to make sure that the ipaddress are configured properly.
We want to come up with BP to avoid these ma
Are the below observations on Havana?
From: Gopi Krishna B [mailto:gopi97...@gmail.com]
Sent: Tuesday, October 22, 2013 12:52 PM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] Merge multiple OVS bridges ?
Hi
Currently in Neutron the integration bridge (br-int) and other bridges
+1
I would like to contribute for this BP.
Regards,
Balaji.P
> -Original Message-
> From: openst...@cdl.asgaard.org [mailto:openst...@cdl.asgaard.org]
> Sent: Wednesday, October 23, 2013 9:47 AM
> To: OpenStack Development Mailing List
> Subject: Re: [openstack-dev] Distributed Virtual R
+1 for Kyle and
+1 for Armando
Both are going to adding muscle to Neutron Core Team.
Congrats Guys!
On 07/23/2013 03:15 PM, Mark McClain wrote:
> All-
>
> I'd like to propose that Kyle Mestery and Armando Migliaccio be added to the
> Neutron core team. Both have been very active with valuabl
: OpenStack Development Mailing List
Subject: Re: [openstack-dev] [Neutron] Network Information Sharing with
OpenFlow Controller
On Aug 4, 2013, at 1:20 AM, P Balaji-B37839 wrote:
> Hi,
>
> Anyone in the community is working on the OpenStack Controller and OpenFlow
> Controller Integration
Though we can add multiple subnets to the Network. We don't have an option to
attach/select subnet to Network. It is observed that when all the IP Address
are consumed from first subnet, then it starts using the next subnet available
for the network.
More flexibility in selecting subnet to Netw
Hi Zhidong,
Thanks for pointers.
IMHO, we need to have a flexibility to attach/select a Subnet for Networks and
as well support for L2/L3 mode selection.
Certainly this will extend the Neutron use cases for ex: NFV deployments etc.
Any comments?
Regards,
Balaji.P
From: Zhidong Yu [mailto:zdy
Thanks Justin.
Sure, we will take your help as it is required on this. We will prepare
blue-print capturing all the details and will assign you as reviewer.
Regards,
Balaji.P
From: Justin Hammond [mailto:justin.hamm...@rackspace.com]
Sent: Thursday, August 29, 2013 7:39 PM
To: OpenStack Develop
Hi Mark,
Do you suggest us to pause on this BP. Let us know if someone is already
working on this.
Regards,
Balaji.P
From: Mark McClain [mailto:mark.mccl...@dreamhost.com]
Sent: Friday, August 30, 2013 5:41 AM
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] [Neutron] Resourc
Hi,
We have gone through the below link for new plug-in development.
https://wiki.openstack.org/wiki/NeutronDevelopment#Developing_a_Neutron_Plugin
Just want to confirm that is it mandatory to be Core Neutron Developer for
submitting a new plug-in.?
How do we get a reviewer for this like Can w
it getting in now are pretty slim (you are
welcome to ask for e feature freeze exception but it is very late int he game).
I suggest that you target for the Icehouse version.
Thanks
Gary
From: P Balaji-B37839 mailto:b37...@freescale.com>>
Reply-To: OpenStack Development Mailin
twork devices
or controllers, and can work in conjunction with the existing L2 agents if
needed. See
https://wiki.openstack.org/wiki/Neutron/ML2 for more info.
-Bob
>
> mark
>
> On Sep 10, 2013, at 9:37 AM, "Kyle Mestery (kmestery)"
> wrote:
>
>> On Sep 10, 2
27 matches
Mail list logo
