Hi,
I've created a patchset that introduces a script to run Python tests in
fuel-library [1] and a
Jenkins job [2]
I also would like to backport those tests to stable branches to assure that
any fix backported to stable branches will be also
checked.
Best,
Sebastian
[1] https://review.openstack
On 20/02/15 20:15, Andrew Bogott wrote:
> On 2/20/15 9:06 AM, Mike Dorman wrote:
>> I can report that we do use this option (‘global' setting.) We have to
>> enforce name uniqueness for instances’ integration with some external
>> systems (namely AD and Spacewalk) which require unique naming.
>>
>
On 02/19/2015 12:45 PM, Richard W.M. Jones wrote:
On Wed, Feb 18, 2015 at 07:23:52PM +0100, Raphael Glon wrote:
I entcountered a similar case more recently on powerkvm 2.1.0
(defect with the libguestfs)
What's the actual bug? We've worked hard, with IBM, to make
libguestfs work on POWER 7 and
On Fri, Feb 20, 2015 at 06:03:46PM +0100, Markus Zoeller wrote:
> It seems to me that the blueprint serial-ports[1] didn't implement
> everything which was described in its spec. If one of you could have a
> look at the following examples and help me to understand if these
> observations are righ
On Mon, Feb 23, 2015 at 11:08:31AM +0100, Raphael Glon wrote:
> On 02/19/2015 12:45 PM, Richard W.M. Jones wrote:
> >On Wed, Feb 18, 2015 at 07:23:52PM +0100, Raphael Glon wrote:
> >>I entcountered a similar case more recently on powerkvm 2.1.0
> >>(defect with the libguestfs)
> >What's the actual
On 02/23/2015 11:23 AM, Daniel P. Berrange wrote:
The alternative Nova implementation is*not* using fuse, it is using real
mounts on the host FS. This is not a potential issue, it is an*actual*
issue. There have been bugs in Linux filesystem drivers, including ext4,
that would have allowed a mal
On 02/23/2015 11:23 AM, Daniel P. Berrange wrote:
Fedora 19 is end of life so not really relevant any more as a target.
powerkvm 2.1.x is not eol
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
On Mon, Feb 23, 2015 at 11:54:40AM +0100, Raphael Glon wrote:
> On 02/23/2015 11:23 AM, Daniel P. Berrange wrote:
> >Fedora 19 is end of life so not really relevant any more as a target.
> powerkvm 2.1.x is not eol
Well Fedora 19 is end of life, so if powerkvm is using Fedora 19, then
it is runni
On Mon, Feb 23, 2015 at 11:52:29AM +0100, Raphael Glon wrote:
> On 02/23/2015 11:23 AM, Daniel P. Berrange wrote:
> >The alternative Nova implementation is*not* using fuse, it is using real
> >mounts on the host FS. This is not a potential issue, it is an*actual*
> >issue. There have been bugs in
On 02/23/2015 11:23 AM, Daniel P. Berrange wrote:
The alternative Nova implementation is*not* using fuse,
yeah you're right -> read your page too quickly
https://www.berrange.com/tags/nbd/
added the term fuse where it should not have been
Thank you guys for response.
There is no cons, so we migrate validation to separate repo.
Best regards,
Kamil Sambor
On Wed, Feb 18, 2015 at 9:34 AM, Evgeniy L wrote:
> +1 to extract validators for granular deployment tasks
>
> Dmitry, do you mean that we should create some cli to generate grap
Hi Angus,
I am working Timur and Drago on HOT builder. I am using this ->
https://github.com/rackerlabs/hotbuilder as the base and made some improvements
over the existing code and wish to give a demonstration on how easy it is to
create a HOT template from Horizon.
Regards,
Nikunj
From: Angu
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 query the driver for
> instances and compare that against the expected host of the the instance
> acco
Lazy-Stacker summary:
I am doing some work on Neutron IPAM code for IP Allocation, and I need to
found whether it's better to use db locking queries (SELECT ... FOR UPDATE)
or some sort of non-blocking algorithm.
Some measures suggest that for this specific problem db-level locking is
more efficien
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 query the driver for
>> instances and compare th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/20/2015 11:01 PM, Matt Riedemann wrote:
>
>
> On 2/20/2015 6:23 AM, Alan Pevec wrote:
https://review.openstack.org/#/c/157535/
>>>
>>> Do you know where it ends ? We could set up Depends lines on
>>> those requirements stable/* reviews an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ivar,
Thanks! Please add me to review list.
is the agent leaving the tree this cycle? If so, there is no big
reason to introduce a new agent in master just to yank it several
weeks ago.
/Ihar
On 02/21/2015 01:41 AM, Ivar Lazzaro wrote:
> Hi Ihar,
>
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
On Mon, Feb 23, 2015 at 9:18 PM, Aggarwal, Nikunj
wrote:
> Hi Angus,
>
> I am working Timur and Drago on HOT builder. I am using this ->
> https://github.com/rackerlabs/hotbuilder as the base and made some
> improvements over the existing code and wish to give a demonstration on how
> easy it i
I am also looking forward to present it. Please support this by giving your
vote ☺
Regards,
Nikunj
From: Angus Salkeld [mailto:asalk...@mirantis.com]
Sent: Monday, February 23, 2015 5:53 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [horizon][he
On 23/02/15 12:13, Gary Kotton wrote:
>
>
> 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 wi
The devref has merged:
http://docs.openstack.org/developer/nova/devref/api_microversions.html
There are a few corner cases being worked on now, but the information
in there should be enough to add a new API change & version.
MG
On Fri, Feb 20, 2015 at 12:33 AM, Christopher Yeoh wrote:
> Hi,
>
>
+ [Fuel] tag
+ openstack-operators ML
Joe Gordon joe.gordon0 at gmail.com
Thu Dec 4 13:26:59 UTC 2014
>On Wed, Dec 3, 2014 at 3:31 PM, Mike Scherbakov
>wrote:
>> Hi all,
>> enable_new_services in nova.conf seems to allow add new compute nodes in
>> disabled state:
>>
>>
https://github.com/opens
Just for a few clarifications:
1. The link below is for the nova priority tracking
2. It was requested that we do not add bug fixes to that list. There are
other tracking tools for that
3. The list does have a "Quick/Trivial Hit Bugs". Please read the
description before you start to add
On 02/20/2015 11:33 PM, Sourabh Patwardhan (sopatwar) wrote:
> Nova core reviewers,
>
> May I request an FFE for Cisco VIF driver:
> https://review.openstack.org/#/c/157616/
>
> This is a small isolated change similar to the vhostuser / open contrail
> vif drivers for which FFE has been granted.
On Mon, Feb 23, 2015 at 11:08:31AM +0100, Raphael Glon wrote:
> sudo sysctl -w fs.protected_hardlinks=0 + common user nova/qemu
We fixed this a while back (in July 2013 in fact).
I think if you forked at Fedora 19 then you're probably using
libguestfs 1.24 + supermin 4. I'd definitely recommend
On Mon, Feb 23, 2015, at 01:29 AM, Joshua Zhang wrote:
> Hi Doug,
>
> I can't find above error when using the latest codes (2015-02-22),
> but
> new error occur ( see [1] ). I feel it has no concern with the
> code(ConfigOpts.import_opt), the same code can be run in both bash and
> py
On Mon, Feb 23, 2015 at 03:47:20PM +0100, Nikola Đipanov wrote:
> On 02/20/2015 11:33 PM, Sourabh Patwardhan (sopatwar) wrote:
> > Nova core reviewers,
> >
> > May I request an FFE for Cisco VIF driver:
> > https://review.openstack.org/#/c/157616/
> >
> > This is a small isolated change similar t
On Mon, Feb 23, 2015, at 07:17 AM, Ihar Hrachyshka wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 02/20/2015 11:01 PM, Matt Riedemann wrote:
> >
> >
> > On 2/20/2015 6:23 AM, Alan Pevec wrote:
> https://review.openstack.org/#/c/157535/
> >>>
> >>> Do you know where it en
Sorry for the late notice. We’re cancelling our team meeting today. Several
team members are on official holidays.
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe
On 02/16/2015 05:00 AM, Nikolay Makhotkin wrote:
Well, if we use trust-scoped token for getting server-list from nova
(simply use nova.servers.list() ),
Novaclient somehow tries to get another token:
https://github.com/openstack/python-novaclient/blob/master/novaclient/client.py#L690-L724
Ac
On 02/18/2015 12:02 PM, David Chadwick wrote:
I think this GUI is not intuitive to users and therefore should not be
encouraged or supported.
It is a fist hack. I think you don't mean "any gui" just that there
are some warning flags raised by this design?
If you ask a user "what does authe
Hey Folks,
In case you missed it, many of you might find the work we’ve done in maintaing
catalogs of heat templates interesting.
The proposal is here:
https://www.openstack.org/vote-vancouver/presentation/one-heat-template-to-rule-them-all
Please take a look if you haven’t already, and vote ac
Hi Adam
there is some work being done on this by HP, Intel and IBM, and they
have some designs at
http://invis.io
pieter.c.kruithof...@hp.com can send you the details as he invited me
to comment on the designs, which I have done.
As you know, we already have our own federated Horizon login scr
We have a library called "flame" :
https://github.com/cloudwatt/flame
https://pypi.python.org/pypi/python-flameclient/0.1.0
It generates heat templates from "existing" resources:
http://dev.cloudwatt.com/en/blog/introducing-flame-automatic-heat-template-generation.html
Could it help?
Le 23/02/
On 02/23/2015 11:16 AM, Pratik Mallya wrote:
> Hey Folks,
>
> In case you missed it, many of you might find the work we’ve done in
> maintaing catalogs of heat templates interesting.
> The proposal is here:
> https://www.openstack.org/vote-vancouver/presentation/one-heat-template-to-rule-them-al
On Mon, Feb 23, 2015 at 8:49 AM, Ihar Hrachyshka
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 02/20/2015 07:16 PM, Joshua Harlow wrote:
> > Sean Dague wrote:
> >> On 02/20/2015 12:26 AM, Adam Gandelman wrote:
> >>> Its more than just the naming. In the original proposal,
> >>>
[branching off a discussion on ovs-dev at this point:
http://openvswitch.org/pipermail/dev/2015-February/051609.html]
On Fri, Feb 20, 2015 at 6:56 PM, Kyle Mestery wrote:
> One thing to keep in mind, this ties somewhat into my response to Russell
> earlier on the decision around ML2 vs. core plug
> What's the alternative proposed release model?
I deleted a couple paragraphs of the above before sending this, thinking
(like Joe) that there probably needs to be a specific discussion aimed
at this topic. But:
> What's the compatibility story with Glance / Neutron / Cinder in
> whatever that m
On 02/23/2015 04:02 PM, Sean Dague wrote:
On 02/23/2015 03:45 PM, Dan Smith wrote:
Seriously, what is the point of 6-month releases again? We are a
free-form open source set of projects, with a lot of intelligent
engineers. Why are we stuck using an outdated release model?
I've been wondering
Bogdan,
I think we should keep bugs open and not "supersed" them by blueprint. I
see following reasons for it.
Often, we can find workaround in order to fix the bug. Even if bug
naturally seems to be falling into some blueprint's scope. Then problem is
that when you close the bug, you don't even t
On Fri, Feb 20, 2015, at 11:24 AM, Philipp Marek wrote:
> Hi all,
>
> this is a reflection of the discussion I just had on #openstack-infra;
> it's
> about (re-)using the central CI infrastructure for our Open-Source DRBD
> driver too.
>
>
> The current status is:
> * The DRBD driver is alrea
On Mon, Feb 23, 2015 at 11:04 AM, Doug Hellmann
wrote:
>
>
> On Mon, Feb 23, 2015, at 12:26 PM, Joe Gordon wrote:
> > On Mon, Feb 23, 2015 at 8:49 AM, Ihar Hrachyshka
> > wrote:
> >
> > > -BEGIN PGP SIGNED MESSAGE-
> > > Hash: SHA1
> > >
> > > On 02/20/2015 07:16 PM, Joshua Harlow wrote:
Was:
http://lists.openstack.org/pipermail/openstack-dev/2015-February/057578.html
There has been frustration with our current 6 month development cadence.
This is an attempt to explain those frustrations and propose a very rough
outline of a possible alternative.
Currently we follow a 6 month re
The python-glanceclient release management team is pleased to announce:
python-glanceclient version 0.16.0 has been released on Tuesday, Feb 24th
around 05:50 UTC.
For more information, please find the details at:
https://launchpad.net/python-glanceclient/+milestone/v0.16.0
Please repor
45 matches
Mail list logo