Hello everyone.
Got a problem: we want to use same physical interface for external
networks and virtual (tenant) networks. All inside vlans with different
ranges.
My expected config was:
[ml2]
type_drivers = vlan
tenant_network_types = vlan
[ml2_type_vlan]
network_vlan_ranges = external:1:10
I am told that dual stacking is supported for compute instances. What
does that look like? Can I associate both an IPv4 and an IPv6 address
with a Neutron Port?
Thanks,
Mike
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.or
On 2015-05-07 22:32, George Shuklin wrote:
> Hello everyone.
>
> Got a problem: we want to use same physical interface for external
> networks and virtual (tenant) networks. All inside vlans with different
> ranges.
>
> My expected config was:
>
> [ml2]
> type_drivers = vlan
> tenant_network_t
On 2015-05-07 23:17, gustavo panizzo (gfa) wrote:
>
> neutron net-create vlanN --provider:network-type vlan
> --provider:physical_network blabla --provider:segmentation_id N
>
> ...
>
> neutron net-create vlanN+nn --provider:network-type vlan
> --provider:physical_network blabla --provider:s
Hi all,
For those of you who were interested in our network IP usage API
extensions from the PHL meet up, we have this spec in play for it. Please
review and comment!
As a reminder, the raw code/patch for this is also available at
https://github.com/godaddy/openstack-neutron/tree/network-ip-u
At Symantec we use YiDB for CMDB data - however - we find it to be lacking as
it is NOT a GraphDB, but emulates GraphDB like behavior. In addition, it
requires MongoDB as a backing store - and that will eventually corrupt and lose
your data...often silently (please direct your flame mail to /d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi All
On 17/04/15 21:15, James Page wrote:
> The Ubuntu OpenStack Engineering team is pleased to announce the
> general availability of the first release candidate of the
> OpenStack Kilo release in Ubuntu 15.04 development and for Ubuntu
> 14.04
On 05/07/2015 06:17 PM, gustavo panizzo (gfa) wrote:
On 2015-05-07 22:32, George Shuklin wrote:
Hello everyone.
Got a problem: we want to use same physical interface for external
networks and virtual (tenant) networks. All inside vlans with different
ranges.
My expected config was:
[ml2]
typ
I added information about Assimilation Monitoring to the etherpad. It's
not strictly a CMDB, but it can be used for what CMDB's often are used
for, and is worth noting in the discussion.
Excerpts from Shane Gibson's message of 2015-05-07 08:27:01 -0700:
>
> At Symantec we use YiDB for CMDB data -
On 2015-05-08 00:39, George Shuklin wrote:
> I wanted to put tenant networks and external networks on the same
> network, but than I realised that there is no way to say neutron to
> avoid specific vlan_id's once you set up tenant_network_types=vlan and
> add vlan_id to the list of available fo
If one set of VLANs is for external networks which are created by admins,
why even specify network_vlan_ranges for that set?
For example, even if network_vlan_ranges is 'local:1000:4000', you can
still successfully run the following as an admin:
neutron net-create --provider:network_type=vlan
--pr
11 matches
Mail list logo
