2013 at 2:11 PM, Aaron Rosen wrote:
> I still don't see why you want to have two nics on the same L2? We don't
> allow this because we don't want to allow a tenants to bridge them
> creating a loop in the network.
>
> Aaron
>
>
> On Thu, May 23, 2013 at 8:1
Hi Salvatore:
Thanks, I will try that.
Liu Wenmao
On Wed, May 29, 2013 at 6:07 PM, Salvatore Orlando wrote:
> I am afraid there is no way of having two NICs on the same network at the
> moment.
>
> If you are trying to deploy a VM which provides some form of network
> servi
ports (--nic port-id).
> Even if Quantum does not allow you to move these ports to another network
> perhaps it might still satisfy your requirements.
>
> Salvatore
>
>
>
> On 24 May 2013 04:23, Istimsak Abdulbasir wrote:
>
>> Are you saying the the VM sees two vir
Hello:
I have a network with a subnet, I want create a VM with one NIC connected
with this subnet, with one or two extra NIC left, because I want to do some
more things such as intrusion protection
I wonder is it possible to create a VM with more NICs than its connected
network?
_
> in /etc/quantum/l3_agent.ini
>
> Regards
> Balu
>
> On Fri, May 17, 2013 at 3:22 PM, Liu Wenmao wrote:
>
>> Hi
>>
>> Suppose there are two tenants: A and B, they can create their own
>> networks, but the networks are both 100.0.0.0/24, I think it is po
existing network already.
I wonder is it possible to create two identical networks for two tenant?
Liu Wenmao
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More
100.0.0.1/24 brd 100.0.0.255 scope global qr-8af2e01f-bb
inet6 fe80::f816:3eff:fef7:3d5e/64 scope link
valid_lft forever preferred_lft forever
On Tue, May 7, 2013 at 5:01 PM, Liu Wenmao wrote:
> hi
>
> I use quantum grizzly with namespace and floodlight, but VMs can not p
It seems OK after I set controller for both br-tun and br-int. but
floodlight official installation only set br-int's controller, am I correct?
On Tue, May 7, 2013 at 2:33 PM, Liu Wenmao wrote:
> hi all:
>
> I have set up quantum+floodlight, there are a compute node and a
>
hi
I use quantum grizzly with namespace and floodlight, but VMs can not ping
its gateway. It seems that floodlight ignore devices whose status
is PORT_DOWN or LINK_DOWN, somehow the subnetwork gateway is
really PORT_DOWN and LINK_DOWN.. is it normal?or how can I change its
status to normal?
root@
hi all:
I have set up quantum+floodlight, there are a compute node and a
controller, so I create a VM in the compute node, but the VM(100.0.0.4) can
not ping its gateway(100.0.0.1) in the controller node.
When the VM send a ARP request to OVS of the compute node, a packet_in
request is sent to th
hi all:
I set up quantum without namespace support, now VMs can ping
gateway(100.0.0.1) but I can not capture any packet at gateway interface,
br-int or br-tun:
root@controller:/var/log/openvswitch# tcpdump -i qr-c5496165-c7 -nn
tcpdump: verbose output suppressed, use -v or -vv for full protocol
Hi list:
I set up quantum without namespace support, quantum-server/l3 agent/dhcp
agent are running at the same node, besides there is a compute node.
I create a router connecting two network(100.0.0.0/24, 200.0.0.0/24), so
there should be two gateways(100.0.0.1 and 200.0.0.1) in the controller,
, 2013 at 8:16 PM, Heiko Krämer wrote:
> Hi Wenmao,
>
> i think you should plan your network topologie first and after that you
> can decide which controller are the best choice for you.
>
> Greetings
> Heiko
>
>
> On 17.04.2013 14:01, Liu Wenmao wrote:
>
> I ha
I have tried floodlight, but it does not support namespace, so I wonder is
there a better network controller to support quantum?(nox, ryu ..)
Wenmao Liu
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubs
Hi all:
I set up openstack with quantum successfully, but I use floodlight as the
network controller, VMs can not ping their gateway.
I use a host as compute/network controller(30.0.0.1), and another host as a
compute node(30.0.0.11). The VM X address is 100.0.0.7 and the subnet
gateway G is 100.
hi all:
I can use namespace to build and isolate virtual networks with quantum and
its l3-agent. Everythings goes fine.
I need floodlight controller, but big switch restproxy can not work with
l3-agent, so I have to disable l3-agent. Still, I quantum server outputs
errors:
AttributeError: No suc
Wed, Apr 10, 2013 at 6:10 AM, Liu Wenmao wrote:
>
>> Actually this is not over.
>>
>> The main reason of service failure is that central/manager.py
>> and service.py use different vairables:
>>
>> central/manager.py
>> 70 def interval_task(se
'http://localhost:5000/v2.0'),
So after I change all "-" to "_" and modify all options in
/etc/ceilometer/ceilometer.conf, the service starts OK.
On Wed, Apr 10, 2013 at 2:02 PM, Liu Wenmao wrote:
> I solve this problem by two steps:
=ceilometer
os-password=nsfocus
os-tenant-name=service
os-auth-url=http://controller:5000/v2.0
On Wed, Apr 10, 2013 at 1:36 PM, Liu Wenmao wrote:
> Hi all:
>
> I have just install ceilometer grizzly github version, but fail to
> start ceilometer-agent-central service. I think it is d
Hi all:
I have just install ceilometer grizzly github version, but fail to
start ceilometer-agent-central service. I think it is due to that I didn't
set up the keystone user/password like other projects. but I follow the
instructions(
http://docs.openstack.org/developer/ceilometer/install/manual.
Thanks Thierry, it seems to make sense.
On Tue, Apr 9, 2013 at 4:53 PM, Thierry Carrez wrote:
> Rahul Upadhyaya wrote:
> > I think you should use : rootwrap_config=/etc/quantum/rootwrap.conf
> >
> > Found this at below mentioned wiki page. I think this should hold true
> > for Quantum too.
>
> N
upgrade if you want to use
> another port than the default one, or i think removing the option
> metadata_port
> from l3_agent.ini should also make it work for you.
>
>
> HTH,
>
> --
> Mouad
>
>
> On Tue, Apr 9, 2013 at 11:48 AM, Liu Wenmao wrote:
>
>>
hi all:
I setup quantum and nova grizzly, but vms can not get public key from
169.254.169.254:
debug end ##
cloudsetup: failed to read iid from metadata. tried 30
WARN: /etc/rc3.d/S45cloudsetup failed
Starting dropbear sshd: generating rsa key... generating dsa key...
aster/etc/proxy-server.conf-sample#L61
>
> account_autocreate
>
> https://github.com/openstack/swift/blob/master/etc/proxy-server.conf-sample#L69
>
>
> +Hugo Kuo+
> h...@swiftstack.com
> tonyt...@gmail.com
> +886 935004793
>
>
> 2013/4/9 Liu Wenmao
>
>
Hi all:
In quantum dhcp grizzly log, I find the following warnings:
2013-04-09 15:12:48 WARNING [quantum.agent.common.config] Deprecated:
DEFAULT.root_helper is deprecated!
I do set root_helper in the ini file:
root_helper = sudo /usr/local/bin/quantum-rootwrap
/etc/quantum/rootwrap.conf
After
Hi all:
I just installed swift from github, after I configure a proxy node and a
storage node, and run the stat command, it fails:
# swift -v -V 2.0 -A http://controller:5000/v2.0 -U service:swift -K
nsfocus stat
Account not found
Keystone and disk configuation seem OK, syslog gives:
Apr 9 13:45
Tue, Apr 2, 2013 at 2:46 PM, Liu Wenmao wrote:
> hi Aaron:
>
> thanks anyway..
>
> it's really a weird problem
>
>
> On Tue, Apr 2, 2013 at 2:29 PM, Aaron Rosen wrote:
>
>> I've not encountered these errors. If you didn't drop the list perhaps
>>
Hi all:
I use github to install nova and quantum, but when I launch an instance,
nova-compute fails:
2013-04-02 11:00:15DEBUG [nova.openstack.common.lockutils] Released
file lock "iptables" at /var/lock/nova/nova-iptables for method "_apply"...
2013-04-02 11:00:17ERROR [nova.compute.manag
Thank Oleg and Thierr, it's really helpful
On Wed, Mar 27, 2013 at 5:20 PM, Thierry Carrez wrote:
> Oleg Gelbukh wrote:
> > Generally, grizzly-X is a milestone tag inside release cycle codenamed
> > 'Grizzly'.
> > Note that tagging scheme has changed between milestones 2 and 3 of
> > 'Grizzly' r
Hi:
I am integrating floodlight with openstack quantum, but the bigswitch
restproxy plugin seems have some error in the latest git version:
the quantum-server and l3-agent log give the following errors:
File
"/usr/local/lib/python2.7/dist-packages/quantum-2013.2.a331.g9ac82ee-py2.7.egg/quantum/
I notice that openstack components have two different develop code names,
for example, openstack grizzly has 2013.1 and grizzly, so what is the
difference between the two?
There is a rc version of 2013.1 but none of grizzly, so I think they are
not equal to the developers.
root@controller:/usr/sr
der Error: Upgrade DB using Essex
release first.
2013-02-05 11:39:39 15121 TRACE cinder
end of the error prompt--
I use ubuntu 12.10 and apt-get to install openstack folsom, so it's strange
why should I use Essex release.
Any hints?
Thanks
Liu Wenmao
_
-- Forwarded message --
From: Liu Wenmao
Date: Tue, Jan 22, 2013 at 4:55 PM
Subject: Re: [Openstack] using Win AD authentication as keystone backend
To: Tim Bell
Thanks Bell
is it possible to use active directory and mysql database at the same time?
for example, keystone first
hello all:
My company use Windows AD(active directory) authentication for internal
user login, is it possible to integrate the current authentication with
keystone backend, so that we do not extra user/password maintaining. Hope
Openstack Folsom has an easy and stable solution.
thanks
Wenmao Li
hi all:
I want to detect internal network flow by a physical IDS(Intrustion
detection system) device, so a possible approach is switch span.
first, I create a mirror with the openvswitch and redirect all data to an
pysical interface eth1
ovs-vsctl -- --id=@m create mirror name=mirror0 -- add bri
hi all
I set up an openstack scenario on a physical computer. The computer runs
ubuntu 12.10 on a kvm hypervior. And then I emulate a virtualized
controller node and two virtualized compute nodes
with qemu-system-x86_64/kvm.
Everything seems ok, but after some time, I ssh a vm on the compute no
I fail to restart the quantum-server recently without any error log output.
root@controller:~# service quantum-server restart
stop: Unknown instance:
quantum-server start/running, process 3763
root@controller:~# service quantum-server restart
stop: Unknown instance:
quantum-server start/running, p
I follow the OpenStack Network (Quantum) Administration Guide and build an
internal network and I want VMs in the private network to access Internet.
So I follow the instructions and create a "external network", and the
internal VM has a floating ip, but it can not connect to the physical
Interne
hi all:
I have 3 compute nodes,but one(node 3) is down:
root@controller:~/vms# nova-manage service list
2012-12-11 15:10:50 DEBUG nova.utils
[req-a103d7d9-265c-4ef4-a11d-1dba1ccbc9e2 None None] backend from
(pid=14904) __get_backend /usr/lib/python2.7/dist-packages/nova/utils.py:494
Binary
39 matches
Mail list logo
