Hi All,
I try to contribute code to openstack.
I made a patch to migrate swift test code from unittest to testtools.
https://review.openstack.org/#/c/192960/
And I found that my patch often break if other patch change the test code.
For example, the testtools requires that the subclass of the
Hi folks
I am wondering if it is possible to differenciate nodes within a same role.
Is it possible for example to apply aplugin to a compute node A but not a
compute node B?
It will be more clear with examples :
1) for the nfs plugin I want to use nfs storage backend for compute node A
but LVM
Hi All,
I try to contribute code to openstack.
I made a patch to migrate swift test code from unittest to testtools.
https://review.openstack.org/#/c/192960/
And I found that my patch often break if other patch change the test code.
For example, the testtools requires that the subclass of the
Just a reminder of today's meeting
On Mon, Jun 22, 2015 at 12:45 PM, Zhipeng Huang zhipengh...@gmail.com
wrote:
Hi Team,
Thanks for expressing your interests in Tricircle. The meeting logistics
has been approved by the infra team, therefore starting from Wednesday this
week, we will have
Hi Kunal,
Did you also include use cases per our last discussion on IRC?
I prefer to start with use cases before we dive into APIs.
Thanks,
-Sam.
-Original Message-
From: Gandhi, Kunal [mailto:kunalhgan...@gmail.com]
Sent: Wednesday, June 24, 2015 6:47 AM
To: OpenStack
Please, note the blueprint I created for the documentation feature [1].
There is also a linked blueprint to create a configuration reference
document [2]. I targeted the blueprint to 'future', as we most likely won't
be able to fit it into 7.0 cycle.
I will start working on spec for the reference
Hi,
I setup an openstack env as one controller + network node on OL7.1 and two
compute node on windows 2012 server with cloudbase hyper-v compute node
driver. Every compute node has two nics. I created a vswitch on the second
one and use it to connect to instances. Below is my
Hi Zhou,
Try Fuel 6.1 where we have a lot of very nice features including 'advanced
networking'. Feel free to read release notes [1]. It's one of the most
significant releases with many many features and improvements. I am very
proud of it.
[1]
Hi Sam
Yes. we discussed the use cases 2 weeks ago on irc. The IRC logs can be found
here
http://eavesdrop.openstack.org/meetings/gslb/2015/gslb.2015-06-09-16.00.log.html
http://eavesdrop.openstack.org/meetings/gslb/2015/gslb.2015-06-09-16.00.log.html
and the use case document can be found
Hello,
I have downloaded the redfish available code and I want to run the
test_redfish program to understand what happens.
Whenever I set the host name and give the username and password and try to run
the file test_redfish.py I get the below error.
Thank you guys!
I'm reading the advanced networking spec and think it's good. I'll try
to comment it. It's too epic for me for now. I wrote a patch to move
Ceph public network to storage network. It's based on Fuel 6.0, so I'm
trying to rebase it to lastest master then maybe ask you for a review.
Only if all the hosts managed by OpenStack are capable for measured boot
process, then let 3rd-party tool call nova fencing API might be better than
using TrustedFilter.
But if not all the hosts support measured boot, then with TrustedFilter we can
schedule VM to only measured and trusted
Hi All,
*What this mail is about ?*
As part of the below blueprint, we are planning for a boot deploy interface
separation in Ironic.
https://blueprints.launchpad.net/ironic/+spec/new-boot-interface
*Whom does this concern ?*
* If you have an out of the tree driver for Ironic
* If you are in
(general point, could we please try not top-posting ? It makes a little
harder to follow the conversation)
Replies inline.
Le 24/06/2015 08:15, Wei, Gang a écrit :
Only if all the hosts managed by OpenStack are capable for measured boot
process, then let 3rd-party tool call nova fencing API
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/23/2015 08:48 PM, Paul Ward wrote:
I haven't dug into the code yet, but from testing via CLI and REST
API, it appears neutron does not honor the order in which users
specify their dns-nameservers. For example, no matter what order I
The problem there is that it takes (significant) time for the connection
attempt to time out - every cinder command taking several minutes is not
acceptable.
Obviously this depends on the network setup of the cloud - I can only talk
about the case we saw
On 24 Jun 2015 00:25, Jeremy Stanley
-Original Message-
From: Sylvain Bauza [mailto:sba...@redhat.com]
Sent: Wednesday, June 24, 2015 9:39 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] How to properly detect and fence a
compromised host (and why I dislike
Robert Collins wrote:
[...]
I propose the following to reconcile:
- I'll add a lint command to openstack/requirements
- it will check for \n
- it will accept the set that openstack/requirements accepts in each
of non-strict and strict mode
- anything that parses will be checked against
Irina,
Thanks for the link. Unfortunatly it does not cover my use cases. What we
would like to do is not define a new role.
We would like to be able to apply plugin to some compute node for example
and not in the others compute nodes or to be able to execute plugin with a
given config on some
Samuel, I would like you to consider this proposal:
https://review.openstack.org/#/c/184076/6/specs/7.0/node-custom-attributes.rst
This is about support of custom node labels. I think plugins should be able
to assign its own labels to nodes via Nailgun API. Is it possible? Will it
suit your case?
Hello
My five cents :)
I also very proud of our 6.1 release
Unfortunately we still do not have this separation for ceph public and
cluster networks in 6.1.
One little hint
In 6.1 we have granular deployment (
++ to make a single source of enforcement.
thanks,
dims
On Wed, Jun 24, 2015 at 6:06 AM, Thierry Carrez thie...@openstack.org wrote:
Robert Collins wrote:
[...]
I propose the following to reconcile:
- I'll add a lint command to openstack/requirements
- it will check for \n
- it will
On 06/24/2015 07:57 AM, Chris Dent wrote:
On Wed, 24 Jun 2015, Sean Dague wrote:
So on https://review.openstack.org/#/c/194442 ... I was kind of thinking
we'd be able to get keystone-wsgi-public into a bin directory. I put up
a half baked sketch of this idea in
On 06/23/2015 07:31 PM, Robert Collins wrote:
You may have seen your requirements update proposals start to include
things like:
MySQL-python;python_version=='2.7'
like in
https://review.openstack.org/#/c/194325/
https://review.openstack.org/#/c/194325/3/test-requirements.txt
This is
On 06/24/2015 09:18 AM, Nanda Devi Sahu wrote:
Hello,
I have downloaded the redfish available code and I want to run the
test_redfish program to understand what happens.
Whenever I set the host name and give the username and password and try
to run the file test_redfish.py I get the below
Hey Nova,
I'll cut to the chase and keep this email short for brevity and clarity:
Specs don't work! They do nothing to facilitate good design happening,
if anything they prevent it. The process layered on top with only a
minority (!) of cores being able to approve them, yet they are a prereq
of
On 06/23/2015 04:07 PM, Brant Knudson wrote:
I've got a few related changes proposed to keystone and devstack:
https://review.openstack.org/#/c/193891/ - Changes Apache Httpd config
so that /identity is the keystone public (aka main) handler and
/identity_admin is the keystone admin handler.
On Wed, 24 Jun 2015, Sean Dague wrote:
On 06/24/2015 07:57 AM, Chris Dent wrote:
If the primary reason is so that we can rely on the console_scripts
entry point to handle getting the application somewhere useful then
that too feels a bit crufty, in the sense of that's a hack.
[snip]
The
On Wed, Jun 24, 2015 at 11:28:59AM +0100, Nikola Đipanov wrote:
Hey Nova,
I'll cut to the chase and keep this email short for brevity and clarity:
Specs don't work! They do nothing to facilitate good design happening,
if anything they prevent it. The process layered on top with only a
Mike Perez wrote:
Two options:
1) Revert version discovery which was introduced in Kilo for Cinder client.
2) Grant exception on backporting [4] a patch that helps with this
problem, and introduces a config option that does not change default
behavior. I'm also not sure if this should be
Hello,
The python-redfish module is in its infancy atm.
One of my colleagues (René) is working on revamping the code so we can
start adding more functions. You may want to watch his branch at
https://github.com/bcornec/python-redfish/tree/prototype
(Or in his own repo
Thank you Sergii,
I read the release notes but didn't find a specific 'Advanced
Networking' part. It seems advanced networking is a spec [1] mentioned
by Igor in a previous mail. Maybe I overlook something? Anyway, I think
6.1 is a great release, for it solves some major problems in my previous
Le 24/06/2015 10:35, Dulko, Michal a écrit :
-Original Message-
From: Sylvain Bauza [mailto:sba...@redhat.com]
Sent: Wednesday, June 24, 2015 9:39 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] How to properly detect and fence a
Samuel,
Currently, there is a spec on introducing a new role through a plugin [1] -
the feature is targeted at 7.0.
Feel free to comment on it and ask questions right in the commit.
[1] https://review.openstack.org/#/c/185267/
--
Best regards,
Irina
Partner Management Business Analyst
skype:
On 06/24/2015 07:19 AM, Sean Dague wrote:
On 06/23/2015 04:07 PM, Brant Knudson wrote:
I've got a few related changes proposed to keystone and devstack:
https://review.openstack.org/#/c/193891/ - Changes Apache Httpd config
so that /identity is the keystone public (aka main) handler and
On Wed, 24 Jun 2015, Sean Dague wrote:
So on https://review.openstack.org/#/c/194442 ... I was kind of thinking
we'd be able to get keystone-wsgi-public into a bin directory. I put up
a half baked sketch of this idea in
https://review.openstack.org/#/c/195044. Would be curious if some
version
Hi guys,
I worked on running nova-api on http://localhost/compute.
I prepared raw reviews:
nova review: https://review.openstack.org/#/c/195303/1
devstack review: https://review.openstack.org/#/c/195300/
We need to determine proper URLs for ec2-api(used 8773 port) and
metadata(used 8775 port)
Many of you are aware that I’m still working through the Oslo libraries,
removing the ‘oslo’ namespace package in favor of library-specific names like
‘oslo_config’. If you’re not, you’ll find details in the blueprint [1].
I have been submitting patches to projects as I find the old import
Hi everyone,
Just a quick reminder that the weekly OpenStack QA team IRC meeting will be
tomorrow Thursday, June 25th at 22:00 UTC in the #openstack-meeting channel.
The agenda for tomorrow's meeting can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting
Anyone is welcome to
On Wed, Jun 24, 2015 at 10:04 AM, Ed Leafe e...@leafe.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 06/24/2015 08:38 AM, Nikola Đipanov wrote:
I urge people to reply to this instead of my original email as the
writing is more detailed and balanced.
OK, I've read what
Please note the IRC meeting is scheduled for 16:00 UTC in
#openstack-meeting-alt
Please review meeting agenda and update if there is something you wish to
discuss.
https://etherpad.openstack.org/p/fuel-weekly-meeting-agenda
--
--
Andrew Woodward
Mirantis
Fuel Community Ambassador
Ceph
On 06/24/2015 08:42 AM, Daniel P. Berrange wrote:
On Wed, Jun 24, 2015 at 11:28:59AM +0100, Nikola Đipanov wrote:
Hey Nova,
I'll cut to the chase and keep this email short for brevity and clarity:
Specs don't work! They do nothing to facilitate good design happening,
if anything they prevent
Hi! Our next OpenStack App Catalog meeting will take place this
Thursday June 25th at 17:00 UTC in #openstack-meeting-3
The agenda can be found here:
https://wiki.openstack.org/wiki/Meetings/app-catalog
Please add agenda items if there's anything you would like to discuss.
One important topic
On Wed, Jun 24, 2015 at 11:42 AM, Kashyap Chamarthy kcham...@redhat.com
wrote:
On Wed, Jun 24, 2015 at 10:02:27AM -0500, Matt Riedemann wrote:
On 6/24/2015 9:09 AM, Kashyap Chamarthy wrote:
On Wed, Jun 24, 2015 at 02:51:38PM +0100, Nikola Đipanov wrote:
On 06/24/2015 02:33 PM, Matt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/24/2015 03:23 PM, Sahid Orentino Ferdjaoui wrote:
I do not consider specs don't work, personnaly I refer myself to
this relatively good documentation [1] instead of to dig in code
to remember how work a feature early introduced.
I think
Hi Team,
Thanks for the great discussions. Meeting minutes could be found at
http://eavesdrop.openstack.org/meetings/tricircle_weekly_meeting_2015_06_24/2015/tricircle_weekly_meeting_2015_06_24.2015-06-24-13.04.html.
Let's start hacking and reconvene next week :)
--
Zhipeng (Howard) Huang
On 2015-06-24 09:01:51 +0300 (+0300), Duncan Thomas wrote:
The problem there is that it takes (significant) time for the connection
attempt to time out - every cinder command taking several minutes is not
acceptable.
[...]
Another silly idea from an end user of cinderclient here, but try
both
On 06/24/2015 01:42 PM, Daniel P. Berrange wrote:
On Wed, Jun 24, 2015 at 11:28:59AM +0100, Nikola Đipanov wrote:
Hey Nova,
I'll cut to the chase and keep this email short for brevity and clarity:
Specs don't work! They do nothing to facilitate good design happening,
if anything they
On 24 June 2015 at 14:34, Jeremy Stanley fu...@yuggoth.org wrote:
On 2015-06-24 09:01:51 +0300 (+0300), Duncan Thomas wrote:
The problem there is that it takes (significant) time for the connection
attempt to time out - every cinder command taking several minutes is not
acceptable.
[...]
On Wed, Jun 24, 2015 at 02:51:38PM +0100, Nikola Đipanov wrote:
On 06/24/2015 02:33 PM, Matt Riedemann wrote:
[. . .]
I agree completely. The nicely rendered feature docs which is a
byproduct of the specs process in gerrit is a great part of it. So when
someone is trying to use a new
On 06/24/2015 03:08 PM, Dan Smith wrote:
Why do cores need approved specs for example - and indeed for many of us
- it's just a dance we do. I refuse to believe that a core can be
trusted to approve patches but not to write any code other than a bugfix
without a written document explaining
Like this idea too, we should have done that long ago. :)
On 24 Jun 2015, at 02:17, Adam Spiers aspi...@suse.com wrote:
Digimer li...@alteeve.ca wrote:
Resending to the Cluster Labs mailing list, this list is deprecated
Thanks, I only realised that after getting a deprecation warning :-(
On 6/24/2015 7:42 AM, Daniel P. Berrange wrote:
On Wed, Jun 24, 2015 at 11:28:59AM +0100, Nikola Đipanov wrote:
Hey Nova,
I'll cut to the chase and keep this email short for brevity and clarity:
Specs don't work! They do nothing to facilitate good design happening,
if anything they prevent
On 2015-06-24 16:03:18 +1200 (+1200), Robert Collins wrote:
[...]
We also have a strict/nonstrict mode which appears to be the same to me.
The requirements validation check compares old vs. new versions of
files so that it can only enforce matching on lines which are being
changed. The
On 6/24/2015 8:23 AM, Sahid Orentino Ferdjaoui wrote:
On Wed, Jun 24, 2015 at 11:28:59AM +0100, Nikola Đipanov wrote:
Hey Nova,
I'll cut to the chase and keep this email short for brevity and clarity:
Specs don't work! They do nothing to facilitate good design happening,
if anything they
Great!
Thanks you. I have missed this one.
From: Gandhi, Kunal [mailto:kunalhgan...@gmail.com]
Sent: Wednesday, June 24, 2015 12:21 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [designate] and [lbaas] - GSLB API and backend
support
Hi Sam
On Wed, Jun 24, 2015 at 11:28:59AM +0100, Nikola Đipanov wrote:
Hey Nova,
I'll cut to the chase and keep this email short for brevity and clarity:
Specs don't work! They do nothing to facilitate good design happening,
if anything they prevent it. The process layered on top with only a
Why do cores need approved specs for example - and indeed for many of us
- it's just a dance we do. I refuse to believe that a core can be
trusted to approve patches but not to write any code other than a bugfix
without a written document explaining themselves, and then have a yet
more
On Wed, Jun 24, 2015 at 04:09:16PM +0200, Kashyap Chamarthy wrote:
On Wed, Jun 24, 2015 at 02:51:38PM +0100, Nikola Đipanov wrote:
On 06/24/2015 02:33 PM, Matt Riedemann wrote:
[. . .]
I agree completely. The nicely rendered feature docs which is a
byproduct of the specs process in
On Wed, 2015-06-24 at 17:25 +0100, Daniel P. Berrange wrote:
On Wed, Jun 24, 2015 at 11:52:37AM -0400, Adam Young wrote:
On 06/24/2015 06:28 AM, Nikola Đipanov wrote:
Gerrit and our spec template are a horrible tool for
discussing design.
This is the heart of the problem.
I think
On 06/24/2015 06:42 PM, Jay Pipes wrote:
I also think the way we couple spec approval reviews to the dev
cycles is counterproductive. We should be willing to accept and
review specs at any point in any cycle, and once approved they should
remain valid for a prolonged period of time - not
At the IRC this week, Bryan asked how he could replicate the environment we
used at the Vancouver hands-on-lab. So we added some basic instructions at
the end of the lab write-up.
https://docs.google.com/document/u/1/d/1lXmMkUhiSZYK45POd5ungPjVR--Fs_wJHeQ6bXWwP44/pub
Bryan: hope that helps.
Hi, Mistral team,
With recent introduction of programmatic annotations in requirements [1],
projects need to upgrade their version of pbr to work nicely with such
annotations.
Solum's devstack gate is currently failing [2] because the version of pbr in
python-mistralclient is
incompatible
Hi Team,
Just a reminder that as what was discussed in yesterday's meeting, let's
start the API reuse design with new BP registration at
https://launchpad.net/tricircle and online doc edit/discuzz
--
Zhipeng (Howard) Huang
Standard Engineer
IT Standard Patent/IT Prooduct Line
Huawei
Hi, Devdatta,
Thanks for the info in time, and sorry for blocking Solum project,
I'll take a look and help we merge it ASAP.
On Thu, Jun 25, 2015 at 8:43 AM, Devdatta Kulkarni
devdatta.kulka...@rackspace.com wrote:
Hi, Mistral team,
With recent introduction of programmatic annotations in
Hello Andrew,
I did some similar modifications in Fuel 6.0 as [1][2]. However in [3]
it says Ceph monitor have to run on the public network.
In the file deployment/puppet/ceph/manifests/conf.pp, we can see it
calls 'ceph-deploy new ${::hostname}:${::internal_address}'.
In
On 6/24/2015 9:09 AM, Kashyap Chamarthy wrote:
On Wed, Jun 24, 2015 at 02:51:38PM +0100, Nikola Đipanov wrote:
On 06/24/2015 02:33 PM, Matt Riedemann wrote:
[. . .]
I agree completely. The nicely rendered feature docs which is a
byproduct of the specs process in gerrit is a great part of
On 06/24/2015 02:33 PM, Matt Riedemann wrote:
On 6/24/2015 8:23 AM, Sahid Orentino Ferdjaoui wrote:
On Wed, Jun 24, 2015 at 11:28:59AM +0100, Nikola Đipanov wrote:
Hey Nova,
I'll cut to the chase and keep this email short for brevity and clarity:
Specs don't work! They do nothing to
Hi Lily,
What version are you running, Icehouse, Juno, Kilo or master?
A full copy of the nova-compute.log and neutron_hyperv_agent.log on a pastebin
might be helpful. Additionally, your neutron.conf from the neutron server could
help along with your neutron network configuration.
Finally, the
On Tue, Jun 23, 2015 at 08:49:55AM -0700, Mike Perez wrote:
There was a bug raised [1] from some large deployments that the Cinder
client 1.2.0 and beyond is not working because of version discovery.
Unfortunately it's not taking into account of deployments that have a
proxy.
A little bit
Hello,
From what I can see in the trace you included, it seems to be either Kilo or
master (it uses networking-hyperv, which was introduced in Kilo).
Also, it might be useful to know if you are using Windows Server 2012 or
Windows Server 2012 R2. Running this in Powershell should yield the OS
All,
A subgroup [1] has formed within the Magnum project, who's mission is providing
first class networking support for containers. Please join us [2] this Thursday
at 1800 UTC for our first meeting to discuss the native Docker networking
blueprint [3] and overall direction of the team.
[1]
On 06/24/2015 06:28 AM, Nikola Đipanov wrote:
Gerrit and our spec template are a horrible tool for
discussing design.
This is the heart of the problem.
I think that a proper RFE description in the bug tracker is the best
place to start. Not a design of the solution, but a statement of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Since the current meeting time is problematic for several people, we
ran a poll for preferences for different times on Tuesdays and
Wednesdays. No single time was acceptable for all of the main people
involved in the Scheduler effort, so we're
Julia,
It is exactly what i was thinking. With such a mechanism we would be able
to define custom labels to apply different type of task on compute nodes
according to their labels. I add a comment on the review. As for now I
don't see how we would be able to create custom label from plugin. In
Hi Alessandro and Claudiu,
Thank you for your quick reply.
The version I am running is kilo. Yes I use networking-hyperv. And the
windows version is Windows Server 2012 R2. Below are the output for the
commands mentioned:
Get-VMSwitch
Name
On 24 June 2015 at 16:42, Dave Walker em...@daviey.com wrote:
As Jeremy points out, I fail to see why fallback default behaviour
cannot be used.. Attempt to use version discovery feature, if fail -
fall back to legacy behaviour..
What are the issues associated with this?
So the issue is
On Wed, Jun 24, 2015 at 11:52:37AM -0400, Adam Young wrote:
On 06/24/2015 06:28 AM, Nikola Đipanov wrote:
Gerrit and our spec template are a horrible tool for
discussing design.
This is the heart of the problem.
I think that a proper RFE description in the bug tracker is the best place
On 06/24/2015 04:42 PM, Andrew Laski wrote:
On 06/24/15 at 02:38pm, Nikola Đipanov wrote:
On 06/24/2015 01:42 PM, Daniel P. Berrange wrote:
On Wed, Jun 24, 2015 at 11:28:59AM +0100, Nikola Đipanov wrote:
Hey Nova,
I'll cut to the chase and keep this email short for brevity and
clarity:
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 neil.jer...@metaswitch.com wrote:
On 17/06/15 16:17, Kris G. Lindgren wrote:
See inline.
Kris Lindgren
Senior Linux Systems
TL/DR: I think the original poster is simply frustrated with how long it
takes to go from spec to landed feature. How about we stop talking about
whether specs are good or not (I think everyone agrees that they are
beneficial), and try to actually make the process better?
And by make it better, I
Hi,
I also notice that in latest ceph-deploy source code, it allows us to
define public_network and cluster_network argument when calling
'ceph-deploy new'. It also checks if monitor IP address is in either of
the two networks.
On 06/24/15 at 02:38pm, Nikola Đipanov wrote:
On 06/24/2015 01:42 PM, Daniel P. Berrange wrote:
On Wed, Jun 24, 2015 at 11:28:59AM +0100, Nikola Đipanov wrote:
Hey Nova,
I'll cut to the chase and keep this email short for brevity and clarity:
Specs don't work! They do nothing to facilitate
On Wed, Jun 24, 2015 at 10:45 AM, Sean Dague s...@dague.net wrote:
On 06/24/2015 01:31 PM, Joe Gordon wrote:
On Tue, Jun 16, 2015 at 9:58 AM, Sean Dague s...@dague.net
mailto:s...@dague.net wrote:
Back when Nova first wanted to test partial upgrade, we did a bunch
of
On 06/24/2015 01:51 PM, Brant Knudson wrote:
On Wed, Jun 24, 2015 at 7:27 AM, Chris Dent chd...@redhat.com
mailto:chd...@redhat.com wrote:
On Wed, 24 Jun 2015, Sean Dague wrote:
On 06/24/2015 07:57 AM, Chris Dent wrote:
If the primary reason is so that we can
On 06/24/2015 01:41 PM, Russell Bryant wrote:
On 06/24/2015 01:31 PM, Joe Gordon wrote:
On Tue, Jun 16, 2015 at 9:58 AM, Sean Dague s...@dague.net
mailto:s...@dague.net wrote:
Back when Nova first wanted to test partial upgrade, we did a bunch of
slightly odd conditionals inside of
Hi Kyle and Neutron Cores,
I would like to nominate Intel-Networking-CI
(https://wiki.openstack.org/wiki/ThirdPartySystems/Intel-Networking-CI) to have
voting (non-gating) rights.
It's been commenting on each proposed patch-set in Neutron since Feb 10 '15:
The projects with the check job can't get updates to python specific
requirements until the new longer is in place. I've nearly got that done,
and its a critical priority for me since we don't want this stuff wedged.
Projects can manually submit changes to non marker based requirements in
the
On Wed, Jun 24, 2015 at 11:02 AM, Joe Gordon joe.gord...@gmail.com wrote:
On Wed, Jun 24, 2015 at 11:01 AM, Joe Gordon joe.gord...@gmail.com
wrote:
On Wed, Jun 24, 2015 at 10:45 AM, Sean Dague s...@dague.net wrote:
On 06/24/2015 01:31 PM, Joe Gordon wrote:
On Tue, Jun 16, 2015 at
On Wed, Jun 24, 2015 at 11:01 AM, Joe Gordon joe.gord...@gmail.com wrote:
On Wed, Jun 24, 2015 at 10:45 AM, Sean Dague s...@dague.net wrote:
On 06/24/2015 01:31 PM, Joe Gordon wrote:
On Tue, Jun 16, 2015 at 9:58 AM, Sean Dague s...@dague.net
mailto:s...@dague.net wrote:
Back
Samuel,
AFAIK labels will not be related to tasks, it's just marks for filtering
nodes.
What roles means for you?
we have tasks (A, B, C, D) and on some nodes tasks A B D should be
executed, on some B C etc. So plugin can provide specials marks or tags or
sets (we call it roles) and link
tasks
On 25 Jun 2015 1:24 am, Jeremy Stanley fu...@yuggoth.org wrote:
On 2015-06-24 16:03:18 +1200 (+1200), Robert Collins wrote:
[...]
We also have a strict/nonstrict mode which appears to be the same to me.
The requirements validation check compares old vs. new versions of
files so that it can
On Wed, Jun 24, 2015 at 10:02:27AM -0500, Matt Riedemann wrote:
On 6/24/2015 9:09 AM, Kashyap Chamarthy wrote:
On Wed, Jun 24, 2015 at 02:51:38PM +0100, Nikola Đipanov wrote:
On 06/24/2015 02:33 PM, Matt Riedemann wrote:
[. . .]
This is one of the _baffling_ aspects -- that a so-called
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 06/24/2015 08:38 AM, Nikola Đipanov wrote:
I urge people to reply to this instead of my original email as the
writing is more detailed and balanced.
OK, I've read what others have written, and want to throw in my own
0.8316 BTC.
The
On Wed, Jun 24, 2015 at 04:46:57PM +, Michael Krotscheck wrote:
On Wed, Jun 24, 2015 at 6:30 AM Matt Riedemann mrie...@linux.vnet.ibm.com
wrote:
There is the openstack-specs repo for cross-project specs:
http://specs.openstack.org/openstack/openstack-specs/
That'd be a good
On Tue, Jun 16, 2015 at 9:58 AM, Sean Dague s...@dague.net wrote:
Back when Nova first wanted to test partial upgrade, we did a bunch of
slightly odd conditionals inside of grenade and devstack to make it so
that if you were very careful, you could just not stop some of the old
services on a
On 06/24/2015 01:31 PM, Joe Gordon wrote:
On Tue, Jun 16, 2015 at 9:58 AM, Sean Dague s...@dague.net
mailto:s...@dague.net wrote:
Back when Nova first wanted to test partial upgrade, we did a bunch of
slightly odd conditionals inside of grenade and devstack to make it so
If multi-node isn't reliable more generally yet, do you think the
simpler implementation of partial-upgrade testing could proceed? I've
already done all of the patches to do it for Neutron. That way we could
quickly get something in place to help block regressions and work on the
On Wed, Jun 24, 2015 at 7:27 AM, Chris Dent chd...@redhat.com wrote:
On Wed, 24 Jun 2015, Sean Dague wrote:
On 06/24/2015 07:57 AM, Chris Dent wrote:
If the primary reason is so that we can rely on the console_scripts
entry point to handle getting the application somewhere useful then
that
Lets make sure we have checked on outstanding reviews
1 - 100 of 112 matches
Mail list logo
