Re: [openstack-dev] [Monasca] Monasca Meeting @ Tokyo Summit

Hi, On Wed, Oct 14, 2015 at 7:36 AM, Fabio Giannetti (fgiannet) < fgian...@cisco.com> wrote: > Guys, >I have a Cisco room S3 to held a Monasca meeting over the Tokyo Summit. > The time slot is Thursday 4:30pm to 6pm. > Please mark your calendar and see you there. > Fabio > > Will this meeting

Re: [openstack-dev] [all][stable][release] 2015.1.2

> On 13 Oct 2015, at 21:56, Matt Riedemann wrote: > > > > On 10/13/2015 1:57 PM, Chuck Short wrote: >> Hi >> >> Im just in the last stages of release 2015.1.2. I dont think anything is >> stopping us from opening it up agian. The tabrlls have been created. So >> go for it. >> >> Chuck >> >>

Re: [openstack-dev] [puppet][Fuel] Using Native Ruby Client for Openstack Providers

On 14/10/15 10:36, Colleen Murphy wrote: > > > On Tue, Oct 13, 2015 at 6:13 AM, Vladimir Kuklin > wrote: > > Puppetmaster and Fuelers, > > Last week I mentioned that I would like to bring the theme of using > native ruby OpenStack client and use it wi

Re: [openstack-dev] [kuryr] Proposing Taku Fukushima as Kuryr core

+1 On Tue, Oct 13, 2015 at 5:07 PM, Gal Sagie wrote: > +1 > > Taku is a great addition to the team and hoping to see him continue > deliver high quality > contribution in all aspects of the project. > > On Tue, Oct 13, 2015 at 4:52 PM, Antoni Segura Puimedon < > toni+openstac...@midokura.com> w

Re: [openstack-dev] [Neutron][dns]What the meaning of"dns_assignment" and "dns_name"?

Hi, Miguel Thank you so much for your reply. You are so patient! After reading your reply, I still have some questions to ask you. :-) Below, is my opinion about the http://paste.openstack.org/show/476210/, please read it and tell me whether I was right. (1). Define a DNS domain

Re: [openstack-dev] getting rid of tablib completely (Requests + urllib3 + distro packages)

2015-10-14 0:14 GMT+09:00 Doug Hellmann : > Excerpts from Thomas Goirand's message of 2015-10-13 12:38:00 +0200: >> On 10/12/2015 11:09 PM, Steve Baker wrote: >> > On 13/10/15 02:05, Thomas Goirand wrote: >> >> >> >> BTW, the same applies for tablib which is in a even more horrible state >> >> that

[openstack-dev] [Neutron] Functional job instability

Hi folks, There are a number of outstanding stability issues that affect the functional job [1]. No particular bug is a major offender, but taken all together they hurt quite a bit. If we don't get a good handle on this (even on a 'good' day there is a wide gap between the job failure rate and th

[openstack-dev] [Monasca] Monasca Meeting @ Tokyo Summit

Guys, I have a Cisco room S3 to held a Monasca meeting over the Tokyo Summit. The time slot is Thursday 4:30pm to 6pm. Please mark your calendar and see you there. Fabio [http://www.cisco.com/c/dam/assets/email-signature-tool/logo_06.png?ct=1430182397611] Fabio Giannetti Cloud Innovation Archi

Re: [openstack-dev] [Nova] Migration state machine proposal.

On 10/14/2015 11:14 AM, Zhenyu Zheng wrote: I think it will be better if you can submit a spec for your proposal, it will be easier for people to give comment. OK, will submit one soon. Thanks. On Wed, Oct 14, 2015 at 10:05 AM, Tang Chen > wrote: Hi, a

Re: [openstack-dev] [Neutron][dns]What the meaning of "dns_assignment" and "dns_name"?

Zhi Chang, Thank you for your questions. We are in the process of integrating Neutron and Nova with an external DNS service, using Designate as the reference implementation. This integration is being achieved in 3 steps. What you are seeing is the result of only the first one. These steps are: 1)

Re: [openstack-dev] [Nova] Migration state machine proposal.

I think it will be better if you can submit a spec for your proposal, it will be easier for people to give comment. On Wed, Oct 14, 2015 at 10:05 AM, Tang Chen wrote: > Hi, all, > > Please help to review this BP. > > https://blueprints.launchpad.net/nova/+spec/live-migration-state-machine > > >

[openstack-dev] [Nova] Migration state machine proposal.

Hi, all, Please help to review this BP. https://blueprints.launchpad.net/nova/+spec/live-migration-state-machine Currently, the migration_status field in Migration object is indicating the status of migration process. But in the current code, it is represented by pure string, like 'migrating',

[openstack-dev] [Neutron] Revision of the RFE/blueprint submission process

Hi neutrinos, >From last cycle, the team has introduced the concept of RFE bugs [0]. I have suggested a number of refinements over the past few days [1,2,3] to streamline/clarify the process a bit further, also in an attempt to deal with the focus and breadth of the project [4,5]. Having said tha

Re: [openstack-dev] [Neutron] Do not merge until further notice

On 13 October 2015 at 16:55, Hirofumi Ichihara < ichihara.hirof...@lab.ntt.co.jp> wrote: > > > > On 2015/10/14, at 4:07, Armando M. wrote: > > > > Hi folks, > > > > We are in the last hours of Liberty, let's pause for a second and > consider merging patches only if absolutely necessary. The gate

Re: [openstack-dev] [all] FYI - Depends-On vs. backports

Could you put this in the devref? Or getting started or something so this info isn't lost and new devs will be educated? Thanks! --Rocky > -Original Message- > From: Sean Dague [mailto:s...@dague.net] > Sent: Tuesday, October 13, 2015 2:44 AM > To: openstack-dev@lists.openstack.org > S

Re: [openstack-dev] [TripleO] review priorities etherpad

On Tue, 2015-10-13 at 10:32 +0300, marios wrote: > On 10/10/15 00:16, Dan Prince wrote: > > On Thu, 2015-10-08 at 09:17 -0400, James Slagle wrote: > > > At the TripleO meething this week, we talked about using an > > > etherpad > > speaking of which - and given attendance since the time change, >

Re: [openstack-dev] [tc] projects.yaml (project since data)

Sure. Thanks. > On Oct 13, 2015, at 8:55 PM, Robert Collins wrote: > > Makes sense to me. Care to propose such a change to the repo? > >> On 14 October 2015 at 11:53, Shamail Tahir wrote: >> Hi, >> >> In the older integrated release model we used to have a field that showed >> "integrated-si

Re: [openstack-dev] [TripleO] Auto-abandon bot

On Mon, 2015-10-12 at 11:38 -0500, Ben Nemec wrote: > On 10/10/2015 08:12 AM, Jeremy Stanley wrote: > > On 2015-10-09 17:10:15 -0500 (-0500), Ben Nemec wrote: > > > As discussed in the meeting a week or two ago, we would like to > > > bring > > > back the auto-abandon functionality for old, unloved

Re: [openstack-dev] [tc] projects.yaml (project since data)

Makes sense to me. Care to propose such a change to the repo? On 14 October 2015 at 11:53, Shamail Tahir wrote: > Hi, > > In the older integrated release model we used to have a field that showed > "integrated-since" data about a project. I was just reviewing the current > projects.yaml[1] file

[openstack-dev] [infra] Upgrade to Gerrit 2.11

Hello All, The openstack-infra team would like to upgrade from our Gerrit 2.8 to Gerrit 2.11. We are proposing to do the upgrade shortly after the Mitaka summit. The main motivation behind the upgrade is to allow us to take advantage of some of the new REST api, ssh commands, and stream events f

Re: [openstack-dev] [Neutron] Do not merge until further notice

> On 2015/10/14, at 4:07, Armando M. wrote: > > Hi folks, > > We are in the last hours of Liberty, let's pause for a second and consider > merging patches only if absolutely necessary. The gate is getting clogged and > we need to give priority to potential RC3 fixes or gate stability fixes.

Re: [openstack-dev] [puppet][Fuel] Using Native Ruby Client for Openstack Providers

On Tue, Oct 13, 2015 at 6:13 AM, Vladimir Kuklin wrote: > Puppetmaster and Fuelers, > > Last week I mentioned that I would like to bring the theme of using native > ruby OpenStack client and use it within the providers. > > Emilien told me that I had already been late and the decision was made >

Re: [openstack-dev] [OpenStack-docs][Neutron] Networking Guide - Call for contributors

Thanks my friend! Edgar From: "John Davidge (jodavidg)" Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Tuesday, October 13, 2015 at 8:55 AM To: "OpenStack Development Mailing List (not for usage questions)" Subject: Re: [openstack-dev] [OpenStack-docs][Neutron] Net

[openstack-dev] [tc] projects.yaml (project since data)

Hi, In the older integrated release model we used to have a field that showed "integrated-since" data about a project. I was just reviewing the current projects.yaml[1] file and noticed that there is no information in there that shows how long a project has been under OpenStack governance. That

Re: [openstack-dev] [Zaqar][cli][openstackclient] conflict in nova flavor and zaqar flavor

On 10/13/2015 05:15 PM, Dean Troyer wrote: On Tue, Oct 13, 2015 at 3:58 PM, Shifali Agrawal mailto:shaifali.agrawa...@gmail.com>> wrote: All above make sense, just one thing, how about using word "zaqar" instead of messaging? That is what all other projects are doing, for example:

Re: [openstack-dev] [Zaqar][cli][openstackclient] conflict in nova flavor and zaqar flavor

On 14/10/15 10:15, Dean Troyer wrote: On Tue, Oct 13, 2015 at 3:58 PM, Shifali Agrawal mailto:shaifali.agrawa...@gmail.com>> wrote: All above make sense, just one thing, how about using word "zaqar" instead of messaging? That is what all other projects are doing, for example: Th

[openstack-dev] [ptl][release] communication during mitaka

PTLs and release liaisons This is the first of what will likely be several emails describing differences in the way we will be handling release management for the Mitaka cycle. To start I want to make sure the expectations for communication are clear to everyone so there is no confusion or miscomm

[openstack-dev] [Nova][Cinder][Manila] Liberty RC3 available

Hello everyone, Due to Murphy's law and a mix of not-so-fun dependencies issues, we just respinned a release candidate for Nova, Cinder and Manila. The list of RC3 fixes, as well as RC3 tarballs are available at: https://launchpad.net/nova/liberty/liberty-rc3 https://launchpad.net/cinder/liberty/

Re: [openstack-dev] Cross-project meeting, Tue Oct 13th, 21:00 UTC

On 10/12/2015 10:33 AM, Emilien Macchi wrote: > Dear PTLs, cross-project liaisons, and interested team members, > > We'll have a cross-project meeting tomorrow at 21:00 UTC, with the > following agenda: > > https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting#Proposed_agenda > > * Re

Re: [openstack-dev] [Zaqar][cli][openstackclient] conflict in nova flavor and zaqar flavor

On Tue, Oct 13, 2015 at 3:58 PM, Shifali Agrawal < shaifali.agrawa...@gmail.com> wrote: > All above make sense, just one thing, how about using word "zaqar" > instead of messaging? That is what all other projects are doing, for > example: > These are the old project-specific CLIs, note that the

Re: [openstack-dev] [cinder] RemoteFS drivers refactoring: move code, which works with images to separate classes

On Tue, Oct 13, 2015 at 07:01:45PM +, D'Angelo, Scott wrote: > If you create a blueprint and a spec for this, the details can be discussed > in the spec. Yes, something like this we should definitely have a spec and blueprint for. Please write up a spec and propose to the cinder-specs repo so

Re: [openstack-dev] [puppet] Proposing Denis Egorenko core

On Tue, Oct 13, 2015 at 2:29 PM, Emilien Macchi wrote: > Denis Egorenko (degorenko) is working on Puppet OpenStack modules for > quite some time now. > > Some statistics [1] about his contributions (last 6 months): > * 270 reviews > * 49 negative reviews > * 216 positive reviews > * 36 disagreeme

Re: [openstack-dev] [Zaqar][cli][openstackclient] conflict in nova flavor and zaqar flavor

On Tue, Oct 13, 2015 at 12:05 PM, Flavio Percoco wrote: > On 12/10/15 19:25 -0300, Victoria Martínez de la Cruz wrote: > >> HI all, >> >> Thanks for your feedback. We discussed this topic in this week weekly >> meeting >> and we came to the conclusion that it would be better to use "pool-flavor"

Re: [openstack-dev] [Fuel] Changes in bugs workflow on Launchpad

Dima What I think is that we need to somehow group the bugs so that after they are initially triaged particular component developers can understand which bugs to get from the pool of unassigned bugs. Could you please show how you are going to tackle this? On Tue, Oct 13, 2015 at 11:24 PM, Mike Sc

[openstack-dev] [fuel] Component Leads elections

Fuelers, Please remember that the open candidacy period for Fuel Component Leads nominations is now open. It closes in two days, on October 15. [0] [0] https://wiki.openstack.org/wiki/Fuel/Elections_Fall_2015 We already have one nomination for fuel-python lead [1], thank you Igor for volunteerin

[openstack-dev] [puppet] Proposing Denis Egorenko core

Denis Egorenko (degorenko) is working on Puppet OpenStack modules for quite some time now. Some statistics [1] about his contributions (last 6 months): * 270 reviews * 49 negative reviews * 216 positive reviews * 36 disagreements * 30 commits Beside stats, Denis is always here on IRC participatin

Re: [openstack-dev] [Fuel] Changes in bugs workflow on Launchpad

Dmitry, I think that #1 is reasonable. For #2, separate LP projects, I'd want to assess pros/cons before making a decision. I see more cons at the moment. I've started adding it in the etherpad, I'd appreciate if other folks would join and provide their input there. Thank you, On Tue, Oct 13, 201

Re: [openstack-dev] [puppet][Fuel] Using Native Ruby Client for Openstack Providers

On 10/13/2015 01:49 PM, Dean Troyer wrote: On Tue, Oct 13, 2015 at 10:33 AM, Rich Megginson > wrote: I think if we did end up using a ruby library, we'd also want to make sure it was not only vendored, but also usable independently, to increase the audien

Re: [openstack-dev] [puppet][Fuel] OpenstackLib Client Provider Better Exception Handling

On 10/13/2015 12:57 PM, Emilien Macchi wrote: On 10/08/2015 07:38 AM, Vladimir Kuklin wrote: [...] * Proposed solution Introduce a library of exception handling methods which should be the same for all puppet openstack providers as these exceptions seem to be generic. Then, for each of the pro

Re: [openstack-dev] [all][stable][release] 2015.1.2

On 10/13/2015 02:57 PM, Chuck Short wrote: > Hi > > Im just in the last stages of release 2015.1.2. I dont think anything is > stopping us from opening it up agian. The tabrlls have been created. So > go for it. Chuck, I think that whoever sets the tag should also push those fixes. We had some k

Re: [openstack-dev] [all][stable][release] 2015.1.2

On 10/13/2015 1:57 PM, Chuck Short wrote: Hi Im just in the last stages of release 2015.1.2. I dont think anything is stopping us from opening it up agian. The tabrlls have been created. So go for it. Chuck On Tue, Oct 13, 2015 at 2:46 PM, Matt Riedemann mailto:mrie...@linux.vnet.ibm.com>> w

Re: [openstack-dev] [puppet][Fuel] Using Native Ruby Client for Openstack Providers

On Tue, Oct 13, 2015 at 10:33 AM, Rich Megginson wrote: > I think if we did end up using a ruby library, we'd also want to make sure > it was not only vendored, but also usable independently, to increase the > audience. > > > . . . and then are we also going to be gated by the distros in the same

Re: [openstack-dev] getting rid of tablib completely (Requests + urllib3 + distro packages)

On Tue, Oct 13, 2015 at 10:14 AM, Doug Hellmann wrote: > Now that we have a cliff with the formatters provided by tablib, we can > update those dependencies to remove cliff-tablib. Someone just needs to > follow through on that with patches to the requirements files for the > clients. For OpenS

Re: [openstack-dev] [cinder] RemoteFS drivers refactoring: move code, which works with images to separate classes

On 10/13/2015 02:57 PM, Dmitry Guryanov wrote: > Hello, > > RemoteFS drivers combine 2 logical tasks. The first one is how to mount > a filesystem and select proper share for a new or existing volume. The > second one: how to deal with an image files in given directory (mount > point) (create, del

Re: [openstack-dev] [all][stable][release] 2015.1.2

On 10/13/2015 01:46 PM, Matt Riedemann wrote: > > > On 10/7/2015 7:42 PM, Chuck Short wrote: >> Hi, >> stable/kilo is now frozen. I expect to do a release on Tuesday. If you >> need to include something please let me know. >> >> Thanks >> chuck >> >> >> ___

[openstack-dev] [Neutron] Do not merge until further notice

Hi folks, We are in the last hours of Liberty, let's pause for a second and consider merging patches only if absolutely necessary. The gate is getting clogged and we need to give priority to potential RC3 fixes or gate stability fixes. Thanks, Armando _

Re: [openstack-dev] [cinder] RemoteFS drivers refactoring: move code, which works with images to separate classes

If you create a blueprint and a spec for this, the details can be discussed in the spec. -Original Message- From: Dmitry Guryanov [mailto:dgurya...@virtuozzo.com] Sent: Tuesday, October 13, 2015 12:57 PM To: OpenStack Development Mailing List; Maxim Nestratov Subject: [openstack-dev] [ci

Re: [openstack-dev] [puppet] WARNING - breaking backwards compatibility in puppet-keystone

As a quick note, we decided during our weekly meeting to move forward with that patch and accept some use-cases are not backward compatible that time. Reviewers, please look at the code and vote for it. Thanks, On 10/12/2015 01:53 AM, Gilles Dubreuil wrote: > > > On 08/10/15 07:17, Rich Meggins

Re: [openstack-dev] [all][stable][release] 2015.1.2

Hi Im just in the last stages of release 2015.1.2. I dont think anything is stopping us from opening it up agian. The tabrlls have been created. So go for it. Chuck On Tue, Oct 13, 2015 at 2:46 PM, Matt Riedemann wrote: > > > On 10/7/2015 7:42 PM, Chuck Short wrote: > >> Hi, >> stable/kilo is

Re: [openstack-dev] [puppet][Fuel] OpenstackLib Client Provider Better Exception Handling

On 10/08/2015 07:38 AM, Vladimir Kuklin wrote: [...] > * Proposed solution > > Introduce a library of exception handling methods which should be the > same for all puppet openstack providers as these exceptions seem to be > generic. Then, for each of the providers we can introduce > provider-spe

[openstack-dev] [cinder] RemoteFS drivers refactoring: move code, which works with images to separate classes

Hello, RemoteFS drivers combine 2 logical tasks. The first one is how to mount a filesystem and select proper share for a new or existing volume. The second one: how to deal with an image files in given directory (mount point) (create, delete, create snapshot e.t.c.). The first part is diffe

[openstack-dev] [openstack-ansible][security] All STIGs proposed -- time for reviews!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello there, Thanks again to everyone who is helping to make openstack-ansible-security better! Various members of the openstack-ansible team, the security team, and other OpenStack contributors have been providing help with reviews and reaching

Re: [openstack-dev] [all][stable][release] 2015.1.2

On 10/7/2015 7:42 PM, Chuck Short wrote: Hi, stable/kilo is now frozen. I expect to do a release on Tuesday. If you need to include something please let me know. Thanks chuck __ OpenStack Development Mailing List (not fo

[openstack-dev] [Fuel] Changes in bugs workflow on Launchpad

Guys, I propose several changes in bugs workflow on Launchpad. 1) Let's stop using component based team groups as assignees for bugs 2) Let's create separate Launchpad projects for qa, docs and infra teams It will affect everyone who tracks any list of bugs. So I want to be sure that everyone can

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

Thank you, Olga! On Tue, Oct 13, 2015 at 1:58 AM, Olga Gusarenko wrote: > More than 5 days passed, and no objections. > Congratulations, Svetlana, and welcome on board =) ! > > On Fri, Oct 9, 2015 at 9:44 AM, Olga Gusarenko > wrote: > >> +1 >> Svetlana, thank you for your contribution, and look

Re: [openstack-dev] [tc] New project: rally-ci

On 2015-10-13 20:20:43 +0300 (+0300), Sergey Skripnick wrote: [...] > It sounds much like zuul but it is not zuul. The primary goal of > rally-ci is simpleness. [...] First of all Rally-CI is simple way > to get up and running Third Party CI. [...] Little tutorial "How > to run third party CI on a

Re: [openstack-dev] Scheduler proposal

On 2015-10-13 10:17:26 -0700 (-0700), Joshua Harlow wrote: [...] > Interesting, doesn't the foundation have money? I was under the > assumption it does (but I'm not a finance person); seeing that the > membership fee to become a member afaik is not cheap, and there > seems to be quite a-lot of memb

Re: [openstack-dev] Scheduler proposal

Clint Byrum wrote: Excerpts from Ian Wells's message of 2015-10-13 09:24:42 -0700: On 12 October 2015 at 21:18, Clint Byrum wrote: We _would_ keep a local cache of the information in the schedulers. The centralized copy of it is to free the schedulers from the complexity of having to keep tra

[openstack-dev] [tc] New project: rally-ci

Rally-CI is single daemon which listens gerrit events, run tests and publish results. It sounds much like zuul but it is not zuul. The primary goal of rally-ci is simpleness. It does not any git merges, it have not any complex pipeline logic. Just test every single CR and put +1 or -1. First of a

Re: [openstack-dev] Scheduler proposal

Clint Byrum wrote: Excerpts from Jeremy Stanley's message of 2015-10-13 06:13:32 -0700: On 2015-10-12 20:49:44 -0700 (-0700), Joshua Harlow wrote: Does the openstack foundation have access to a scaling area that can be used by the community for this kind of experimental work? The OpenStack Fou

[openstack-dev] [ironic] weekly subteam status report

Hi, Following is the subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) - (diff with Oct 5, no diff for inspector) - Open: 143 (+6). 2 new (-2), 36 in progress (+2), 0 critical, 12 high (+5) and 10 incomplete

[openstack-dev] [magnum] Networking Subteam Meeting Cancelations

All, I have a conflict this week and will be unable to chair the weekly irc meeting [1]. Therefore, we will not meet this week. 10/22 and 10/29 meetings will also be canceled due to the Mitaka Design Summit. We will resume are regularly scheduled meetings on 11/5. [1] https://wiki.openstack.o

Re: [openstack-dev] Scheduler proposal

Excerpts from Ian Wells's message of 2015-10-13 09:24:42 -0700: > On 12 October 2015 at 21:18, Clint Byrum wrote: > > > We _would_ keep a local cache of the information in the schedulers. The > > centralized copy of it is to free the schedulers from the complexity of > > having to keep track of i

Re: [openstack-dev] [neutron-LBaaS] Can anyone help to share a procedure to install lbaas on Kilo?

Ah, in that case try this: https://wiki.openstack.org/wiki/Neutron/LBaaS/HowToRun On Oct 13, 2015, at 15:05, WANG, Ming Hao (Tony T) mailto:tony.a.w...@alcatel-lucent.com>> wrote: Kobi, Thanks for your info very much! Is there any document to install lbaas manually? My environment is installed

Re: [openstack-dev] Scheduler proposal

On 12 October 2015 at 21:18, Clint Byrum wrote: > We _would_ keep a local cache of the information in the schedulers. The > centralized copy of it is to free the schedulers from the complexity of > having to keep track of it as state, rather than as a cache. We also don't > have to provide a way

Re: [openstack-dev] Scheduler proposal

On 2015-10-13 09:15:02 -0700 (-0700), Clint Byrum wrote: > Excerpts from Jeremy Stanley's message of 2015-10-13 06:13:32 -0700: [...] > > it's not even within an order of magnitude of being 1k host > > scale (and at that, it's still a multi-cycle plan just to reach > > viability). > > Infra-cloud

Re: [openstack-dev] Scheduler proposal

Excerpts from Dulko, Michal's message of 2015-10-13 03:49:44 -0700: > On Mon, 2015-10-12 at 10:13 -0700, Clint Byrum wrote: > > Zookeeper sits in a very different space from Cassandra. I have had good > > success with it on OpenJDK as well. > > > > That said, we need to maybe go through some featu

Re: [openstack-dev] Scheduler proposal

Excerpts from Jeremy Stanley's message of 2015-10-13 06:13:32 -0700: > On 2015-10-12 20:49:44 -0700 (-0700), Joshua Harlow wrote: > > Does the openstack foundation have access to a scaling area that > > can be used by the community for this kind of experimental work? > > The OpenStack Foundation h

Re: [openstack-dev] [puppet] weekly meeting #55

On 10/12/2015 10:36 AM, Emilien Macchi wrote: > Hello! > > Here's an initial agenda for our weekly meeting, tomorrow at 1500 UTC > in #openstack-meeting-4: > > https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20151013 > > Feel free to add any item

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

Thomas Goirand wrote: On 10/13/2015 12:44 AM, Joshua Harlow wrote: Anvil gets somewhat far on this, although its not supporting DEBs it does build its best attempt at RPMs building them automatically and turning git repos of projects into RPMs. http://anvil.readthedocs.org/en/latest/topics/summ

Re: [openstack-dev] [Zaqar][cli][openstackclient] conflict in nova flavor and zaqar flavor

On 13/10/15 16:46, Fox, Kevin M wrote: > lb's use the term pools too. A little more specific might be good. > > Thanks, > Kevin > > *From:* Victoria Martínez de la Cruz [victo...@vmartinezdelacruz.com] > *Sent:* Tuesday, Octo

Re: [openstack-dev] [OpenStack-docs][Neutron] Networking Guide - Call for contributors

Hi Edgar, Happy to continue contributing here. Currently in GMT timezone, but probably PST by the end of the year. Looking forward to the first meeting! Cheers, John Davidge From: Edgar Magana mailto:edgar.mag...@workday.com>> Reply-To: "OpenStack Development Mailing List (not for usage quest

Re: [openstack-dev] Scheduler proposal

Well great! When is that going to be accessible :-P Dulko, Michal wrote: On Mon, 2015-10-12 at 10:58 -0700, Joshua Harlow wrote: Just a related thought/question. It really seems we (as a community) need some kind of scale testing ground. Internally at yahoo we were/are going to use a 200 hyper

Re: [openstack-dev] Scheduler proposal

Jeremy Stanley wrote: On 2015-10-12 20:49:44 -0700 (-0700), Joshua Harlow wrote: Does the openstack foundation have access to a scaling area that can be used by the community for this kind of experimental work? The OpenStack Foundation has a staff of fewer than 20 full-time employees, with a p

Re: [openstack-dev] [Zaqar][cli][openstackclient] conflict in nova flavor and zaqar flavor

lb's use the term pools too. A little more specific might be good. Thanks, Kevin From: Victoria Martínez de la Cruz [victo...@vmartinezdelacruz.com] Sent: Tuesday, October 13, 2015 5:28 AM To: Flavio Percoco; OpenStack Development Mailing List (not for usage questi

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

On 10/08/2015 07:39 PM, Robert Collins wrote: > This is a bugbear that keeps cropping up and biting us. I'm hoping we > can figure out a permanent fix. > > The problem that occurs is the result of a few interacting things: > - requests has very very specific versions of urllib3 it works with. > S

Re: [openstack-dev] [sahara] Proposing Vitaly Gridnev to core reviewer team

+1! On 10/12/2015 07:19 AM, Sergey Lukjanov wrote: Hi folks, I'd like to propose Vitaly Gridnev as a member of the Sahara core reviewer team. Vitaly contributing to Sahara for a long time and doing a great job on reviewing and improving Sahara. Here are the statistics for reviews [0][1][2] and

Re: [openstack-dev] [puppet][Fuel] Using Native Ruby Client for Openstack Providers

On 10/13/2015 09:22 AM, Clayton O'Neill wrote: I agree that ideally, using a native ruby library would be better, but I also share Matt's concern. We'd need a commitment from more than one person to maintain the library if we went that route. I think the big advantages I see with the ruby cli

Re: [openstack-dev] [puppet][Fuel] Using Native Ruby Client for Openstack Providers

set of providers and allow users and operators to pick whichever they want 4) we leave OpenStackClient default one Would you support it and allow such code to be merged into upstream puppet-openstack modules? I would be in favor of such a plan if https://etherpad.opensta

Re: [openstack-dev] [puppet][Fuel] Using Native Ruby Client for Openstack Providers

I agree that ideally, using a native ruby library would be better, but I also share Matt's concern. We'd need a commitment from more than one person to maintain the library if we went that route. I think the big advantages I see with the ruby client would be: - Potentially better performance

Re: [openstack-dev] [puppet][Fuel] Using Native Ruby Client for Openstack Providers

Matt Thanks for your input. So, I mentioned the following - Fuel guys can contribute into Ruby client for OpenStack as we are also interested in making it faster. That's why I asked for support in case we invest substantial effort (as we do not want to waste our time on things that will not land i

Re: [openstack-dev] [puppet][Fuel] Using Native Ruby Client for Openstack Providers

se up to the level that it > eliminates issues that are mentioned in 'Cons' section > 3) we introduce additional set of providers and allow users and operators > to pick whichever they want > 4) we leave OpenStackClient default one > > Would you support it and allow su

Re: [openstack-dev] getting rid of tablib completely (Requests + urllib3 + distro packages)

Excerpts from Thomas Goirand's message of 2015-10-13 12:38:00 +0200: > On 10/12/2015 11:09 PM, Steve Baker wrote: > > On 13/10/15 02:05, Thomas Goirand wrote: > >> > >> BTW, the same applies for tablib which is in a even more horrible state > >> that makes it impossible to package with Py3 support.

Re: [openstack-dev] [puppet][Fuel] Using Native Ruby Client for Openstack Providers

>From a technical point of view, not forking and using a native library makes total sense. I think it would likely be faster and certainly cleaner than parsing output. Unfortunately I don't think that we have the resources to actively maintain the library. I think that's the main blocker for me. O

Re: [openstack-dev] Scheduler proposal

On 10/12/15, 12:05 PM, "Monty Taylor" wrote: >On 10/12/2015 02:45 PM, Joshua Harlow wrote: >> Alec Hothan (ahothan) wrote: >>> >>> >>> >>> > >I want to do 100k hypervisors. No, that's not hyperbole. > >Also, I do not think that ZK/consul/etcd are very costly for small >deployments. Given th

[openstack-dev] [Neutron][dns]What the meaning of "dns_assignment" and "dns_name"?

Hi, all I install the latest devstack and create a vm by nova. I get the port's info which created by Neutron. I'm confused that what the meaning of column "dns_assignment" and column "dns_name". First, column "dns_assignment" is a read-only attribute. What is it used for? I think that t

[openstack-dev] [neutron][fwaas] fwaas driver development steps

Hi, I need to write a driver for our friewall hardware to integrate it to our Openstack environment. I checked the Neutron Development wiki page, FWaaS wiki page, fwaas driver codes written at the Github. Since there is no clear documentation about howto write a direwall driver for Neutron i need

Re: [openstack-dev] Proposed solution to "Admin" ness improperly scoped:

On 10/13/2015 12:15 AM, Shinobu Kinjo wrote: Sorry for my lack of explanation. Are the both scopes of admin and non-admin totally different? Is each project not nested in admin scope like: So, a couple terms: We use the term 'scope' to refer to the project. Think of this as a container that h

Re: [openstack-dev] [all] Cross-project track schedule draft: Feedback needed

On Tue, Oct 13, 2015 at 3:18 AM, Thierry Carrez wrote: > Flavio Percoco wrote: > > We have a draft schedule for the cross-project track for the Mitaka > > summit[0] (find it at the bottom of the etherpad). Yay! > > > > We would like to get feedback from folks that have proposed these > > sessions

Re: [openstack-dev] [puppet][Fuel] Using Native Ruby Client for Openstack Providers

uld be in favor of such a plan if https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20151013 questions 0.4.1-0.4.7 could be answered in the affirmative. [0] https://groups.google.com/a/puppetlabs.com/forum/#!searchin/puppet-openstack/aviator$20openstackclient/puppet-openstack/GJwDHNAFVYw/

Re: [openstack-dev] [kuryr] Proposing Taku Fukushima as Kuryr core

+1 Taku is a great addition to the team and hoping to see him continue deliver high quality contribution in all aspects of the project. On Tue, Oct 13, 2015 at 4:52 PM, Antoni Segura Puimedon < toni+openstac...@midokura.com> wrote: > Hi fellow Kurýrs, > > I would like to propose Taku Fukushima f

Re: [openstack-dev] From where will start particiption in Neutron Component?

On Tue, Oct 13, 2015 at 1:41 AM, Neil Jerram wrote: > On 13/10/15 08:45, chandraprakash mishra wrote: > > Hi Folks, > > > > I have just started looking OpenStack ,As of now i would like to start > > participation for neutron component . So where can i start participate > > for neutron component .

[openstack-dev] [kuryr] Proposing Taku Fukushima as Kuryr core

Hi fellow Kurýrs, I would like to propose Taku Fukushima for the core Kuryr team due to his unparalleled dedication to the project. He has written most of the code and battled through the continuous libnetwork API changes. He will be a great addition to the reviewing tasks. Current core members,

[openstack-dev] [cinder][glance] Completion of Glance store's driver for Cinder

Greetings, Another review request from Glance's land. There's a spec proposing to use os-brick to complete glance_store's driver for Cinder. YAY! Some reviews have been done from Glance's side but I believe it could use some extra eyes from the Cinder side. https://review.openstack.org/#/c/183

Re: [openstack-dev] The state of systemd _sd_notify & oslo.service in OpenStack

For neutron-server, we use notify type since very long time, ~ RDO Icehouse. https://github.com/openstack-packages/neutron/blob/rpm-master/neutron-server.service#L6 > On 13 Oct 2015, at 09:01, Thomas Goirand wrote: > > Hi, > > As oslo.service implements _sd_notify, I am deeply thinking about >

[openstack-dev] [puppet][Fuel] Using Native Ruby Client for Openstack Providers

Puppetmaster and Fuelers, Last week I mentioned that I would like to bring the theme of using native ruby OpenStack client and use it within the providers. Emilien told me that I had already been late and the decision was made that puppet-openstack decided to not work with Aviator based on [0]. I

Re: [openstack-dev] Scheduler proposal

On 2015-10-12 20:49:44 -0700 (-0700), Joshua Harlow wrote: > Does the openstack foundation have access to a scaling area that > can be used by the community for this kind of experimental work? The OpenStack Foundation has a staff of fewer than 20 full-time employees, with a primary focus on event

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

Congrats Dmitry! Well deserved. > On 09 Oct 2015, at 19:13, Mike Scherbakov wrote: > > 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

Re: [openstack-dev] [Zaqar][cli][openstackclient] conflict in nova flavor and zaqar flavor

Fair enough, +1 to Flavio's suggestion Thanks all, Victoria 2015-10-13 3:35 GMT-03:00 Flavio Percoco : > On 12/10/15 19:25 -0300, Victoria Martínez de la Cruz wrote: > >> HI all, >> >> Thanks for your feedback. We discussed this topic in this week weekly >> meeting >> and we came to the conclus

Re: [openstack-dev] The state of systemd _sd_notify & oslo.service in OpenStack

Hi, We used a Launchpad bug [1] to track the process of moving to graduated oslo.service so you can refer to the list of affected projects. _sd_notify is called when a service is launched just before a wait loop [2], [3] so you can check projects from [1] and look for those that start services us

  1   2   >