Hi Ian,
On 20/07/15 18:00, Ian Wells wrote:
On 19 July 2015 at 03:46, Neil Jerram <mailto:neil.jer...@metaswitch.com>> wrote:
The change at [1] creates and describes a new 'routed' value for
provider:network_type. It means that a compute host handles data
to/fr
On 20/07/15 18:36, Carl Baldwin wrote:
> I'm looking for feedback from anyone interest but, in particular, I'd
> like feedback from the following people for varying perspectives:
> Mark McClain (proposed alternate), John Belamaric (IPAM), Ryan Tidwell
> (BGP), Neil Jerra
On 20/07/15 23:27, Ian Wells wrote:
There are two routed network models:
- I give my VM an address that bears no relation to its location and ensure the
routed fabric routes packets there - this is very much the routing protocol
method for doing things where I have injected a route into the netw
[Sorry, mistaken send as mixed format, so quoting may not have come out
right. Hope this time is better...]
On 20/07/15 23:27, Ian Wells wrote:
> There are two routed network models:
>
> - I give my VM an address that bears no relation to its location and
> ensure the routed fabric routes packets
maric (IPAM), Ryan Tidwell
>> (BGP), Neil Jerram (L3 networks), Aaron Rosen (help understand
>> multi-provider networks) and you if you're reading this list of names
>> and thinking "he forgot me!"
>>
>> We have been struggling to develop a way to model a
On 21/07/15 15:45, Salvatore Orlando wrote:
> On 21 July 2015 at 14:21, Neil Jerram <mailto:neil.jer...@metaswitch.com>> wrote:
>
>
> You've probably seen Robert Kukura's comment on the related bug at
> https://bugs.launchpad.net/neutron/+bug/1458890
On 20/07/15 18:50, Ian Wells wrote:
> On 20 July 2015 at 10:21, Neil Jerram <mailto:neil.jer...@metaswitch.com>> wrote:
>
> Hi Ian,
>
> On 20/07/15 18:00, Ian Wells wrote:
>
> On 19 July 2015 at 03:46, Neil Jerram
> &
I'd like to announce networking-calico, a new project within the Neutron
stadium to provide OpenStack integration pieces for Project Calico
[1][2]. In a sentence, Calico is a backend that uses routing and
iptables to provide IP-level connectivity between VMs, instead of - as
most Neutron backends
On 17/08/15 18:47, Neil Jerram wrote:
> I'd like to announce networking-calico [...]
> Then the plan for networking-calico is that it will contain docs, an ML2
> mechanism driver, a DHCP interface driver, and a Devstack plugin for
> Calico. These aren't yet at [10], but I w
No, still not, I'm afraid.
Original Message
From: Sean M. Collins
Sent: Tuesday, 18 August 2015 19:15
To: OpenStack Development Mailing List (not for usage questions)
Reply To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron] New networking-cal
in
the Liberty timescale, ask neutron-drivers to approve that, and update the
patches to reference that bug instead.
Does that sound right?
Regards,
Neil
Original Message
From: Neil Jerram
Sent: Monday, 17 August 2015 18:47
To: OpenStack Development Mailing List (not for usage quest
Hi Andreas,
Thanks for looking at this. I'm happy to say that Jeremy already
identified the problem, in a thread on openstack-infra [1], and I've
submitted a fix for it [2].
Regards,
Neil
[1]
http://lists.openstack.org/pipermail/openstack-infra/2015-August/003087.html
[2] https://review.ope
FYI, I've raised the new RFE bug that I suggested below:
https://bugs.launchpad.net/neutron/+bug/1486649
Neil
On 18/08/15 23:22, Neil Jerram wrote:
> Although the DHCP-related patches below are I think very close to mergeable,
> Brian Haley on IRC queried what, process-wise
Can anyone recommend how best to make deb and rpm packages for a
networking-* project?
(Specifically, I mean for networking-calico, but I imagine, if there's a
best current practice, that it would apply to all such projects.)
I'm aware that there were recently some discussions on increased
unific
. It's
getting late in the Liberty cycle, but if you can get Brian, Cedric and Carl to
review this and ensure they are onboard, this is the best way to move forward.
Ensuring the L3 team is ok with the direction would make me comfortable here.
Thanks!
Kyle
On Wed, Aug 19, 2015 at
On 25/08/15 01:02, Skyler Berg wrote:
> Any feedback would be appreciated. We plan to open source this project
> soon and welcome contributions from anyone interested. For the moment,
> any bugs, concerns, or ideas can be sent to openstack-...@tintri.com.
>
> [1] ci-watch.tintri.com
>
>
Wow, super
On 28/08/15 13:39, Kevin Benton wrote:
> For the py34 failures, they seem to have started around the same time
> as a change was merged that adjusted the way they were ran so I
> proposed a revert for that patch
> here: https://review.openstack.org/218244
>
>
Which leads on to https://review.opens
Hi Kevin,
I currently have an example of this kind of thing that I'm working on, and I'd
appreciate hearing your view on what is the best solution.
My requirement was to change some of the command line options with which the
DHCP agent invokes Dnsmasq. My first implementation of this was in co
of the
OVS agent or ML2 plugin and claiming that it is still using the OVS agent or
ML2 plugin.
On Mon, Aug 31, 2015 at 4:36 AM, Neil Jerram
mailto:neil.jer...@metaswitch.com>> wrote:
Hi Kevin,
I currently have an example of this kind of thing that I'm working on, and I'd
appreciate
Was the --is-public option to 'glance image-create ...' just removed? I've
been running Devstack successfully during the last week, but now see this:
glance: error: unrecognized arguments: --is-public=true
from running this:
wget http://download.cirros-cloud.net/0.3.2/cirros-0.3.2-x86_64-disk.
>
> You can track updates using the release on pypi and related
> documentation on [1]; announcements are on the openstack-announce ML.
>
> [1] http://docs.openstack.org/developer/python-glanceclient/
>
> On 9/2/15 10:42 AM, Neil Jerram wrote:
>> Was the --is-public option
On 15/09/15 10:59, Ihar Hrachyshka wrote:
>> On 11 Sep 2015, at 23:12, Kyle Mestery wrote:
>>
>> I'm writing to let everyone know that I do not plan to run for Neutron PTL
>> for a fourth cycle. Being a PTL is a rewarding but difficult job, as Morgan
>> recently put it in his non-candidacy email
On 16/09/15 13:13, Bruno Cornec wrote:
> Hello,
>
> Sorry was meant as a private answer to Thierry.
> Anyway for those curious, here is the translation now it's public (my
> bad).
For what it's worth, I enjoyed seeing some French on the list... :-)
Neil
_
Thanks to the interesting 'default network model' thread, I now know
that Neutron allows booting a VM on an external network. :-) I didn't
realize that before!
So, I'm now wondering what connectivity semantics are expected (or even
specified!) for such VMs, and whether they're the same as - or ve
ce allow
interconnection between the external network and private Neutron networks.
> We want to get rid of as much special casing as possible for the
> external network.
>
I don't understand here. What 'special casing' do you mean?
Regards,
Neil
> On Sep 17,
ges to it would have to make
> sense in the context of all networks. That's why I want to make sure
> that whatever we come up with makes sense in all contexts and isn't
> just a bolt on corner case.
>
> On Sep 17, 2015 8:21 AM, "Neil Jerram" <mailto:neil.jer..
But on the Internet, no one knows that I'm really a crocodile, and
writing from Midway...
Neil
On 17/09/15 18:29, Kevin Benton wrote:
>
> Maybe it would be a good idea to switch to 23:59 AOE deadlines like
> many paper submissions use for academic conferences. That way there is
> never a nee
external network has an internal
> Neutron router interface that leads to another external network via a
> Neutron router.
Agreed.
Many thanks for your input in this thread!
Regards,
Neil
>
>
> On Thu, Sep 17, 2015 at 10:17 AM, Neil Jerram
> mailto:neil.jer...@
To most people who write on this list about requirements, constraints
and gate deadlocks, not just Robert...
FWIW - this email is tagged [all], and asks for help, but I don't
understand it. Even though I've been fairly heavily engaged with
OpenStack for more than a cycle now.
Obviously we can't
On 21/09/15 20:31, Victoria Mart?nez de la Cruz wrote:
Hi all,
I'm glad to announce that Mahati Chamarthy (mahatic) will join the current
coordination efforts for the Outreachy internships. Thanks Mahati!
Also, I wanted to share this Etherpad [0]with you the current list of
applicants and mento
Yes, a 'git review' just took around 20s for me.
On 24/09/15 13:21, Miguel Angel Ajo wrote:
>I am experiencing it, yes :/
>>Gary Kotton wrote:
>>Hi,
>>Anyone else experiencing bad performance with gerri at the moment? Access
>>files in a review takes ages. So now the review cycle will be months i
On 30/09/15 19:58, Kyle Mestery wrote:
> Folks:
>
> In trying to release some networking sub-projects recently, I ran into
> an issue [1] where I couldn't release some projects due to them not
> being registered on pypi. I have a patch out [2] which adds pypi
> publishing jobs, but before that can
On 02/10/15 11:42, Neil Jerram wrote:
> Thanks Kyle! I'm looking at this now for networking-calico.
Done, please see https://pypi.python.org/pypi/networking-calico.
When you release, how will the version number be decided? And should I
make a change to put that version into the source s
On 02/10/15 16:03, Jeremy Stanley wrote:
> On 2015-10-02 11:33:05 + (+), Neil Jerram wrote:
> [...]
>> For the PyPI registration I put 0.1.0, but that doesn't mean that I
>> expect that to be the version number when networking-calico is actually
>> releas
On 01/10/15 14:47, Ihar Hrachyshka wrote:
> Hi all,
>
> I talked recently with several contributors about what each of us plans for
> the next cycle, and found it’s quite useful to share thoughts with others,
> because you have immediate yay/nay feedback, and maybe find companions for
> next adv
Just some initial thoughts here, as I'm not yet clear on many of your
details.
On 06/10/15 16:55, Peter V. Saveliev wrote:
> …
>
>
> The problem.
>
>
>
> There are use cases, when it us needed to attach vnic to some specific
> network interface instead of br-int.
>
> For example, wor
On 07/10/15 12:12, Sean Dague wrote:
> We've had devstack plugins for about 10 months. They provide a very "pro
> user" experience by letting you enable arbitrary plugins with:
>
> enable_plugin $name git://git.openstack.org/openstack/$project [$branch]
>
> They have reasonable documentation here
>
On 07/10/15 12:26, Sean Dague wrote:
> On 10/07/2015 07:17 AM, Neil Jerram wrote:
>> On 07/10/15 12:12, Sean Dague wrote:
>>> We've had devstack plugins for about 10 months. They provide a very "pro
>>> user" experience by letting you enable arbitrary plu
FWIW - and somewhat ironically given what you said just before - I couldn't
parse your last sentence below... You might like to follow up with a corrected
version.
(On the broad point, BTW, I really agree with you. So much OpenStack discussion
is rendered difficult to get into by use of wrong o
Please note that you jumped there from developer-focus to user-focus. Of
course some users are also developers, and vice versa, but I would expect doc
focussed on development to be quite different from that focussed on use.
For development doc, I think the Neutron devref is a great example, so
On 13/10/15 08:45, chandraprakash mishra wrote:
> Hi Folks,
>
> I have just started looking OpenStack ,As of now i would like to start
> participation for neutron component . So where can i start participate
> for neutron component .Is there any documentation for this components
> so that I can sta
On 02/10/15 12:33, Neil Jerram wrote:
> On 02/10/15 11:42, Neil Jerram wrote:
>> Thanks Kyle! I'm looking at this now for networking-calico.
> Done, please see https://pypi.python.org/pypi/networking-calico.
>
> When you release, how will the version number be decided
If you go to
http://docs.openstack.org/developer/openstack-projects.html, then go
from there into any project page, the 'Project Source' URL in the
sidebar is wrong.
(Well, I say 'any', but I've only actually tried for ironic,
networking-midonet and networking-calico. Those all show the following
I'm happy to announce the first release of networking-calico. As it
says at http://docs.openstack.org/developer/networking-calico/:
networking-calico is the Neutron ‘stadium’ sub-project that provides
‘Calico’ connectivity and security in an OpenStack/Neutron cloud.
Calico [1] uses IP rout
On 16/10/15 13:53, Christian Berendt wrote:
> On 10/16/2015 01:46 PM, Neil Jerram wrote:
>> I'd be happy to submit a fix for this, but I haven't yet found which
>> project generates this URL. Can someone advise?
> The developer documentations use the oslosphinx
>
On 16/10/15 15:51, Jeremy Stanley wrote:
> On 2015-10-16 10:20:17 -0400 (-0400), Doug Hellmann wrote:
>> Excerpts from Neil Jerram's message of 2015-10-16 13:10:41 +:
> [...]
>>> Well, it would appear that 'git config --local --get remote.origin.url'
>>> on the docs build machine gives a URL wh
On 19/10/15 14:57, Adam Young wrote:
> While I tend to play up bug 968696 for dramatic effect, the reality is
> we have a logical contradiction on what we mean by 'admin' when talking
> about RBAC.
>
> In early iterations of OpenStack, roles were global. This is reflected
> in many of the Poli
On 12/10/15 16:32, Sean M. Collins wrote:
> On Thu, Oct 08, 2015 at 01:47:31PM EDT, Mike Spreitzer wrote:
>> ..
In the section
http://docs.openstack.org/developer/devstack/guides/
>>> neutron.html#using-neutron-with-a-single-interface
there is a helpful display of localrc contents.
On 14/05/15 20:23, Matt Riedemann wrote:
Regarding RHEL, I think this is a safe bet because in Kilo nova dropped
python 2.6 support and RHEL > 6 doesn't have py26 so you'd be in trouble
running kilo+ nova on RHEL 6.x anyway.
I'm personally happy to hear this, because it is a pain supporting o
Hi Thomas,
On 16/05/15 06:52, Thomas Goirand wrote:
On 05/15/2015 10:37 AM, neil.jer...@metaswitch.com wrote:
Out of interest, have you done this by re-releasing the Ubuntu
packaging? Or have you taken an independent approach?
Regards,
Neil
It's been since Folsom that I've released pac
On 29/05/15 14:41, Thierry Carrez wrote:
Hi everyone,
TL;DR:
- We propose to stop tagging coordinated point releases (like 2015.1.1)
- We continue maintaining stable branches as a trusted source of stable
updates for all projects though
[...]
I initially misunderstood your email as saying th
Hi Gal,
Thanks for starting this thread, and I'm sorry not to have met you
during the summit.
Vancouver was my first summit, and I very much enjoyed it. My
reflection is that I came to the summit with two overall expectations,
of which one proved correct and one false.
The correct expecta
Hi all,
Per yesterday's IRC meeting [1], and discussion in Vancouver, Nova work
is being somewhat driven by the etherpad at [2]. But this etherpad
doesn't have a section for libvirt / vif driver changes. The log at [1]
briefly touched on this, but moved on after noting that Dan PB had
disba
On 01/06/15 14:23, Daniel P. Berrange wrote:
On Mon, Jun 01, 2015 at 09:44:24AM +0100, John Garbutt wrote:
On 29 May 2015 at 18:32, Neil Jerram wrote:
Hi all,
Per yesterday's IRC meeting [1], and discussion in Vancouver, Nova work is
being somewhat driven by the etherpad at [2]. But
On 01/06/15 17:45, Neil Jerram wrote:
Many thanks, John & Dan. I'll start by drafting a summary of the work
that I'm aware of in this area, at
https://etherpad.openstack.org/p/liberty-nova-libvirt-vif-work.
OK, my first draft of this is now there at [1]. Please could folk wit
Where are the source RPMs that correspond to the binary RPMs at
https://repos.fedorapeople.org/repos/openstack/openstack-kilo/el7/ ?
I guess that
https://repos.fedorapeople.org/repos/openstack/openstack-kilo/testing/source/
might be quite close - but the 'testing' in this URL suggests that
ht
Many thanks, Haïkel, that looks like the information that my team needed.
Neil
On 03/06/15 11:18, Haïkel wrote:
Hi Neil,
We're already having this discussion on the downstream list.
RDO is currently moving packages publication for RHEL/CentOS over CentOS
mirrors. That's just a matter
Hi John,
On 04/06/15 12:21, John Garbutt wrote:
Hi,
We had a great discussion at the summit around priorities:
https://etherpad.openstack.org/p/YVR-nova-liberty-priorities
I have made a stab at writing that up here, please to review if you
are interested:
https://review.openstack.org/#/c/18727
On 05/06/15 12:32, Sean Dague wrote:
https://dague.net/2015/06/05/the-nova-api-in-kilo-and-beyond-2/
This is really informative and useful, thanks.
A few comments / questions, with bits of your text in quotes:
"Even figuring out what a cloud could do was pretty terrible. You could
approximat
On 04/06/15 22:54, Thomas Goirand wrote:
The init scripts used to be hard to maintain because they were many, but
since Debian & Ubuntu are using automatic generation out of a tiny
template (with sysv-rc, systemd and upstart all supported), this is a
problem solved.
Ooh, that sounds like somet
My team has seen a problem that could be related: in a churn test where
VMs are created and terminated at a constant rate - but so that the
number of active VMs should remain roughly constant - the size of the
host and addn_hosts files keeps increasing.
In other words, it appears that the conf
reading issues between the agent and the Neutron
server. You might like to review that thread and see if it describes
any problems analogous to your DHCP one.
Regards,
Neil
On 08/06/15 17:53, Neil Jerram wrote:
My team has seen a problem that could be related: in a churn test w
On 08/06/15 18:22, Jay Pipes wrote:
On 06/05/2015 10:56 AM, Neil Jerram wrote:
I guess that's why the GNU autoconf/configure system has always advised
testing for particular wanted features, instead of looking at versions
and then relying on carnal knowledge to know what those versions
fwm/5.1.2/ubuntu/pool/main/
[3] https://ci.fuel-infra.org/
[4] https://bugs.launchpad.net/mos/+filebug
On Mon, Jun 8, 2015 at 10:15 AM Neil Jerram
mailto:neil.jer...@metaswitch.com>> wrote:
Two further thoughts on this:
1. Another DHCP agent problem that m
On 04/06/15 13:05, Neil Jerram wrote:
Hi John,
On 04/06/15 12:21, John Garbutt wrote:
Hi,
We had a great discussion at the summit around priorities:
https://etherpad.openstack.org/p/YVR-nova-liberty-priorities
I have made a stab at writing that up here, please to review if you
are interested
On 09/06/15 15:28, Daniel P. Berrange wrote:
On Tue, Jun 09, 2015 at 03:07:51PM +0100, Neil Jerram wrote:
Secondly there is the VIF plug script idea, and it's here that the elephant
may be. I'm afraid that some of the interested people (including me) missed
it, but I heard that the
On 10/06/15 15:47, Andreas Scheuring wrote:
Hi Daniel, Neil and others,
I was thinking about introducing libvirt-network as a new vif type to
nova. It can be used when Neutron prepares a libvirt network for
attaching guests.
Would you see any general concerns with such an approach? Anything tha
On 08/06/15 22:02, Kevin Benton wrote:
This depends on what initialize is supposed to be doing. If it's just a
one-time sync with a back-end, then I think calling it once in each
child process might not be what we want.
I left a comment on Terry's patch. I think we should just use the
callback
/32 dev tap12345-CD
where tap12345-CD is the TAP interface towards the VM. Does that answer
your question, and would that be possible with a libvirt network?
Thanks,
Neil
--
Ian.
On 10 June 2015 at 12:16, Neil Jerram mailto:neil.jer...@metaswitch.com>> wrote:
On 10/06
On 11/06/15 10:47, changzhi wrote:
Hi, all.
I create a vm and it's neutron port's mac address is
"fa:16:3e:3f:02:ff". I see "fa:16:3e:3f:02:ff" inside vm when I run
"ifconfig eth0". Why does vm's tap device's mac address is
"fe:16:3e:3f:02:ff"? Why different between neutron port's mac address
and
Hi Carl et al.,
I see from [1] that L3 routed network segments are on the Neutron L3
subteam's roadmap for Liberty, and I wanted to say that I'm very
interested in this work, and - if there isn't someone else already -
happy to take the lead on making it happen.
I'm aware already of several
Hi Sam,
On 17/06/15 01:31, Sam Morrison wrote:
We at NeCTAR are starting the transition to neutron from nova-net and neutron
almost does what we want.
We have 10 “public" networks and 10 “service" networks and depending on which
compute node you land on you get attached to one of them.
In ne
[Sorry - unintentionally dropped -operators below; adding it back in
this copy.]
On 17/06/15 11:35, Neil Jerram wrote:
Hi Sam,
On 17/06/15 01:31, Sam Morrison wrote:
We at NeCTAR are starting the transition to neutron from nova-net and
neutron almost does what we want.
We have 10 “public
Hi Kris,
Apologies in advance for questions that are probably really dumb - but
there are several points here that I don't understand.
On 17/06/15 03:44, Kris G. Lindgren wrote:
We are doing pretty much the same thing - but in a slightly different way.
We extended the nova scheduler to help
Couple more dumb comments here - sorry that I'm processing this thread
backwards!
On 16/06/15 15:20, Jay Pipes wrote:
Adding -dev because of the reference to the Neutron "Get me a network
spec". Also adding [nova] and [neutron] subject markers.
Comments inline, Kris.
On 05/22/2015 09:28 PM, K
Hi Carl,
I know you said at the end of your message below to ping you on IRC, but
there are details here that I'm not sure about, and some suggestions
that I'd like to make, and I think it will be clearer to discuss those
in context. I hope that's OK.
On 11/06/15 17:26, Carl Baldwin wrote:
On 17/06/15 16:17, Kris G. Lindgren wrote:
See inline.
Kris Lindgren
Senior Linux Systems Engineer
GoDaddy, LLC.
On 6/17/15, 5:12 AM, "Neil Jerram" wrote:
Hi Kris,
Apologies in advance for questions that are probably really dumb -
On 22/06/15 11:28, neil.jer...@metaswitch.com wrote:
It seems like we're possibly stuck now on the VIF plugin script spec [1];
there being core comments in apparently conflicting directions. I wonder if
it's still feasible for a version of this to land during Liberty?
[1] https://review.ope
On 22/06/15 15:11, Daniel P. Berrange wrote:
On Mon, Jun 22, 2015 at 11:28:35AM +0100, neil.jer...@metaswitch.com wrote:
It seems like we're possibly stuck now on the VIF plugin script spec [1];
there being core comments in apparently conflicting directions. I wonder if
it's still feasible fo
Thanks Kris and Sam for your replies!
On 18/06/15 01:20, Kris G. Lindgren wrote:
On 6/17/15, 10:59 AM, "Neil Jerram" wrote:
On 17/06/15 16:17, Kris G. Lindgren wrote:
See inline.
Kris Lindgren
Senior Linux Systems Engineer
GoDaddy, LL
Hi Andreas,
On 26/06/15 14:04, Andreas Scheuring wrote:
Hi together,
for a new ml2 plugin I would like to pass over some data from neutron to
nova on port creation and update (exploiting port binding extension
[1]). For my prototype I thought of using one of the following response
dictionaries t
Hi there,
For my team's networking backend, we want to catch security group
updates in our ML2 mechanism driver code.
Currently we're doing this by monkey patching the AgentNotifierApi:
# This section monkeypatches the
AgentNotifierApi.security_groups_rule_updated
# method to ensure
Cool, thank you!
On 29/06/15 14:08, Gal Sagie wrote:
Yes, look at this patch: https://review.openstack.org/#/c/174588/
On Mon, Jun 29, 2015 at 3:42 PM, Neil Jerram mailto:neil.jer...@metaswitch.com>> wrote:
Hi there,
For my team's networking backend, we want to catch sec
Apologies if this is an FAQ - I tried a quick search, but that didn't
find anything that looked both up to date and authoritative.
I keep going back to Gerrit jobs that I've reviewed or commented on, and
finding that there have been other comments since mine, but that Gerrit
didn't email me ab
On 30/06/15 14:33, Julien Danjou wrote:
On Tue, Jun 30 2015, Neil Jerram wrote:
Apologies if this is an FAQ - I tried a quick search, but that didn't find
anything that looked both up to date and authoritative.
I keep going back to Gerrit jobs that I've reviewed or commented on, a
Thanks Sean, + Andreas for your similar reply...
Yes, I guess that could be it. My company's setup is Exchange, and the
IT folk here assure me that any spam emails would be in my Junk folder -
and the missing Gerrit emails aren't there. But, maybe that's not the
100% full story, for some rea
On 30/06/15 16:14, Jeremy Stanley wrote:
On 2015-06-30 14:08:45 +0100 (+0100), Neil Jerram wrote:
[...]
I keep going back to Gerrit jobs that I've reviewed or commented
on, and finding that there have been other comments since mine,
but that Gerrit didn't email me about.
[...]
Look
Well, the bug discussion seems to point specifically to this dnsmasq fix:
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=9380ba70d67db6b69f817d8e318de5ba1e990b12
Neil
On 01/07/15 07:34, Daniel Comnea wrote:
Hi,
sorry for no feedback, i've been doing more and more test and
ll be too crazy?
Cheers,
Dani
On Wed, Jul 1, 2015 at 9:23 AM, Neil Jerram mailto:neil.jer...@metaswitch.com>> wrote:
Well, the bug discussion seems to point specifically to this dnsmasq
fix:
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git
Hi Jeremy,
On 30/06/15 17:45, Neil Jerram wrote:
On 30/06/15 16:14, Jeremy Stanley wrote:
On 2015-06-30 14:08:45 +0100 (+0100), Neil Jerram wrote:
[...]
I keep going back to Gerrit jobs that I've reviewed or commented
on, and finding that there have been other comments since mine,
but
I understand the semantic versioning algorithm for calculating a new
version. But what do I run, in a git repository, to do that calculation
for me, and output:
- the new semantic version that would be used if I asked for a formal
release to PyPI
- the corresponding Debian version
- the corr
On 26/02/16 11:16, Neil Jerram wrote:
> I understand the semantic versioning algorithm for calculating a new
> version. But what do I run, in a git repository, to do that calculation
> for me, and output:
>
> - the new semantic version that would be used if I asked for a formal
&g
(not for usage questions)
Reply To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] How do I calculate the semantic version prior to a
release?
On 27 February 2016 at 00:13, Neil Jerram wrote:
> I understand the semantic versioning algorithm for calc
I've just tried to start using gertty, installed in a virtualenv using 'pip
install gertty' - which means I have version 1.3.1.
When I try to look at any Diff, though, I get a traceback ending with:
git.exc.GitCommandError: 'git diff --color=never -U 1 [...]' returned with
exit code 128
std
d git diff -U problem
On 2016-02-28 19:33:29 + (+0000), Neil Jerram wrote:
> I've just tried to start using gertty, installed in a virtualenv
> using 'pip install gertty' - which means I have version 1.3.1.
[...]
> Any recommendations for getting past this? I think i
FYI, all working fine after 'pip install GitPython=1.0.1' (in the virtualenv).
Original Message
From: Neil Jerram
Sent: Sunday, 28 February 2016 20:42
To: Jeremy Stanley; OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] gertty and git diff
I'm happy to announce the release of networking-calico 1.1.3.
networking-calico is a Neutron driver that connects instances using IP
routing instead of layer 2 bridging and tunneling.
networking-calico's server-side code works with Liberty and previous
OpenStack releases back to Icehouse, and t
On 07/03/16 09:42, Gk Gk wrote:
> Hi All,
>
> I am confused about tenant vlan networks. Is there a such a thing as
> 'Tenant vlan networks' ? I am aware of provider vlan networks ? How
> can a non admin tenant user create a vlan network ?
A non-admin tenant can create a network, but cannot spe
?
On Mon, Mar 7, 2016 at 4:06 PM, Neil Jerram
mailto:neil.jer...@metaswitch.com>> wrote:
On 07/03/16 09:42, Gk Gk wrote:
> Hi All,
>
> I am confused about tenant vlan networks. Is there a such a thing as
> 'Tenant vlan networks' ? I am aware of provider vlan networ
On 07/03/16 11:24, Neil Jerram wrote:
> That’s not at all what I said. Please reread my message more carefully.
Well, I see that I could have been clearer in my answer...
> *From:*Gk Gk [mailto:ygk@gmail.com]
> *Sent:* 07 March 2016 11:17
> *To:* OpenStack Development Mailing L
101 - 200 of 303 matches
Mail list logo
