Hi,
quantum.conf:
core_plugin =
quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2
ovs_quantum_plugin.ini:
network_vlan_ranges = physnet1
enable_tunneling = False
bridge_mappings = physnet1:br-eth0
To create a shared provider network:
quantum net-create sharednet1 --shared
read on:
we will send the host to compute manager:
def _provision_resource(self, context, weighted_host, request_spec,
filter_properties, requested_networks, injected_files,
admin_password, is_first_time, instance_uuid=None):
Create the requested resource in
Try to define allow_overlapping_ips = True
On 10/12/2012 09:37 PM, Srikanth Kumar Lingala wrote:
Hi all,
Is it possible to create two networks with same subnet across two
different tenants?
I tried this with latest quantum, but got the following error:
*/ Invalid input for operation: Requested
It seems that you are using quantum cli v1.0, which is not supported in
new quantum version v2.0 API.
Are u using quantum v1.x, right?
On 10/16/2012 10:39 AM, Raja Gajju wrote:
Hi All,
I am testing the Quantum CLIs in my set up. When I am creating a new
network using create_net CLI
for an
should work for the corresponding Quantum version.
Regards,
Girija Sharan Singh
*From:* gong yong sheng gong...@linux.vnet.ibm.com
*To:* Raja Gajju gajjur...@yahoo.com
*Cc:* openstack@lists.launchpad.net openstack
In fact you can run multiple nova-networks, which I call it as multiple
instances mode, and multi-host mode with each nova-network on each
nova-compute.
in multiple instance mode, you can use nova-manage network modify to
host a given network on a given host, which is running a nova-network:
can u send out nova.conf file?
On 10/22/2012 07:30 PM, Srikanth Kumar Lingala wrote:
Hi,
I am using latest devstack I am trying to create a VM with one
Ethernet interface card. I am able to create the VM successfully, but
not able to get IP for the ethernet interface.
I have Openstack
to run quantum-server, dhcp agent, ovs and linuxbridge agent, we need to
specify the quantum.conf as one of the configure files.
Besides the RPC sections, some of other parts are useful too.
RPC parts are used for communication between quantum-server and dhcp
agent, ovs agent or linux bridge
Hi,
In fact, we can split Quantum network Node into two categories:
one is for dhcp, which install ovs agent and dhcp agent. We can have one
such kind of node
one is for l3 agent, we can deal with one external network on one l3
agent. We can have many nodes of this kind.
Regards,
Yong Sheng
this explanation helps.
Please help me in this regard.
-
Trinath
On Tue, Oct 30, 2012 at 1:58 PM, gong yong sheng
gong...@linux.vnet.ibm.com mailto:gong...@linux.vnet.ibm.com wrote:
to run quantum-server, dhcp agent, ovs and linuxbridge agent, we
need to specify the quantum.conf
Following is my understanding:
usage:
scheduler queue is used for compute api server. For example of nova
boot, API server will send a msg to scheduler queue for a booting
scheduler_*fanout_ is used for service*s to report service
capability. For example, nova compute **will use
.
TO have multiple l3 agent nodes, we can distribute traffic from VMs
among l3 agent nodes.
Regards,
Balaji
On Tue, Oct 30, 2012 at 2:26 PM, gong yong sheng
gong...@linux.vnet.ibm.com mailto:gong...@linux.vnet.ibm.com wrote:
Hi,
In fact, we can split Quantum network Node into two categories
On 10/31/2012 05:00 PM, Trinath Somanchi wrote:
Hi Stackers-
I'm testing a dummy plugin which does and RPC based communication with
Quantum.
I have done this following:
[1] I have written dummy agent like DHCP agent - Present in HOST
[2] I have written dummy_rpc_base like the
I think we already fixed this bug.
please see if it helps:
https://review.openstack.org/#/c/14756/
On 11/05/2012 05:52 PM, Skible OpenStack wrote:
Hello Stackers !
i am finding a weird error in my l3_agent.log file:
Stderr: ''
2012-11-05 10:22:59ERROR
There is a router_id in l3_agent.ini,
You can create a router for a tenant and then start a l3 agent for
it.
On 11/11/2012 01:34 AM, Skible OpenStack wrote:
that these Quantum Network Node is not per
Tenant basis and it can serve all the Tenants of DC setup.
Just want to understand what will be the advantages we are
thinking of by doing so.
Regards,
Balaji
On Tue, Oct 30, 2012 at 2:26 PM, gong yong sheng
gong...@linux.vnet.ibm.com
Trye to start your nova-compute with --config-file {your nova.conf}. and
look at the log at the beginning to see what options values are used truly.
On 11/16/2012 06:17 AM, Ahmed Al-Mehdi wrote:
Hello,
On the compute node (IP addr : 10.176.20.4) I am seeing the following
error message in
the rabbitmq-server)? If so, is that how the
control node knows of all the compute node that it can talk to?
Thank you,
Ahmed.
From: gong yong sheng gong...@linux.vnet.ibm.com
mailto:gong...@linux.vnet.ibm.com
Date: Thursday, November 15, 2012 3:39 PM
To: Ahmed Al-Mehdi ah...@coraid.com mailto:ah
Hi Ahmed,
and with nova host-xxx as assistance.
On 11/16/2012 07:29 AM, Narayanan, Krishnaprasad wrote:
Hi Ahmed,
You can use the command nova-manage service list from the command line of
control node to get the list of compute nodes along with the nova-compute service status.
Thanks
I think we have already Bp for this:
https://blueprints.launchpad.net/quantum/+spec/quantum-scheduler
also the quantum agents multi-hosts and multiple dhcp agents and l3
agents will depend on it.
On 11/16/2012 08:02 AM, Dan Wendlandt wrote:
Yes, this has been suggested before and I think
Can u check if the time is synchronized? Times on compute node and
control node should be synchronized.
On 11/16/2012 12:28 PM, Ahmed Al-Mehdi wrote:
Hi Narayanan,
Awesome, thank you. There reason I was not seeing the nova-compute
listed is because it did not launch on the compute node. I
Hi,
can u give out more traceback?
quantum context has a session attribute. It seems this context is not
quantum context.
On 11/21/2012 07:54 PM, Trinath Somanchi wrote:
Hi-
With respect to folsom release,
.
What does this sqlalchemy and rpc based error denote.
File
On 11/21/2012 04:15 AM, Ahmed Al-Mehdi wrote:
Hello,
I am getting a RPC message timeout in nova-network.
2012-11-18 15:50:29 DEBUG nova.openstack.common.rpc.amqp [-] Making
asynchronous call on network.sonoma ... from (pid=1375) multicall
On 11/22/2012 08:23 AM, Ahmed Al-Mehdi wrote:
Hello,
I have a question about setting up Quantum, following the steps
described by Bilel Msekni (
https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst
), which uses 3 NICs.
On 11/29/2012 07:56 AM, Ahmed Al-Mehdi wrote:
Hello,
I have a few questions related to private and external network in
Quantum. I am running into some odd behavior with networking related
to my VM instance that I am trying to resolve.
I used the following commands to create a private
It seems the error is related to sql_connection for your glance.
On 12/03/2012 08:21 PM, Chris St wrote:
Hello,
I am a newbie in Openstack and I try to get a first overview. For my
overview I want to install and implement OpenStack.
I have installed two CentOS Server (Version 6.3) with all
It seems be about sudo.
to create one sudo file under /etc/sudoers.d
mine is: nova_sudoers:
Defaults:gongysh !requiretty
gongysh ALL = (ALL) NOPASSWD: ALL
On 03/20/2013 09:37 AM, Martinx - ジェームズ wrote:
Hi!
I just rollback to the default namespace options, my Instance now get
its IP without
that depends what user is running the dhcp agent.
On 03/20/2013 09:52 AM, Martinx - ジェームズ wrote:
My /etc/sudoers.d/nova_sudoers contains:
--
Defaults:nova !requiretty
nova ALL = (root) NOPASSWD: /usr/bin/nova-rootwrap
--
Do I need to change it?
Tks!
Thiago
On 19 March 2013 22:46, gong yong
March 2013 22:55, gong yong sheng
gong...@linux.vnet.ibm.com mailto:gong...@linux.vnet.ibm.com
wrote:
that depends what user is running the dhcp agent.
On 03/20/2013 09:52 AM, Martinx - ジェ�`ムズ wrote:
My /etc/sudoers.d/nova_sudoers contains
Can u give us your quantum server log?
On 04/02/2013 04:35 PM, Dennis Højgaard wrote:
I really need some help on quantum.. i've been trying to find a
solution on an error for many days now, but google has really betrayed
me. I hope there is someone who can help me: I have quantum-server on
my
It seems there is a gap between these two packages, can u upgrade the
openstack quantum to latest git repo?
On 05/23/2013 08:08 AM, Craig E. Ward wrote:
I'm configuring a single-node installation of the Grizzly release and
I am having some strange issues with the Quantum agents.
The install
the fastest way to learn the API is to run quantum client with -v:
# quantum port-create --request-format xml net1 -v
.
REQ: curl -i http://localhost:9696/v2.0/ports.xml -X POST -H
X-Auth-Token: 22ac5a38128949adaa852282a9ec8bd3 -H Content-Type:
application/xml -H Accept: application/xml -H
32 matches
Mail list logo
