-Original Message-
From: Sumit Naiksatam (snaiksat)
Sent: Wednesday, August 15, 2012 1:59 PM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [Quantum] Proposing Mark McClain & Nachi Ueno for core
dev
Hi All,
I feel Mark McClain (markmcclain) and Nachi Ueno have
Hi,
Yes, if you do not specify networks using the “–nic” option you will get a vnic
on each of the public networks and one for each network belonging to that
tenant. Using the “—nic net-id=uuid-xyz” option you can refer to specific
networks on which you want the vnics.
Thanks,
~Sumit.
From: n
Hi,
Yes, if you do not specify networks using the “–nic” option you will get a vnic
on each of the public networks and one for each network belonging to that
tenant. Using the “—nic net-id=uuid-xyz” option you can refer to specific
networks on which you want the vnics.
Thanks,
~Sumit.
From: n
Hi,
I believe there are two topics of discussion here, one of which is the
terminology. The way things are implemented today, I agree that the “plugin”
terminology seems a bit confusing. However, probably the bigger topic of
discussion is what kind of a design is preferable, “backend” versus “p
Hi All,
I second Gary's suggestion here for a network type attribute. I was curious to
know why we moved away from the kwargs mechanism which we had earlier in the
core API. That made it easier to pass any plugin-specific parameters which need
not be core attributes, and not have to necessarily
I think it's fair to expect that, for a plugin to be in the community repo, it
be maintained by at least one core dev. Also, in cases where a new plugin is
being introduced by new contributors, at least one of them can be promoted to
core dev (if none of the existing core devs take responsibilit
Hi All,
The following bugs are not assigned to anyone but are targeted for F2. Is
anyone working, or wants to work, on them?
* https://bugs.launchpad.net/quantum/+bug/1014989 - "check foreign key
ownership for port/subnet creation"
* https://bugs.launchpad.net/quantum/+bug/1007998 - "xml suppo
Hi All,
As we head into the weekend, just wanted to take a stock of the pending reviews
(it's my turn today :-)).
** Quantum reviews:
https://review.openstack.org/#/q/status:open+project:openstack/quantum,n,z
* https://review.openstack.org/#/c/8822/ - "Add simple file loggin to
ovs_quantum_a
Hi Gary,
As for #3 it might be an intermittent failure, console output says:
14:08:19 Build step 'Execute shell' marked build as failure
14:08:19 Looks like the node went offline during the build. Check the slave
log for the details.
You probably want to kick off the build again (I am not sur
+1
From: netstack-bounces+snaiksat=cisco@lists.launchpad.net
[mailto:netstack-bounces+snaiksat=cisco@lists.launchpad.net] On
Behalf Of Dan Wendlandt
Sent: Monday, June 04, 2012 6:18 PM
To: netstack@lists.launchpad.net
Subject: [Netstack] proposing Yong Sheng Gong for quantum-core
On
+1
From: netstack-bounces+snaiksat=cisco@lists.launchpad.net
[mailto:netstack-bounces+snaiksat=cisco@lists.launchpad.net] On
Behalf Of Dan Wendlandt
Sent: Monday, June 04, 2012 10:18 AM
To: netstack@lists.launchpad.net
Subject: [Netstack] proposing gary kotton for quantum-core
Hi fo
...@redhat.com
Cc: Sumit Naiksatam (snaiksat); netstack@lists.launchpad.net
Subject: Re: [Netstack] Fwd: [Openstack] [devstack/quantum]
Configuration issue
On Wed, May 16, 2012 at 1:43 AM, Gary Kotton wrote:
Thanks!
As far as I recall, and I may certain be wrong here, but in the past I
did not see
This is probably not a devstack issue. The problem is with the LB
gateway driver wherein the IP address is trying to be set on a bridge
device which already has an IP address. The check for an existing bridge
is being performed, but the IP address is being set outside that check.
Ideally, this code
2.
Thanks
Gary
On 05/10/2012 10:05 AM, Gary Kotton wrote:
On 05/10/2012 12:55 AM, Sumit Naiksatam (snaiksat) wrote:
Hi Gary,
Thanks for initiating this. A couple of comments/questions -
1. Do we really need the VIF driver to communicate the agent's identity;
I am referring to the
Hi Gary,
Thanks for initiating this. A couple of comments/questions -
1. Do we really need the VIF driver to communicate the agent's identity;
I am referring to the agent ID being sent by the VIF driver in the
message? In general, I am not sure if there is a need to have the VIF
driver send messa
nts WITHIN a Quantum deployment. Connectivity between different
Quantum deployments, or to remote datacenters not running Quantum is
viewed many as a separate service (e.g., L3VPN-service).
On Tue, Apr 24, 2012 at 12:08 PM, Robert Kukura
wrote:
On 04/24/2012 10:12 AM, Sumit Naiksatam (sn
e: [Netstack] L3/IPAM summit discussion follow-up...
>
> On 04/24/2012 10:12 AM, Sumit Naiksatam (snaiksat) wrote:
> > Hi All,
> >
> > Thanks for your feedback on the L3 (forwarding) proposal during the
> > summit and also prior to that. The action item coming out of t
Hi Gary,
Thanks for taking up the work on improving the HA aspects of some of the
agents. (I will respond to your review request once I get a chance to
test the changes, but the diff looks good.)
I agree with your assessment that the factoring of common agent code is
probably a larger activ
Hi All,
Thanks for your feedback on the L3 (forwarding) proposal during the
summit and also prior to that. The action item coming out of the summit
session was to further discuss this with the Melange/IPAM team to
identify points of overlap and/or what are the additional requirements.
Accordingly,
April 11, 2012 2:09 PM
To: Sumit Naiksatam (snaiksat)
Cc: netstack@lists.launchpad.net; Brad Hall; Carl Perry
Subject: Re: L3 Forwarding
On Mon, Apr 2, 2012 at 8:59 PM, Sumit Naiksatam (snaiksat)
wrote:
Hi All,
Per the context setup by Dan in his email on the topic of Quantum L3
Forwardi
Thanks Andi. Responses inline...
> -Original Message-
> From: andi abes [mailto:andi.a...@gmail.com]
> Sent: Wednesday, April 11, 2012 7:22 PM
> To: Dan Wendlandt
> Cc: Sumit Naiksatam (snaiksat); netstack@lists.launchpad.net
> Subject: Re: [Netstack] L3 Forwarding
; Sent: Tuesday, April 03, 2012 3:28 PM
> To: Sumit Naiksatam (snaiksat)
> Cc: Jason Kölker;
> Subject: Re: [Netstack] L3 Forwarding
>
> Sumit,
>
> You can see the latest Melange documentation here:
>
> http://melange.readthedocs.org/en/latest/apidoc.html
>
> The
Here's a thought - to the point on having to avoid churn in the nova
code (on account Quantum plugin specific VIFs), how about we try to
solve this issue via packaging? What if we have a separate Quantum nova
driver package which when deployed will install the VIF drivers in the
appropriate locatio
Thanks Dan, let me go through these and sync up with you directly (to
avoid unnecessary noise on the mailer).
Thanks,
~Sumit.
From: Dan Wendlandt [mailto:d...@nicira.com]
Sent: Tuesday, April 03, 2012 2:44 PM
To: Sumit Naiksatam (snaiksat)
Cc: netstack@lists.launchpad.net
Subject: Re
2 5:56 AM
> To: Sumit Naiksatam (snaiksat)
> Cc: Jason Kölker;
> Subject: Re: [Netstack] L3 Forwarding
>
>
> On Apr 3, 2012, at 12:24 AM, Sumit Naiksatam (snaiksat) wrote:
>
> > Hi Jason,
> >
> > Per the information published, Melange is an IPAM service
> (
Hi Dan,
On the documentation part, I can try to help to the extent I can. Please
let me know how I can pitch in.
Thanks,
~Sumit.
From: netstack-bounces+snaiksat=cisco@lists.launchpad.net
[mailto:netstack-bounces+snaiksat=cisco@lists.launchpad.net] On
Behalf Of Dan Wendlandt
nchpad.net] On
> Behalf Of Jason Kölker
> Sent: Monday, April 02, 2012 9:16 PM
> To: netstack@lists.launchpad.net
> Subject: Re: [Netstack] L3 Forwarding
>
> On Mon, 2012-04-02 at 20:59 -0700, Sumit Naiksatam (snaiksat) wrote:
> > Following is a summary of the additio
Hi All,
Per the context setup by Dan in his email on the topic of Quantum L3
Forwarding, here is an addition we are making to the earlier proposal -
API/specification pertaining to creating and managing "targets". I have
updated the API specification with this addition and posted the new
version o
how your work can
complement those?
Thanks,
~Sumit.
From: Juliano Martinez [mailto:juliano.marti...@locaweb.com.br]
Sent: Thursday, March 29, 2012 3:33 PM
To: Sumit Naiksatam (snaiksat)
Cc: Willian Molinari;
Subject: Re: [Netstack] Kickstart for Layer 3 discussions
Hi Sumit
Hi Willian, All,
Thanks for your thoughts on this. The discussions around L3 abstractions/API
have been ongoing for a while now. To be precise, the discussions started
during the Essex design summit, and we took action items away from the summit
to work during the past few months. Subsequen
Hi William,
>From the looks of it, you seem to be trying to use the Quantum
LinuxBridge plugin and facing the issue. The error you mention below
suggests that you might not be pointing to the right
linuxnet_interface_driver (you should be seeing bridge names starting
with a "brq-" and then firs
quot;ALL" instead of "USAGE".)
Thanks,
~Sumit.
> -Original Message-
> From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of
> Christian Berendt
> Sent: Tuesday, March 27, 2012 2:53 AM
> To: Sumit Naiksatam (snaiksat)
> Subject: [Bug 966079] [NEW]
Hi Dave,
Thanks for sharing this. I had been independently working on this a few
days back, and wanted to compare notes with you (I saw other emails as
well on this topic, hence thought it might be helpful to have a broader
discussion).
For the localrc files,
* Would it be better to use HOST_IP_
; plans
> >
> > We would also like to cover some topics that relate to running
> Quantum at
> > scale. This would include API rate limiting and caching,
> understanding the
> > models for scaling out the service and where we should make things
> more
> > asynchron
s.launchpad.net] On
> Behalf Of Tomasz Paszkowski
> Sent: Wednesday, March 21, 2012 12:13 AM
> To: netstack@lists.launchpad.net
> Subject: Re: [Netstack] Fwd: [Openstack] Quantum 2012.1 RC1 available
>
> Hi,
>
> Comments inline
>
> On Wed, Mar 21, 2012 at 12:18 AM
Hi Deepak, and All,
I feel this is very good dimension to factor in while prioritizing which tasks
to take up for Folsom - what are the consumers of the Quantum service asking
for? Not to say that any, or all of what has already been mentioned in this
thread is not driven by requirements; I am
agent has to be run so that the
per-host configuration is done correctly. So the agent is needed. Of course,
if there are any issues, those need to be fixed.
Dnia 20-03-2012 o godz. 22:29 "Sumit Naiksatam (snaiksat)"
napisał(a):
Hi Ghe,
Thanks for this up
Hi Ghe,
Thanks for this update. The Linux Bridge plugin also needs an agent. I would
imagine that the packaging of that agent would be very similar to that of the
openvswitch-agent, but I don't know enough on the packaging to say with any
certainty.
Also, the Cisco plugin does not use an
Thanks Monty, problem seems to have gone away.
> -Original Message-
> From: Monty Taylor [mailto:mord...@inaugust.com]
> Sent: Friday, March 16, 2012 1:32 AM
> To: Dan Wendlandt
> Cc: Sumit Naiksatam (snaiksat); netstack@lists.launchpad.net; Thierry
> Carrez; James E. B
Thanks Dan for your prompt attention. Plan sounds good, we will stay
tuned for any updates on this.
~Sumit.
From: Dan Wendlandt [mailto:d...@nicira.com]
Sent: Thursday, March 15, 2012 11:53 PM
To: Sumit Naiksatam (snaiksat)
Cc: netstack@lists.launchpad.net; Thierry Carrez; Monty Taylor
Hi All,
It's failing with the following trace, and we are not sure what's
causing it:
Installing collected packages: quantum
Running setup.py install for quantum
Installing quantum-linuxbridge-agent script to
/home/jenkins/workspace/gate-quantum-unittests/.tox/jenkins27/bin
Install
We are following a similar approach, as indicated by Brian here, in the
Linux-bridge plugin for Quantum. There is a dummy tap device created
with the requested MAC address, and is the first one to get added to the
bridge. Subsequently, the bridge's MAC address stays anchored to this
tap device's MA
+1 for all!
From: netstack-bounces+snaiksat=cisco@lists.launchpad.net
[mailto:netstack-bounces+snaiksat=cisco@lists.launchpad.net] On
Behalf Of Debo Dutta (dedutta)
Sent: Tuesday, March 13, 2012 4:09 PM
To: Debo Dutta (dedutta); Dan Wendlandt; netstack@lists.launchpad.net
Subject: Re: [
Hi Bob, Thanks for taking this up. Responses inline.
~Sumit.
> -Original Message-
> From: Robert Kukura [mailto:rkuk...@redhat.com]
> Sent: Tuesday, March 13, 2012 9:40 AM
> To: Sumit Naiksatam (snaiksat); Dan Wendlandt; Brad Hall;
> netstack@lists.launchpad.net
> Cc:
Hi Tomoe,
I don't think we, as a community, have discussed this requirement. In
general, for plugin-specific features, there is always an option to
expose/implement them as extensions. Check the section on API Extensions
here:
http://wiki.openstack.org/QuantumDevelopment
Thanks,
~Sumit.
> -O
Hi Michael,
Thanks for taking the lead on this. I was curious to know as to what the
agenda is on the following sprint topic:
"defining a first draft of an API for layer 3 networking support"
Is this discussion in the context of Nova or Quantum (probably both)?
While on that, I would like to dra
Hi Michael,
Thanks for taking the lead on this. I was curious to know as to what the
agenda is on the following sprint topic:
"defining a first draft of an API for layer 3 networking support"
Is this discussion in the context of Nova or Quantum (probably both)?
While on that, I would like to dra
Thanks Dan for the heads up; as mentioned on the IRC, we are looking at
it. Also am signed up for the review.
~Sumit.
From: netstack-bounces+snaiksat=cisco@lists.launchpad.net
[mailto:netstack-bounces+snaiksat=cisco@lists.launchpad.net] On
Behalf Of Dan Wendlandt
Sent: Tuesday, Feb
Hi Dan,
Thanks for the clarifying this, and also kudos for keeping the documentation in
sync. While on this, is there a way to subscribe to changes in the Quantum
documentation (or better still, subscribe the netstack mailer)? I think that
might help to preempt these kind of issues. The general
o=eu.citrix.com@lists.launchpad
.net] On Behalf Of Sumit Naiksatam (snaiksat)
Sent: 02 February 2012 03:15
To: Edgar Magana (eperdomo); netstack@lists.launchpad.net
Subject: Re: [Netstack] where did the common folder go?
Hi Edgar,
With the splitting of repos, I believe you will need the
pytho
Hi Edgar,
With the splitting of repos, I believe you will need the
python-quantumclient package and the quantum-common packages:
https://launchpad.net/ubuntu/+source/quantum/+index
Per my understanding, there is a common git repo for the client and the
common code:
https://github.com/open
A quick comment (and not to distract from the theme of the thread), the UCS
plugin does support plug and unplug operations.
From: netstack-bounces+snaiksat=cisco@lists.launchpad.net
[mailto:netstack-bounces+snaiksat=cisco@lists.launchpad.net] On Behalf Of
Salvatore Orlando
Sent: Wedn
Hi,
In its current implementation Libvirt makes sure that the network
interfaces that it passes/provision to a VM (for example to qemu[-kvm])
are already connected to its backend (interfaces/networks) by the time
the VM starts its boot process. In a non virtualized setup it would be
like booting a
Hi,
In its current implementation Libvirt makes sure that the network
interfaces that it passes/provision to a VM (for example to qemu[-kvm])
are already connected to its backend (interfaces/networks) by the time
the VM starts its boot process. In a non virtualized setup it would be
like booting a
Hi All,
We have posted some tests and fixes in the Diablo code for review (this
is all within the Cisco plugin/extensions):
https://review.openstack.org/1070
We need one more person to review.
Thanks,
~Sumit.
--
Mailing list: https://launchpad.net/~netstack
Post to : netstack@lists.laun
Hi Salvatore/Dan, Yes, we can take a look a this. Salvatore we will sync
with you on a separate thread on how to go about it.
Thanks,
~Sumit.
From: Salvatore Orlando [mailto:salvatore.orla...@eu.citrix.com]
Sent: Thursday, October 20, 2011 10:22 AM
To: Sumit Naiksatam (snaiksat); Dan
Hi Salv, Echo Dan's suggestions and comments, great write-up.
Just a general comment (& this is a nit) - "Examples of situations in
which a resource might not be operative include faults, insufficient
capabilities in the physical or virtual switching layer, or simply, in
the case of ports, the
Hi Brad,
Thanks for starting this discussion. A quick note in the context of the
reference to the Cisco plugin in your email (and don't mean to distract
from the broader theme of the discussion), the changes will have to be
made in multiple interfaces & modules (since there is a hierarchy), not
ju
Apologies for the incorrect link, the link should be:
http://wiki.openstack.org/l3-service?action=AttachFile&do=view&target=qu
antum-nova-parity-SumitNaiksatam-v3.pdf
From: Sumit Naiksatam (snaiksat)
Sent: Tuesday, October 18, 2011 2:46 PM
To: 'Dan Wendlandt'; netstack@l
Hi,
Following up on the topic of nova-network parity, we also wanted to
continue the discussion around how the proposed L3 service can be
leveraged to achieve this.
We have posted a very preliminary flow in the document here:
http://wiki.openstack.org/quantum-multi-switch-plugin?action=Atta
On that note, I would also like to nominate Rohit Agarwalla for membership. He
participated & will continue to do so with code and review activities.
+1 for Edgar
Thanks,
~Sumit.
> -Original Message-
> From: netstack-bounces+snaiksat=cisco@lists.launchpad.net
> [mailto:netstack-boun
Hi Salvatore,
Thanks for starting this. A few comments/questions -
* You mention - "This model however implies that the Quantum plugin will
be doing not just the 'logical' plugging of the VIF/vNIC, but also the
'physical' plugging, which is not what happens today." May be I am not
reading t
Hi Dan,
I have looked at the changes and they seem to be fine. Thanks for taking
care of this.
We will need to do more testing on this, and there are other changes as
well for which we will propose a merge soon from another branch. Until
then, this is fine on the trunk.
Since the branch
http://etherpad.openstack.org/l3service
Thanks,
~Sumit.
--
Mailing list: https://launchpad.net/~netstack
Post to : netstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~netstack
More help : https://help.launchpad.net/ListHelp
Thanks Salvatore. I am fine on item 6 and will get back to you with more
info.
I am guessing that the discussion on item 2 will help to address the
asynchronous API requirements.
As a general suggestion on item 3, can we also consider having the
following attributes be a part of every quant
Perfect Dan; yes Vif flags as described in Section 4.2.
From: Dan Wendlandt [mailto:d...@nicira.com]
Sent: Monday, September 26, 2011 2:28 PM
To: Sumit Naiksatam (snaiksat)
Cc: netstack@lists.launchpad.net
Subject: Re: [Netstack] Quantum 2011.3 Diablo is out!
Thanks Sumit, I will turn
Thanks,
~Sumit.
From: Dan Wendlandt [mailto:d...@nicira.com]
Sent: Monday, September 26, 2011 9:06 AM
To: Sumit Naiksatam (snaiksat)
Cc: netstack@lists.launchpad.net
Subject: Re: [Netstack] Quantum 2011.3 Diablo is out!
Thanks Sumit, great feedback. Most comments I just applied
Hi Dan,
As always, great work. Here are some minor suggestions after a quick
read -
Page 2, 2.2.1, "At its core, Quantum control the network
connectivity..." --> controls
Page 2, 2.2.2 - "For an OpenStack service (e.g., Nova) to work with
Quantum, it must be modified to inform Quantum a
Thanks Dan. I am pretty much in line with your thinking.
From: Dan Wendlandt [mailto:d...@nicira.com]
Sent: Monday, September 19, 2011 1:03 PM
To: Sumit Naiksatam (snaiksat)
Cc: Salvatore Orlando; Ram Durairaj (radurair);
netstack@lists.launchpad.net
Subject: Re: [Netstack] Proposing
session if there is an overlap.
Thanks,
~Sumit.
From: Dan Wendlandt [mailto:d...@nicira.com]
Sent: Monday, September 19, 2011 12:16 PM
To: Sumit Naiksatam (snaiksat)
Cc: Salvatore Orlando; Ram Durairaj (radurair);
netstack@lists.launchpad.net
Subject: Re: [Netstack] Proposing sessions for Openst
Hi All,
Here are a few more issues which we think need to be tackled -
* A framework for Rollback after Operation Failure, Troubleshooting &
Diagnostics:
The realization of the APIs supported by the Quantum service (such as
create_network, create_port) results in a series of steps in the
Done on the first count, not on the second J...thanks for pointing it
out...
From: Dan Wendlandt [mailto:d...@nicira.com]
Sent: Friday, August 26, 2011 1:38 AM
To: Sumit Naiksatam (snaiksat)
Cc: Salvatore Orlando; netstack@lists.launchpad.net
Subject: Re: [Netstack] D-4 drop delayed: cli
J I could do it, but I think someone like Tyler who has more familiarity
with the code can do a better job. On seeing this thread, I did reach
out to him and made that suggestion.
From: netstack-bounces+snaiksat=cisco@lists.launchpad.net
[mailto:netstack-bounces+snaiksat=cisco@lists.lau
rlando [mailto:salvatore.orla...@eu.citrix.com]
> Sent: Wednesday, August 24, 2011 3:15 AM
> To: Sumit Naiksatam (snaiksat); netstack@lists.launchpad.net
> Subject: RE: Quantum tenant <--> Nova ?
>
> I haven't looked in detail at this issue yet, though I expected it
> w
My apologies if this question has already been answered/discussed - what
is a tenant within Quantum mapped to in Nova? I noticed that Nova is
still refers to project-id and apparently uses that a tenant when
interfacing with Keystone. So does a Quantum tenant map to a Nova
project?
Thanks,
~Sumit.
Thanks Salv for spelling out the deliverables on this topic.
On the point of the "simplified mode", I wasn't very clear on what you
meant by "Although in theory several users can be defined for a tenant,
we will assume that each user has the same administrative rights." Does
this mean that each
Thanks Salvatore for outlining the efforts around aligning the API.
As for the issue of synchronous versus asynchronous. I agree that
leaving it to the plugin to implement the behavior might be more
flexible and also alleviate the burden on the API framework
implementation. Having said that, ea
, July 25, 2011 6:18 PM
To: Sumit Naiksatam (snaiksat)
Cc: Ishimoto, Ryu; netstack@lists.launchpad.net
Subject: Re: "network-refactoring-l2" branch, and Quantum
Hi Sumit,
On Mon, Jul 25, 2011 at 10:30 AM, Sumit Naiksatam (snaiksat)
wrote:
(4)This last one is probably not specif
ross more than one tenant?
Thanks,
~Sumit.
From: Troy Toman [mailto:troy.to...@rackspace.com]
Sent: Monday, July 25, 2011 10:41 AM
To: Sumit Naiksatam (snaiksat)
Cc: Ishimoto, Ryu;
Subject: Re: [Netstack] "network-refactoring-l2" branch, and Quantum
On Jul 25, 2011, at
on as well in
communicating between nova and Quantum.
Thanks,
~Sumit.
From: Ishimoto, Ryu [mailto:r...@midokura.jp]
Sent: Monday, July 25, 2011 4:58 AM
To: Sumit Naiksatam (snaiksat)
Cc: Dan Wendlandt; netstack@lists.launchpad.net
Subject: Re: "network-refactoring-l2" branch,
n the nova API side (and not on the
Quantum side as my email seemed to suggest), right?
Thanks,
~Sumit.
From: Dan Wendlandt [mailto:d...@nicira.com]
Sent: Sunday, July 24, 2011 10:46 PM
To: Sumit Naiksatam (snaiksat)
Cc: Ishimoto, Ryu; netstack@lists.launchpad.net
Subject: Re: "networ
Hi Ryu, Dan, and others involved,
I had some questions regarding how the code base in the
"network-refactoring-l2" branch currently works (or is supposed to) with
Quantum.
As I understand, eventually we want to get to a point where one should
be able to run the Quantum service instead of the nova
Hi Ryu,
Wanted to point out a small change required in the 802.1Qbh template, it
should be:
Notice that the place holders should have a "'" around them, which is
missing in the current templat
seems like even in that case, the system does look at this.
Setting it to NULL helped get past this.
Thanks,
~Sumit.
From: Deepak N [mailto:dee...@thoughtworks.com]
Sent: Tuesday, July 19, 2011 11:39 PM
To: Sumit Naiksatam (snaiksat)
Cc: Ishimoto, Ryu; netstack@lists.launchpad.net
Subject: Re
Hi Ryu,
I am seeing the following exception when starting a VM, any clue as to
what might be going wrong in my setup?
Thanks,
~Sumit.
nova-compute.log:
2011-07-19 20:29:13,287 DEBUG nova.rpc [-] received
{u'_context_request_id': u'15OCH-PML6F3OL-761VR',
u'_context_read_deleted': False, u'args':
Hi,
Just wanted to follow up on the discussion in today's NetStack meeting
around the different network interface attachment types to be covered by
the nova refactoring effort.
I had a question on how Quantum gets the information about where a VM is
being placed (so as to configure networking on
Hi,
I encountered a regular expression error when running Quantum service on
a Red Hat installation. The Quantum service is not able to process any
requests on account of which this error. The exception trace is appended
to this email, but in short, the offending regular expression appears to
be c
Hi Salvatore,
Just to confirm, the proposal is to keep:
POST /networks/{net_id}/ports/{port_id}/attachment
DELETE /networks/{net_id}/ports/{port_id}/attachment
GET /networks/{net_id}/ports/{port_id}/attachment
But remove:
POST /networks/{net_id}/attachments
GET /networks/{net_id}
Hi,
Is there a preference to use one versus the other in OpenStack? I
noticed that libxml2 is currently being used in places, however there
are comments suggesting the need to be move to ElementTree.
Kindly suggest.
Thanks,
~Sumit.
___
Mailing list: h
e "source dev" and "profiled"?
Thanks,
~Sumit.
From: Dan Wendlandt [mailto:d...@nicira.com]
Sent: Tuesday, May 31, 2011 9:53 AM
To: Sumit Naiksatam (snaiksat)
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack][NetStack] "Attach resource to port" sema
between Nova and Quantum fleshed out).
Thanks,
~Sumit.
From: Dan Wendlandt [mailto:d...@nicira.com]
Sent: Monday, May 30, 2011 11:15 PM
To: Sumit Naiksatam (snaiksat)
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] [NetStack] "Attach resource to port" semantics
Hi Sum
Hi,
I would like to request clarity on the semantics of the "attach resource
to port" operation proposed in Quantum in the context of spawning a VM.
Let's discuss this with respect to a specific example. As of today,
nova-compute generates the domain configuration (libvirt.xml), including
the n
92 matches
Mail list logo
