Dear all,
The issue is that we want to create a virtual link between two VMs on
the same physical machine (regardless of their interfaces and network
already created by neutron that inter-connect them through br-int or
ovs). Let us consider the most simple scenario: same physical machine,
same pro
Hi Roua,
AFAIK this is not possible with OpenStack. Neutron only has the concept
of attaching ports to a network. A concept where you do not attach a
port to a network - but create a direct link between instances does not
exist yet (except that you can create dedicated a network for each
direct li
Hello Roua Touihri,
I think you should consider neutron service plugin.
with neutron service plugin, you could crdate your own network service what you
want.
you could insert your codes into service plugin interacting with event(create,
delete, update) and resource(port, sunnet, network..)
Tha
We have deployed VYOS Firewall in deployment with the current scope of APIs
somewhat like Van mentioned in his mail. But my experience says the current
FWaaS API still need work for most of cloud deployment.
On Wed, Feb 1, 2017 at 3:36 PM, Jose Manuel Ferrer Mosteiro <
jmferrer.paradigmatecnolog.
Hi
Firewall policies can be implemented with security groups.
You can create as many isolated networks and routers as you want so an
instance can be isolated in its own network ... but I prefer using
security groups and creating a network for service (kubernetes: master
network, minion proje
Hey Cesar,
First of all, I haven’t use Vyattas at all, but I noticed that there is neutron
driver for that[1]. If you want to keep the current Vyattas deployment it’s
fine, more likely you’ll need to install a neutron agent there. I’m not sure if
you also need to populate the Neutron Database
> We currently have a cloud infrastructure meeting our own requirements.
> Let's focus on some Networking features (firewall, instances isolation,
> spoofing control). We are thinking about moving to OpenStack and when we
> focus on these Networking features, Neutron comes into play
> We are curr
what’s your l3agent.ini says about external?
> On Oct 6, 2016, at 06:16, kamalakannan sanjeevan
> wrote:
>
> Hello,
>
> I am not able to connect to internet in teh spawned VM's.
>
>
> Ethernet card details:
> Eth1 bridged through OVS(mybridge) - 172.27.10.76
> Eth3
+1
On Mon, Apr 25, 2016, 5:32 PM Armando M. wrote:
> On 25 April 2016 at 10:01, Ihar Hrachyshka wrote:
>
>> WAT???
>>
>> It was never supposed to be core only. Everyone is welcome!
>>
>
> In fact this should be cross-posted the other openstack ML too.
>
>
>> Sent from my iPhone
>>
>> > On 25 Ap
On 25 April 2016 at 10:01, Ihar Hrachyshka wrote:
> WAT???
>
> It was never supposed to be core only. Everyone is welcome!
>
In fact this should be cross-posted the other openstack ML too.
> Sent from my iPhone
>
> > On 25 Apr 2016, at 11:56, Edgar Magana wrote:
> >
> > Would you extend it to
I agree that the current definition can be improved.
"Provider Network" vs "Self service network" highlights who can
provision a network.
In my understanding, "Provider Network" is a network provisioned by
the cloud operator. Practically the operator cannot provision a network
for a tenant, so a
Yes, I think of it as:
A provider network in OpenStack is simply a record specifying the necessary
details of the underlying infrastructure so that OpenStack can utilize it. The
actual networking services (layer 2 and 3 forwarding, for example) are provided
by the infrastructure and configured
I'm walking away :-) let Mirantis pay! Lol
Sent from my iPhone
On May 18, 2015, at 8:26 PM, Kevin Benton
mailto:blak...@gmail.com>> wrote:
Don't forget to pay your tab. This event isn't sponsored! :)
Cheers,
Kevin Benton
On May 17, 2015 1:19 PM, "Kevin Benton"
mailto:blak...@gmail.com>> wro
Hey guys sorry for the delayed reply. The problem was with the whitelist. I
had whitelisted the id of the physical function instead of the virtual
function.
On Mon, Dec 8, 2014 at 9:33 AM, shihanzhang wrote:
> I think the problem is in nova, can you show your
> "pci_passthrough_whitelist" in no
Hi Kyle,
I am not missing the point. I understand the proposal. I just think that it has
some shortcomings (unless I misunderstand, which will certainly not be the
first time and most definitely not the last). The thinning out is to have a
shim in place. I understand this and this will be the en
Hi,
I have raised my concerns on the proposal. I think that all plugins should be
treated on an equal footing. My main concern is having the ML2 plugin in tree
whilst the others will be moved out of tree will be problematic. I think that
the model will be complete if the ML2 was also out of tree
Hi,
I think it's better to ask this question at ask.openstack.org or the
openstack mailing list.
BR,
Itzik
On 12/04/2014 12:26 PM, Akilesh K wrote:
Hi,
I am using neutron-plugin-sriov-agent.
I have configured pci_whitelist in nova.conf
I have configured ml2_conf_sriov.ini.
But when I laun
I WANNA GO
2014-11-06 19:52 GMT-02:00 Armando M. :
> Thanks for everyone who turned up!
>
> It was nice seeing you there, it was last minute planning...but we manage
> to squeeze in okay!
>
> Cheers,
> Armando
>
> On 6 November 2014 17:16, Oleg Bondarev wrote:
>
>> Please count me in.
>>
>>
Thanks for everyone who turned up!
It was nice seeing you there, it was last minute planning...but we manage
to squeeze in okay!
Cheers,
Armando
On 6 November 2014 17:16, Oleg Bondarev wrote:
> Please count me in.
>
> Thanks,
> Oleg
>
> ___
> OpenSta
Hi All,
Putting it in the right forum. Please help.
Regards,
Vishal
From: Vishal2 Agarwal
Sent: Wednesday, May 07, 2014 12:28 PM
To: 'openstack-...@lists.openstack.org'
Subject: [openstack-dev] [Neutron][Subnet] Unable to update external network
subnet's gateway-ip
Hi All,
I am trying below s
On Thu, 2014-01-16 at 17:41 +0900, NOTSU Arata wrote:
> Hello,
>
> I'm trying to add a new configuration option for Neutron OVS agent. Although
> I've submitted a patch and it is being reviewed [1], I'm posting to this
> mailing list seeking opinion from a wider range.
>
> At present, when you
Guys,
Let me ask something about this...
Apparently, VXLAN can be easier to implement/maintain when using it with
IPv6 (read about it here: www.nephos6.com/pdf/OpenStack-on-IPv6.pdf), so,
I'm wondering if local_ip can be an IPv6 address (for IceHouse-3 / Ubuntu
14.04) and, of course, if it is bet
On 16 January 2014 21:41, NOTSU Arata wrote:
> Hello,
>
> I'm trying to add a new configuration option for Neutron OVS agent. Although
> I've submitted a patch and it is being reviewed [1], I'm posting to this
> mailing list seeking opinion from a wider range.
>
> At present, when you deploy an
..
--
Trinath Somanchi - B39208
trinath.soman...@freescale.com | extn: 4048
-Original Message-
From: Robert Kukura [mailto:rkuk...@redhat.com]
Sent: Saturday, November 16, 2013 4:11 AM
To: openstack@lists.openstack.org
Subject: Re: [Openstack] [openstack-dev] [Neutron] Server restart failes when
|
>> | provider:network_type | local|
>> | provider:physical_network | |
>> | provider:segmentation_id | |
>> | shared | False
| |
> | tenant_id | 18088213420b45109da582f677ed8367 |
> +---+--+
>
> I have a Doubt here, Why is that the provider:network_type is “local” when
> the tenant_network_type is
> But if there are two
> physical NIC's which were diced up with SRIOV, then VM's on the diced
> parts of the first physical NIC cannot communicate easily with the
> VM's on the diced parts of the second physical NIC. So a native
> implementation has to be there on the Compute Node which will aid
On 10/10/2013 01:19 AM, Prashant Upadhyaya wrote:
Hi Chris,
I note two of your comments --
When we worked on H release, we target for basic PCI support
like accelerator card or encryption card etc.
PU> So I note that you are already solving the PCI pass through
usecase somehow ? How ? If y
Hi Chris,
I note two of your comments --
> > When we worked on H release, we target for basic PCI support like
> > accelerator card or encryption card etc.
PU> So I note that you are already solving the PCI pass through usecase somehow
? How ? If you have solved this already in terms of archite
Hi,
When compared to Nova URL implementations, It is observed that the Neutron
URL support cannot be used for more than TWO levels.
Applications which want to add as PLUG-IN may be restricted with this.
We want to add support for changes required for supporting more than TWO
Levels of URL by add
30 matches
Mail list logo
