+1 (binding)
This is what I did for RC1:
I created a new cloud using commit 5f48487dc62fd1decaabc4ab2a10f549d6c82400
(RC1). I ran the automated regression tests for managed storage. All tests
passed.
This is what I did for RC2:
I looked at the Git changelog and didn’t see anything that seemed
- release checksums all check out.
- I installed an all-KVM 4.9.3.1 with a redundant VPC and two nets with
VMs. I upgraded to 4.11.1. The only glitch was that the documentation says
to register new system VMs as 'systemvm-kvm-4.11'. This should be
'systemvm-kvm-4.11.1'. The nets kept running and up
On 06/12/2018 12:11 PM, Rafael Weingärtner wrote:
> In theory, the object (either in Java or a DB table) that represents a VLAN
> should not have IP information. However, it seems that someone “reused” the
> object. We would need to check if the IP data stored there is not really
> used before r
On 06/12/2018 12:23 PM, Ivan Kudryavtsev wrote:
> Hi, Devs, ipv6 in vlan table is used. Without the information in that
> table, ipv6 wouldn't work with basic zone.
>
Yes, I'm aware of that. Would be a rather simple fix. Just a few lines
of code. I know where to find it.
Wido
> вт, 12 июн. 2
Hi!
I just checked our own vlan table and noticed the (obviously dhcp?) range
of the L3 subnet is only present in the `vlan`.`description` field.
It looks like it's getting used if the corresponding
`network`,`specify_ip_range` is 1.
cheers,
- Stephan
Am Dienstag, den 12.06.2018, 12:11 +0200
Hi, Devs, ipv6 in vlan table is used. Without the information in that
table, ipv6 wouldn't work with basic zone.
вт, 12 июн. 2018 г., 13:11 Rafael Weingärtner :
> In theory, the object (either in Java or a DB table) that represents a VLAN
> should not have IP information. However, it seems that s
In theory, the object (either in Java or a DB table) that represents a VLAN
should not have IP information. However, it seems that someone “reused” the
object. We would need to check if the IP data stored there is not really
used before removing it.
On Tue, Jun 12, 2018 at 11:32 AM, Daan Hoogland
Wido, I think we can remove ip data from the vlan table, though it is going
to require some hacking. Removing the vlan table seems not prudent to me,
especially since we now have l2 networks (without ip provisioned).
On Tue, Jun 12, 2018 at 11:12 AM, Wido den Hollander wrote:
> Hi,
>
> Looking a
Hi,
Looking at our design and tables in the database I'm wondering why both
a VLAN and a Network has IP information.
A VLAN is a Layer 2 domain and shouldn't have any IP(4/6) information
and we also seem to store redundant information in there.
Below is some information I have in a test database
Hi Glen,
Are you using basic or advanced zone? How is your networking configured on your
KVM host? My guess is you run guest traffic and management traffic on the same
NICs?
Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
On 12/06/2018, 04:40, "Glen Baars" wrote:
Hello Devs,
Whe
10 matches
Mail list logo
