[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

[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

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

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] 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

[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] [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

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] [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

+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

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

>> 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

+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

[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] [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" >

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] [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'

[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] [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] [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: *

[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

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

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] [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

[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

[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

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

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

> 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] [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] [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] [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] [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] 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] [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] [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

[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] [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

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] [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] [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

[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).

[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

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.

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] [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

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] [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] [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] [all] Recording little everyday OpenStack successes

On 10/09/2015 05:42 AM, 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 > and progre

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] Requests + urllib3 + distro packages

> On 9 Oct 2015, at 14:40, William M Edmonds wrote: > > 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 shou

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

On 2015-10-09 15:53:17 +0200 (+0200), Ihar Hrachyshka wrote: [...] > There are already multiple karmabot implementations that could be > reused, like https://github.com/chromakode/karmabot > > Can we just adopt one of those? Perhaps, though we're trying to reduce rather than increase the number o

Re: [openstack-dev] [kolla] Backport policy for Liberty

On Thu, Oct 8, 2015 at 2:47 PM, Steven Dake (stdake) wrote: > Kolla operators and developers, > > The general consensus of the Core Reviewer team for Kolla is that we > should embrace a liberal backport policy for the Liberty release. An > example of liberal -> We add a new server service to Ans

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

On 2015-10-09 14:58:36 +0100 (+0100), Cory Benfield wrote: [...] > IMO, what OpenStack needs is a decision about where it’s getting > its packages from, and then to refuse to mix the two. I have yet to find a Python-based operating system installable in whole via pip. There will always be _at_leas

[openstack-dev] [all] service catalog: TNG

It looks like some great conversation got going on the service catalog standardization spec / discussion at the last cross project meeting. Sorry I wasn't there to participate. A lot of that ended up in here (which was an ether pad stevemar and I started working on the other day) - https://etherpa

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

For those who are interested in more of the historical aspect around this, https://github.com/kennethreitz/requests/issues/1811 https://github.com/kennethreitz/requests/pull/1812 My own thoughts are varied here, I get the angle of vendoring, but I don't get the resistance to unvendoring it (whi

[openstack-dev] [Horizon] Suggestions for handling new panels and refactors in the future

I have two suggestions for handling both new panels and refactoring existing panels that I think could benefit us in the future: 1) When we are creating a panel that's a major refactor of an existing it should be a new separate panel, not a direct code replacement of the existing panel 2) New panel

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

On Fri, Oct 9, 2015 at 3:42 AM, 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 > a

Re: [openstack-dev] [all] service catalog: TNG

On Fri, Oct 9, 2015 at 9:39 AM, Sean Dague wrote: > Lastly, I think it's pretty clear we probably need a dedicated workgroup > meeting to keep this ball rolling, come to a reasonable plan that > doesn't break any existing deployed code, but lets us get to a better > world in a few cycles. annegen

Re: [openstack-dev] We should move strutils.mask_password back into oslo-incubator

On 10/9/2015 1:49 AM, Paul Carlton wrote: On 08/10/15 16:49, Doug Hellmann wrote: Excerpts from Matt Riedemann's message of 2015-10-07 14:38:07 -0500: Here's why: https://review.openstack.org/#/c/220622/ That's marked as fixing an OSSA which means we'll have to backport the fix in nova but

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

> On 9 Oct 2015, at 15:18, Jeremy Stanley wrote: > > On 2015-10-09 14:58:36 +0100 (+0100), Cory Benfield wrote: > [...] >> IMO, what OpenStack needs is a decision about where it’s getting >> its packages from, and then to refuse to mix the two. > > I have yet to find a Python-based operating sy

Re: [openstack-dev] [all] service catalog: TNG

I'm in too. David On Fri, Oct 9, 2015 at 8:51 AM, Dean Troyer wrote: > On Fri, Oct 9, 2015 at 9:39 AM, Sean Dague wrote: >> >> Lastly, I think it's pretty clear we probably need a dedicated workgroup >> meeting to keep this ball rolling, come to a reasonable plan that >> doesn't break any exist

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

> On Oct 9, 2015, at 10:49 AM, John Griffith wrote: > > ​Great idea Thierry, great to promote some positive things! Thanks for > putting this together.​ +1 Great indeed... thanks Thierry. Regards, Shamail __ OpenStack

[openstack-dev] [Neutron] L2 gateway project

Hi, Who will be creating the stable/liberty branch? Thanks Gary __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.o

Re: [openstack-dev] [all] service catalog: TNG

On 10/09/2015 11:07 AM, David Lyle wrote: I'm in too. Yes please. On Fri, Oct 9, 2015 at 8:51 AM, Dean Troyer wrote: On Fri, Oct 9, 2015 at 9:39 AM, Sean Dague wrote: Lastly, I think it's pretty clear we probably need a dedicated workgroup meeting to keep this ball rolling, come to a rea

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

>-Original Message- >From: Jeremy Stanley [mailto:fu...@yuggoth.org] >Sent: Friday, October 9, 2015 1:17 PM >To: OpenStack Development Mailing List (not for usage questions) > >Subject: Re: [openstack-dev] [infra] Try to introduce RFC mechanism to CI. > >On 2015-10-09 18:06:55 +0800

Re: [openstack-dev] [all] service catalog: TNG

> On Oct 9, 2015, at 10:39 AM, Sean Dague wrote: > > It looks like some great conversation got going on the service catalog > standardization spec / discussion at the last cross project meeting. > Sorry I wasn't there to participate. > Apologize if this is a question that has already been addr

Re: [openstack-dev] [all] service catalog: TNG

On 10/09/2015 10:39 AM, Sean Dague wrote: It looks like some great conversation got going on the service catalog standardization spec / discussion at the last cross project meeting. Sorry I wasn't there to participate. Just so folks know, the collection of existing service catalogs has been up

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

On 10/09/2015 12:58 PM, Dmitry Tantsur wrote: 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

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

On Fri, Oct 9, 2015 at 8:52 AM, Russell Bryant wrote: > On 10/09/2015 05:42 AM, 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

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

+1 Great idea! On Fri, Oct 9, 2015 at 3:42 AM, 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 littl

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

This is AWESOME! And I've already found useful resources on the list of successes. Beautiful job, and fantastic idea! Nick On 10/09/2015 05:42 AM, Thierry Carrez wrote: > Hello everyone, > > OpenStack has become quite big, and it's easier than ever to feel lost,

Re: [openstack-dev] [all] service catalog: TNG

On 10/09/2015 11:21 AM, Shamail wrote: On Oct 9, 2015, at 10:39 AM, Sean Dague wrote: It looks like some great conversation got going on the service catalog standardization spec / discussion at the last cross project meeting. Sorry I wasn't there to participate. Apologize if this is a ques

Re: [openstack-dev] [Neutron] L2 gateway project

On Fri, Oct 9, 2015 at 10:13 AM, Gary Kotton wrote: > Hi, > Who will be creating the stable/liberty branch? > Thanks > Gary > > I'll be doing this once someone from the L2GW team lets me know a commit SHA to create it from. Thanks, Kyle > ___

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

On Fri, Oct 09, 2015 at 09:06:57AM -0400, Jay Dobies wrote: > 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 m

Re: [openstack-dev] [congress] Symantec's security group management policies

Hi Su, This looks very good. Will it be possible to put your usecase as part of the Usecase VM. Have you tried it out on the Usecase VM that I published earlier. I can help if you get stuck. LMK, Thanks, -Shiv From: Su Zhang [mailto:westlif...@gmail.com] Sent: Thursday, October 08, 2015 1:2

Re: [openstack-dev] [all] service catalog: TNG

On 10/09/2015 12:28 PM, Monty Taylor wrote: On 10/09/2015 11:21 AM, Shamail wrote: On Oct 9, 2015, at 10:39 AM, Sean Dague wrote: It looks like some great conversation got going on the service catalog standardization spec / discussion at the last cross project meeting. Sorry I wasn't there

Re: [openstack-dev] [kolla] Backport policy for Liberty

Hello, Since we have little actual logic, and ansible itself is pretty pluggable by its very nature, backporting should be quite easy and would not affect existing deployment much. We will make sure that it will be safe to have stable/liberty code and will keep working at all times. I agree wit

Re: [openstack-dev] [nova] nova-manage db archive_deleted_rows broken

On 10/07/2015 11:04 AM, Matt Riedemann wrote: I'm wondering why we don't reverse sort the tables using the sqlalchemy metadata object before processing the tables for delete? That's the same thing I did in the 267 migration since we needed to process the tree starting with the leafs and then eve

Re: [openstack-dev] [all] service catalog: TNG

> On Oct 9, 2015, at 12:28 PM, Monty Taylor wrote: > >> On 10/09/2015 11:21 AM, Shamail wrote: >> >> >>> On Oct 9, 2015, at 10:39 AM, Sean Dague wrote: >>> >>> It looks like some great conversation got going on the service catalog >>> standardization spec / discussion at the last cross proj

Re: [openstack-dev] Scheduler proposal

On 08/10/15 21:32, Ian Wells wrote: > 2. if many hosts suit the 5 VMs then this is *very* unlucky,because we should be choosing a host at random from the set of suitable hosts and that's a huge coincidence - so this is a tiny corner case that we shouldn't be designing around He

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

++ on both counts! On Thu, Oct 8, 2015 at 2: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 bas

Re: [openstack-dev] [fuel] PTL & Component Leads elections

Congratulations to Dmitry! Now you are officially titled with PTL. It won't be easy, but we will support you! 118 contributors voted. Thanks everyone! Thank you Sergey for organizing elections for us. On Thu, Oct 8, 2015 at 3:52 PM Sergey Lukjanov wrote: > Voting period ended and so we have an

Re: [openstack-dev] [all] service catalog: TNG

Excerpts from Adam Young's message of 2015-10-09 09:51:55 -0700: > On 10/09/2015 12:28 PM, Monty Taylor wrote: > > On 10/09/2015 11:21 AM, Shamail wrote: > >> > >> > >>> On Oct 9, 2015, at 10:39 AM, Sean Dague wrote: > >>> > >>> It looks like some great conversation got going on the service catalo

Re: [openstack-dev] [all] service catalog: TNG

On Fri, Oct 09, 2015 at 01:01:20PM -0400, Shamail wrote: :> On Oct 9, 2015, at 12:28 PM, Monty Taylor wrote: :> :>> On 10/09/2015 11:21 AM, Shamail wrote: :>> :>> :>>> On Oct 9, 2015, at 10:39 AM, Sean Dague wrote: :>>> :>>> It looks like some great conversation got going on the service catal

Re: [openstack-dev] [Openstack-operators] Scheduler proposal

Excerpts from Chris Friesen's message of 2015-10-08 23:52:41 -0700: > On 10/08/2015 01:37 AM, Clint Byrum wrote: > > Excerpts from Maish Saidel-Keesing's message of 2015-10-08 00:14:55 -0700: > >> Forgive the top-post. > >> > >> Cross-posting to openstack-operators for their feedback as well. > >>

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

Serg, Jeremy, Thank you for your response, so the issue I ran into with my patch is the gate job failing on python26. You can see it here: https://review.openstack.org/#/c/232271/ Serg suggested that we add 2.6 support to tosca-parser, which is fine with us. But I got a bit confused after readi

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

Thierry Carrez wrote on 10/09/2015 05:42:49 AM: ... > So whenever you feel like you made progress, or had a little success in > your OpenStack adventures, or have some joyful moment to share, just > throw the following message on your local IRC channel: > > #success [Your message here] > > The

Re: [openstack-dev] [all] service catalog: TNG

On Fri, Oct 9, 2015 at 1:28 PM, Jonathan D. Proulx wrote: > On Fri, Oct 09, 2015 at 01:01:20PM -0400, Shamail wrote: > :> On Oct 9, 2015, at 12:28 PM, Monty Taylor wrote: > :> > :>> On 10/09/2015 11:21 AM, Shamail wrote: > :>> > :>> > :>>> On Oct 9, 2015, at 10:39 AM, Sean Dague wrote: > :>>> >

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

On Fri, Oct 9, 2015, at 10:32 AM, Vahid S Hashemian wrote: > Serg, Jeremy, > > Thank you for your response, so the issue I ran into with my patch is the > gate job failing on python26. > You can see it here: https://review.openstack.org/#/c/232271/ > > Serg suggested that we add 2.6 support to

Re: [openstack-dev] Scheduler proposal

On 10/09/2015 11:09 AM, Zane Bitter wrote: The optimal way to do this would be a weighted random selection, where the probability of any given host being selected is proportional to its weighting. (Obviously this is limited by the accuracy of the weighting function in expressing your actual pref

Re: [openstack-dev] Scheduler proposal

Excerpts from Chris Friesen's message of 2015-10-09 10:54:36 -0700: > On 10/09/2015 11:09 AM, Zane Bitter wrote: > > > The optimal way to do this would be a weighted random selection, where the > > probability of any given host being selected is proportional to its > > weighting. > > (Obviously t

Re: [openstack-dev] [kolla] Backport policy for Liberty

As an Op, that sounds reasonable so long as they aren't defaulted on. In theory it shouldn't be much different then a distro adding additional packages. The new packages don't affect existing systems unless the op requests them to be installed. With my App Catalog hat on, I'm curious how horizo

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

This sounds good, I was hoping it'd be acceptable to use etherpad. I filed a blueprint [1] but I'm anticipating using the etherpad much more regularly to track which files are being worked or completed. [1] https://blueprints.launchpad.net/heat/+spec/mox-to-mock-conversion [2] https://etherpad.

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

Thank Clark. That really helps. We'll consider this timeline and make a decision on which way to go bearing in mind that waiting for 2.6 phase out would mean a 2 months delay in getting this blueprint implemented. Regards, -

Re: [openstack-dev] [nova] nova-manage db archive_deleted_rows broken

On 10/9/2015 12:03 PM, Jay Pipes wrote: On 10/07/2015 11:04 AM, Matt Riedemann wrote: I'm wondering why we don't reverse sort the tables using the sqlalchemy metadata object before processing the tables for delete? That's the same thing I did in the 267 migration since we needed to process th

Re: [openstack-dev] [all] service catalog: TNG

On 10/09/2015 01:39 PM, David Stanek wrote: On Fri, Oct 9, 2015 at 1:28 PM, Jonathan D. Proulx mailto:j...@csail.mit.edu>> wrote: On Fri, Oct 09, 2015 at 01:01:20PM -0400, Shamail wrote: :> On Oct 9, 2015, at 12:28 PM, Monty Taylor mailto:mord...@inaugust.com>> wrote: :> :>> On

Re: [openstack-dev] Scheduler proposal

Still the point from Chris is valid. I guess the main reason openstack is going with multiple concurrent schedulers is to scale out by distributing the load between multiple instances of schedulers because 1 instance is too slow. This discussion is about coordinating the many instances of schedu

  1   2   >