Re: [openstack-dev] [all] Recording little everyday OpenStack successes

> On 09 Oct 2015, at 15:46, Jeremy Stanley wrote: > > On 2015-10-09 13:51:39 +0200 (+0200), Ihar Hrachyshka wrote: > [...] >> Another IRC service that I find useful to encourage collaboration >> in teams is a karma bot. Something that would calculate >> ++ messages in tracked channels. Having suc

Re: [openstack-dev] [Neutron] Returning of HEAD files?

> On 09 Oct 2015, at 15:28, Anna Kamyshnikova > wrote: > > Some time ago we merged change [1] that removes HEADS file. Validation of > migration revisions using HEADS file was replaced with pep8. This allows us > to avoid merge conflicts that appeared every time a new migration was merged. >

Re: [openstack-dev] [Sender Auth Failure] [neutron] New cycle started. What are you up to, folks?

I¹d like to help out in some fashion with FwaaS and the IPV6 needs mentioned. Current working on the DSCP Spec and patches to implement ontop of QOS. I liked Seans comments about devstack, we have been doing tons of testing for DSCP there without really understanding how things are going to be up

Re: [openstack-dev] [all] Recording little everyday OpenStack successes

On 2015-10-09 13:51:39 +0200 (+0200), Ihar Hrachyshka wrote: [...] > Another IRC service that I find useful to encourage collaboration > in teams is a karma bot. Something that would calculate > ++ messages in tracked channels. Having such a > lightweight and visible way to tell ‘thank you’ to a co

Re: [openstack-dev] Requests + urllib3 + distro packages

Cory Benfield writes: > > The problem that occurs is the result of a few interacting things: > > - requests has very very specific versions of urllib3 it works with. > > So specific they aren't always released yet. > > This should no longer be true. Our downstream redistributors pointedout to us

Re: [openstack-dev] [Murano] py26 support in python-muranoclient

On 2015-10-09 12:22:12 +0300 (+0300), Serg Melikyan wrote: > unfortunately we don't plan to remove support for py26 from the > python-muranoclient, most of the python-client support py26 > in order to work out of the box on different OS including CentOS 6.5 > and so on. [...] Bear in mind that we

Re: [openstack-dev] Requests + urllib3 + distro packages

Robert Collins writes: > - Linux vendors often unbundle urllib3 from requests and then apply > what patches were needed to their urllib3; while not updating their > requests package dependencies to reflect this. I opened a bug on Fedora for them to update their requests package dependencies. Se

Re: [openstack-dev] [Heat] mox to mock migration

Jay, I think, that only one person who partially do the same job is Qiming. Please ask him about it. Also I think, that will be good to create BP for it, which you may mention in commit messages. In this Bp you may specify list of directories for parallel work. There is nothing else from my side.

[openstack-dev] [Neutron] Returning of HEAD files?

Some time ago we merged change [1] that removes HEADS file. Validation of migration revisions using HEADS file was replaced with pep8. This allows us to avoid merge conflicts that appeared every time a new migration was merged. The problem was pointed by Kevin Benton as the original idea of HEAD f

[openstack-dev] [Heat] mox to mock migration

I forget where we left things at the last meeting with regard to whether or not there should be a blueprint on this. I was going to work on some during some downtime but I wanted to make sure I wasn't overlapping with what others may be converting (it's more time consuming than I anticipated).

Re: [openstack-dev] [stable][horizon] adding stable reviewer

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 09/10/15 13:44, Thierry Carrez wrote: > Ihar Hrachyshka wrote: >> Welcome Doug! > > Please (re)read and apply the policy at: > https://wiki.openstack.org/wiki/StableBranch#Stable_branch_policy Thank you Ihar! Best, Matthias -BEGIN PGP SIG

Re: [openstack-dev] [mistral] [heat] Mistral Workflow resource type - resource signal handling

> On 08 Oct 2015, at 23:27, ELISHA, Moshe (Moshe) > wrote: > > Hi, > > I would like to propose a change in the behavior of the OS::Mistral::Workflow > resource signal. > > CURRENT: > The OS::Mistral::Workflow resource type is expecting the following request > body on resource signal reque

Re: [openstack-dev] [CI] Try to introduce RFC mechanism to CI.

On 2015-10-09 17:00:27 +0800 (+0800), Tang Chen wrote: [...] > I'm not sure if it is a good idea. Please help to review the > following BP. > > https://blueprints.launchpad.net/openstack-ci/+spec/ci-rfc-mechanism The Infra team doesn't rely on blueprints, and instead uses http://specs.openstack.o

Re: [openstack-dev] [infra] Try to introduce RFC mechanism to CI.

On 2015-10-09 18:06:55 +0800 (+0800), Tang Chen wrote: [...] > It is just a waste of resource if reviewers are discussing about > where this function should be, or what the function should be > named. After all these details are agreed on, run the CI. [...] As one of the people maintaining the ups

[openstack-dev] [All][Elections] Vote Vote Vote in the TC election!

We are coming down the the last hours for voting in the TC election. Search your gerrit preferred email address[0] for the following subject: Poll: OpenStack Technical Committee (TC) Election - October 2015 That is your ballot and links you to the voting application. Please vote. If you have vo

Re: [openstack-dev] [CI] Try to introduce RFC mechanism to CI.

On 10/09/2015 12:06 PM, Tang Chen wrote: On 10/09/2015 05:48 PM, Jordan Pittier wrote: Hi, On Fri, Oct 9, 2015 at 11:00 AM, Tang Chen mailto:tangc...@cn.fujitsu.com>> wrote: Hi, CI systems will run tests for each patch once it is submitted or modified. But most CI systems occu

Re: [openstack-dev] [ceilometer] Inconsistent timestamping of polled data

Hi! Looks good to me, especially for cases when after some incident we gather a great amount of notifications in queue and stated to work with it so some data will have incorrect timestamp if it set only when sample is created. Cheers, Igor Degtiarov Software Engineer Mirantis Inc. www.mirantis.

Re: [openstack-dev] Metadata via dhcp namespace not working for icehouse release

> On 09 Oct 2015, at 09:00, Pradeep kumar wrote: > > > Hii Guys, > I am trying to run Metadata via the DHCP namespace by following blog post > mentioned below: > > http://techbackground.blogspot.in/2013/06/metadata-via-dhcp-namespace.html > > Commands mentioned on above link for debugging o/p

Re: [openstack-dev] [all] Recording little everyday OpenStack successes

> On 09 Oct 2015, at 11:42, Thierry Carrez wrote: > > Hello everyone, > > OpenStack has become quite big, and it's easier than ever to feel lost, > to feel like nothing is really happening. It's more difficult than ever > to feel part of a single community, and to celebrate little successes > an

Re: [openstack-dev] [stable][horizon] adding stable reviewer

Ihar Hrachyshka wrote: > Welcome Doug! Please (re)read and apply the policy at: https://wiki.openstack.org/wiki/StableBranch#Stable_branch_policy -- Thierry Carrez (ttx) signature.asc Description: OpenPGP digital signature __

Re: [openstack-dev] [swift] Plan to port Swift to Python 3

Hi, Le 09/10/2015 12:12, vishal yadav a écrit : However I was just checking if you considered using 2to3. I can understand that translation using this tool might not cover every area in the code more specifically custom/3rd party libraries (non-standard python libraries) but IMO it can do fixer

Re: [openstack-dev] [Fuel] py.test vs testrepository

Thank you guys for all your help! Special thanks to Robert who helped to find a workaround for an issue [1] that didn’t let us use testr for Fuel Client. The patch [2] was merged and both unit and functional tests are launched by subunit and the data is maintained by testrepository. Please also

Re: [openstack-dev] [stable][horizon] adding stable reviewer

> On 09 Oct 2015, at 12:44, Matthias Runge wrote: > > Hello, > > who would be the person to talk to, to add a new reviewer to > horizon-stable-maint > > I would like Doug Fish aka drfish (on launchpad) added. > > Unfortunately, the fields on > https://review.openstack.org/#/admin/groups/537,me

Re: [openstack-dev] [all] jobs that make break when we remove Devstack extras.d in 10 weeks

On 10/09/2015 12:35 PM, Sean Dague wrote: From now until the removal of devstack extras.d support I'm going to send a weekly email of jobs that may break. A warning was added that we can track in logstash. Here are the top 25 jobs (by volume) that are currently tripping the warning: gate-muran

Re: [openstack-dev] [stable][horizon] adding stable reviewer

Hi Matthias That group is owned by stable-maint-core So you should look at members there (https://review.openstack.org/#/admin/groups/530,members) and ask some of them to add Doug. Best Yolanda El 09/10/15 a las 12:44, Matthias Runge escribió: Hello, who would be the person to talk to, to a

[openstack-dev] [stable][horizon] adding stable reviewer

Hello, who would be the person to talk to, to add a new reviewer to horizon-stable-maint I would like Doug Fish aka drfish (on launchpad) added. Unfortunately, the fields on https://review.openstack.org/#/admin/groups/537,members are greyed out for me. Thanks, Matthias

[openstack-dev] [all] jobs that make break when we remove Devstack extras.d in 10 weeks

>From now until the removal of devstack extras.d support I'm going to send a weekly email of jobs that may break. A warning was added that we can track in logstash. Here are the top 25 jobs (by volume) that are currently tripping the warning: gate-murano-devstack-dsvm gate-cue-integration-dsvm-ra

Re: [openstack-dev] [ironic] Nominating two new core reviewers

+2 for both, Vladyslav and John. On 10/09/2015 12:47 AM, Jim Rollenhagen wrote: Hi all, I've been thinking a lot about Ironic's core reviewer team and how we might make it better. I'd like to grow the team more through trust and mentoring. We should be able to promote someone to core based on

Re: [openstack-dev] [swift] Plan to port Swift to Python 3

Victor, I appreciate for your effort. However I was just checking if you considered using 2to3. I can understand that translation using this tool might not cover every area in the code more specifically custom/3rd party libraries (non-standard python libraries) but IMO it can do fixer translation

Re: [openstack-dev] [CI] Try to introduce RFC mechanism to CI.

On 10/09/2015 05:48 PM, Jordan Pittier wrote: Hi, On Fri, Oct 9, 2015 at 11:00 AM, Tang Chen > wrote: Hi, CI systems will run tests for each patch once it is submitted or modified. But most CI systems occupy a lot of resource, and take a long ti

[openstack-dev] [ceilometer] Inconsistent timestamping of polled data

Hi all, As Gordon descriped in https://bugs.launchpad.net/ceilometer/+bug/1491509 , many of pollsters define the timestamp individually for each sample that is generated rather than basing on when the data was polled. I agree with Gordon on that the timestamping of samples should base on when the

[openstack-dev] [Magnum] Testing result of new atomic-6 image

Testing result of new atomic-6 image [1] built by Tango atomic-5 image has issue to start a container instance(docker version is 1.7.1), Tango built a new atomic-6 image with docker 1.8.1 version. eghobo and I (eliqiao) did some testing works (eghobo_ did most of them) Here is the summary: *

Re: [openstack-dev] [CI] Try to introduce RFC mechanism to CI.

Hi, On Fri, Oct 9, 2015 at 11:00 AM, Tang Chen wrote: > Hi, > > CI systems will run tests for each patch once it is submitted or modified. > But most CI systems occupy a lot of resource, and take a long time to > run tests (1 or 2 hours for one patch). > > I think, not all the patches submitted n

[openstack-dev] [all] Recording little everyday OpenStack successes

Hello everyone, OpenStack has become quite big, and it's easier than ever to feel lost, to feel like nothing is really happening. It's more difficult than ever to feel part of a single community, and to celebrate little successes and progress. In a (small) effort to help with that, I suggested ma

Re: [openstack-dev] [Fuel] Plugins related functionality in Fuel Client

In that case I would suggest to also use Keystone service directory for discovering services. > 9 жовт. 2015 р. о 11:00 Evgeniy L написав(ла): > > >> I’d say even if it will be a separate service it’s better to proxy > >> requests through Nailgun’s API to have a single entry point. > > I don'

Re: [openstack-dev] [Murano] py26 support in python-muranoclient

Hi Vahid, unfortunately we don't plan to remove support for py26 from the python-muranoclient, most of the python-client support py26 in order to work out of the box on different OS including CentOS 6.5 and so on. >So the options are: >1. support py26 in tosca-parser Support for py26 is pretty e

Re: [openstack-dev] [swift] Plan to port Swift to Python 3

Victor Stinner wrote: > Good news, we made good progress last weeks on porting Swift to Python > 3, a few changes were merged and all dependencies now work on Python 3. > We only need two more simple changes to have a working pyhon34 check job: > > * "py3: Update pbr and dnspython requirements" >

[openstack-dev] [CI] Try to introduce RFC mechanism to CI.

Hi, CI systems will run tests for each patch once it is submitted or modified. But most CI systems occupy a lot of resource, and take a long time to run tests (1 or 2 hours for one patch). I think, not all the patches submitted need to be tested. Even those patches with an approved BP and spec

Re: [openstack-dev] [Fuel] Plugins related functionality in Fuel Client

+1, that would allow to install plugins from Fuel UI 2015-10-09 15:53 GMT+07:00 Sergii Golovatiuk : > +1 to Roman. > > -- > Best regards, > Sergii Golovatiuk, > Skype #golserge > IRC #holser > > On Fri, Oct 9, 2015 at 10:45 AM, Roman Prykhodchenko > wrote: > >> I’d say even if it will be a separ

Re: [openstack-dev] [Fuel] Plugins related functionality in Fuel Client

>> I’d say even if it will be a separate service it’s better to proxy requests through Nailgun’s API to have a single entry point. I don't think that application such as Nailgun should be responsible for proxying requests, we solved similar problem for OSTF with adding proxy rule in Nginx. Thanks

Re: [openstack-dev] [Fuel] Plugins related functionality in Fuel Client

Actually it's an old issue https://blueprints.launchpad.net/fuel/+spec/plugin-manager-as-separate-service On 10/09/2015 11:53 AM, Sergii Golovatiuk wrote: +1 to Roman. -- Best regards, Sergii Golovatiuk, Skype #golserge IRC #holser On Fri, Oct 9, 2015 at 10:45 AM, Roman Prykhodchenko mailto:m

Re: [openstack-dev] [Fuel] Plugins related functionality in Fuel Client

+1 to Roman. -- Best regards, Sergii Golovatiuk, Skype #golserge IRC #holser On Fri, Oct 9, 2015 at 10:45 AM, Roman Prykhodchenko wrote: > I’d say even if it will be a separate service it’s better to proxy > requests through Nailgun’s API to have a single entry point. > > 9 жовт. 2015 р. о 10:2

Re: [openstack-dev] [Fuel] Plugins related functionality in Fuel Client

I’d say even if it will be a separate service it’s better to proxy requests through Nailgun’s API to have a single entry point. > 9 жовт. 2015 р. о 10:23 Evgeniy L написав(ла): > > Hi, > > +1, but I think it's better to spawn separate service, instead of adding it > to Nailgun. > > Thanks, >

Re: [openstack-dev] [Fuel] Plugins related functionality in Fuel Client

Hi, +1, but I think it's better to spawn separate service, instead of adding it to Nailgun. Thanks, On Fri, Oct 9, 2015 at 1:40 AM, Roman Prykhodchenko wrote: > Folks, > > it’s time to speak about Fuel Plugins and the way they are managed. > > Currently we have some methods in Fuel Client that

Re: [openstack-dev] [ironic] Nominating two new core reviewers

On 10/08/2015 11:47 PM, Jim Rollenhagen wrote: Hi all, I've been thinking a lot about Ironic's core reviewer team and how we might make it better. I'd like to grow the team more through trust and mentoring. We should be able to promote someone to core based on a good knowledge of *some* of the

[openstack-dev] [All][Glance] Feedback on the proposed refactor to the image import process required

Greetings, There was recently a discussion[0] on the mailing list, started by Doug Hellman, to discuss some issues related to Glance's API, the conflicts between v1 and v2 and how this is making some pandas sad. The above served as a starting point for a discussion around the current API, how it

Re: [openstack-dev] Metadata via dhcp namespace not working for icehouse release

Hi Pradeep, see inline please... On 10/09/2015 09:00 AM, Pradeep kumar wrote: Hii Guys, and girls :) I am trying to run Metadata via the DHCP namespace by following blog post mentioned below: http://techbackground.blogspot.in/2013/06/metadata-via-dhcp-namespace.html Commandsmentioned on

Re: [openstack-dev] Requests + urllib3 + distro packages

Robert Collins writes: > The problem that occurs is the result of a few interacting things: > - requests has very very specific versions of urllib3 it works with. > So specific they aren't always released yet. This should no longer be true. Our downstream redistributors pointed out to us that th

Re: [openstack-dev] [stable][horizon] adding Doug Fish to horizon stable-maint

On 01/10/15 11:21, Matthias Runge wrote: > Hello, > > I would like to propose to add > > Doug Fish (doug-fish) > > to horizon-stable-maint team. > > I'd volunteer and introduce him to stable branch policy. A week has passed, no negative votes. Doug, I'll request to add you to horizon-stable-ma

[openstack-dev] [fuel] Nominate Svetlana Karslioglu for fuel-docs core

Hi all, Svetlana is doing great work and I hope our Fuel documentation will become even better; +1 from me -- Best regards, Irina *Business Analyst* *unloc...@mirantis.com * __ OpenStack Development Mailing List (not for

[openstack-dev] Metadata via dhcp namespace not working for icehouse release

Hii Guys, I am trying to run Metadata via the DHCP namespace by following blog post mentioned below: http://techbackground.blogspot.in/2013/06/metadata-via-dhcp-namespace.html Commands mentioned on above link for debugging o/p is exactly same for my setup. Also i am able to ping 169.254.169.254 m

<    1   2