** Changed in: nova
Milestone: None = havana-rc1
** Changed in: nova
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1226450
Hi,
Not related to the stable branches, but related to trunk. At the moment I am
working on https://review.openstack.org/#/c/47788/. This patch adds a timeout
to the access to the OVS database.
The neutron gate fails on this -
Yay!!
On 9/26/13 10:47 AM, Michael Still mi...@stillhq.com wrote:
On Thu, Sep 26, 2013 at 2:49 PM, Clint Byrum cl...@fewbar.com wrote:
Excerpts from Joe Gordon's message of 2013-09-25 17:56:15 -0700:
Hi All,
TL;DR: We will be automatically identifying your flaky tempest runs,
so you
just
Hi,
The minutes from the meeting are below.
Minutes:
http://eavesdrop.openstack.org/meetings/scheduling/2013/scheduling.2013-09-24-15.03.html
6:59
Minutes (text):
http://eavesdrop.openstack.org/meetings/scheduling/2013/scheduling.2013-09-24-15.03.txt
Log:
Hi,
Anyone know the root cause of:
2013-09-24 06:47:01.670 | Cleaning up...
2013-09-24 06:47:01.670 | No distributions matching the version for
pyparsing=2.0.1 (from cliff=1.4.3-python-neutronclient=2.3.0,3--r
/home/jenkins/workspace/gate-nova-pep8/requirements.txt (line 25))
2013-09-24
This just seems to affect Nova.
Thanks
Gary
From: Administrator gkot...@vmware.commailto:gkot...@vmware.com
Reply-To: OpenStack Development Mailing List
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Tuesday, September 24, 2013 11:15 AM
To: OpenStack Development
Hi,
Done is still away on his vacation (lucky guy).
Last week we did not have time to discuss the proposals by Mike Spreitzer
(https://docs.google.com/document/d/1hQQGHId-z1A5LOipnBXFhsU3VAMQdSe-UXvL4VPY4ps/edit).
Today can give us an opportunity to go over that and additional scheduling
Hi,
This is a known issue and it was addressed by
https://review.openstack.org/#/c/40298/ (this was approved a few days ago). Can
you please pull the latest nova code and the issue will be resolved.
Thanks
Gary
From: openstack learner
openstacklea...@gmail.commailto:openstacklea...@gmail.com
Hi,
Anyone know why the devstack gating is broken?
Thanks
Gary
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Thanks!
On 9/22/13 6:41 PM, Sean Dague s...@dague.net wrote:
On 09/22/2013 11:10 AM, Gary Kotton wrote:
Hi,
Anyone know why the devstack gating is broken?
Thanks
Gary
I was just looking over logs, especially the last merge on integrated
projects before things went funny (at about midnight
Thanks to everyone for the reviews over the last 24 hours. I really
appreciate the time and effort from all in the review process. I hope that
once we have the tempest results posted automatically for each for each
patch then it will give the core reviewers more confidence in the Vmware
fixes.
Hi,
The following two patches are really important (they are really simple and
have been around since beginning of August - they are rebased every couple
of days):-
- https://review.openstack.org/#/c/40298/ - Tempest snapshot fails
- https://review.openstack.org/#/c/43994/ - Disk copy fails
There
Hi,
Can a core reviewer please look at https://review.openstack.org/#/c/45691/. The
has one +2 and a number of +1's
Thanks
Gary
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
Hi,
Don is on vacation. Lets try and have the meeting today.
Topics that come to mind:
1. https://etherpad.openstack.org/IceHouse-Nova-Scheduler-Sessions
* We discussed this extensively last week. Are there any open issues
related to this
2. Discuss resource tracking (alaski)
3.
Hi,
Can you please join us at the up and coming scheduler meeting. That will give
you a chance to bring up the idea's and discuss them with a larger audience.
https://wiki.openstack.org/wiki/Meetings#Scheduler_Sub-group_meeting
I think that for the summit it would be a good idea if we could also
:Gary Kotton gkot...@vmware.commailto:gkot...@vmware.com
To:OpenStack Development Mailing List
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org,
Date:09/11/2013 06:06 AM
Subject:Re: [openstack-dev] [heat] Comments/questions on the
instance-group-api
+1
From: Day, Phil philip@hp.commailto:philip@hp.com
Reply-To: OpenStack Development Mailing List
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Thursday, September 12, 2013 3:40 PM
To: OpenStack Development Mailing List
@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: [openstack-dev] [heat] Comments/questions on the
instance-group-api-extension blueprint
First, I'm a newbie here, wondering: is this the right place for
comments/questions on blueprints? Supposing it is...
[Gary Kotton] Yeah, as Russel
Hi,
Don is on vacation. Lets try and have the meeting today.
Topics that come to mind:
1. https://etherpad.openstack.org/IceHouse-Nova-Scheduler-Sessions
2. Scheduling BP's that missed H. Bad timing or do we need to discuss and see
how we can improve the process
3. Open issues
Thanks
Gary
Hi,
Anyone can submit a new plugin :). The proposed code will go through the
regular review process.
It is best to open a blueprint for the proposed plugin
(https://launchpad.net/neutron). At the moment we are in a feature freeze for
the H cycle. So the chances of it getting in now are pretty
.
The scheduling after a failed attempt would not invoke the anti affinity
scheduling, which may lead to an invalid host being selected.
I am going to post a patch soon.
Thanks
Gary
On 9/6/13 3:18 PM, Gary Kotton gkot...@vmware.com wrote:
Hi,
Sorry for the delayed response (it is new years my side
, policies etc. Hence a little sad.
Hopefully we will have better luck next time :) Thanks to all the
reviewers esp Chris Yeoh, Dan Smith, Alex Xu and Russell Bryant for
their time. Thanks Thierry for trying to help with the FFE!
debo
On Fri, Sep 6, 2013 at 9:09 AM, Gary Kotton gkot...@vmware.com
Hi,
The following patch was approved but failed as it required a rebase -
https://review.openstack.org/#/c/41058/. Would it be possible that a core
reviewer takes a look.
Thanks in advance
Gary
___
OpenStack-dev mailing list
I
got it now.
Best regards,
Simon
[1] http://paste.openstack.org/show/45672/
[2] http://paste.openstack.org/show/45671/
[3]
https://github.com/openstack/nova/blob/master/nova/scheduler/driver.py#L
137
Le 03/09/2013 10:49, Gary Kotton a écrit :
Hi,
Hopefully I will be able to address
On 9/6/13 5:07 PM, Russell Bryant rbry...@redhat.com wrote:
On 09/06/2013 05:06 AM, Thierry Carrez wrote:
Debojyoti Dutta wrote:
As per my IRC chats with dansmith, russellb, this feature needs the
user auth checks (being taken care of in
https://bugs.launchpad.net/nova/+bug/1221396).
Dan
Hi,
Hopefully I will be able to address your questions. First lets start with
the group anti-affinity. This was added towards the end of the Grizzly
release cycle as a scheduling hint. At the last summit we sat and agreed
on a more formal approach to deal with this and we proposed and developed
Hi,
Whilst reviewing the olso messaging (my poor browser with all of the open tabs)
it has come to my attention that the nova sample configuration file no longer
has the RPC message configuration values. The common CFG values are also no
longer in the file. I think that this is a bug and would
Hi,
Would it be possible for a core reviewer to please look at
https://review.openstack.org/#/c/40105/.
Thanks
Gary
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Hi,
Which Neutron plugin are you using (this was previously known as Quantum)?
You can look at
https://wiki.openstack.org/wiki/NovaVMware/DeveloperGuide#Developer.27s_Dev
Stack_.2B_vSphere_Guide for an example on to do it with devstack (this may
provide some in sites on how to configure the
Hi,
Whilst reviewing the code I think that I have stumbled on an issue (I hope that
I am mistaken). The change set (https://review.openstack.org/#/c/35749/)
expects pci stats to be returned from the host. There are a number of issues
here that I have concern with an would like to know what the
Hi,
I am not sure that there is a good solution. I guess that we all need to
'vasbyt' (that is Afrikaans for bite the bullet) and wait for the code posted
to be reviewed. In Neutron when we were heading towards the end of a cycle and
there were a ton of BP's being added the PTL would ensure
://blueprints.launchpad.net/nova/+spec/utilization-aware-scheduling
1+ month ago.
The first patch is to add a column to save metrics collected by plugins -
https://review.openstack.org/#/c/35759/.
Is there anyone who is interested in that, would it be possible to get some
reviews for that?
[Gary Kotton] I have
passion:)
[Gary Kotton] Cool. Nice to hear.
--
Shane
-Original Message-
From: Gary Kotton [mailto:gkot...@vmware.com]
Sent: Tuesday, August 27, 2013 3:36 PM
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] [Nova] Requesting feedback on review
35759
- which will implicitly enforce a LOC limit but will let patches like
s/assertEquals/assertEqual/ land, which make sense to me.
This should be evaluated in a case-by-case basis.
[Gary Kotton] Agreed. The reviewers should use their discretion when it comes
to the patch size. The flip side
Hi,
This bug is no longer relevant following the fix for
https://code.launchpad.net/bugs/1215352
(https://review.openstack.org/#/c/43268/).
If passwords are to be used for VNC then these should be generated per
instance. This is not something that is specific to VMware and should maybe be
?
If this is a viable approach, I prefer that we attempt to fix the code in tree.
We attempted to get this code in grizzly and had to revert. I'd hate to go
through the cycle again in I if we can fix it now.
[Gary Kotton] I too prefer this approach.
Vish
2013/8/20 Andrew Laski
andrew.la
[cid:image001.jpg@01CE98FD.2A08F120]
inline: image001.jpg___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Hi,
At the moment we have some blocking bugs with the VMware drivers. Would it be
possible to get some reviews for this:
https://review.openstack.org/#/c/39046/ - tempest tests fail with
rescue/unrescue
https://review.openstack.org/#/c/40105/ - attempting to attach/detach a volume
causes an
driver.
[Gary Kotton] This works for me :)
By the way, can nova core or those who are interested in the bp review our
patch sets at
https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/ubs,n,z?
Thanks.
--
Shane
From: Gary Kotton [mailto:gkot...@vmware.com
+1
-Original Message-
From: Sean Dague [mailto:s...@dague.net]
Sent: Thursday, August 01, 2013 1:51 PM
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] [Nova] Proposal to add Nikola Đipanov to nova-core
On 07/31/2013 03:10 PM, Russell Bryant wrote:
Greetings,
I
on other components) but we should look into
scheduler/ceilometers integration for the future (good session topic for the
Icehouse summit).
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
From: Gary Kotton [mailto:gkot...@vmware.com]
Sent: Tuesday, July 30, 2013 3:42 AM
Hi,
I have a question regarding the RPC versioning and backports. More specifically
a patch was added upstream to fix a bug. This required a new RPC version. If
this patch is to be backported to stable/grizzly, what is required treatment
for the RPC versions. Please see
:17 AM, Gary Kotton
gkot...@vmware.commailto:gkot...@vmware.com wrote:
Hi,
I have a question regarding the RPC versioning and backports. More specifically
a patch was added upstream to fix a bug. This required a new RPC version. If
this patch is to be backported to stable/grizzly, what
Hi,
From reviewing the patches for
https://blueprints.launchpad.net/nova/+spec/utilization-aware-scheduling it
seems like there is a lot of code here that may already existing the
Ceilometer. I wonder if this is something that should be implemented in Nova
or if Nova should receive the
Hi,
Would it be possible that we also discuss the instance groups. This was blocked
because the new API did not support objects. The relevant patches for objects
have been added and it is pending review.
Thanks
Gary
-Original Message-
From: Dugger, Donald D
Hi,
There was also talk of having neutron as the default network setting. Do we
still want to move towards this in devstack? I know that Yong is working on a
solution for having the multi node support for the floating IP's.
At the last summit I was going to look into the option of doing a live
Hi,
Over the last few days I have been battling with this script (I am only human).
Recently there was a nice change that removed the number of entries which helps
with the merges. One thing that I have encountered over the last 2 days is that
the pep8 passes with my environment and fails with
Hi,
Since the addition of https://review.openstack.org/#/c/32966/ there have been a
number of failures with unit tests (sadly this is not consistent) but examples
are:
https://review.openstack.org/#/c/35189/
https://review.openstack.org/#/c/33504/
I have managed to reproduce this on a local
A big +2 for both!
They have been doing a great job as of late.
-Original Message-
From: Mark McClain [mailto:mark.mccl...@dreamhost.com]
Sent: Tuesday, July 23, 2013 10:15 PM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [Neutron] Proposal to add new neutron-core
Hi,
I have run into a problem with pep8 for
https://review.openstack.org/#/c/37539/. The issue is that have run the script
in the subject and the pep8 fails.
Any ideas?
Thanks
Gary
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
Hi,
There are a number of ways of going about this:
1. You can run devstack (www.devstack.orghttp://www.devstack.org). This
is from the sources.
2. You can do installation via the manuals
3. RDO also has a very nice and easy way of going about things - it make
use of
Hi,
Can someone please clarify what the DB status is in OSLO. Last week the
code was imported to Neutron (aka Quantum). The review process is Nova
has been -1'ed due to issues with the common code
(https://review.openstack.org/#/c/34671/).
What is the current status? Does the code need to be
On 07/01/2013 06:13 PM, Mark McLoughlin wrote:
(Oslo is not an acronym)
ok.
can someone please clarify what the database status is in Oslo?
On Mon, 2013-07-01 at 18:07 +0300, Gary Kotton wrote:
Hi,
Can someone please clarify what the DB status is in OSLO. Last wee
Hi,
This bug is no longer valid due to fix of bug
https://bugs.launchpad.net/neutron/+bug/1191768
(https://review.openstack.org/#/c/33254/).
Thanks
Gary
** Changed in: neutron
Status: In Progress = Invalid
--
You received this bug notification because you are a member of Yahoo!
On 06/19/2013 07:13 PM, Mark McClain wrote:
All-
The OpenStack Networking team is happy to announce that the Quantum project
will be changing its name to Neutron. You'll soon see Neutron in lots of places
as we work to implement the name change within OpenStack.
I hope that Nickelodeon does
On 06/19/2013 09:39 PM, Abhishek Chanda wrote:
Hi all,
Is there an official guide to migrate nova network plugins to quantum
plugins (or rather, neutron plugins)?
Hi,
Sadly we have not made much progress with this. There are a number of
issues to consider when moving from traditional nova
Hi,
This is by design. If you wish to create a port without and IP address then you
should not create a subnet and just allocate a port on the network.
Thanks
Gary
** Changed in: quantum
Status: In Progress = Invalid
--
You received this bug notification because you are a member of
On 05/21/2013 07:04 AM, Qinglong.Meng wrote:
Hi all,
Here is output of cmd 'ovs-vsctl show'. But how to explain it. Can
anybody help me?
Please look at the following diagram to see how the VM connects to the
OVS when using the Hybrid driver:
On 05/21/2013 06:34 AM, Qinglong.Meng wrote:
Hi friends,
the nova-compute log say 'brctl addif qbr876fed87-40
qvb876fed87-40' error, when I reboot the server by 'init 6', and the
nova-compute service
Can you please clarify which server you reboot?
Please loot at
Hi,
Just a few things about the stable branch:
1. Open reviews:
https://review.openstack.org/#/q/status:open+project:openstack/quantum+branch:stable/grizzly,n,z
2. Pending backport (not 100% sure we should hence the questions):
- https://bugs.launchpad.net/quantum/+bug/1174111 - this
On 05/13/2013 03:03 PM, Salvatore Orlando wrote:
I don't think we need to backport bug 1174111.
Otherwise we will have to backport all the similar bug reports - two
are up for review, others coming up.
Thanks! I'll remove the backport tag.
Salvatore
On 13 May 2013 13:22, Gary Kotton
Thanks for the clarifications. This is not a bug!
** Changed in: quantum
Status: In Progress = Invalid
** Tags removed: grizzly-backport-potential
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to quantum.
Hi,
By default the scheduler allocates one agent. You are then able to add
additional ones.
Please see the example below:
openstack@openstack:~/devstack$ quantum dhcp-agent-list-hosting-net private
** Changed in: quantum
Status: Opinion = Confirmed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to quantum.
https://bugs.launchpad.net/bugs/1174132
Title:
Only one instance of a DHCP agent is run per network
Status in
On 04/27/2013 12:44 PM, Michaël Van de Borne wrote:
Anybody has an idea about why the nova metadata server rejects the VM
requests?
Hi,
Just a few questions:-
1. Can you please check /etc/quantum/metadata_agent.ini to see that you
have the correct quantum keystone credential configured?
2.
Luckily I bumped into Akihiro. I'll be coming with maybe one other person.
On 04/15/2013 02:41 AM, Dan Wendlandt wrote:
otherwise you'll have to play catch-up :P
On Sun, Apr 14, 2013 at 4:10 PM, Sumit Naiksatam
sumitnaiksa...@gmail.com mailto:sumitnaiksa...@gmail.com wrote:
Yeah, my
On 04/11/2013 01:59 PM, Arindam Choudhury wrote:
Hi,
I am trying to install openstack folsom on fedora 18. while installing
quantum I am having this problem:
# cat dhcp-agent.log
2013-04-11 12:53:31 INFO [quantum.common.config] Logging enabled!
2013-04-11 12:55:39ERROR
On 04/09/2013 11:01 AM, Mike Kolesnik wrote:
- Original Message -
On 04/09/2013 10:16 AM, Mike Kolesnik wrote:
- Original Message -
On 04/08/2013 07:13 PM, Dan Kenigsberg wrote:
On Fri, Mar 22, 2013 at 08:34:14AM +0200, Gary Kotton wrote:
On 03/21/2013 11:06 PM, Dan
On 04/08/2013 07:13 PM, Dan Kenigsberg wrote:
On Fri, Mar 22, 2013 at 08:34:14AM +0200, Gary Kotton wrote:
On 03/21/2013 11:06 PM, Dan Kenigsberg wrote:
On Thu, Mar 21, 2013 at 03:53:38PM +0200, Gary Kotton wrote:
On 03/21/2013 03:12 PM, Dan Kenigsberg wrote:
On Mon, Mar 18, 2013 at 04:23
this option will include in Grizzly. We get
now (since the switch to Quantum) network I/O bottlenecks without
using all NIC's of our nodes.
So I'm looking forward to Grizzly
Greetings
Heiko
Am 12.12.2012 17:11, schrieb Gary Kotton:
On 12/12/2012 05:58 PM, Xin Zhao wrote:
Hello,
If I
Hi,
I have back ported all of the patches that were marked as backport
potential.
Please take a look at
https://review.openstack.org/#/q/status:open+project:openstack/quantum+branch:stable/grizzly,n,z
Thanks
Gary
--
Mailing list: https://launchpad.net/~quantum-core
Post to :
On 04/03/2013 01:35 PM, Nux! wrote:
Hello,
I'm currently testing Grizzly on EL6 from
http://repos.fedorapeople.org/repos/openstack/openstack-grizzly/epel-6/
I'm using packstack to deploy it on 3 physical machines, one of them
acts also as controller, the other 2 are just nova-compute
On 04/03/2013 02:36 PM, Nux! wrote:
On 03.04.2013 12:27, Gary Kotton wrote:
On 04/03/2013 01:35 PM, Nux! wrote:
Hello,
I'm currently testing Grizzly on EL6 from
http://repos.fedorapeople.org/repos/openstack/openstack-grizzly/epel-6/
I'm using packstack to deploy it on 3 physical machines
Hi,
I have seen something like this with stable folsom. We have yet to be
able to reproduce it. In our setup we saw that there were timeouts with
the quantum service. In addition to this we had 2 compute nodes. My gut
feeling was that one of the nodes has a failer and the scheduler selects
the posting to
milestone-proposed makes sense.
dan
On Sun, Mar 24, 2013 at 12:58 AM, Gary Kotton gkot...@redhat.com
mailto:gkot...@redhat.com wrote:
Hi,
Last week I found a bug in OSLO with the lockutils. The patch was
approved upstream and has been backported to stable/grizzly
Hi,
I will be on vacation till the 3rd of April. Not sure if I will have
email or internet access.
I have backported a bug that Alex found - 1159616
(https://review.openstack.org/#/c/25268/). I will not be able to attend
the meeting this evening.
Thanks
Gary
--
Mailing list:
Hi,
Last week I found a bug in OSLO with the lockutils. The patch was
approved upstream and has been backported to stable/grizzly for OSLO
(https://review.openstack.org/#/c/25233/ - this is currently in review).
I have done the backport to milestone proposed version -
On 03/21/2013 03:12 PM, Dan Kenigsberg wrote:
On Mon, Mar 18, 2013 at 04:23:32AM -0400, Mike Kolesnik wrote:
- Original Message -
On Mon, Mar 18, 2013 at 03:20:45AM -0400, Mike Kolesnik wrote:
Hi all,
The feature page for integrating OpenStack Quantum into oVirt is
available on the
On 03/20/2013 06:16 PM, Sylvain Bauza wrote:
Hi,
As per https://bugs.launchpad.net/quantum/+bug/1155050 and also other
litterature, I do see doc alerts saying that Quantum L3 and DHCP
agents must be on different hosts.
Let me be honest, I successfully installed and configured both on the
On 03/18/2013 05:14 AM, tommy(??) wrote:
more:
means we can not command : quantum component-list
This command was replaced by quantum agent-list. Please note that you
need to an admin user to be able to invoke this.
Thanks
Gary
Thanks,
Tommy Bao
2013/3/18 tommy(??) bychya...@gmail.com
Hi,
I'd like to run for the Technical Committee in the up and coming elections.
I am a Principle Software Engineer at Red Hat. I have been actively
developing OpenStack since the Essex release. I am currently a Quantum
core developer. In addition to this I am also core on the Stable
On 03/12/2013 12:13 AM, Greg Chavez wrote:
So I'm setting up Folsom on Ubuntu 12.10, using the Github Folsom
Install Guide:
https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst
After following the steps to instantiate the
? Thanks!
Yes, that is correct. Even the first time that it starts it is out of
sync :)
On Tue, Mar 12, 2013 at 3:18 AM, Gary Kotton gkot...@redhat.com
mailto:gkot...@redhat.com wrote:
On 03/12/2013 12:13 AM, Greg Chavez wrote:
So I'm setting up Folsom on Ubuntu 12.10, using
On 03/11/2013 09:58 AM, Dan Wendlandt wrote:
Hi team,
Great work reviewing bug fixes in the past few days. Thanks to that
effort, we're in good shape to get RC1 out on schedule on Tuesday.
A few reviews remain:
- killing metadata proxy properly: https://review.openstack.org/#/c/21489/
- nvp
Hi,
I have done the following:
1. Updated https://review.openstack.org/#/c/21424/ (please let me know
if I have missed anything)
2. With the reviewing of the changes for the Quotas we found -
https://review.openstack.org/#/c/23686/ (this needs to be backported -
so does the fix above)
3. Yong
On 03/04/2013 05:45 PM, Guilherme Russi wrote:
Found the problem, when I did the step: ovs-vsctl add-port br-ex eth2,
it stopped my lan communication.
The l3 agent makes changes to the routing table. This may cause a
conflict with the default gateway. I would suggest having a static route
On 03/04/2013 09:00 PM, Kyle Mestery (kmestery) wrote:
On Mar 3, 2013, at 2:58 AM, Gary Kottongkot...@redhat.com wrote:
On 03/03/2013 04:24 AM, Kyle Mestery (kmestery) wrote:
On Mar 2, 2013, at 4:48 AM, Gary Kottongkot...@redhat.com wrote:
On 03/02/2013 12:27 AM, Kyle Mestery (kmestery)
On 03/03/2013 04:24 AM, Kyle Mestery (kmestery) wrote:
On Mar 2, 2013, at 4:48 AM, Gary Kottongkot...@redhat.com wrote:
On 03/02/2013 12:27 AM, Kyle Mestery (kmestery) wrote:
Looking at the documentation, it appears not. But there is some Puppet code in
there around configuring Quantum. Is
On 03/02/2013 12:27 AM, Kyle Mestery (kmestery) wrote:
Looking at the documentation, it appears not. But there is some Puppet code in
there around configuring Quantum. Is it a work in progress?
At the moment packstack does not support Quantum. This is WIP. Soon I'll
post a link to a wiki
Hi,
There seems to be a change in the unit tests that cases a ton of print
outs. Anyone else encountered this?
Thanks
Gary
--
Mailing list: https://launchpad.net/~quantum-core
Post to : quantum-core@lists.launchpad.net
Unsubscribe : https://launchpad.net/~quantum-core
More help :
making any other changes.
Also, IIRC, the cmd2 author is west of me, so is unlikely to have seen
the email I sent this morning, yet.
Doug
On Wednesday, February 27, 2013, Gary Kotton wrote:
Hi,
Following Doug Hellmans mail:
I have updated cliff with a patch to peg the version
The latest common code has been added.
** Changed in: quantum
Status: In Progress = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to quantum.
https://bugs.launchpad.net/bugs/1131162
Title:
fails to get version
Are we able to go ahead and approve these patches. I was not sure if we
wanted these for G release?
Thanks
Gary
On 02/22/2013 02:38 AM, Dan Wendlandt wrote:
Hi folks. Please see email below from Monty.
First off, great work on writing so many tests :)
Second, please start enforcing Mony's
for Quantum.
Dan
On Fri, Feb 22, 2013 at 5:49 AM, Gary Kotton gkot...@redhat.com
mailto:gkot...@redhat.com wrote:
Are we able to go ahead and approve these patches. I was not
sure if we
wanted these for G release?
Thanks
Gary
Hi,
If possible can people please take a look at
https://review.openstack.org/#/c/22546/ - the problem here is with the
iptable rules (if the default rules are drop).
Thanks and have a good weekend
Gary
On 02/21/2013 08:15 PM, Sumit Naiksatam wrote:
Thanks Dan. Are bugs related to code
I have rebased and run the tests. They pass.
Something is certainly fishy.
On 02/20/2013 03:43 AM, Salvatore Orlando wrote:
Which ones?
I saw same failures related to a new dependency, netifaces, in the Ryu plugin.
Recreating the tox environment might solve your problem, hopefully.
(eg: tox -r
Hi,
It looks like things have improved. I think that the real test is when
the guys in the US start working.
Thanks
Gary
On 02/20/2013 01:14 AM, Dan Wendlandt wrote:
Note: if the gate conditions do not improve, we may consider letting
things merge past the deadline, but presumably that would
Hi Greg,
Sorry to hear you woes. I agree with you that setting things up is
challeniging and sometimes problematic. I would suggest a number of things:
1. Give devstack a bash. This is very helpful and useful to try and
understand how everything fits and works together. www.devstack.org
2. A
On 02/19/2013 01:57 PM, Sylvain Bauza wrote:
Hi,
I progressed in investigating the bug. I forgot to mention I was
following Provided Router/single tenancy setup.
So, at reboot, my tap/qg/qr network interfaces were down :
7: qg-c39e5df4-7f: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN
On 02/19/2013 03:47 PM, Sylvain Bauza wrote:
Le 19/02/2013 13:31, Gary Kotton a écrit :
On 02/19/2013 01:57 PM, Sylvain Bauza wrote:
Hi,
I progressed in investigating the bug. I forgot to mention I was
following Provided Router/single tenancy setup.
So, at reboot, my tap/qg/qr network
801 - 900 of 1125 matches
Mail list logo
