Dear Nova Community,
I want to announce the new focal point for Nova s390x libvirt/kvm.
Please welcome "Cathy Zhang” to the Nova team. She and her team will be
responsible for maintaining the s390x libvirt/kvm Thirdparty CI [1] and any
s390x specific code in nova and os-brick.
I personally took
Hi Ihar, it was always a pleasure learning from and working with you. Wish you
all the best for your new project!
---
Andreas Scheuring (andreas_s)
On 4. Jun 2018, at 22:31, Ihar Hrachyshka wrote:
Hi neutrinos and all,
As some of you've already noticed, the last several months
succeed again in the check
queue - merge it.
Then you can put your new great custom code on top of this patch.
---
Andreas Scheuring (andreas_s)
On 9. May 2018, at 10:04, Andreas Scheuring wrote:
neutron.plugins.ml2.driver_api got moved to neutron-lib. You probably need to
update the networking
The root cause seems to be bug [1]. It’s related to nova cells v2 configuration
in devstack. Stephen Finucane already promised to have a look later the day
(thx!!!). I keep the CI running for now...
[1] https://bugs.launchpad.net/devstack/+bug/1770143
---
Andreas Scheuring (andreas_s)
On 9
Hi all, the nova CI for zKVM is currently broken - need to investigate. It
seems like the vnc console gets configured for some reason (vnc is not
supported on s390x)...
---
Andreas Scheuring (andreas_s)
__
OpenStack
neutron.plugins.ml2.driver_api got moved to neutron-lib. You probably need to
update the networking-onos code and fix all imports there and push the
changes...
---
Andreas Scheuring (andreas_s)
On 9. May 2018, at 10:00, Sangho Shin wrote:
Hello,
I am getting the following unit test
Looks good IMO.
---
Andreas Scheuring (andreas_s)
On 11. Apr 2018, at 15:46, Eric Fried wrote:
Jichen was able to use this information immediately, to great benefit
[1]. (If those paying attention could have a quick look at that to make
sure he used it right, it would be appreciated; I&#
Yes, that’s how it works!
---
Andreas Scheuring (andreas_s)
On 10. Apr 2018, at 16:05, Matt Riedemann wrote:
On 4/9/2018 9:57 PM, Chen CH Ji wrote:
> Could you please help to share whether this kind of event is sent by
> neutron-server or neutron agent ? I searched neutron code
> f
No problem from s390x point of view. With Ubuntu we’re currently using* qemu: 2.10.1* libvirt: 3.6.0Thanks!
---Andreas Scheuring (andreas_s)
On 30. Mar 2018, at 16:26, Kashyap Chamarthy <kcham...@redhat.com> wrote:The last version bump was in "Pike" release (commit: b980df0,11-F
].
[1]
https://github.com/svinota/pyroute2/commit/02328faf0de10073bc9e71d593b1656db62f6f6b
---
Andreas Scheuring (andreas_s)
On 14. Mar 2018, at 17:29, Andreas Scheuring
wrote:
A brief update: The root cause is that Neutron patch [1] broke Neutron DHCP and
L3 agent on s390x (both use
/openstack/neutron/commit/c4d4336
[2] https://github.com/svinota/pyroute2/pull/469
---
Andreas Scheuring (andreas_s)
On 13. Mar 2018, at 17:14, Andreas Scheuring
wrote:
Hello, the s390x CI for nova is currently broken again. The reason seems to be
a recent change that merged in neutron. I’m
Hello, the s390x CI for nova is currently broken again. The reason seems to be
a recent change that merged in neutron. I’m looking into it...
---
Andreas Scheuring (andreas_s)
__
OpenStack Development Mailing List (not
CI seems to be running again, but with a reduced number of tests for now (only
nova.api, excluded scenario tests). Will continue working on getting all tests
executing again.
---
Andreas Scheuring (andreas_s)
On 5. Mar 2018, at 09:35, Andreas Scheuring wrote:
Hi all,
the s390x nova CI is
Hi all,
the s390x nova CI is currently broken due to the bump of the grpcio version.
I’m working on fixing it….
Regards,
---
Andreas Scheuring (andreas_s)
__
OpenStack Development Mailing List (not for usage questions
x27; is part of the daily nodepool image
build.
---
Andreas Scheuring (andreas_s)
On 25. Jan 2018, at 10:57, Andreas Scheuring
wrote:
Hi, the Nova IBM zKVM CI is currently producing invalid builds. Please ignore
the -1 results for now. I’m working on fixing it. Will let you know once it’s
wor
Hi, the Nova IBM zKVM CI is currently producing invalid builds. Please ignore
the -1 results for now. I’m working on fixing it. Will let you know once it’s
working fine again. Thanks!
---
Andreas Scheuring (andreas_s
Hi Laurene,
at the moment the z/VM CI is posting a +1 even though the job failed. That’s
because in zuul layout.yaml the job is probably set to "voting: false.” You can
easily fix this by setting it to “true”.
For example see https://review.openstack.org/#/c/512190/
Regards,
---
An
Yes, job_name_in_report = true did it!
---
Andreas Scheuring (andreas_s)
> On 6. Oct 2017, at 17:01, Andreas Scheuring
> wrote:
>
> Probably it’s the following setting in zuul.conf
>
> job_name_in_report = true
>
> We’ll see if it works out in 1.5h when
Probably it’s the following setting in zuul.conf
job_name_in_report = true
We’ll see if it works out in 1.5h when the first test succeeded…
Thanks!
---
Andreas Scheuring (andreas_s)
> On 6. Oct 2017, at 12:53, Sean Dague wrote:
>
> On 10/06/2017 04:07 AM, Andreas Scheuring wro
com/project?project=nova>
[3] http://lists.openstack.org/pipermail/openstack-dev/2017-October/123195.html
Andreas Scheuring (andreas_s)__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-de
Thanks!
> On 6. Oct 2017, at 04:25, Ian Wienand wrote:
>
> On 10/06/2017 02:19 AM, Andreas Scheuring wrote:
>> seems like there is some confusing information about the DIB
>> meetings in the wiki [1]. The meeting is alternating between 15:00
>> and 20:00 UTC. But w
iscussions.
Thanks!
[1] https://wiki.openstack.org/wiki/Meetings/diskimage-builder
--
Andreas Scheuring (andreas_s)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...
ect=nova
[4]
http://eavesdrop.openstack.org/irclogs/%23openstack-meeting/%23openstack-meeting.2017-02-02.log.html#t2017-02-02T21:08:46
---
Andreas Scheuring (andreas_s)
__
OpenStack Development Mailing List (not for usage questions)
Uns
Hi all,
I would like to get clarity about the sate of the Barbican PKCS#11
Plug-in. We did some tests against against the PKCS#11 implementation
opencryptoki configured with a s390x hardware backend.
The main issue seems to be, that the plug-in has been developed against
PKCS#11 2.40 draft [2]- b
ainst devstack to track the discussion [3]
[1] https://review.openstack.org/#/c/467436/
[2] https://github.com/coreos/etcd/issues/7978
[3] https://bugs.launchpad.net/devstack/+bug/1693192
--
-
Andreas
IRC: andreas_s
On Mi, 2017-05-24 at 13:48 +0200, Andreas Scheuring wrote:
> Hi
Hi together,
recently etcd3 was enabled as service in devstack [1]. This breaks
devstack on s390x Linux, as there are no s390x binaries availabe and
there's no way to disable the etcd3 service.
I pushed a patch to allow disabling the etcd3 service in local.conf [2].
It would be great if we could
Rossella, we will miss you! All the best for your future engagements!
--
-
Andreas
IRC: andreas_s
On Do, 2017-05-04 at 15:52 +0200, Rossella Sblendido wrote:
> Hi all,
>
> I've moved to a new position recently and despite my best intentions I
> was not able to devote to Neutron as much
Really sad to hear that.
It was a pleasure working with you - all the best for your future!
--
-
Andreas
IRC: andreas_s
On Mi, 2017-05-03 at 00:39 +, Das, Anindita wrote:
> Hi All,
>
>
>
> Some of you already know about the recent changes in OSIC.
> Unfortunately, I am impacted by
Hi,
I wanted to understand which project requirement files get updated by
the OpenStack proposal bot. Only requirements.txt and
test-requirements.txt, or also foo-requirements.txt?
Pointing me to the OpenStack proposal bot code would also help I
guess...
Thanks
--
-
Andreas
IRC: andreas_s
even daily except during the requirements freeze?
Thanks!
--
-
Andreas
IRC: andreas_s
On Fr, 2017-02-24 at 11:22 -0500, Tony Breeds wrote:
> On Fri, Feb 24, 2017 at 02:09:33PM +0100, Andreas Scheuring wrote:
> > Hi, I have a couple of questions in regards of how updates of
> &g
Hi, I have a couple of questions in regards of how updates of
requirements are handled and what happens if I release a new version of
a library. I read along the README [1], but a few points are still
unclear to me.
I have the following projects:
* os-dpm [4]
* is a openstack library that gets
sense?
--
-
Andreas
IRC: andreas_s
On Di, 2017-01-31 at 10:43 -0600, Matthew Thode wrote:
> On 01/31/2017 09:35 AM, Andreas Scheuring wrote:
> > Hi, I'm requesting a feature freeze exception for raising the upper
> > constraint of the os-dpm library. Therefore the following patch got
&
Hi, I'm requesting a feature freeze exception for raising the upper
constraint of the os-dpm library. Therefore the following patch got
submitted to gerrit [1].
os-dpm is a shared library between the projects nova-dpm [2] and
networking-dpm [3]. Those projects are still under development (first
r
T_IP=10.0.2.15
>
>
> PUBLIC_INTERFACE=eth0
>
>
> Q_USE_SECGROUP=True
> ENABLE_TENANT_VLANS=True
> TENANT_VLAN_RANGE=1000:1999
> PHYSICAL_NETWORK=default
> OVS_PHYSICAL_BRIDGE=br-ex
>
>
>
>
> Q_USE_PROVIDER_NETWORKING=True
> Q_L3_ENABLE
Without looking into the details
you're specifying
Q_USE_PROVIDER_NETWORKING=True
in your local.conf - usually this results in the creation of a single
provider network called "public". But the manila devstack plugin seems
not to be able to deal with provider networks as it's expecting a
I'm sad to see you stepping down. Thanks a lot Armando for your amazing
service as PTL!
--
-
Andreas
IRC: andreas_s
On Mo, 2017-01-09 at 15:11 +0100, Armando M. wrote:
> Hi neutrinos,
>
>
> The PTL nomination week is fast approaching [0], and as you might have
> guessed by the subject
+1
--
-
Andreas
IRC: andreas_s
On Fr, 2016-12-16 at 00:14 +0100, Armando M. wrote:
> Hi neutrinos,
>
>
> Miguel Lavalle has been driving the project forward consistently and
> reliably. I would like to propose him to be entrusted with +2/+A
> rights in the areas he's been most prolific,
Henry, it was a pleasure working with you! Thanks!
All the best for your further journey!
--
-
Andreas
IRC: andreas_s
On Do, 2016-12-01 at 17:51 -0500, Henry Gessau wrote:
> I've already communicated this in the neutron meeting and in some neutron
> policy patches, but yesterday the PTL
Hi infra team,
would you mind adding myself (andreas.scheur...@de.ibm.com) to the
following gerrit groups?
- networking-dpm-core
- networking-dpm-release
Thanks a lot!
Andreas
IRC: andreas_s
__
OpenStack Development Mail
Hi everybody,
as I cannot join todays Neutron meeting, I wanted to give a brief update
via ML. All bugs are tracked in the following etherpad:
https://etherpad.openstack.org/p/bugs-2016-11-08
Of interest are the sections
- High/Critical
- Tagged but not able to confirm (reaching out to subsyste
I just pushed an update to the neutron spec [1], describing the general
purpose portbinding API that we decided on in Tuesdays Nova-Neutron
Cross project session.
Please review it and let me know, if I understood everything correctly!
When going down the path with the general purpose API, some
-1 I'm sorry, but I also need to cancel.
Andreas
On 10/26/2016 08:10 PM, John McDowall wrote:
-1
Unfortunately, a business meeting has come up
Regards
John
__
OpenStack Development Mailing List (not for usage questi
+1
--
-
Andreas
IRC: andreas_s
On Di, 2016-10-18 at 16:18 -0700, Isaku Yamahata wrote:
> +1
> Thanks for organizing this.
>
> On Fri, Oct 14, 2016 at 01:30:57PM -0500,
> Miguel Lavalle wrote:
>
> > Dear Neutrinos,
> >
> > I am organizing a social event for the team on Thursday 27th at
Hi,
I'm currently working on solving Nova-Neutron issues during Live
Migration. This mail is intended to raise awareness cross project and
get things kicked off.
The issues
==
#1 When portbinding fails, instance is migrated but stuck in error state
#2 Macvtap agent live Migration when so
While reviewing [1] I got hung up on the terms "device" and "interface".
It seems like in sr-iov agent they are used in a different manner than
in the linuxbridge agent.
For Example the lb agent uses a config option
"physical_interface_mappings" (mapping between uplink interface for
bridge and ph
Now I'm blaming myself - had a closer look at the code - it's NOT a
message via the Bus, but some nova external events interface that I was
not aware of.
Sorry for all the confusion
--
-
Andreas
IRC: andreas_s
On Mi, 2016-06-08 at 08:09 +0200, Andreas Scheuring wrote:
> >
at 20:17 +0200, Armando M. wrote:
>
>
> On 6 June 2016 at 17:05, Andreas Scheuring
> wrote:
> Is there a chance to get rid of this vif-plugged event at all?
> E.g. by
> transitioning it to an ReST API interface? As far as I know
> this is
The ovs agent reports if it uses hybrid plug or not since [1]. At least
the hybrid plug is part of the agent state - haven't tested if it's
visible via the API. Might that be helpful?
[1]https://review.openstack.org/#/c/311814/
--
-
Andreas
IRC: andreas_s (formerly scheuran)
On Mo, 2016-
Is there a chance to get rid of this vif-plugged event at all? E.g. by
transitioning it to an ReST API interface? As far as I know this is the
only RPC interface between neutron and nova.
--
-
Andreas
IRC: andreas_s (formerly scheuran)
On Mo, 2016-06-06 at 20:25 +0900, Akihiro Motoki wr
--
-
Andreas (IRC: andreas_s)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listi
After some discussion how portbinding handling could be improved during
live migration, the following idea came up:
Why not bind a port to both, the source and the target host during
migration?
This would allow us to set the portbinding for the target already in
pre_live_migration. Doing so, we
After a great chat with Kevin we agreed to follow up the multiple
binding approach until the summit and see if this is the right
direction. [1]
[1] http://eavesdrop.openstack.org/irclogs/%23openstack-neutron/%
23openstack-neutron.2016-04-13.log.html#t2016-04-13T09:43:46
--
-
Andreas (IRC:
I must admit, I really like this idea of getting rid of all the devstack
params. It's always a mess looking up the functionality of the various
variables in the code when trying out something new.
I also understand the concern that was raised by somebody (couldn't find
it anymore) that the Neutron
Hi Kevin, thanks for your input! See my comments in line
--
-
Andreas (IRC: scheuran)
On Di, 2016-04-12 at 04:12 -0700, Kevin Benton wrote:
> We can't change the host_id until after the migration or it will break
> l2pop other drivers that use the host as a location indicator (e.g.
> many
possible).
Thanks!
--
-
Andreas (IRC: scheuran)
On Di, 2016-04-12 at 12:33 +0200, Rossella Sblendido wrote:
> On 04/12/2016 12:05 PM, Andreas Scheuring wrote:
> > Hi together,
> > I wanted to start discussion about Live Migration problem that currently
> > exists in the nova neu
Hi together,
I wanted to start discussion about Live Migration problem that currently exists
in the nova neutron communication.
Basics Live Migration and Nova - Neutron communication
--
On a high level, Nova Live Migration happens in 3 stages.
Hi,
On Live Migration, I want to update the domain.xml with the required
network interface definition for the target node. For code, please see
the prototype [2]
I'm reaching our for feedback about the right way to implement this!
Use Cases/Problem:
=
#1 Live Migration with Neut
Just to make sure you're aware of that - there is this new Curvature
Network Topology view since Liberty [1]. Maybe you want to integrate
with it as well...
[1] https://www.openstack.org/software/liberty/
--
-
Andreas (IRC: scheuran)
On Mi, 2016-03-16 at 12:30 +0900, Soichi Shigeta wrote:
Hi Pratti,
yes, this is working! For Openvswitch ml2 driver just configure on the
neutron server in the ml2 configuration file [1][2]
[ml2]
tenant_network_types = flat
type_drivers = local, flat, vlan, gre, vxlan
[ml2_type_vlan]
network_vlan_ranges = physnet1:30:40 #where 30-40 is the range of
Nice overview!
--
-
Andreas (IRC: scheuran)
On Mo, 2016-01-25 at 17:26 +, Brian Stajkowski wrote:
> We completed mapping relationships for OVO with this
> ERD: https://www.gliffy.com/go/publish/9741595
>
>
> We are looking into adding sphinx for auto generation of these
> diagrams but
Convinced :)
--
-
Andreas (IRC: scheuran)
On Mi, 2016-01-20 at 19:58 +, Sean M. Collins wrote:
> On Wed, Jan 20, 2016 at 02:24:35PM EST, Sourabh Patwardhan wrote:
> > This option is used to configure a global multicast group IP for VXLAN
> > networks.
> > The Cisco Nexus1000V mech driver
I agree, I would vote for killing ml2 option, too!
I wanted to reach out via the ML to find potential users of it or to
clarify why it has been added at all!
--
-
Andreas (IRC: scheuran)
On Mi, 2016-01-20 at 10:11 +0100, Ihar Hrachyshka wrote:
> Andreas Scheuring wrote:
>
> &g
There was some discussion if the ml2_type_vxlan.vxlan_group of the ml2
config file (Neutron Server) can be removed [1], as it is not being used
by in-tree drivers (ovs, lb, sriov).
OVS: does not support vxlan mcast
LB: uses it's own agent configuration today.
SRIOV: does not support vxlan at all
+1 for Kyles proposal as well!
I think we can give it a try. If we realize that it becomes kind of a
"second class" meeting, as only less people will join or that the
meeting has no impact, we still can go back to the weekly meeting slot
on Monday IMO.
Andreas (IRC: scheuran)
On Mi, 2016-01-20
Hi everybody,
I stumbled over a definition that explains the difference between a
Provider network and a self service network. [1]
To summarize it says:
- Provider Network: primarily uses layer2 services and vlan segmentation
and cannot be used for advanced services (fwaas,..)
- Self-service Ne
I want to quickly share the status on the modular l2 agent (common
agent) refactoring blueprint [1] - I'm not able to attend this
afternoon...
- Till Christmas, I would like to see the extension manager patchset
merged [2]
- The goal for Mitaka-2 is to make the split between the common part and
t
Great work!
--
Andreas
(IRC: scheuran)
On Mo, 2015-12-07 at 21:05 +, Sean M. Collins wrote:
> It's been a couple months - the last time I posted on this subject we
> were still working on getting Linux Bridge to become an experimental[1]
> job. During the Liberty cycle, the Linux Bridge CI
Praveen,
there are many error in your q-svc log.
It says:
InvalidInput: Invalid input for operation: (u'Tunnel IP %(ip)s in use
with host %(host)s', {'ip': u'10.81.1.150', 'host':
u'localhost.localdomain'}).\n"]
Did you maybe specify duplicated ips in your controllers and compute
nodes neutron
Please have a look at your neutron server log and neutron agent log and
provide this information if you have troubles interpreting the messages.
Probably you'll find the reason there!
--
Andreas
(IRC: scheuran)
On Di, 2015-11-24 at 12:17 +0100, Praveen MANKARA RADHAKRISHNAN wrote:
> Hi,
>
>
r a second stage.
Thanks
--
Andreas
(IRC: scheuran)
On Mi, 2015-11-18 at 15:28 +0100, Ihar Hrachyshka wrote:
> Andreas Scheuring wrote:
>
> > Hi all,
> > I wonder if this is somehow in conflict with the modular l2 agent
> > approach I'm currently followin
Hi all,
I wonder if this is somehow in conflict with the modular l2 agent
approach I'm currently following up for linuxbridge, macvtap and sriov?
- RFE: [1]
- Frist patchset [2]
I don't think so, but to be sure I wanted to raise it up.
[1] https://bugs.launchpad.net/neutron/+bug/1468803
[2] h
Hi together,
I think it would be very helpful if you all could update your launchpad
profile with your timezone information. This makes it more easy to
figure out the timeframe when a person can be reached in theory.
To update your account, use this link
https://launchpad.net/people/+me/+editlo
Hi everybody,
I'm trying to to achieve 2 things:
#1 Add common macvtap support for all kind of interfaces to neutron core
(via a macvtap ml2-plugin & agent) [1]. There has been a long discussion
where this should land but finally we Kyle decided to do it in tree [2].
For the agent part, Sean Co
Hi,
I wonder if it makes sense to update the section "Proposing and
Implementing a Feature" [1] of the Neutron development wiki with the new
RFE workflow described here [2]. Or even better just add a link?
Thanks
[1]
https://wiki.openstack.org/wiki/NeutronDevelopment#Proposing_and_Implementing
help to allay fears about code proliferation. Actually given
> Kevin's
> mention of the modular agent stuff, maybe it isn't worth
> putting much
> effort in to the refactor patch at all.
>
> My $0.02.
>
Can you try answer 1 of [1]?
I've never tried it, but I heard from folks who configured it like that.
With this masquerading, your vm should be able to reach your 192.x
network. But as it's NAT it won't work the other way round (e.g.
establish a connection from outside into your vm)
The proper wa
Hi,
I'm planning to add a new ml2 driver and agent to neutron supporting
macvtap attachments [1]. Kyle already decided, that this code should
land in the neutron tree [2]. The normal approach till now was to copy
an existing agent code and modify accordingly, which lead to a lot of
duplicated code
Hi,
as there is no official feature freeze in neutron anymore, there still
must be a cut off date or at least a cut off time frame for liberty
code.
Can anyone tell me when this is (round about)? Is this liberty-3?
I wonder if it's still possible to propose a RFE and get it into
liberty...
Than
ecause the user API
> interaction wouldn't change.
>
> On Fri, Jun 26, 2015 at 8:14 AM, Neil Jerram
> wrote:
> Hi Andreas,
>
> On 26/06/15 14:04, Andreas Scheuring wrote:
> Hi together,
> for a new ml2 pl
Hi together,
for a new ml2 plugin I would like to pass over some data from neutron to
nova on port creation and update (exploiting port binding extension
[1]). For my prototype I thought of using one of the following response
dictionaries to add my information:
- binding:vif_details
- binding:pro
I want to proclaim a new networking project that we plan to start:
It's called 'networking-macvtap'.
This project will contain a neutron ml2 driver and an corresponding
neutron l2 agent. It's aim is to allow instance network attachments via
macvtap in bridge mode independent of the physical netwo
Hi John and others,
for my new neutron ml2 driver [3] I depend on a new vif_type in nova
being introduced [1]. I also added Sourabh to cc, as he probably tries
to achieve the same goal for another driver.
I'm also aware of the current discussion regarding vif-plug-script [2].
This approach only
> But I still need to
> figure out more details about device renaming and what other side
> effects might come with it.
Device renaming might not be a good idea in the macvtap context, as the
interface used could also be used with by other applications that might
insist on a fixed device name. It
Maybe this helps (taken from [1])
"Actually there is one way that the MAC address of the tap device
affects
proper operation of guest networking - if you happen to set the tap
device's MAC identical to the MAC used by the guest, you will get errors
from the kernel similar to this:
kernel: vnet
Daniel, thanks a lot for your input! Please see my novel below ;)
> I could have sworn I've previously reviewed patches which dealt with
> NIC device naming changes across migration, but I can't find them
> now. Did you ever submit patches which tried to fix this, or am I
> perhaps thinking of som
On Thu, 2015-06-11 at 09:30 +0100, Daniel P. Berrange wrote:
> It seems the main reason for your new proposal is to deal with
> the fact that on migration, you need to specify a different
> NIC name in the XML. This is not particularly difficult - Nova
> already has code for dealing with pdating t
tap12345-CD
>
> where tap12345-CD is the TAP interface towards the VM. Does that answer
> your question, and would that be possible with a libvirt network?
>
> Thanks,
> Neil
>
>
> > --
> > Ian.
> >
> >
> > On 10 June 2015 at 12:16, Nei
Hi Daniel, Neil and others,
I was thinking about introducing libvirt-network as a new vif type to
nova. It can be used when Neutron prepares a libvirt network for
attaching guests.
Would you see any general concerns with such an approach? Anything that
I need to consider with libvirt networks in
Daniel,
if I got it right, the vif script blueprint only is about plug/unplug
operations and not about generating new xml representations for vif
types. What if for a new vif type it's sufficient to have the
get_config_* method updated? In this case plug/unplug would be handled
by libvirt (like wi
Hi,
what are the prereqs to get a spec for a new nova VIF type approved?
In my case I'm planning for a new neutron ml2 driver and agent (on
stackforge) that adds general support for macvtap to neutron. I've not
yet published anything regarding the neutron part so far - but this will
happen in the
Mathieu,
now I'm getting curious, is it possible to combine Linuxbridge and OVS
VXLAN Nodes in the same cloud?
I thought this does not work as Linuxbridge-vxlan uses multicast for
instances broad- and multicasts (e.g. an arp request), while ovs-vxlan
only does unicast? At least one can specify a
Hello,
I was looking at the neutron pci sriov integration, to see what's the
current state, but I still have a few questions. Maybe one of you could
help out. I'm referring to the direct passthrough and not to the macvtap
passthrough right now:
- Only VLAN for the tenant network is supported. Is
Hello everybody,
is there a reason why devstack is only able to either deploy vpnaas or
l3-router?
Nevertheless both services are enabled in the local.conf on the
HowToInstall Page [1]. But the code says it's a either or [2] (line
725).
if is_service_enabled q-vpn; then
run_process q-vpn "$
Hi,
I was playing around with the various dhcp/radvd options of neutron.
Very helpful was the matrix [1] that describes the combinations of ra
and adress mode that can be configured.
For dhcpv6-stateful (ra & adress mode) it says: "VM obtains IPv6 address
from dnsmasq using DHCPv6 stateful and op
Hi,
is there a central place where I can find a matrix (or something
similar) that shows what is currently supposed to work in the sense of
IPv6 Networking?
I also had a look at a couple of blueprints out there, but I'm looking
for a simple overview containing what's supported, on which features
Thanks Ihar for sharing your thoughts!
--
Andreas
(irc: scheuran)
On Mon, 2015-01-26 at 11:30 +0100, Ihar Hrachyshka wrote:
> Hi Andreas,
>
> On 01/26/2015 10:58 AM, Andreas Scheuring wrote:
> > Hi Ihar,
> > we're currently running stable/juno devstack on rhel7 ba
Hi Ihar,
we're currently running stable/juno devstack on rhel7 base. But I see
troubles to get it running on the master branch due to bug 1408297.
The fix for this bug increases the minimal dnsmasq version for master
branch up to 2.67. I also recognized the stable/juno item that leaves a
warning
Hi,
is there a way to get access to the slides from the DVR session of the
Paris summit? Unfortunately the slides in the video are not readable.
Speakers were Swaminathan Vasudevan, Jack McCann, Vivekanandan,
Narasimhan, Rajeev Grover, Michael Smith. So maybe one of you can post
them on slidesha
Hi,
do you think we could backport this bug to the devstack stable/juno
release?
https://review.openstack.org/#/c/131334/
This bug prohibits people to use the local.conf from icehouse, when they
take use of variables for defining configuration values
An example. The local.conf looks like this
ginal Message -
> From: "Andreas Scheuring"
> To: "openstack-dev"
> Sent: Wednesday, 26 November, 2014 2:04:57 PM
> Subject: [openstack-dev] [devstack] environment variables in local.conf
> post-config section
>
> Hi together,
> is there a wa
1 - 100 of 114 matches
Mail list logo
