Re: [openstack-dev] CI for NUMA, SR-IOV, and other features that can't be tested on current infra.

Hi Steve, Regarding SR-IOV testing, at Mellanox we have CI job running on bare metal node with Mellanox SR-IOV NIC. This job is reporting on neutron patches. Currently API tests are executed. The contact person for SRIOV CI job is listed at driverlog: https://github.com/stackforge/driverlog/blo

Re: [openstack-dev] [Ironic] A mascot for Ironic

How cute. maybe we could call him bear-thoven. Chris On Sun, Nov 16, 2014 at 5:14 AM, Lucas Alvares Gomes wrote: > Hi Ironickers, > > I was thinking this weekend: All the cool projects does have a mascot > so I thought that we could have one for Ironic too. > > The idea about what the mascot

Re: [openstack-dev] Solving the client libs stable support dilemma

On Nov 15, 2014, at 5:50 PM, Jeremy Stanley wrote: > During the Kilo design summit session on Oslo versioning changes, we > mostly resolved to switch to semver without alphas and pin stable > branch libs to less than the next nontrivial version number > (allowing for backports to fix bugs with s

Re: [openstack-dev] [Ironic] A mascot for Ironic

- Original Message - > Hi Ironickers, > > I was thinking this weekend: All the cool projects does have a mascot > so I thought that we could have one for Ironic too. > > The idea about what the mascot would be was easy because the RAX guys > put "bear metal" their presentation[1] and th

Re: [openstack-dev] Solving the client libs stable support dilemma

On 2014-11-16 09:06:02 -0500 (-0500), Doug Hellmann wrote: > So we would pin the client libraries used by the servers and > installed globally, but then install the more recent client > libraries in a virtualenv and test using those versions? That's what I was thinking anyway, yes. > I like that.

Re: [openstack-dev] Solving the client libs stable support dilemma

On Nov 16, 2014, at 9:54 AM, Jeremy Stanley wrote: > On 2014-11-16 09:06:02 -0500 (-0500), Doug Hellmann wrote: >> So we would pin the client libraries used by the servers and >> installed globally, but then install the more recent client >> libraries in a virtualenv and test using those version

Re: [openstack-dev] [Ironic] A mascot for Ironic

It's awesome. How about IRONicBEAR? On 11/16/2014 06:44 PM, Lucas Alvares Gomes wrote: > Hi Ironickers, > > I was thinking this weekend: All the cool projects does have a mascot > so I thought that we could have one for Ironic too. > > The idea about what the mascot would be was easy because the RA

Re: [openstack-dev] [Ironic] A mascot for Ironic

> On Nov 16, 2014, at 8:57 AM, Chris K wrote: > > How cute. > > maybe we could call him bear-thoven. > > Chris > I like Blaze Bearly, lead singer for Ironic Maiden. :) https://en.wikipedia.org/wiki/Blaze_Bayley > > On Sun, Nov 16, 2014 at 5:

Re: [openstack-dev] [stable] New config options, no default change

All, This is a question I have been struggling with for Cinder recently. Where do we draw the line on backports. How do we handle config changes? One thing for Cinder I am also considering, in addition to whether it changes the default functionality, is whether it is specific to the submitt

Re: [openstack-dev] [Horizon] the future of angularjs development in Horizon

On 11/15/2014 06:27 AM, Gabriel Hurley wrote: > So, I propose that a group gets together and defines criteria: > we need to accept that the Horizon team (and those knowledgeable > about web-app development) know best what tools they need, and > they need to produce such a list as a starting point.

Re: [openstack-dev] [Horizon] the future of angularjs development in Horizon

On 11/15/2014 05:34 PM, Martin Geisler wrote: > I'm sorry if I came across as being hostile towards packagers and > distros. I've been running Debian for 15 years and that is because of > the work the Debian developers put into making the system work well > together at a whole. > > When it comes t

Re: [openstack-dev] [Ironic] A mascot for Ironic

On 2014-11-16 13:51:07 -0500 (-0500), David Shrewsbury wrote: > I like Blaze Bearly, lead singer for Ironic Maiden. :) [...] Ironically, it works on too many levels. -- Jeremy Stanley ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org ht

Re: [openstack-dev] CI for NUMA, SR-IOV, and other features that can't be tested on current infra.

I guess we can assist with this one. We have the HW needed and a ci environment. We will be happy to do so. I need some help to understand the needed in order integrate into os ci. Who can assist with that? Itai Sent from my iPhone > On Nov 16, 2014, at 3:31 PM, Irena Berezovsky wrote: > >

Re: [openstack-dev] [all] testtools 1.2.0 release breaks the world

2014-11-15 23:06 GMT+01:00 Robert Collins : > We did find a further issue, which was due to the use of setUpClass in > tempest (a thing that testtools has never supported per se - its > always been a happy accident that it worked). I've hopefully fixed > that in 1.3.0 and we're babysitting tempest

Re: [openstack-dev] [Nova] v2 or v3 for new api

On Thu, Nov 13, 2014 at 12:14 AM, Pasquale Porreca < pasquale.porr...@dektech.com.au> wrote: > Hello > > I am working on an api for a new feature in nova, but I am wondering what > is the correct way to add a new extension: should it be supported by v2, v3 > or both? > > You need now to have at le

Re: [openstack-dev] [api] Cross-Project Liaison for the API Working Group

On Sat, Nov 15, 2014 at 7:26 AM, Everett Toews wrote: > On Nov 14, 2014, at 1:43 PM, Jay Pipes wrote: > > > On 11/14/2014 05:13 PM, Everett Toews wrote: > >> The liaison should be a core reviewer for the project, but does not > >> need to be the PTL. By default, the liaison will be the PTL. > >

Re: [openstack-dev] [Horizon] the future of angularjs development in Horizon

On 17 November 2014 06:42, Thomas Goirand wrote: > > On 11/15/2014 06:27 AM, Gabriel Hurley wrote: > > So, I propose that a group gets together and defines criteria: > > we need to accept that the Horizon team (and those knowledgeable > > about web-app development) know best what tools they need,

Re: [openstack-dev] [all] testtools 1.2.0 release breaks the world

On 17 November 2014 11:29, Alan Pevec wrote: > 2014-11-15 23:06 GMT+01:00 Robert Collins : >> We did find a further issue, which was due to the use of setUpClass in >> tempest (a thing that testtools has never supported per se - its >> always been a happy accident that it worked). I've hopefully f

Re: [openstack-dev] [oslo] oslo.messaging outcome from the summit

I started the following issue on kombu's github page (to see if there is any interest on there side to such an effort): https://github.com/celery/kombu/issues/430 It's about seeing if the kombu folks would be ok with a 'rpc' subfolder in there repository that can start to contain 'rpc' like fu

Re: [openstack-dev] [cinder] Adding support for iSCSI helper

On 01:35 Wed 05 Nov , Anish Bhatt wrote: > This is very helpful, thank you ! Is this planned for kilo ? Yes. -- Mike Perez ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openst

Re: [openstack-dev] [Horizon] the future of angularjs development in Horizon

On 11/15/2014 05:03 AM, Matthias Runge wrote: > On 14/11/14 16:21, Adam Young wrote: > >> Example: I don't need Grunt to run a web server. I need Apache for >> that. Grunt does not need to be in the distro, mod_wsgi does. > > I will need every tool required to run e.g. unit tests or selenium t

Re: [openstack-dev] [Horizon] the future of angularjs development in Horizon

On 17 November 2014 11:11, Thomas Goirand wrote: > On 11/15/2014 05:03 AM, Matthias Runge wrote: > > On 14/11/14 16:21, Adam Young wrote: > > > >> Example: I don't need Grunt to run a web server. I need Apache for > >> that. Grunt does not need to be in the distro, mod_wsgi does. > > > > I wil

Re: [openstack-dev] [infra][devstack] CI failed The plugin token_endpoint could not be found

Hi Gord, Seems this not work for me. I've pip uninstalled all python-*client . # pip list|grep -P 'python-.*client' python-barbicanclient (3.0.1) python-ceilometerclient (1.0.12) python-cinderclient (1.1.1) python-glanceclient (0.14.2) python-heatclient (0.2.12) python-keystoneclient (0.11.2) p

Re: [openstack-dev] [infra][devstack] CI failed The plugin token_endpoint could not be found

Hi Sean, Seems once I unset ' DEVSTACK_PROJECT_FROM_GIT=python-keystoneclient,python-openstackclient', devstack will fail with ' ERROR: openstack The plugin token_endpoint could not be found'. How should I overcome this issue then? Thanks and regards Sam -Original Message- From:

Re: [openstack-dev] [all] testtools 1.2.0 release breaks the world

On 17 November 2014 11:29, Alan Pevec wrote: > 2014-11-15 23:06 GMT+01:00 Robert Collins : >> We did find a further issue, which was due to the use of setUpClass in >> tempest (a thing that testtools has never supported per se - its >> always been a happy accident that it worked). I've hopefully f

[openstack-dev] [cinder] Anyone Using the Open Solaris ZFS Driver?

The Open Solaris ZFS driver [1] is currently missing a lot of the minimum features [2] that the Cinder team requires with all drivers. As a result, it's really broken. I wanted to gauge who is using it, and if anyone was interested in fixing the driver. If there is not any activity with this drive

[openstack-dev] Query regarding vRouters & Openstack

Hi All, Can someone please help in clarifying below doubts regarding vRouter (say vyyata/quagga for example). How we can use openstack framework for communicating to vRouters? To be more precise: * How we can make the communication between neutron and vRouter possible? * How w

Re: [openstack-dev] Query regarding vRouters & Openstack

Here are several hints: 1. Brocade has implemented a service plugin [1] for vRouter using its own vyatta image(seems not free and open sourced), but you can read the plugin source code as reference. 2. Here's a new method [2] for L3 fabric. It's totally open source and can use any routing st

Re: [openstack-dev] [cinder] Anyone Using the Open Solaris ZFS Driver?

We (here at Oracle) have a replacement for this driver which includes local ZFS, iSCSI and FC drivers all with ZFS as the underlying driver. We're in the process of getting CI set up so we can contribute the driver upstream along with our ZFSSA driver (which is already in the tree). If anybody has

Re: [openstack-dev] [all] testtools 1.2.0 release breaks the world

Thanks Robert! Looks like it failed the Travis CI job due to an intermittent connectivity issue and I don't have the rights to kick-off the job again. I would appreciate it if you could kick it off again when you get a chance. Cheers, Nikhil On Sun, Nov 16, 2014 at 6:44 PM, Robert Collins wrote

Re: [openstack-dev] [Horizon] the future of angularjs development in Horizon

On 17/11/14 02:07, Richard Jones wrote: > Except that selenium is non-free: it's in the non-free repository of > Debian, because it contains a pre-built .xpi plugin for firefox, which > itself contains pre-built .so and .dll files. > > > Hasn't this issue already been addressed? Horiz

Re: [openstack-dev] [Horizon] the future of angularjs development in Horizon

On 15/11/14 03:21, Richard Jones wrote: > On 15 November 2014 00:58, Radomir Dopieralski wrote: [...] >> 4. additions and upgrades of libraries moderated by the packagers, > > Is there already some mechanism for handling the creation and management > of xstatic packages and how they interac