Thanks for the update. Will there be an option of connecting remotely? Google
chat? Webex?
From: "Armando M." mailto:arma...@gmail.com>>
Reply-To: OpenStack List
mailto:openstack-dev@lists.openstack.org>>
Date: Saturday, February 20, 2016 at 2:32 AM
To: OpenStack List
mailto:openstack-dev@lists
I think that IBM has a very interesting policy in that two IBM cores should not
approve a patch posted by one of their colleagues (that is what Chris RIP used
to tell me). It would be nice if the community would follow this policy.
Thanks
Gary
From: "Armando M." mailto:arma...@gmail.com>>
Reply-
Hi,
I suggest that the guys who maintain this driver provide you the reasons why
they maintain the Nova driver like this It is problematic and at times the
driver can break as it is not in tree.
Thanks
Gary
From: Monotosh Das mailto:monotosh@ericsson.com>>
Reply-To: OpenStack List
mailto:op
+1
Gracias Dims!
On 3/3/16, 2:26 PM, "Sean Dague" wrote:
>On 03/03/2016 06:32 AM, Davanum Srinivas wrote:
>> Team,
>>
>> It has been great working with you all as PTL for Oslo. Looks like the
>> nominations open up next week for elections and am hoping more than
>> one of you will step up f
Hi,
The resent addition of https://review.openstack.org/#/c/269887/ has broken our
unit tests with random tests with listing of security groups – for example –
test_list_security_groups
Has anyone else also hit this issue?
Thanks
Gary
__
The tests that are failing are those where the security groups are being
searched by the ‘description’. When running these tests individually they pass
but when running all of the tests together they fail.
From: Gary Kotton mailto:gkot...@vmware.com>>
Reply-To: OpenStack List
mailto:ope
ering seems to be messed up on the association
proxy that references the other table.
On Sun, Mar 6, 2016 at 2:07 AM, Gary Kotton
mailto:gkot...@vmware.com>> wrote:
The tests that are failing are those where the security groups are being
searched by the ‘description’. When running these tes
Hi,
The commit
https://review.openstack.org/#q,4c2c983618ddb7a528c9005b0d7aaf5322bd198d,n,z
causes the CI to fail. This is due to the fact that the port creation does not
return the created_at and updated_at keys. The tempest test that the keys are
the same. Please see [I]
I posted patch https:
/
Thanks
Gary
From: Gary Kotton mailto:gkot...@vmware.com>>
Reply-To: OpenStack List
mailto:openstack-dev@lists.openstack.org>>
Date: Sunday, March 6, 2016 at 4:04 PM
To: OpenStack List
mailto:openstack-dev@lists.openstack.org>>
Subject: [openstack-dev] [Neutron][tempest] Timestamp
calls.
Hi,
Gal Sagie pointed me to patch in ML2 and OVN that address this by re-reading
the networks and ports to ensure that the information is read.
For those interested and whom it affects please see:
ML2 - https://review.openstack.org/#/c/276219/
OVN - https://review.openstack.org/#/c/277844
lacing it somewhere in the core before returning the API response may be
possible, but the difficult part is getting the DB object to pass to the hooks
without an additional read since plugins only return dicts.
On Mar 7, 2016 01:06, "Gary Kotton"
mailto:gkot...@vmware.com>> wrote
ict extend function, it
should be the same.
As far as order goes, python doesn't guarantee order on dictionary keys. Or did
I misinterpret what you meant by order?
On Mar 7, 2016 01:41, "Gary Kotton"
mailto:gkot...@vmware.com>> wrote:
Another issue that we have with the rea
Hi,
It would be nice if we could get a little more reviews in the neutron-lib.
I think that we should maybe strive to cut a new version prior to the
release.
Thanks
Gary
On 3/14/16, 6:17 PM, "Venkata Anil" wrote:
>Hi All
>
> I have added a new flag in neutron-lib
>https://review.openstack.org/#
Hi,
The review https://review.openstack.org/#/c/255285/ breaks our CI. Since this
has landed we are getting failed tests with the:
"Details: {u'message': u"Quota exceeded for resources: ['port'].", u'type':
u'OverQuota', u'detail': u’’}"
When I revert the patch and run our CI without it the tests
c&m=0W0JwODAYJdy_tB4tQT0nd1zhv2OJ35zOHr5UM4KUSs&s=yxUgpc6J-xovf-ZwLu-wFeU6dGj4Ne6P-vTR32UCjrI&e=>
On Thu, Mar 17, 2016 at 1:30 AM, Gary Kotton
mailto:gkot...@vmware.com>> wrote:
Hi,
The review https://review.openstack.org/#/c/255285/ breaks our CI. Since this
has landed we are
+1
From: Dave Walker mailto:em...@daviey.com>>
Reply-To: OpenStack List
mailto:openstack-dev@lists.openstack.org>>
Date: Sunday, March 20, 2016 at 12:27 PM
To: OpenStack List
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [stable] Proposing Tony Breeds for
stable-maint-
Hi,
Thanks for posting this. This is very interesting. I think that there are a
number of different things to take into account here:
1. There is a service chaining project in Neutron
https://wiki.openstack.org/wiki/Neutron/ServiceInsertionAndChaining. Is the API
there sufficient or differen
Hi,
In the M cycle BGP support was added in tree. I have seen specs in the L2 GW
project for this support too. Are we planning to consolidate the efforts? Will
the BGP code be moved from the Neutron git to the L2-GW project? Will a new
project be created?
Sorry, a little in the dark here and it
1560003
[2]: https://review.openstack.org/#/c/268726
Thanks,
Hirofumi
On 2016/03/28 15:36, Gary Kotton wrote:
Hi,
In the M cycle BGP support was added in tree. I have seen specs in the L2 GW
project for this support too. Are we planning to consolidate the efforts? Will
the BGP code be moved from the Neutro
Hi,
Thanks for the clarification. I still feel like there may be some overlap here.
Thanks
Gary
From: Irena Berezovsky mailto:irenab@gmail.com>>
Date: Monday, March 28, 2016 at 11:16 AM
To: OpenStack List
mailto:openstack-dev@lists.openstack.org>>,
Gary Kotton mailto:gkot..
Hi,
At the mid cycle meet up it was discussed that we need to prioritize the BP's
that require review. This will at least get us a chance of getting something
into Nova this cycle.
The following BP's are ready for review:
1. Ephemeral disk support -
https://blueprints.launchpad.net/nova/+spe
On 2/11/15, 3:26 PM, "Nikola Đipanov" wrote:
>On 02/11/2015 02:13 PM, Sean Dague wrote:
>>
>> If core team members start dropping off external IRC where they are
>> communicating across corporate boundaries, then the local tribal effects
>> start taking over. You get people start talking about
Hi,
I do not think that that is a healthy solution. That effectively would
render a cluster down if the compute node goes down. That would be a real
disaster. The ugly work around is setting the host names to be the same
value.
This is something that we should discuss at the next summit and I would
I posted a fix that does not break things and supports HA.
https://review.openstack.org/154029
On 2/11/15, 5:55 PM, "Matthew Booth" wrote:
>On 11/02/15 15:49, Gary Kotton wrote:
>> Hi,
>> I do not think that that is a healthy solution. That effectively would
>&g
On 2/11/15, 6:35 PM, "Sylvain Bauza" wrote:
>
>Le 11/02/2015 17:04, Gary Kotton a écrit :
>> I posted a fix that does not break things and supports HA.
>> https://review.openstack.org/154029
>
>
>Just let's be clear, HA is *not* supported by Nova
Hi,
The support for the feature has been in flight for over a year now. There is
one outstanding patch - the resize of ephemeral disks [I].
The patch is based on a series of patches that address critical issues when
resizing (which were exposed when we were testing this feature).
I really hope th
Hi,
I think that the filters should be applied to the list of hosts that are in
'force_hosts'. I am not sure if this is what you are suggesting. If this is not
then case then it sounds like a bug.
Thanks
Gary
From: Rui Chen mailto:chenrui.m...@gmail.com>>
Reply-To: OpenStack List
mailto:opensta
I understand the fact that an opertaor can and should be able to place the VM
where she/he wants. The VM should just adhere to the scheduling constraints :)
(which are defined in the filters)
:)
From: Rui Chen mailto:chenrui.m...@gmail.com>>
Reply-To: OpenStack List
mailto:openstack-dev@lists.o
On 2/12/15, 1:33 PM, "Chmouel Boudjnah" wrote:
>Jaume Devesa writes:
>
>> Following the conversation...
>>
>> We have seen that glusterfs[1] and ec2api[2] use different approach
>> when it comes to repository managing: whereas glusterfs is a single
>> 'devstack' directory repository, ec2api is
Hi,
Over the last few IRC meetings we have discussed the following:
1. Providing a platform for people other than those working on the Nova
driver to take part. There are efforts with the Glance, Cinder, Ceilometer and
Neutron projects. Hopefully people working on those can also take part and
Hi,
This support was added to the libvirt driver in J. The support is isolated to
the Vmware driver and enables admins to get a better understanding of what is
happening with the running instances. Any chance of getting a sponsor for this?
https://review.openstack.org/#/c/141028/
This also enabl
Hi,
Yes, I think that they go out in batches. It would be best to check with
Stefano if you have any issues.
Thanks
Gary
On 2/15/15, 4:11 AM, "Nick Chase" wrote:
>Does anybody know if a) ATC emails have started to go out yet, and b)
>when proposal voting will start?
>
>Thanks
>
>--- Nick
>
Hi,
MS is back up and running.
Thanks
Gary
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/li
Hi,
With the current master in devstack I am unable to create a neutron network. It
looks like there is an issue with keystone. Anyone else hit this?
Thanks
Gary
__
OpenStack Development Mailing List (not for usage questions)
On 2/16/15, 12:48 PM, "Kashyap Chamarthy" wrote:
>On Mon, Feb 16, 2015 at 09:54:30AM +, Gary Kotton wrote:
>> Hi, With the current master in devstack I am unable to create a
>> neutron network.
>>
>> It looks like there is an issue with keystone.
Retitled
From: Gary Kotton mailto:gkot...@vmware.com>>
Reply-To: OpenStack List
mailto:openstack-dev@lists.openstack.org>>
Date: Saturday, February 14, 2015 at 8:01 PM
To: OpenStack List
mailto:openstack-dev@lists.openstack.org>>
Subject: [openstack-dev] [nova] FFE
Hi,
The same issue is the for the backe end drivers. I think that they always
need to be aligned with the master branch. When we cut stable all of the
aaS and drivers also need to be cut.
This was one of the pain points that we brought up with the split and the
consensus was: we¹ll deal with it whe
Hi,
Please see
http://docs.openstack.org/openstack-ops/content/logging_monitoring.html
If you have installed from packages this may be in
/var/log/nova/nova-compute.log
Thanks
Gary
From: Vedsar Kushwaha
mailto:vedsarkushw...@gmail.com>>
Reply-To: OpenStack List
mailto:openstack-dev@lists.opens
On 2/23/15, 2:05 PM, "Matthew Booth" wrote:
>On 20/02/15 11:48, Matthew Booth wrote:
>> Gary Kotton came across a doozy of a bug recently:
>>
>> https://bugs.launchpad.net/nova/+bug/1419785
>>
>> In short, when you start a Nova compute, it will qu
Hi,
Not sure if everyone is aware of this. There is a ether pad where the priority
of the project appears:
https://etherpad.openstack.org/p/kilo-nova-priorities-tracking. This has the
major bullets for the K cycle.
So in short - if you reviews are not on the page they may not get review cycles
u start to add to that list. Feel free to reach out to the
guys who regularly contribute to this list if you feel that you want to dive in
A luta continua
Gary
From: Gary Kotton mailto:gkot...@vmware.com>>
Reply-To: OpenStack List
mailto:openstack-dev@lists.openstack.org>>
Date: Monday
Hi,
There is an issue with the statistics reported when a nova compute driver has
shared storage attached. That is, there may be more than one compute node
reporting on the shared storage. A patch has been posted -
https://review.openstack.org/#/c/155184. The direction here was to add a extra
p
Hi,
There are pros and cons for what you have mentioned. My concern, and I
mentioned them with the neutron driver decomposition, is that we are are
loosing the community inputs and contributions. Yes, one can certainly move
faster and freer (which is a huge pain point in the community). How are
Hi,
I am just relaying pain-points that we encountered in neutron. As I have
said below it makes the development process a lot quicker for people
working on external drivers. I personally believe that it fragments the
community and feel that the external drivers loose the community
contributions an
+100Š.000
Very long overdue!
On 3/4/15, 10:23 PM, "Maru Newby" wrote:
>+1 from me, Ihar has been doing great work and it will be great to have
>him finally able to merge!
>
>> On Mar 4, 2015, at 11:42 AM, Kyle Mestery wrote:
>>
>> I'd like to propose that we add Ihar Hrachyshka to the
On 3/8/15, 2:34 PM, "Flavio Percoco" wrote:
>On 07/03/15 23:16 +, Nikhil Komawar wrote:
>>Thank you for the response, Hemanth! Those are some excellent questions.
>>
>>
>>In order to avoid diverging the conversation, I would like to give my
>>general
>>sense of direction. Please do keep in
Hi,
As mentioned a few weeks ago we would like to have alternate meeting times for
the Vmware driver(s) meeting. So for all interested lets meet tomorrow at 10:00
UTC on #openstack-meeting-4.
Thanks
Gary
__
OpenStack Develo
Hi,
Not 100% sure that I understand. This is for the BP¹s and specs that were
approved for Kilo. Bug fixes if I understand are going to be reviewed
until the release of Kilo.
Is launchpad not a sufficient source for highlighting bugs?
Thanks
Gary
On 3/11/15, 2:13 PM, "John Garbutt" wrote:
>Hi,
>
Hi,
It appears that https://review.openstack.org/#/c/158420/ update the base
attributes for the networks. Is there any reason why this was not added as a
separate extension like all others.
I do not think that this is the correct way to go and we should do this as all
other extensions have been
Hi,
This patch has the same addition too -
https://review.openstack.org/#/c/154921/. We should also revert that one.
Thanks
Gary
From: Gary Kotton mailto:gkot...@vmware.com>>
Reply-To: OpenStack List
mailto:openstack-dev@lists.openstack.org>>
Date: Thursday, March 19, 2015 a
- mtu and
vlan_transparency
Reverts for them are:
https://review.openstack.org/165801 (mtu) and
https://review.openstack.org/165776 (vlan transparency).
In my opinion these should be added as separate extensions.
Thanks
Gary
From: Gary Kotton mailto:gkot...@vmware.com>>
Reply-To: OpenStac
unless
I’m mis-reading those reviews. Additional of new output fields to a json
object, or adding optional inputs, is not generally considered to be backwards
incompatible behavior in an API. Does OpenStack have a stricter standard on
that?
Thanks,
doug
On Mar 19, 2015, at 6:37 AM, Gary Kott
Hi,
Just the fact that we did this does not make it right. But I guess that we
are starting to bend the rules. I think that we really need to be far more
diligent about this kind of stuff. Having said that we decided the
following on IRC:
1. Mtu will be left in the core (all plugins should be aware
1ZFbdlXoi2cfdhw&e=>
(admittedly first link I found, but there's no shortage of them)
On 19 March 2015 at 05:32, Gary Kotton
mailto:gkot...@vmware.com>> wrote:
Hi,
This patch has the same addition too -
https://review.openstack.org/#/c/154921/. We should also revert that one.
Than
nks,n,z
[5] https://review.openstack.org/#/c/136760/
On 19 March 2015 at 12:01, Gary Kotton
mailto:gkot...@vmware.com>> wrote:
With regards to the MTU can you please point me to where we validate that the
MTU defined by the tenant is actually <= the supported MTU on the netw
Hi,
One of the issues that we had in Nova was that when we moved to oslo
libraries configuration options support by the libraries were no longer
present in the generated configuration file. Is this something that is
already supported or planned (sorry for being a little ignorant here).
In neutron t
Hi,
Any idea when this will be up and running again:
gkotton@ubuntu:~/nova$ git review
Problem running 'git remote update gerrit'
Fetching gerrit
ssh: connect to host review.openstack.org port 29418: Network is unreachable
fatal: Could not read from remote repository.
Please make sure you h
utron-specs/specs/kilo/mtu-selection-and-advertisement.html
> [2]
> http://specs.openstack.org/openstack/neutron-specs/specs/kilo/nfv-vlan-trunks.html
> [3]
> https://review.openstack.org/#/q/project:openstack/neutron+branch:master+topic:bp/mtu-selection-and-advertisement,n,z
> [4]
&
Please see
http://lists.openstack.org/pipermail/openstack-infra/2015-February/002425.h
tml
That should explain.
On 3/23/15, 8:53 AM, "trinath.soman...@freescale.com"
wrote:
>Hi-
>
>The Issue is resolved. Its an update to the NEW IP address of Gerrit.
>
>
>
>--
>Trinath Somanchi - B39208
>trinat
From: Jordan Pittier
mailto:jordan.pitt...@scality.com>>
Reply-To: OpenStack List
mailto:openstack-dev@lists.openstack.org>>
Date: Wednesday, March 25, 2015 at 1:47 PM
To: OpenStack List
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [nova] CI report formatting (citrix
On 3/25/15, 10:27 PM, "Matt Riedemann" wrote:
>
>
>On 3/25/2015 3:01 PM, Jennifer Mulsow wrote:
>> Would anyone be willing to review
>> https://review.openstack.org/#/c/164308/ (Expand valid server group name
>> character set)? It has a few +1s, but there hasn't been any activity on
>> it in a
On 3/25/15, 3:21 PM, "Sean Dague" wrote:
>On 03/25/2015 09:03 AM, Gary Kotton wrote:
>>
>> From: Jordan Pittier > <mailto:jordan.pitt...@scality.com>>
>> Reply-To: OpenStack List > <mailto:openstack-dev@lists.openstack.org>>
>> Dat
Hi,
I have added a few comments to the review and have a fixed a few issues
that I have encountered along the way. I guess we can discuss on gerrit.
Thanks
Gary
On 3/27/15, 12:54 AM, "Russell Bryant" wrote:
>Gary and Kyle, I saw in my IRC backlog that you guys were briefly
>talking about testing
Hi,
I am also fine with the shim extension.
Thanks
Gary
On 3/31/15, 1:44 AM, "Carl Baldwin" wrote:
>Thanks for your support, Akihiro. We will get this up for review very
>soon.
>
>Carl
>
>On Mon, Mar 30, 2015 at 2:59 PM, Akihiro Motoki wrote:
>> Hi Carl,
>>
>> I am now reading the detail from
On 4/3/15, 8:24 PM, "Dugger, Donald D" wrote:
>The goal is not `splitting for the sake of splitting'. The goal is to
>have a separate scheduler that is ultimately usable by other projects
>inside OpenStack. Currently Cinder has its own filter based scheduler
>(duplicating scheduling code in 2
Hi,
Can a core please take a look at https://review.openstack.org/#/c/171037. The
CI is broken due to commit e7ae5bb7fbdd5b79bde8937958dd0a645554a5f0.
Thanks
Gary
__
OpenStack Development Mailing List (not for usage questions)
dated the bug so it's high priority and tagged with
>> kilo-rc-potential, and added your note from below as a comment on the
>>bug.
>>
>> It looks like it might be worth a backport so it gets into RC2? Can
>>anyone
>> take that bit on please?
>>
>>
Hi,
I am very saddened to read this. Not only will Chris be missed on a
professional level but on a personal level. He was a real mensh
(http://www.thefreedictionary.com/mensh). He was always helpful and
supportive. Wishing his family a long life.
Thanks
Gary
On 4/13/15, 4:33 AM, "Michael Still"
+1
From: Alex Xu mailto:sou...@gmail.com>>
Reply-To: OpenStack List
mailto:openstack-dev@lists.openstack.org>>
Date: Friday, May 1, 2015 at 6:30 AM
To: OpenStack List
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [nova] Proposal to add Melanie Witt to nova-core
I'm not
Hi,
We are pretty blocked at the moment with our gating on stable/ocata. This is
due to the fact that there is no networking-sfc version tagged for ocata.
Is there any ETA for this?
Thanks
Gary
__
OpenStack Development Mailin
the
latest.
[0] http://lists.openstack.org/pipermail/openstack-dev/2017-February/112580.html
On Sun, Mar 5, 2017 at 3:01 PM, Gary Kotton
mailto:gkot...@vmware.com>> wrote:
Hi,
We are pretty blocked at the moment with our gating on stable/ocata. This is
due to the fact that there is no netwo
-dev] [neutron][sfc] stable/ocata version
This is talked in [0]. sfc team said
> we will pull a stable/ocata branch around end of Feb or early March the
latest.
[0] http://lists.openstack.org/pipermail/openstack-dev/2017-February/112580.html
On Sun, Mar 5, 2017 at 3:01 PM, Gary Kot
Hi,
When we recheck https://review.openstack.org/#/c/388157/ or any patch that
depends on this one, they just hang. Any idea why?
Thanks
Gary
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: opensta
schedule, even though it
> may
> cause some cherry-pick, but it is safer and how OpenStack project live.
>
>
> On Sun, Mar 5, 2017 at 3:44 PM, Gary Kotton
> mailto:gkot...@vmware.com>> wrote:
>>
>> Please note that things are going to start to get messy now – th
Thanks!
439565 was abandoned. Sorry for the trouble
On 3/6/17, 5:32 PM, "Paul Belanger" wrote:
On Mon, Mar 06, 2017 at 03:44:59PM +0000, Gary Kotton wrote:
> Hi,
> When we recheck https://review.openstack.org/#/c/388157/ or any patch
that depends on this one, the
Hi,
I was asked to create a release tag for stable/ocata. This fails with:
gkotton@ubuntu:~/networking-l2gw$ git push gerrit tag 10.0.0
Enter passphrase for key '/home/gkotton/.ssh/id_rsa':
Counting objects: 1, done.
Writing objects: 100% (1/1), 533 bytes | 0 bytes/s, done.
Total 1 (delta 0), reus
Hi,
Can the tap guys please look at https://review.openstack.org/447277. All
projects using the tap project are currently stuck
Thanks
Gary
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack
Hi,
I am still unable to do this – this is after
https://review.openstack.org/#/c/447279/ landed.
Any ideas?
Thanks
Gary
On 3/14/17, 3:04 PM, "Jeremy Stanley" wrote:
On 2017-03-14 05:39:35 + (+0000), Gary Kotton wrote:
> I was asked to create a release tag for stabl
2gw.git'
Any idea here?
This is blocking people who want to package…
Thanks
Gary
On 3/21/17, 7:18 PM, "Gary Kotton" wrote:
Hi,
I am still unable to do this – this is after
https://review.openstack.org/#/c/447279/ landed.
Any ideas?
Thanks
Gary
On
Thu, Mar 23, 2017 at 5:18 PM, Gary Kotton
mailto:gkot...@vmware.com>> wrote:
Hi,
I have tried updating my gpg key and still nothing works:
gkotton@ubuntu:~/networking-l2gw$ git push gerrit tag 10.0.0
Enter passphrase for key '/home/gkotton/.ssh/id_rsa':
Counting objects: 1, done.
Hi,
Please see below for a current update on the status of the project.
1. stable/ocata:
a. a tag 10.0.0 has been created
b. code has been updated to pass unit tests (there was a breakage as it
was pulling master neutron)
2. master:
a. Due to the tag above being
+1
On 3/31/17, 12:55 AM, "Ihar Hrachyshka" wrote:
On Thu, Mar 30, 2017 at 2:11 PM, Kevin Benton wrote:
> Hi,
>
> I would like to add Miguel Lavalle (mlavalle) to the Neutron drivers team
> [1].
It's not completely clear if you seek support here, but in case you do,
Hi,
The change https://review.openstack.org/#/c/402750/ has broken the vmware-nsx
plugin. I am not sure if this has had effect on any other decomposed plugins.
One of the issues that we have is when we create a PortDNS object under a
transaction we get an exception: DBReferenceError: (sqlite3.Int
To: OpenStack List
Subject: Re: [openstack-dev] [neutron] Engine facade
Do you have a link to a traceback?
On Apr 2, 2017 09:25, "Gary Kotton"
mailto:gkot...@vmware.com>> wrote:
Hi,
The change https://review.openstack.org/#/c/402750/ has broken the vmware-nsx
plugin. I am not
Hi,
This is done by the agents. For example please see
https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py#L1639
Thanks
Gary
From: Vikash Kumar
Reply-To: OpenStack List
Date: Monday, April 3, 2017 at 9:46 AM
To: OpenStack List
Sub
https://review.openstack.org/#/c/452539/ is about
switching for new facade, does the master branch fails the same?
On Mon, Apr 3, 2017 at 8:35 AM Gary Kotton
mailto:gkot...@vmware.com>> wrote:
Yes, sorry my bad for not adding it -
http://logs.openstack.org/39/452539/2/check/gate-vmware-nsx-python27-ubuntu-xen
of
rolling with the punches). I am just concerned if we are the only folks that
have affected by this.
Thanks
Gary
From: Gary Kotton
Reply-To: OpenStack List
Date: Monday, April 3, 2017 at 3:14 PM
To: OpenStack List
Subject: Re: [openstack-dev] [neutron] Engine facade
Hi,
We needed to make all of
solve them.
And probably you need to revisit your unit tests.
Please, send me email directly with links for traces, does this happen on
master branch, does it happen on one of your changes - it is hard to guess.
On Tue, Apr 4, 2017 at 11:16 AM Gary Kotton
mailto:gkot...@vmware.com>> wrote
Hi,
I would like us to think of considering enabling an API that would allow
‘deny’, for example an admin could overwrite a tenant’s security groups. For
example, and admin may not want a specific source range to access the tenants
VM’s. The guys working on FWaaS say that this may happen in V2,
Hi,
Please note that the L2 GW code is currently broken due to the commit
e6333593ae6005c4b0d73d9dfda5eb47f40dd8da
If someone has the cycles can they please take a look.
Thanks
gary
__
OpenStack Development Mailing List (not f
Hi,
The bot that runs for the requirements update sometimes does not update the
vmware-nsx project. I am not sure if this happens with other projects. Does
anyone know how we can trouble shoot this?
Thanks
Gary
__
OpenStack D
Thanks!
It seems like https://review.openstack.org/440882 is the problem. Now that we
have resolved the issues we should return this.
I have proposed patches to return these.
Thanks
Gary
On 6/4/17, 4:15 PM, "Jeremy Stanley" wrote:
On 2017-06-04 11:35:16 + (+0000), Gary Ko
Hi,
It seems that the pep8 is broken due to
https://github.com/openstack/requirements/commit/99fae827973465147359cc7032c83003802612a7
Should we revert this?
Thanks
Gary
__
OpenStack Development Mailing List (not for usage ques
this was meant to fix it. https://review.openstack.org/#/c/471512/
On Wed, Jun 7, 2017 at 4:51 AM, Gary Kotton
mailto:gkot...@vmware.com>> wrote:
Hi,
It seems that the pep8 is broken due to
https://github.com/openstack/requirements/commit/99fae827973465147359cc7032c83003802612a7
[1;31mE[0m: 56,16: [1;31mUndefined variable 'depr_func'[0m
([1;31mundefined-variable[0m)
2017-06-07
09:57:03.399683<http://logs.openstack.org/66/471666/2/check/gate-vmware-nsx-pep8-ubuntu-xenial/b1bc4df/console.html#_2017-06-07_09_57_03_399683>
| [1;31mE[0m: 56,26: [1;31mUndefine
Sorry my bad.
The problem is that our requirements use six and in 1.10 files are missing
From: Gary Kotton
Reply-To: OpenStack List
Date: Wednesday, June 7, 2017 at 1:00 PM
To: OpenStack List
Subject: Re: [openstack-dev] [neutron] pep8 broken
Seems like the whole world is broken now:
2017
rllib> package.
Thanks and sorry for the spam
Gary
From: Gary Kotton
Date: Wednesday, June 7, 2017 at 2:03 PM
To: OpenStack List
Subject: Re: [openstack-dev] [neutron] pep8 broken
Sorry my bad.
The problem is that our requirements use six and in 1.10 files are missing
From: Gary Kotton
Hi,
Please see bug https://bugs.launchpad.net/neutron/+bug/1696403. Seems like six
1.10.0 has broken us.
I have posted a patch in the requirements project. Not 100% sure that this is
the right way to go. At least that will enable us to address this in neutron.
Thanks
Gary
ion bump should be announced because it
> potentially breaks individual project gate.
>
> Is it better to revert pylint version bump in global-requirements, or
> just to ignore some pylint rules temporarily in neutron?
>
> Akihiro
>
>
> 2017-06-07
Hi,
The commit https://review.openstack.org/284738 has broken decomposed plugins
(those that extend security groups and rules). The reason for this is that
there is a extend callback that we use which expects to get a database object
and the aforementioned patch passes a new neutron object.
I ha
401 - 500 of 629 matches
Mail list logo
