+1 for Doug, he does a great job!
Thanks,
Oleg
On Fri, Jan 16, 2015 at 9:59 AM, Salvatore Orlando sorla...@nicira.com
wrote:
I agree with the proposed changes.
I would also like to take a chance to thank Sumit for the effort he has
put in this project over several years - he has been in the
So what's the difficulty of supporting centos ?
If i want to help to make it happen, do you have some advice?
On Thu Jan 15 2015 at 8:33:20 PM Mike Scherbakov mscherba...@mirantis.com
wrote:
CentOS 7 is not considered as essential / critical priority blueprint for
Fuel 6.1. There is a plan to
Dear all,
+1 for Doug.
Thank you,
Tina
On Jan 16, 2015, at 4:07 PM, Oleg Bondarev
obonda...@mirantis.commailto:obonda...@mirantis.com wrote:
+1 for Doug, he does a great job!
Thanks,
Oleg
On Fri, Jan 16, 2015 at 9:59 AM, Salvatore Orlando
sorla...@nicira.commailto:sorla...@nicira.com
+1
On 01/14/2015 07:34 PM, Robert Collins wrote:
+1
On 15 Jan 2015 07:15, Clint Byrum cl...@fewbar.com
mailto:cl...@fewbar.com wrote:
Hello! It has been a while since we expanded our review team. The
numbers aren't easy to read with recent dips caused by the summit and
+1, It will be very helpful to warn user.
Not all configurations (which can be set via UI/CLI w/o yaml editing) are
supported by network checker. It should be taken into account.
And we could recommend to run the check when user-defined configuration is
uploaded but warn that
given configuration
On Fri, Jan 16, 2015 at 10:10:34AM +0530, Vikash Kumar wrote:
All,
There is blueprint for enabling libvirt memory ballooning
https://blueprints.launchpad.net/nova/+spec/libvirt-memory-ballooning in
openstack nova. I think for Hyper-V , its already in place. Can we discuss
about the
Hi,
I've been asked to implement Ironic instead of other PXE deployment engines
(Cobbler, Foreman).
I have a few questions, though:
a - is it production ready?
b - is it capable of replacing solutions such as the ones mentioned above?
c - is there some more hands-on documentation that would help
Hi,
You have a pdb statement somewhere in your test case. Follow this to run a
single test with pdb. https://wiki.openstack.org/wiki/Testr
Cheers,
Ajaya
Cheers,
Ajaya
On Fri, Jan 16, 2015 at 11:07 AM, Abhishek Talwar/HYD/TCS
abhishek.tal...@tcs.com wrote:
Hi,
I have been trying to debug
Hi Ramy,
Still couldn't get my custom code to execute between installing devstack
and starting tests... i'll try with some custom scripts and skip devstack-*
scripts.
Meanwhile i see another issue:
2015-01-16 11:02:26,283 DEBUG zuul.IndependentPipelineManager: Finished
queue processor: patch
On Fri, Jan 16, 2015 at 11:07:07AM +0530, Abhishek Talwar/HYD/TCS wrote:
Hi,
I have been trying to debug the test cases in OpenStack, but I am not getting
successful with it. So if someone can help me with that. The last response
from the dev-list was to use $ ./run_tests.sh -d [test
Hi eduard,
can you post the whole zuul.log or debug.log after the zuul and zuul-merger
restart along with your layout.yaml
did you test the connection of gearman pulgin in jenkins ?
thanks
On Fri, Jan 16, 2015 at 4:20 PM, Eduard Matei
eduard.ma...@cloudfounders.com wrote:
Hi Ramy,
Still
Hello to All.
I'd like to notify those of you who's interested in clustering
implementation in Trove that i've made big progress with Cassandra
clustering implementation.
There are couple patches that may be useful for those of you who want to
verify given implementation:
-
Hi stackers,
i'm running CI for openstack cinder patches, when zuul reads a new patch
from gerrit, it tries to merge the patch to it's own cinder repo
@/var/lib/zuul/git/openstack/cinder
and returns the comment to gerrit saying
hence it is failing to issue the tempest-job in jenkins via
On 15/01/15 23:41, Sean Dague wrote:
On 01/15/2015 06:25 PM, Joe Gordon wrote:
We can side step the dependency graphing and ordering issue by looking
at the list of curently installed packages via pip freeze and not
installing dependencies (pip install --no-deps)
After looking into this
Hi all,
I have created etherpad page
https://etherpad.openstack.org/p/fuelclient-implementation-ideas
On Wed, Jan 14, 2015 at 12:38 PM, Konstantin Danilov kdani...@mirantis.com
wrote:
Igor,
Yep, I knew that you start to rewrite fuel-client, but it seemd for me
that this ideas is not for
On Thu, Dec 25, 2014 at 01:52:43PM +0400, Sergey Kraynev wrote:
Hi all.
In the last time we got on review several patches, which removes old
deprecation properties [1],A
and one mine [2].
The aim is to delete deprecated code and redundant tests. It looks simple,
but the
Hi Andrew,
What you described is exactly what we were going to do [1],
and everybody understand all of the cons which you described.
Also if you take a look at the blueprint it's not about plugins at all.
Scope of improvements was reduced for the current release and
Role as a plugin was
The whole-disk allocator we use for ceph-osd should be proper to work
around this problem in a way.
Our current constraint for Ubuntu is it cannot be allocated on several
disks,
as far as I remember for ceph-osd Fuel allocates from 1 to N disks, and it
doesn't
allocate any other volumes on the
It's also should be mentioned that these are several changes to do on
backend in order for UI to work faster, not on UI itself. For example,
these are:
- Custom filters, as Vitaly mentioned
- Pagination of collections
- PATCH requests support
- Probably both short and /full representations for
Konstantin,
thank you for your ideas, I think we will definitely want to use something like
that. Lets discuss some nits in the etherpad you’ve created.
- romcheg
16 січ. 2015 о 13:03 Konstantin Danilov kdani...@mirantis.com написав(ла):
Hi all,
I have created etherpad page
Hi,
1) +1 for warning
2) I don't think that we should delete tasks, it's a history which can be
useful,
for example for stats feature, also it's useful for debugging, but each task
should have created_at and updated_at fields, and from api you will be able
to get the latest tasks for specific
Steve, Thanks for the feedback.
On 16 January 2015 at 15:09, Steven Hardy sha...@redhat.com wrote:
On Thu, Dec 25, 2014 at 01:52:43PM +0400, Sergey Kraynev wrote:
Hi all.
In the last time we got on review several patches, which removes old
deprecation properties [1],A
and
- Original Message -
From: Vikash Kumar vikash.ku...@oneconvergence.com
To: openstack-dev openstack-dev@lists.openstack.org
All,
There is blueprint for enabling libvirt memory ballooning
https://blueprints.launchpad.net/nova/+spec/libvirt-memory-ballooning in
openstack nova.
The VO code exists already, as does a public demo (see my original email
for details). I gave demos to the Keystone core in Paris last November.
How soon this gets incorporated into core depends upon public/user
demand. So far, it seems that few people have recognised the value of
this service,
Hi all,
I've figured out that generic linux role had been implemended (
https://blueprints.launchpad.net/fuel/+spec/blank-role-node). It seems very
important feature in terms of further extension for puggable architecture.
In order to implement more complex plugins (e.g. for Zabbix or another
Dmitri,
we are working hard towards stable YAQL 1.0 which is expected to be
released during Kilo cycle. It is going to have proper documentation and
high unit test coverage which can also serve as a documentation source.
YAQL has already migrated to StackForge and adopted OpenStack development
Hi Dmitry,
We have plans to implement role as a plugin [1], but it
was decided to reduce the scope for 6.1 release and
the feature was postponed.
As a workaround you can use pre deployment hook
to perform some actions before any node is deployed.
Thanks,
[1]
Hi,
I am working on the Nova side of Add volume multi-attach support
https://review.openstack.org/#/c/143114/5.
I see a problem with the volume dictionary in nova code while running unit
tests (with the multiattach patches).
ERROR:
--
I get the following error by running the unit test
Hi Punith,
That's the whole log :) Not a lot happening after restart, just default
initialization.
Zuul-merger is not restarted.
Layout.yaml is default.
Gearman plugin tested in Jenkins, reports success.
I disabled now the restart job to see how long it will Look for lost
builds.
Have a nice
Hi Team,
I would like to announce another Review Day schedule on Monday (Jan 19).
During New Year Christmas holidays our CI was broken, and queue with
change-requests is now quote long. And what is more important, many patches
and specs related to Policy Guided Fulfillment are need to be
Evgeniy,
Yes, we shouldn't delete tasks, but for now it is the only way to mark
verification results as obsolete and remove them. When we implement this
new field, we can easily get rid of task deletion in favour of setting this
field.
2015-01-16 15:58 GMT+03:00 Evgeniy L e...@mirantis.com:
On Jan 15, 2015, at 7:27 PM, Michael Krotscheck krotsch...@gmail.com wrote:
I think Oracle's got enough money to support Node.js on SPARC.
How is money relevant here?
Well, normally the argument I've received is We don't have the
time/resources/insert-other-fiscally-motivated-reason
Hi Fuelers,
this is another status update.
- OpenStack-CI is now running pep8 checks [1] for patches to python-fuelclient.
- The script for running python tests in on review [2] and some guys are
requested to test it and give some feedback
- Fuel CI is now allowed to vote on python-fuelclient
On 1/16/15 9:08 AM, Doug Hellmann wrote:
We are, and as this conversation has veered off in a destructive
direction, I think we should back up and look at the compromise Radomir
posted [1] to see if that solves the original technical problem we all have.
Does having the requirements
On 01/16/2015 12:37 AM, Abhishek Talwar/HYD/TCS wrote:
Hi,
I have been trying to debug the test cases in OpenStack, but I am not
getting successful with it. So if someone can help me with that. The
last response from the dev-list was to use $ ./run_tests.sh -d [test
module path] but this
Does having the requirements specified in a JSON file, without requiring a
specific build tool to install the files, solve the packaging, testing, and
deployment issue on platforms where node.js isn’t supported natively right
now?
We only support what we test. Unless I missed something,
Abhishek,
In addition to the tips above, i put up a post for using py.test and
testtools.run as well here:
https://davanum.wordpress.com/2015/01/13/quickly-running-a-single-openstack-nova-test/
-- dims
On Fri, Jan 16, 2015 at 11:44 AM, Adam Young ayo...@redhat.com wrote:
On 01/16/2015 12:37
Also note this script from the oslotest library:
https://github.com/openstack/oslotest/blob/master/tools/oslo_debug_helper
It was added specifically to allow debugging with pdb. I've never
actually used it though. :-)
-Ben
On 01/16/2015 10:56 AM, Davanum Srinivas wrote:
Abhishek,
In
On Wed, Jan 14, 2015 at 6:16 PM, Neil Jerram neil.jer...@metaswitch.com wrote:
Maxime Leroy maxime.le...@6wind.com writes:
Ok, thank you for the details. I will look how to implement this feature.
Hi Maxime,
Did you have time yet to start looking at this? My team now has a use
case that
On Jan 16, 2015, at 11:33 AM, Drew Fisher drew.fis...@oracle.com wrote:
On 1/16/15 9:08 AM, Doug Hellmann wrote:
We are, and as this conversation has veered off in a destructive
direction, I think we should back up and look at the compromise Radomir
posted [1] to see if that solves the
Doug, there still is one open question. Distributing JavaScript libraries
via system packages is unusual. Because of that, most of the JavaScript
libraries used by horizon don't have existing packages. Who will create and
maintain the packages for these JavaScript libraries for production? For
Hi,
I will join to review on Monday from US time zone. I hope someone will be
in IRC to chat.
Thanks
Georgy
On Fri, Jan 16, 2015 at 7:45 AM, Serg Melikyan smelik...@mirantis.com
wrote:
Hi Team,
I would like to announce another Review Day schedule on Monday (Jan 19).
During New Year
Hi,
Murano uses Heat templates with almost all available resources. Neutron
resources are definitely used.
I think Murano can update our Heat resources handling properly, but there
are at least two scenarios which should be considered:
1) Murano generated stacks are long lasting. Murano uses
On Jan 16, 2015, at 12:55 PM, Matthew Farina m...@mattfarina.com wrote:
Doug, there still is one open question. Distributing JavaScript libraries via
system packages is unusual. Because of that, most of the JavaScript libraries
used by horizon don't have existing packages. Who will create
neophy,
It seems like there are left overs that fuel was using in the config
that would not be present when you installed neutron fresh. I'd
compare the config files and start backing out bits you dont need. I'd
start with the lines refrencing br-int, you dont need them on nodes
that aren't using
+1
On Thu, Jan 15, 2015 at 3:31 PM, Kyle Mestery mest...@mestery.com wrote:
The last time we looked at core reviewer stats was in December [1]. In
looking at the current stats, I'm going to propose some changes to the core
team. Reviews are the most important part of being a core reviewer, so
Monday 19 Jan is a holiday for some here in the US, so let’s skip meeting this
week. We’ll reconvene on 26 Jan at the usual time.
Doug
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
Folks:
It's a holiday in the US next Monday [1], so I'm going to cancel the weekly
Neutron team meeting. We'll reconvene per the normal schedule [2] next on
Tuesday, January 27 (my birthday!) at 1400 UTC.
One thing I'd like to mention here is on the topic of reviewing code. When
reviewing code
Hi,
Frankly speaking, Fuel team cares about stability and production readiness.
That requires a lot of testing, some modification to the packages before
releasing Fuel with CentOS 7 support. At the moment Fuel Team is focusing
on Ubuntu 14.04 as it's targeted to 6.1. CentOS 7.0 is targeted to
It’s not pretty, but if the topic has been set correctly, this finds everything
open with a Kilo-2 blueprint:
I'm pretty sure you just destroyed everyone's vision with that.
On Fri, 2015-01-16 at 21:23 +, Doug Wiegley wrote:
It’s not pretty, but if the topic has been set correctly, this finds
everything open with a Kilo-2 blueprint:
Hi openstack-dev@,
The barbican team would like to retire the 2.x branch of python-barbicanclient
in favor of the 3.x branch:
https://review.openstack.org/#/c/146231/
The 3.x branch of python-barbicanclient represents a major improvement of the
Barbican client. The main breaking change
Hello, Neutron developers.
My name is Mario and I am a Masters student in Networking and Security.
I am considering the possibility of integrating IDS technology to Neutron
as part of my Masters project.
As there are many flavors of open ID[P]S out there and those might follow
different
Hi
*,*
localconf.base file in sos-ci/sos-ci/tempates have
*CINDER_BRANCH = master*
*volume_driver=cinder.volume.drivers.solidfire.SolidFireDriver*
similarly in our localconf.base file,we have
*CINDER_BRANCH = master[[post-config|$CINDER_CONF]] [lvmdriver-1]
54 matches
Mail list logo