Ok,
The best thing is to login via the dashboard. Go to your router and
remove the interface to the internal network. There's also an api call,
but I don't know it from the top of my head.
Then try to remove the network again.
Before recreating it:
How did you create your demo-network? Did you
OK Andreas, I have different id's now on the networks,
Since I dropped neutron db yesterday, and created again, ( as well as the
networks)
But it's the same setup, and now the demo network is like this:
root@controller2:/# neutron net-list
+--+-+--
Well, I don't have the dashboard yet. I've installed, but I'm waiting for
access from the network guys...
I'm now in a kind of dilemme, trying to delete the network;
root@controller2:/# neutron port-list
+--+--+---+-
try
> neutron router-interface-delete
ok, then please adapt the tenent_network_types variable on your network
node to just use gre first
Andreas
On Di, 2015-06-30 at 08:14 +, Yngvi Páll Þorfinnsson wrote:
> Well, I don't have the dashboard yet. I've installed, but I'm waiting for
> acc
OK, so after some 'delete' exercises
I managed to delete it;
root@controller2:/# neutron net-delete 3446e54b-346f-45e5-89a2-1ec4eef251ab
Deleted network: 3446e54b-346f-45e5-89a2-1ec4eef251ab
Now, there are no ports in use:
root@controller2:/# source admin-openrc.sh
root@controller2:/#
root@contro
Thanks all !
Out of interest would it be a simple case of following the implementation of
nova-networking but using neutron instead ? Neutron network server by default
gets configured to use GRE but obviously this isn’t needed as it would just be
routing directly out of the interfaces. Would an
Hi
Should it be possible to create instances now?
root@controller2:/# nova boot --flavor m1.tiny --image cirros-0.3.3-x86_64
--nic net-id=5feb7d77-1ede-40bf-8d35-f68805558845 --security-group default
--key-name demo-key demo-instance2
+--+---
And another thing, as you mentioned in your previous post,
This is still reported in log file
/var/log/neutron/server.log
On the neutron server;
2015-06-30 09:56:11.788 2027 DEBUG neutron.plugins.ml2.drivers.mech_openvswitch
[req-a9d36342-d8c0-4904-95d5-82889bce22ed None] Checking segment:
{
Hi,
I know that my situation is not 100% compatible with your's (I have tenant
VLANs and a flat external network) but for comparison
this is my demo setup:
[root@os484001 openstack]# neutron net-list
+--+--+
Every time I try to create an instance, there is a reference to a new reference
to a
physical_network': u'external', 'id':
in the neutron server log file ;
oot@controller2:/# grep "Checking segment" /var/log/neutron/server.log
2015-06-30 09:07:35.627 1977 DEBUG neutr
I've checked in the neutron db as well,
MariaDB [neutron]> select id, tenant_id, status from networks;
+--+--++
| id | tenant_id|
status |
+--
HI Andreas
Just to make it clear,
we need to have our tenant networks as VLANs,
in order to have native connection from VM to physical host on our server
networks.
Best regards
Yngvi
-Original Message-
From: Yngvi Páll Þorfinnsson
Sent: 30. júní 2015 08:15
To: Andreas Scheuring
Cc: ope
Ok, that was not clear to me! I thought your intention was, to have the
data network as vlan (which you configured with vlan 47 or something
like that on top of your bond) and then use gre on this vlan for tenant
networks.
So you want to have one network that uses vlan 47? Or do you want to
have t
Hi Andreas,
Our plan is (or was) to do the following.
Connect the servers with two physical interfaces, configured into a bound
interface in order to provide failover resilance. Use this bound interface to
provide all connectivity for the node (management, ext nets and Tennants).
Additionally w
OK, this is what I got
- 2x External network (flat or fixed vlan?)
- Tenant network: That allows for connecting to other external servers
on the same l2 net + gre
--> I assume you have a fixed vlan that you need to use, right?
--> In addition you want to have gre tenant networks?
OK, now coming
Yes, it's opttion 2) we're intereste in :-)
Best regards
Yngvi
-Original Message-
From: Andreas Scheuring [mailto:scheu...@linux.vnet.ibm.com]
Sent: 30. júní 2015 14:51
To: Yngvi Páll Þorfinnsson
Cc: openstack@lists.openstack.org
Subject: Re: [Openstack] error creating instance
OK, this
Hey guys,
In an autoscaling group on Heat, if i delete a base vm ( let's say I have 2
or 3 as minimum limit and 20 as max), And i just run the minimum amount of
VMs, Heat would spin up another one? To maintein the min limit?
Thanks
___
Mailing list: http
I ran into this a few days ago. The context is we are running a node
that performs several api functions and it is going to be a swift proxy
too (at a later date when usage ramps up many of these functions may
move to individual machines, but for now we'd like to keep them together).
The machi
On 01/07/15 13:10, Mark Kirkwood wrote:
I ran into this a few days ago. The context is we are running a node
that performs several api functions and it is going to be a swift proxy
too (at a later date when usage ramps up many of these functions may
move to individual machines, but for now we'd l
The python-dnspython package is only used in Swift for the cname_lookup
middleware. If you are not using that middleware, you can safely not use
python-dnspython.
--john
> On Jun 30, 2015, at 9:54 PM, Mark Kirkwood
> wrote:
>
> On 01/07/15 13:10, Mark Kirkwood wrote:
>> I ran into this a f
Hello.
I encountered same problem. Did you solve this error?
Thank you in advance.
Regards
Byeong-Gi KIM
2015-05-07 20:15 GMT+09:00 walterxj :
> Hi:all
> today when I create heat_cfn endpoint:
> openstack endpoint create \
> --publicurl http://controller:8000/v1 \
> --internalurl http://
21 matches
Mail list logo
