Hi,
Just a few more questions:
1. Can you send me the results of ps aux |grep dnsmasq
2. Can you also please send the ifconfig. The tap devices for also ip
address. Can you please send me ip addr. (my gut feeling is that we do
not configure 192.168.30.2 but rather 192.168.10.2.
Thanks
Gary
On
Hi,
I have managed to find the problem :). I have spent the whole day on
this :(.
I was running devstack and the code executes ovs_quantum_agent.py.
Whilst going through the mailing mails I came upon this mail and saw
that you are calling quantum-openvswitch-agent.
I'll post a fix soon.
On 08/23/2012 10:16 AM, Trinath Somanchi wrote:
Hi -
Rather than using this installation for every different package can I
use devstack's stack.sh script to install the Openstack latest
milestone release?
devstack does not use the installation packages. This uses the git
repositories. By
+1 for Mark
In favor of voting Nachi in in the near future.
On 08/16/2012 08:22 AM, Yong Sheng Gong wrote:
+1 for Mark,
Look forward to voting for Nachi Ueno in near future too.
Thanks
Yong Sheng Gong
-Nachi Ueno na...@nttmcl.com wrote: -
To: Dan Wendlandt d...@nicira.com
From:
On 08/13/2012 08:42 AM, balaji patnala wrote:
Hello Thierry,
Can we download Folsom branch codebase for understanding Quantum and
other changes in Folsom release?
You can get the code at git://github.com/openstack/quantum.git.
If you would like to see the status of things regarding F-3 then
On 08/01/2012 06:34 PM, Fabian Deutsch wrote:
Am Mittwoch, den 01.08.2012, 09:56 -0400 schrieb Andrew Cathrow:
From: Mark Wuwu...@linux.vnet.ibm.com
Sent: Wednesday, August 1, 2012 8:59:14 AM
Subject: Host network management roadmap inquiry
snip/
quantum
Both the plugins openvswitch and
On 08/03/2012 05:11 PM, Kevin L. Mitchell wrote:
Yesterday, I submitted https://review.openstack.org/#/c/10736/ to sync
up an openstack-common change to policy.py; however, the pep8
configuration for quantum does not match the pep8 configuration for the
openstack-common project, and an error is
On 07/23/2012 11:02 AM, Dan Wendlandt wrote:
On Sun, Jul 22, 2012 at 5:51 AM, Gary Kotton gkot...@redhat.com
mailto:gkot...@redhat.com wrote:
This is an interesting idea. In addition to the creation we will
also need the update. I would prefer that the agents would have
one
On 07/19/2012 07:11 PM, Dan Wendlandt wrote:
On Wed, Jul 18, 2012 at 5:17 AM, Gary Kotton gkot...@redhat.com
mailto:gkot...@redhat.com wrote:
On 07/18/2012 04:23 AM, Dan Wendlandt wrote:
Hi Gary,
Removing much of the thread history, as I think we agree on the
high-level goals
On 07/18/2012 04:23 AM, Dan Wendlandt wrote:
On Mon, Jul 16, 2012 at 3:30 AM, Gary Kotton gkot...@redhat.com
mailto:gkot...@redhat.com wrote:
Hi,
The patch https://review.openstack.org/#/c/9591/ contains the
initial support for the scalable agents (this is currently
This is a problem with the ubuntu packaging of the quantum modules.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1025203
Title:
Trying to overwrite
On 07/17/2012 10:28 AM, Salvatore Orlando wrote:
Hello people of Quantum!
As the Folsom release approaches, it is time to gather together and
finalize the specification for the v2 API, so that the Openstack-doc
team might cast it in stone for the sake of the Quantum users!
In order to make
16, 2012 at 10:05 PM, Gary Kotton gkot...@redhat.com
mailto:gkot...@redhat.com wrote:
Hi,
If the name is intended to be a description then how about the
idea of calling the field description instead. This is far
more descriptive and does not lend the user
Hi,
The patch https://review.openstack.org/#/c/9591/ contains the initial
support for the scalable agents (this is currently implemented on the
linux bridge). At the moment this does not support a network or port
update, that is, the user can set 'admin_status_up' to 0. This means
that either
Hi,
If the name is intended to be a description then how about the idea of
calling the field description instead. This is far more descriptive
and does not lend the user to think that this should be unique.
Thanks
Gary
___
Mailing list:
or not ? Why do you need --public True ?
That just adds confusion...
Endre.
2012/7/12 Gary Kotton gkot...@redhat.com mailto:gkot...@redhat.com
Hi,
1. Is this also applicable to the agents? Say for example a
user wants to ensure that a public network is attached
Hi,
1. Is this also applicable to the agents? Say for example a user wants
to ensure that a public network is attached to network interface em1 and
the private network attached to em2. Is this something that will be
addressed by the blueprint?
2. I prefer option #3. This seems to be a cleaner
--public True ? That just
adds confusion...
Endre.
2012/7/12 Gary Kotton gkot...@redhat.com mailto:gkot...@redhat.com
Hi,
1. Is this also applicable to the agents? Say for example a user
wants to ensure that a public network is attached to network
interface em1 and the private network
Hi,
Anyone having problems with gerrit?
Thanks
Gary
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Hi,
I have posted the first patch for this blueprint
(https://blueprints.launchpad.net/quantum/+spec/scalable-agent-comms
https://blueprints.launchpad.net/quantum/+spec/scalable-agent-comms) -
https://review.openstack.org/#/c/9591. I have marked this as Work in
progress. I have tested on
Hi,
Following the Quantum IRC meeting last night below is an update of the
stable essex additions:
Cherry picks approved and integrated:
https://github.com/openstack/quantum/commit/b226e0c7e91e7089286e0977f7e0f185afe2964f
Hi,
I am in the process of integrating the RPC code from OpenStack common
into Quantum. I initially started working with qpid as the backend
implementation. I ran into problems due to the fact that
control_exchange is defined as 'nova'. This is in
quantum/openstack/common/rpc/__init__.py
On 07/10/2012 06:29 PM, Eric Windisch wrote:
In addition to this I have a few additional questions and or concerns:
1. When we import code from openstack common the test cases for the
modules are not imported (maybe I missed something with running setup).
When the code is copied the imports are
Hi,
Great work regarding the agent. My tests with the OVS have passed
successfully. I nonetheless have some problems regarding the
linuxbridge. The problem is that if a device is created from the network
ID then it should have a gw- as the prefix.
I think that if you create the dnsmasq
. This is not
written in stone but should be taken into account.
Salvatore
On 8 July 2012 08:34, Gary Kotton gkot...@redhat.com
mailto:gkot...@redhat.com wrote:
Hi,
Great work regarding the agent. My tests with the OVS have passed
successfully. I nonetheless have some problems
Hi,
In Quantum we make use of a number of different configuration files. A
quantum plugin may have one or more configuration files. An example of
the configuration files is below.
/etc/quantum/quantum.conf
/etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini
When the quantum service
On 07/02/2012 08:18 PM, Aaron Rosen wrote:
Hello,
I wrote a quick wiki page on get up and running with devstack using
the Quantum v2 api here:
http://wiki.openstack.org/RunningQuantumV2Api .
Great work!
I think that you can remove the the export SERVICE... section. This
information is
Hi,
Can we please make a point to discuss this at tomorrow's meeting. I am
in favor of Dan's proposal. I think that we just need to come to a
consensus. There are a lot of comments regarding V1 and V2 on the
following patches:
- https://review.openstack.org/#/c/9160/
-
Hi,
Does anyone know what can cause the failure below:
Started by userOpenStack Hudson
https://jenkins.openstack.org/user/hudson-openstack
[EnvInject] - Preparing an environment for the build.
Building remotely onprecise6 https://jenkins.openstack.org/computer/precise6
in workspace
Hi,
Anyone encountered any problems. When I try to access the server
(https://review.openstack.org/) I get:
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request /GET /
https://review.openstack.org//.
Reason:
Hi,
With the advent of V2 do we want to continue to support V1?
- Yes:
- Do we want separate plugins or as Bob suggested have the V2
plugin support V1 requests? V2 support for V1 may require changes in the
database. In addition to this we do not have a database upgrade.
- No:
On 06/28/2012 12:12 AM, Willian Molinari wrote:
Hi folks,
I was discussing with Mark about it too.
Our ISC dhcp agent is using rabbitmq to get the server messages and would be
nice to use the RPC for it. The code for generic-firewall
Hi,
I have started to convert the linux bridge plugin to support v2. Please
look at https://review.openstack.org/#/c/9101/. I am still working on
the unit tests. I have yet to understand if I need to make changes to
the agent (this is under investigation)
In the quantum.conf file you need to
Hi,
It seems that this has stopped working today. Any ideas?
Thanks
Gary
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help :
Hi,
Is anyone aware of a problem with Jenkins?
Thanks
Gary
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
On 06/26/2012 09:00 AM, Yong Sheng Gong wrote:
Hi Gary,
How can I query the ports with ip_adress?
At the moment there is no formal way of doing this. Last week there were
a number of mails on the list about this particular issue. We did not
get to the bottom of this.
Your suggestion below
On 06/26/2012 09:33 AM, Yong Sheng Gong wrote:
nova integration:
def get_instance_uuids_by_ip_filter(self, context, filters):
Silly question - is the instance uuid the port uuid?
Thanks
Gary
-Gary Kotton gkot...@redhat.com wrote: -
To: Yong Sheng Gong/China/IBM@IBMCN
From: Gary
Hi,
I recently encountered a problem with the Openstack Quantum service. The
service was installed by doing the following steps:
- sudo yum install openstack-quantum
- sudo systemctl enable quantum-server.service
- sudo systemctl start quantum-server.service
Due to a bug the service
+0300, Gary Kotton wrote:
However, I would probably use a slightly different syntax for
associating IPs:
POST /v2.0/ips
{
subnet_id: some_uuid,
port_id: some_other_uuid,
ip: {ipv4 | ipv6},
}
This entails that a port will have had to be created prior. I like the
fact
Hi,
I have committed a first patch for the IP address allocations. Please
note that I still need to address the port update. This will at least
enable other to make use of the IP address allocations (for example for
nova integration). Please note that
On 06/21/2012 12:27 PM, Salvatore Orlando wrote:
Hi,
I am not entirely sure I've got this thread right - so I apologize in
advance for any non sense.
It seems it started with Gary asking whether we could restructure the
request format for POST /v2/ports, but then it seems the discussion is
now
Hi,
Finally this was approved (yay!!) but Jenkins failed due to conflicts
(oy vey!). I have resolved the conflicts. Can you please look at
https://review.openstack.org/8101 again. There were two changes -
merging quantum/common/utils.py and updating an API in quantum/policy.py
(please note
Hi,
In the API (http://wiki.openstack.org/QuantumV2APIIntro#Port), the user
is able to pass /*fixed_ips_v4*/ and /*fixed_ips_v6*/. If possible can
we please change this to /*fixed_ips*/_,_ where the /*fixed_ips*/ is a
list of dictionary's. The dictionary has the following key value pairs:
On 06/19/2012 05:49 PM, Dan Wendlandt wrote:
On Tue, Jun 19, 2012 at 7:47 AM, Gary Kotton gkot...@redhat.com
mailto:gkot...@redhat.com wrote:
Hi,
I have a question regarding the deletion of a subnet in v2.
If Quantum has allocated IP's from this subnet to port's should we
On 06/18/2012 04:18 PM, Robert Kukura wrote:
On 06/18/2012 08:56 AM, Gary Kotton wrote:
Hi,
I have yet to understand what happened. This afternoon I pushed a fix
and Jenkins failed. I got the following error:
/home/jenkins/workspace/gate-quantum-pep8/.tox/pep8/log$
/home/jenkins/workspace
Hi,
Over the last few weeks I have been trying to add a patch that will
enable Quantum to make use of the common configuration interface
provided by the openstack common library. The task is proving very
challenging. At the moment we have the following:
1. OVS and Linux bridge agents using
Hi,
Quantum has moved to openstack common configuration (the plugin.ini file
no longer exists). Support has been added to devstack to ensure that
quantum and devstack will work irrespective of the version running.
Would it be possible to review this so that we can move forward with the
be hidden from the user.
Best regards,
Kris
On Fri, Jun 15, 2012 at 2:11 PM, Gary Kotton gkot...@redhat.com
mailto:gkot...@redhat.com wrote:
Hi Kris,
You have asked a very interesting and good question. Please see
the answers an explanations below. Both flow are used. The a
flows
Hi,
I was playing around with devstack this morning and there are a few
issues that we should be aware of:
1. Linuxbridge is not supported with the v2 API. I'll open a bug.
2. OVS - looked OK. Was unable to get an image running. From the logs it
looked like it was a glance issue (not 100% sure
also prove challenging for the
2.4 compatibility.
Thanks, Roman Sokolkov
2012/6/7 Gary Kotton gkot...@redhat.com mailto:gkot...@redhat.com
On 06/06/2012 11:25 PM, Roman Sokolkov wrote:
Hello!
XCP uses only Python 2.4. But upstream version of quantum ovs
agent
.
Thanks
Gary
Dan
On Tue, Jun 5, 2012 at 10:55 AM, Gary Kotton gkot...@redhat.com
mailto:gkot...@redhat.com wrote:
Hi,
The reviews of the implementation have brought up a number of
issues (https://review.openstack.org/#/c/8101). These are namely
the management of the various
Hi,
If possible I would like to address the bug as follows:
1. When a network is created the user will be able to configure a base
MAC address. If a base MAC address is not allocated by the user then a
base MAC will be read from the Quantum configuration file (the default
will be
not be neglected.
Thanks
Gary
-netstack-bounces+gongysh=cn.ibm@lists.launchpad.net wrote: -
To: netstack@lists.launchpad.net netstack@lists.launchpad.net
From: Gary Kotton
Sent by: netstack-bounces+gongysh=cn.ibm@lists.launchpad.net
Date: 06/11/2012 06:35PM
Subject: [Netstack] Bug
Hi,
Thanks for the time yesterday. Please see my inline comments.
Please feel free to contact me if you have any additional questions.
Thanks
Gary
On 06/06/2012 09:41 PM, Livnat Peer wrote:
Hi All,
This is a summary of the first quantum-oVirt integration meeting.
In the meeting Garry Kotton
On 06/06/2012 11:25 PM, Roman Sokolkov wrote:
Hello!
XCP uses only Python 2.4. But upstream version of quantum ovs agent is
unsupported by Python 2.4. What do you think about? Could we keep it
in supported? And what about refactoring code in favor using RPC
calls? Will it be possible to use
On 06/07/2012 11:39 AM, Neelakantam Gaddam wrote:
Hi All,
Currently, I don't see any Quantum UI in Horizon in Essex. Does the
Horizon support Quantum UI in the current release? If so, please share
the configuration steps. If not, When can I expect the Quantum UI
integration with Horizon ?
Hi Mike,
There are a quite a few people who are unable to make the meeting today
to speak about the Quantum integration. I was asked by Livnat if we
could move this to next week when they will be able to attend. Livnat
said that she will schedule a special oVirt Engine meeting next week to
go
Hi Monty and Dan,
Background: A short while ago I started to port bug fixes for Quantum
from Folsom-1 to Stable Essex. Jenkins did not accept the patches due to
the fact that the automatic tests did not pass. The failures are due to
2 reasons:
1. pep8 checks (addressed in the tox.ini)
2.
On 06/05/2012 04:29 PM, Monty Taylor wrote:
On 06/05/2012 07:54 AM, Gary Kotton wrote:
Hi Monty and Dan,
Background: A short while ago I started to port bug fixes for Quantum
from Folsom-1 to Stable Essex. Jenkins did not accept the patches due to
the fact that the automatic tests did not pass
On 06/03/2012 02:03 AM, Monty Taylor wrote:
On 06/02/2012 02:25 PM, Dan Wendlandt wrote:
Hi Monty,
So moving forward it seems that we have two options here:
1) add hardcoded pep8 version in tox.ini to match the hardcoded version
in tools/tests-requires. Benefit: avoid randomly having all
:48 +0300
From: Gary Kotton gkot...@redhat.com
Reply-To: gkot...@redhat.com
Organization: Red Hat
To: netstack@lists.launchpad.net
On 06/03/2012 02:03 AM, Monty Taylor wrote:
On 06/02/2012 02:25 PM, Dan Wendlandt wrote:
Hi Monty,
So moving forward it seems that we have two
On 06/01/2012 12:47 AM, Russell Bryant wrote:
On 05/31/2012 04:21 PM, Mark McLoughlin wrote:
I expect to do a pretty detailed review of the patch to add rpc to
openstack-common and make some API design recommendations. But I think
we'll have to balance some of those design ideas between stuff
Hi Mike,
There are a quite a few people who are unable to make the meeting today
to speak about the Quantum integration. I was asked by Livnat if we
could move this to next week when they will be able to attend. Livnat
said that she will schedule a special oVirt Engine meeting next week to
go
Hi Bob,
Great work!
I have a few questions:
1. I do not understand point number 6 about the deletion. Can you please
clarify. If I understand correctly the key is the UUID of the network.
How is this related to the VLAN tags?
2. Would it be possible to add the REST API changes?
3. Will the
Thanks!
On 05/23/2012 04:24 PM, Robert Kukura wrote:
On 05/23/2012 02:29 AM, Gary Kotton wrote:
Hi Bob,
Great work!
I have a few questions:
1. I do not understand point number 6 about the deletion. Can you please
clarify. If I understand correctly the key is the UUID of the network.
How
Hi Mike,
There are a quite a few people who are unable to make the meeting today
to speak about the Quantum integration. I was asked by Livnat if we
could move this to next week when they will be able to attend. Livnat
said that she will schedule a special oVirt Engine meeting next week to
go
,
'external-ids:attached-mac=%s' % mac_address,
run_as_root=True)
Thanks
Gary
On 05/22/2012 09:23 AM, Gary Kotton wrote:
Thanks
On 05/21/2012 11:30 PM, Dan Wendlandt wrote:
Just looking at it now. I'd really caution against having generic
calls like device_added, since
On 05/21/2012 12:43 PM, Eli Mesika wrote:
- Original Message -
From: Mike Kolesnikmkole...@redhat.com
To: engine-develengine-devel@ovirt.org
Sent: Monday, May 21, 2012 10:18:30 AM
Subject: [Engine-devel] MAC address validation
Hi,
We have a bug open on engine to validate MAC
Hi,
Thanks for the comments. Please see my replies inline. I hope that these
will not take up too much CPU on your side.
Thanks
Gary
On 05/21/2012 07:57 PM, Dan Wendlandt wrote:
Btw, this actually isn't the case for the OVS plugin. The OVS vif
driver in Nova passes the entire attachment UUID
-Original Message-
From: netstack-bounces+irenab=mellanox@lists.launchpad.net
[mailto:netstack-bounces+irenab=mellanox@lists.launchpad.net] On Behalf Of
Gary Kotton
Sent: Thursday, May 17, 2012 4:10 PM
To:netstack@lists.launchpad.net; Russell Bryant
Subject: [Netstack] Scalable Agent
On 05/18/2012 01:07 PM, Itamar Heim wrote:
On 05/15/2012 05:34 PM, Gary Kotton wrote:
...
2. host management -- interface
2.1 you are suggesting to remove the vlan field with a fabric field?
are we sure this is something which shouldn't be presented in the main
view and only via extended
On 05/17/2012 02:42 PM, Doron Fediuck wrote:
Hi All,
Currently the VDSM has a CPU pinning hook.
We'd like to add better support of it into the engine itself.
Here's a design draft to cover it:
http://www.ovirt.org/wiki/Features/Design/cpu-pinning
Please review and comment if needed.
Hi,
I
Hi,
Please see the link for a detailed design of the scalable agent
solution. I plan to start to work on the actual implementation beginnig
of next week. Please let me know if you have any comments and or
suggestions. Please note that I have used all of the comments and
suggestions from over
On 05/17/2012 04:18 PM, Kyle Mestery (kmestery) wrote:
On May 17, 2012, at 8:09 AM, Gary Kotton wrote:
Hi,
Please see the link for a detailed design of the scalable agent solution. I
plan to start to work on the actual implementation beginnig of next week.
Please let me know if you have any
Hi,
First and foremost sorry for being a bit unclear last night. I am not my
best at 1:55am. Would it be possible to move the meeting a few hours
forwards or backwards?
Update:
I have a POC running where instead of the agents polling the plugin
database a request is sent from the agent to
Hi,
Can we please look at https://review.openstack.org/#/c/7192/. It would
be great if we can get this in and then have the Melange details added.
It will be very helpful for all of us. In addition it would be great if
all could start to build on this.
Thanks
Gary
--
Mailing list:
Hi,
On the IRC meeting last night the following was discussed -
https://blueprints.launchpad.net/quantum/+spec/authorization-support-for-quantum.
Are these tasks mutually exclusive?
I guess that with the Melange addition the client API may also change -
all I have seen is
@lists.launchpad.net] *On
Behalf Of *Gary Kotton
*Sent:* Monday, May 14, 2012 11:19 PM
*To:* netstack@lists.launchpad.net
*Subject:* [Netstack] Fwd: [Openstack] [devstack/quantum]
Configuration issue
Original Message
*Subject: *
[Openstack] [devstack/quantum] Configuration
On 05/16/2012 12:24 AM, Salman Malik wrote:
Hi Guys,
I am having trouble with launching instances. The launch fails on
networking task with status error. Here is the output (at nova-compute
screen session) on launching instance :
2012-05-02 06:41:52 TRACE nova.rpc.amqp RemoteError: Remote
Original Message
Subject:[Openstack] [devstack/quantum] Configuration issue
Date: Tue, 15 May 2012 09:00:52 +0300
From: Gary Kotton gkot...@redhat.com
Reply-To: gkot...@redhat.com
Organization: Red Hat
To: openst...@lists.launchpad.net
Hi
Hi,
This morning I encountered a problem (which did not happen a few days
ago :)). When devstack is launched, with quantum configured, the gateway
and bridge devices are created. This causes problems with quantum.
For example when devstack is up and running prior to deploying an
instance we
-Original Message-
From: openstack-bounces+eperdomo=cisco@lists.launchpad.net
[mailto:openstack-bounces+eperdomo=cisco@lists.launchpad.net] On
Behalf Of Gary Kotton
Sent: Monday, May 14, 2012 11:01 PM
To: openstack@lists.launchpad.net
Subject: [Openstack] [devstack/quantum] Configuration
Hi,
Please see my inline comments. There are quite a few.
Thanks
Gary
On 05/15/2012 01:38 PM, Itamar Heim wrote:
On 04/29/2012 01:41 PM, Gary Kotton wrote:
Hi,
As part of a POC we have integrated Quantum
(http://wiki.openstack.org/Quantum) into oVirt (http://www.ovirt.org/).
This has been
Hi,
Can we please discuss the integration ideas of Quantum into oVirt
(http://www.ovirt.org/wiki/Quantum_and_oVirt)
Thanks
Gary
On 05/14/2012 05:59 PM, Mike Burns wrote:
Any additional agenda items for next week?
Current topics:
* Status of Next Release
* Sub-project reports
Hi,
Can we please discuss the integration ideas of Quantum into oVirt
(http://www.ovirt.org/wiki/Quantum_and_oVirt)
Thanks
Gary
On 05/14/2012 05:59 PM, Mike Burns wrote:
Any additional agenda items for next week?
Current topics:
* Status of Next Release
* Sub-project reports
becomes necessary, it will be
straightforward to plug in a new transport driver.
Let's keep it simple - distributed computing is complicated enough!
Cheers,
Maru
On 2012-05-10, at 8:22 AM, Gary Kotton wrote:
Hi,
Below is a table that lists a number of options, a short
-bounces+snaiksat=cisco@lists.launchpad.net
[mailto:netstack-bounces+snaiksat=cisco@lists.launchpad.net] On
Behalf Of Gary Kotton
Sent: Wednesday, May 09, 2012 4:27 AM
To:netstack@lists.launchpad.net
Subject: [Netstack] Scalable
Agents(https://blueprints.launchpad.net/quantum/+spec/scalable
Hi,
https://review.openstack.org/#/c/7169/ ensures that all of the open
source agents have uniform database access. This requires a minor change
to the devstack code.
In addition to this I have added in some minor chnages which ensure that
the devstack user is able to run Quantum Plugins and
On 05/10/2012 09:07 AM, Itamar Heim wrote:
Gary - can you please share how quantum solves this?
Hi,
At the moment there is work in progress of integrating Melange
(http://wiki.openstack.org/Melange) into Quantum. This module takes care
of the IP address management. Addition information can be
Hi,
First and foremost I think that it was great chatting about the reviews
last night. A few days ago Maru opened a bug
https://bugs.launchpad.net/quantum/+bug/995283. This was addressed in
https://blueprints.launchpad.net/openstack/?searchtext=man-support (it
was based on the nova support).
Hi,
I have added a very high level description on how to address the issue.
This can be seen at:
https://docs.google.com/document/d/1MbcBA2Os4b98ybdgAw2qe_68R1NG6KMh8zdZKgOlpvg/edit
Comments will be greatly appreciated.
Questions:
1. Do we want agents to be backward compatible (that is, still
the Melange code is going to be added.
Thanks a lot,
Irena
-Original Message-
From: netstack-bounces+irenab=mellanox@lists.launchpad.net
[mailto:netstack-bounces+irenab=mellanox@lists.launchpad.net] On Behalf Of
Gary Kotton
Sent: Wednesday, May 09, 2012 2:42 PM
To:netstack
Hi,
Great document. Would it be possible to add in other flavours of Linux
that support Open Stack?
Thanks
Gary
On 05/07/2012 03:23 PM, Eric Dodemont wrote:
I have written a 50 pages document: Install Your Own OpenStack Cloud
- Essex Edition.
The PDF file can be downloaded here:
Hi,
A few weeks ago I started to work on something like this. I think that
it should also cover the MAN pages for the quantum processes that run. I
wrote https://blueprints.launchpad.net/quantum/+spec/man-support (I have
yet to complete it).
Thanks
Gary
On 05/06/2012 01:26 AM, Maru Newby
manner.
2. vifAdd - this will be called with the MAC address, the VM UUID and
maybe additional information
3. vifDelete
Regards,
Irena
-Original Message-
From: engine-devel-boun...@ovirt.org [mailto:engine-devel-boun...@ovirt.org] On
Behalf Of Gary Kotton
Sent: Monday, April 30, 2012 2:56
Hi,
I have taken a more thorough look at the database implementations. On
the plugin side all of the plugins make use of the common database code
(../quantum/quantum/db/*). Today I tested a number of scenarios with
connectivity to the server. This works well with the linuxbridge and the
On 05/03/2012 07:15 PM, Dan Wendlandt wrote:
Hi Gary,
Great to see all the effort on improving usability + consistency.
On Thu, May 3, 2012 at 7:36 AM, Gary Kotton gkot...@redhat.com
mailto:gkot...@redhat.com wrote:
Hi,
I have taken a more thorough look at the database implementations
-agent-comms
Thoughts?
Maru
On 2012-05-03, at 7:36 AM, Gary Kotton wrote:
Hi,
I have taken a more thorough look at the database implementations. On the
plugin side all of the plugins make use of the common database code
(../quantum/quantum/db/*). Today I tested a number of scenarios
.
What do you suggest?
Dan
On Wed, May 2, 2012 at 12:33 AM, Gary Kotton gkot...@redhat.com
mailto:gkot...@redhat.com wrote:
Hi,
It seems that everything has gone pear shaped. I have conflicts
with the HACKING.rst fix. From the IRC meeting last night I
understood that I should
On 05/02/2012 09:31 PM, Dan Wendlandt wrote:
Ok. I suggested keeping a version of the code that had not be rebased
on top of Maru's changes, as that might be easier to backport to
essex/stable. If you need help with git, I can probably help. In
general, authoring a change for essex/stable
1001 - 1100 of 1125 matches
Mail list logo
