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

On 10/15/2015 12:18 AM, Robert Collins wrote: > On 15 October 2015 at 11:11, Thomas Goirand wrote: >> >> One major pain point is unfortunately something ridiculously easy to >> fix, but which nobody seems to care about: the long & short descriptions >> format. These are usually buried into the set

[openstack-dev] ?????? [keystone federation] some questions aboutkeystone IDP with SAML supported

Many Thanks! John, I agree with you. Keystone is not a general purpose federated IdP. "Web application could use SAML HTTP-Redirect or it could also function as an ECP client." Now Keystone supports token, saml2, oauth1. There is aslo a keystone plugin project try to support oauth2. But Keys

[openstack-dev] [nova] expose quiesce unquiesce api

Hi, Currently the Nova provides VM snapshot API, which will take a consistency snapshot of a VM and regarding volumes, and will quiesce/unquiesce VM automatily with guest agent support. We learned that the exposure of quiesce/unquiesce api in Nova was "abandoned" in the history. Now we have th

Re: [openstack-dev] [devstack] A few questions on configuring DevStack for Neutron

Matt Riedemann wrote on 10/08/2015 09:48:33 PM: > On 10/8/2015 11:38 AM, Sean M. Collins wrote: > > Please see my response here: > > > > http://lists.openstack.org/pipermail/openstack-dev/2015-October/076251.html > > > > In the future, do not create multiple threads since responses will get >

[openstack-dev] [Openstack] Tokyo Summit Survey: Experience Deploying CloudFoundry in OpenStack

Hi, OpenStack users and developers,   In our continued commitment to make CF the ONE true cross-cloud PaaS, we have been wondering what your experience was when deploying CF onto OpenStack using BOSH.   We created this short survey: https://www.surveymonkey.com/r/VQQZ5ZP to aggregate your experienc

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

On Thu, Oct 8, 2015 at 5:38 AM, Vladimir Kuklin wrote: > Hi, folks > > * Intro > > Per our discussion at Meeting #54 [0] I would like to propose the uniform > approach of exception handling for all puppet-openstack providers accessing > any types of OpenStack APIs. > > * Problem Description > > W

Re: [openstack-dev] [Ironic] backwards compat issue with PXEDeply and AgentDeploy drivers

One more try on the ops list as it turns out I wasn't subscribed... :( // jim > On Oct 14, 2015, at 17:39, Jim Rollenhagen wrote: > > Cross posting to the ops list for visibility. > > To follow up on this, we decided not to fix this after all. Besides > Ramesh's (very valid) points below, we

[openstack-dev] [ironic] Ironic design summit schedule

Hey all, I sorted out the design summit schedule today, attempting to reduce conflicts and such as much as possible. The schedule is here: http://mitakadesignsummit.sched.org/type/Ironic I created a general summit etherpad for us, that is here: https://etherpad.openstack.org/p/summit-mitaka-iron

Re: [openstack-dev] [release] establishing release liaisons for mitaka

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 15/10/15 01:25, Doug Hellmann wrote: > As with the other cross-project teams, the release management team > relies on liaisons from each project to be available for coordination of > work across all teams. It's the start of a new cycle, so it's ti

Re: [openstack-dev] [Ironic] backwards compat issue with PXEDeply and AgentDeploy drivers

Cross posting to the ops list for visibility. To follow up on this, we decided not to fix this after all. Besides Ramesh's (very valid) points below, we realized that fixing this for out of tree drivers that depended on Kilo behavior would break out of tree drivers that implemented their own boot

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

On 10/14/2015 11:08 AM, Zaro wrote: We are soliciting feedback so please let us know what you think. Since you asked :) Mostly it's just different which is fine. Two things I noticed when playing around, shown in [1] When reviewing, the order "-1 0 +1" is kind of counter-intuitive to the usu

Re: [openstack-dev] [keystone] [puppet] [neutron] Deprecating nova_admin_ options in puppet-neutron

On re-reading the original email i've been thinking of auth_token middleware rather than nova_admin_* options (i haven't done much neutron config). I think everything still applies though and hopefully this can be a mechanism that's reused across modules. On 15 October 2015 at 10:37, Jamie Lennox

Re: [openstack-dev] [ironic] The scenary to rolling upgrade Ironic

On Wed, Oct 14, 2015 at 04:09:07PM -0700, Dan Smith wrote: > > Conductors will always need to talk to the database. APIs may not need > > to talk to the database. I think we can just roll conductor > > upgrades through, and then update ironic-api after that. This should > > just work, as long as we

[openstack-dev] [Searchlight] Mitaka summit schedule

Hello Search Enthusiasts, Our conference and summit schedule events are now loaded into the system. Main conference presentation and demo: [1] Introducing OpenStack Searchlight - Search your cloud at the speed of light! Design Summit: [2] Prioritizing Search Integrations and Capabilities (

Re: [openstack-dev] [keystone] [puppet] [neutron] Deprecating nova_admin_ options in puppet-neutron

TL;DR: you can fairly easily convert existing puppet params into auth plugin format for now, but we're going to need the hash based config soon. I think as a first step it is a good idea to replace the deprecated options and use the password, v2password or v3password plugins* because you will need

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/14/2015 07:07 PM, Tony Breeds wrote: > On Tue, Oct 13, 2015 at 05:08:29PM -0700, Zaro wrote: >> 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 >>

Re: [openstack-dev] [OpenStack-Infra] [infra] Infra Design Summit Schedule

On 10/14/2015 07:13 PM, Jeremy Stanley wrote: > Based on feedback from our last meeting and the discussion and > subsequent voting in our session ideas pad, I've taken a first pass > at scheduling: > > http://mitakadesignsummit.sched.org/type/Infrastructure > > I did the best I could to avoid

[openstack-dev] [infra] Infra Design Summit Schedule

Based on feedback from our last meeting and the discussion and subsequent voting in our session ideas pad, I've taken a first pass at scheduling: http://mitakadesignsummit.sched.org/type/Infrastructure I did the best I could to avoid obvious conflicts where necessary participants were likely

Re: [openstack-dev] [ironic] The scenary to rolling upgrade Ironic

> Conductors will always need to talk to the database. APIs may not need > to talk to the database. I think we can just roll conductor > upgrades through, and then update ironic-api after that. This should > just work, as long as we're very careful about schema changes (this is > where the expand/c

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

Hi Oğuz, YES this is open to everybody. Thanks, Fabio [http://www.cisco.com/c/dam/assets/email-signature-tool/logo_06.png?ct=1430182397611] Fabio Giannetti Cloud Innovation Architect Cisco Services fgian...@cisco.com Phone: +1 408 527 1134 Mobile: +1 408 854 0020 C

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

On Tue, Oct 13, 2015 at 05:08:29PM -0700, Zaro wrote: > 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 advant

Re: [openstack-dev] [ironic] The scenary to rolling upgrade Ironic

On Wed, Oct 14, 2015 at 08:44:08AM +, Tan, Lin wrote: > Hi guys, > > I am looking at https://bugs.launchpad.net/ironic/+bug/1502903 which > is related to rolling upgrade and here is Jim's patch > https://review.openstack.org/#/c/234450 I really have a concern or > question about how to do Iron

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

Zhi Chang, You got all the steps correct. A few clarifications: 1. Address 104.130.78.191 is the ip address of my devstack VM. When you deploy Designate in devstack, it starts an instance of PowerDNS for you. Designate then pushes all its zones and records to that PowerDNS instance.

Re: [openstack-dev] [magnum] Creating pods results in "EOF occurred in violation of protocol" exception

Hi Bertrand, Thanks for reporting the error. I confirmed that this error was consistently reproducible. A bug ticket was created for that. https://bugs.launchpad.net/magnum/+bug/1506226 Best regards, Hongbin -Original Message- From: Bertrand NOEL [mailto:bertrand.n...@cern.ch] Sent: O

Re: [openstack-dev] Scheduler proposal

On 10/12/2015 07:10 PM, Monty Taylor wrote: > On 10/12/2015 12:43 PM, Clint Byrum wrote: >> Excerpts from Thomas Goirand's message of 2015-10-12 05:57:26 -0700: >>> On 10/11/2015 02:53 AM, Davanum Srinivas wrote: Thomas, i am curious as well. AFAIK, cassandra works well with OpenJDK.

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

On 10/13/2015 09:41 PM, Dean Troyer wrote: > 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 > f

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

On 10/14/2015 07:18 AM, Akihiro Motoki wrote: > 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

Re: [openstack-dev] [fuel] Life cycle management use cases

Great topic... Please note that the Product WG[1] also has a user story focused on Lifecycle Management. While FUEL is one aspect of the overall workflow, we would also like the team to consider project level enhancements (e.g. garbage collection inside the DB). The Product WG would welcome y

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

On 10/13/2015 05:14 PM, Doug Hellmann wrote: > 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

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

On 10/13/2015 09:41 AM, Cory Benfield wrote: > >> On 13 Oct 2015, at 07:42, Thomas Goirand wrote: >> In this particular case (ie: a difficult upstream which makes it >> impossible to have the same result with pip and system packages) > > I don’t know how carefully you’ve followed this email trai

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

On 15 October 2015 at 11:11, Thomas Goirand wrote: > > One major pain point is unfortunately something ridiculously easy to > fix, but which nobody seems to care about: the long & short descriptions > format. These are usually buried into the setup.py black magic, which by > the way I feel is very

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

On 10/13/2015 06:04 PM, Joshua Harlow wrote: > 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 int

[openstack-dev] [fuel] Life cycle management use cases

Hi fuelers, as we all know, Fuel lacks many of life cycle management (LCM) use cases. It becomes a very hot issue for many of our users, as current LCM capabilities are not very rich. In order to think how we can fix it, we need to collect use cases first, and prioritize them if needed. So that wh

Re: [openstack-dev] [nova] novaclient functional test failures

On 10/12/2015 5:12 PM, melanie witt wrote: On Oct 12, 2015, at 12:14, Kevin L. Mitchell wrote: http://logs.openstack.org/77/232677/1/check/gate-novaclient-dsvm-functional/2de31bc/ (For review https://review.openstack.org/232677) http://logs.openstack.org/99/232899/1/check/gate-novaclient-d

[openstack-dev] [Fuel] Fuel Library Component Lead Nomination

Fuel Librarians I would like to nominate myself as a Candidate for Fuel Library Component Lead position Let me mention the list of main points I would like to work on. This list is going to essentially resemble my PTL candidacy item list but it will also differ from it significantly. * General S

[openstack-dev] [fuel][library] component lead candidacy

Hey crew, I'd like to send my candidacy for Fuel component lead election for a next cycle. I would like to focus on the following priorities: - Synchronisation with upstream modules. As a result fuel-library will contain only few manifests. All other manifests will be consumed from upstream. ope

Re: [openstack-dev] [puppet] Tokyo Summit - dev + ops

So we gathered all proposals and I worked on the agenda. If you plan to attend Puppet OpenStack tracks, here is what you need to know: * general etherpad: https://etherpad.openstack.org/p/HND-puppet * schedule http://mitakadesignsummit.sched.org/type/Puppet%20OpenStack#.Vh6myZdm-Zc * etherpads: h

Re: [openstack-dev] [neutron] Neutron rolling upgrade - are we there yet?

> I would like to gather all upgrade activities in Neutron in one place, > in order to summarizes the current status and future activities on > rolling upgrades in Mitaka. Glad to see this work really picking up steam in other projects! > b. TODO: To have the rolling upgrade we have to imple

[openstack-dev] [neutron] Neutron rolling upgrade - are we there yet?

Hi all, I would like to gather all upgrade activities in Neutron in one place, in order to summarizes the current status and future activities on rolling upgrades in Mitaka. 1. RPC versioning a. It is already implemented in Neutron. b. TODO: To have the rolling upgrade we have

Re: [openstack-dev] [neutron] one SDN controller and many OpenStack environments

Hi Piotr, Nuage Networks is supporting the use case you describe and this is actually deployed at operators. Thanks, Kris On Oct 14, 2015 5:34 PM, "Piotr Misiak" wrote: > Hi, > > Do you know if there is a possibility to manage tenants networks in many > OpenStack environments by one SDN contro

Re: [openstack-dev] [Congress] Congress and Monasca Joint Session at Tokyo Design Summit

Hi Fabio, We now have a schedule. I've tentatively booked you for half of our slot Wed 3:40-4:20. Does that work for your team? You can find the other options at... https://wiki.openstack.org/wiki/Design_Summit/Mitaka/Etherpads#Congress Tim On Thu, Oct 1, 2015 at 2:06 PM Fabio Giannetti (fg

[openstack-dev] [Congress] Tokyo summit schedule

Hi all, I put a tentative schedule online for the Tokyo summit. If there are things you'd like to discuss that aren't on there, let me know. https://wiki.openstack.org/wiki/Design_Summit/Mitaka/Etherpads#Congress Masahito: could you reach out to the OPNFV people that wanted to talk about their

Re: [openstack-dev] [neutron] one SDN controller and many OpenStack environments

Please ask this question on openstack-ops, where a lot of operators convene and can probably share experiences with the SDN controllers you listed. My gut says that an SDN controller is expected to handle multiple regions and large topologies, but I can't comment on if any SDN solution handles t

Re: [openstack-dev] [release] establishing release liaisons for mitaka

Excerpts from Armando M.'s message of 2015-10-14 09:32:16 -0700: > On 14 October 2015 at 08:25, Doug Hellmann wrote: > > > As with the other cross-project teams, the release management team > > relies on liaisons from each project to be available for coordination of > > work across all teams. It'

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

Hi Oğuz, Thank you for starting to contribute to Neutron FWaaS. We just got together as a new core team and we are still learning the ropes there. Please be also advised that we are planning some changes in future versions (especially now as the API has been deprecated). In any case a good pla

Re: [openstack-dev] [TripleO] Introspection rules aka advances profiles replacement: next steps

On 10/14/2015 10:57 AM, Ben Nemec wrote: > On 10/14/2015 06:38 AM, Dmitry Tantsur wrote: >> Hi OoO'ers :) >> >> It's going to be a long letter, fasten your seat-belts (and excuse my >> bad, as usual, English)! >> >> In RDO Manager we used to have a feature called advanced profiles >> matching.

Re: [openstack-dev] [keystone federation] some questions about keystone IDP with SAML supported

On 10/14/2015 11:58 AM, Marek Denis wrote: pretty much - yes! Luckily for you the reference libraries (shibboleth) are written in Java so it should be easier to integrate with your application. Only the Shibboleth IdP is written in Java. Shibboleth the SP is written in C++. If you're trying to

Re: [openstack-dev] [nova] Nova Design Summit Schedule

On 14 October 2015 at 15:59, John Garbutt wrote: > Hi, > > We have a draft schedule for the summit uploaded: > http://mitakadesignsummit.sched.org/overview/type/nova > > We generally picked the sessions where in person debate is needed. We > rejected sessions where we felt a nova-spec review, or a

Re: [openstack-dev] [keystone federation] some questions about keystone IDP with SAML supported

On 10/14/2015 07:10 AM, wyw wrote: hello, keystoners. please help me Here is my use case: 1. use keystone as IDP , supported with SAML 2. keystone integrates with LDAP 3. we use a java application as Service Provider, and to integrate it with keystone IDP. 4. we use a keystone as Service Provid

Re: [openstack-dev] [release] establishing release liaisons for mitaka

On 14 October 2015 at 08:25, Doug Hellmann wrote: > As with the other cross-project teams, the release management team > relies on liaisons from each project to be available for coordination of > work across all teams. It's the start of a new cycle, so it's time to > find those liaison volunteers

Re: [openstack-dev] [keystone federation] some questions about keystone IDP with SAML supported

Hello, On 14.10.2015 13:10, wyw wrote: hello, keystoners. please help me Here is my use case: 1. use keystone as IDP , supported with SAML Remember that Keystone is not a fully fledged Identity Provider. For instance it cannot handle WebSSO. To be even more specific it will only handle "Id

Re: [openstack-dev] [devstack] A few questions on configuring DevStack for Neutron

I believe that pulling a localrc off a CI result is tribal knowledge. It can be done, but most likely it's a trick that is only known by someone who has been involved in OpenStack for a long time. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

[openstack-dev] [cinder] Cinder Design Summit Schedule

Hello all, I have the schedule updated for the Design Summit Cinder sessions. Please take a look and let me know if you see any major issues: https://mitakadesignsummit.sched.org/overview/type/cinder Some sessions had to be moved around to accomodate presentation schedules. If we have other conf

[openstack-dev] [neutron] one SDN controller and many OpenStack environments

Hi, Do you know if there is a possibility to manage tenants networks in many OpenStack environments by one SDN controller (via Neutron plugin)? Suppose I have in one DC two or three OpenStack env's (deployed for example by Fuel) and I have a SDN controller which manages all switches in DC. Can I

[openstack-dev] [release] release request process change

During the last cycle, we had several library releases go out without subsequent requirements updates even though projects wanted to use the new features. That meant at the end of the cycle our lower-bound requirements were not accurate. To avoid that happening this cycle, we have modified the rele

[openstack-dev] [release] establishing release liaisons for mitaka

As with the other cross-project teams, the release management team relies on liaisons from each project to be available for coordination of work across all teams. It's the start of a new cycle, so it's time to find those liaison volunteers. We are working on updating the release documentation as p

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

>From my few changes on puppet-openstack I've got several reviews from Dennis, and they were always insightful. +1 Regards 2015-10-14 17:13 GMT+02:00 Sebastien Badia : > On Wed, Oct 14, 2015 at 09:07:04AM (+0200), Yanis Guenane wrote: > > On 10/13/2015 11:02 PM, Matt Fischer wrote: > > > On Tue

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

On Wed, Oct 14, 2015 at 09:07:04AM (+0200), Yanis Guenane wrote: > On 10/13/2015 11:02 PM, Matt Fischer wrote: > > 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 statisti

[openstack-dev] [oslo] Design Summit Schedule

Folks, Here's a draft schedule for tokyo summit: http://mitakadesignsummit.sched.org/overview/type/oslo Please let us know if there are any schedule conflicts etc and we can try to shuffle these around. Thanks, Dims -- Davanum Srinivas :: https://twitter.com/dims __

[openstack-dev] [nova] Nova Design Summit Schedule

Hi, We have a draft schedule for the summit uploaded: http://mitakadesignsummit.sched.org/overview/type/nova We generally picked the sessions where in person debate is needed. We rejected sessions where we felt a nova-spec review, or a discussion in the Friday meetup, or one of the Nova Unconfere

Re: [openstack-dev] [TripleO] Introspection rules aka advances profiles replacement: next steps

On 10/14/2015 06:38 AM, Dmitry Tantsur wrote: > Hi OoO'ers :) > > It's going to be a long letter, fasten your seat-belts (and excuse my > bad, as usual, English)! > > In RDO Manager we used to have a feature called advanced profiles > matching. It's still there in the documentation at > http:/

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

On 10/13/2015 08:08 PM, Dan Prince wrote: > 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 a

[openstack-dev] [Fuel] Modularization activity POC

Hi, We are starting Fuel modularization POC activity which is basically in one sentence can be explained as "Use Fuel without Fuel", it means that we want to provide for a user a way to use some good things from Fuel, without entire master node and other parts which user doesn't need. Currently w

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

Excerpts from Flavio Percoco's message of 2015-10-14 21:46:05 +0900: > On 13/10/15 07:05 +0900, Flavio Percoco wrote: > >Greetings, > > > >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 feedb

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

On 10/14/2015 12:09 AM, Sean McGinnis wrote: 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

Re: [openstack-dev] [mistral] Team meeting minutes - 10/12/2015

Hi Lingxian, Yes, your understanding is correct. > * run_functional_tests.sh is just used locally, will not run tests depend on OpenStack. This script was written just for ability to run suite of api tempest tests locally (with turned off auth in Mistral and 'hacked' auth in tempest in our tests)

[openstack-dev] [magnum] Creating pods results in "EOF occurred in violation of protocol" exception

Hi, I try Magnum, following instructions on the quickstart page [1]. I successfully create the baymodel and the bay. When I run the command to create redis pods (_magnum pod-create --manifest ./redis-master.yaml --bay k8sbay_), client side, it timeouts. And server side (m-cond.log), I get the

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

On 10/13/2015 10:39 PM, Eric Harney wrote: 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 di

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

On 13/10/15 07:05 +0900, Flavio Percoco wrote: Greetings, 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 - hopefully you're all cc'd - or other

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

On 10/14/2015 07:57 AM, Ihar Hrachyshka wrote: >> On 14 Oct 2015, at 02:08, Zaro wrote: >> >> 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 t

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

On 10/14/2015 08:23 AM, Dean Troyer wrote: > On Wed, Oct 14, 2015 at 3:51 AM, Thierry Carrez > wrote: > > My main issue with CS2 is how greedy it is in horizontal space, mostly > due to the waste of space in the "Related changes" panel. If there are > rel

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

> On 14 Oct 2015, at 14:34, Chuck Short wrote: > > > > On Wed, Oct 14, 2015 at 5:01 AM, Thierry Carrez wrote: > Ihar Hrachyshka wrote: > > Chuck, have you forgotten about three more repositories for neutron-*aas? > > My apologies they are available now. Thanks! Ihar signature.asc Descript

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

On Wed, Oct 14, 2015 at 5:01 AM, Thierry Carrez wrote: > Ihar Hrachyshka wrote: > > Chuck, have you forgotten about three more repositories for neutron-*aas? > My apologies they are available now. > > Yeah, if those have fixes they should have been tagged as well. > > Also we'll want a change t

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

On Wed, Oct 14, 2015 at 3:51 AM, Thierry Carrez wrote: > My main issue with CS2 is how greedy it is in horizontal space, mostly > due to the waste of space in the "Related changes" panel. If there are > related changes, the owner/reviewer/voting panel is cramped in the > middle, while "related ch

[openstack-dev] [all] Etherpads list for Mitaka Design Summit

Hi everyone, I just set up the wiki page to collect all the etherpads for the Mitaka Design Summit (yes, only 12 days away): https://wiki.openstack.org/wiki/Design_Summit/Mitaka/Etherpads Please add your etherpads there when you create them, for easy reference and facilitating session preparatio

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

Kobi, Thanks again. I also found this Wiki. ☺ I think the introduction on the Wiki may be out of date, and it can’t work on Kilo. ☹ I figure out From: Kobi Samoray [mailto:ksamo...@vmware.com] Sent: Wednesday, October 14, 2015 12:40 AM To: OpenStack Development Mailing List (not for usage quest

[openstack-dev] [Kosmos] Skipping IRC Meeting for the next 2 weeks

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 In light of all the travelling that will be happening, we have decided to skip the weekly IRC meeting for the next 2 weeks. Thanks, Graham - -- Graham Hayes -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJWHkaIAAo

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

> On 14 Oct 2015, at 02:08, Zaro wrote: > > 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 som

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

Adrien Cunin wrote: > Le 09/10/2015 11:42, Thierry Carrez a écrit : > Nice! I've got a question though: is there another way than the wiki > page to consume those successes? > > I was thinking of an RSS/Atom feed, which would make it possible to > easily publish them elsewhere (website, social med

[openstack-dev] [Cinder][Horizon] Cinder v2 endpoint name: volumev2 is required? volume is okay?

Hi Cinder team, What is the expected service name of Cinder v2 API in keystone catalog? DevStack configures "volumev2" for Cinder v2 API by default. Can we "volume" for Cinder v2 API or do we always need to use "volumev2" in deployments with only Cinder v2 API (i.e. no v1 API) ? The question was

[openstack-dev] [TripleO] Introspection rules aka advances profiles replacement: next steps

Hi OoO'ers :) It's going to be a long letter, fasten your seat-belts (and excuse my bad, as usual, English)! In RDO Manager we used to have a feature called advanced profiles matching. It's still there in the documentation at http://docs.openstack.org/developer/tripleo-docs/advanced_deployme

[openstack-dev] [keystone] [puppet] [neutron] Deprecating nova_admin_ options in puppet-neutron

Hi folks, Currently puppet-neutron module sets nova_admin_* options in neutron.conf which are deprecated since Kilo release. I propose to replace them, but we need to discuss how to do it better. I raised this question at puppet-openstack weekly meeting yesterday [0]. So the main concern here is t

[openstack-dev] [keystone federation] some questions about keystone IDP with SAML supported

hello, keystoners. please help me Here is my use case: 1. use keystone as IDP , supported with SAML 2. keystone integrates with LDAP 3. we use a java application as Service Provider, and to integrate it with keystone IDP. 4. we use a keystone as Service Provider, and to integrate it withe keyst

Re: [openstack-dev] [cinder] NFS mount as cinder user instead of root

Hi, Yes, that worked! Thanks! :) But the process is very slow (about half an hour to create a volume). I think the problem is the execution of "du -sb --apparent-size --exclude *snapshot* /var/lib/cinder/mnt/9ae799cf301b19940950ae49dd800c51", as shown in the logs: 2015-10-13 19:33:14.127 1311 INF

[openstack-dev] [Neutron][Glance] Liberty RC3 available

Hello everyone, OK, last ones. Due to release-critical issues combined with recently-discovered dependencies issues, we just respinned a release candidate for Neutron and Glance. The list of RC3 fixes, as well as RC3 tarballs are available at: https://launchpad.net/glance/liberty/liberty-rc3 http

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

On 13/10/15 17:08 -0700, Zaro wrote: 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

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

On 10/13/2015 08:08 PM, Zaro wrote: > 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

Re: [openstack-dev] Scheduler proposal

On Tue, 2015-10-13 at 08:47 -0700, Joshua Harlow wrote: > 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 s

Re: [openstack-dev] [neutron]What happened when the 3-rd controller restarted?

Hi Salvatore and Kevin, I'm sorry for replying so late. I wanted to see whether the community had considered data sync for these two style(agent and controller) integration. To solve integrating multiple vendor's controllers, I need some help from community. That's the original purpose of this thr

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

On 10/12/2015 07:55 PM, Dean Troyer wrote: > On Mon, Oct 12, 2015 at 5:25 PM, Victoria Martínez de la Cruz > mailto:victo...@vmartinezdelacruz.com>> > wrote: > > So, this commands would look like > > openstack pool-flavor create > openstack pool-flavor get > openstack pool-flavor

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

On 10/14/2015 04:53 PM, Nikola Đipanov wrote: On 10/14/2015 04:29 AM, Tang Chen wrote: On Wed, Oct 14, 2015 at 10:05 AM, Tang Chen mailto:tangc...@cn.fujitsu.com>> wrote: Hi, all, Please help to review this BP. https://blueprints.launchpad.net/nova/+spec/live-migration-state-m

Re: [openstack-dev] [Fuel] Proposal to freeze old Fuel CLI

Roman, this was already discussed in [1]. The conclusion was that we will implement new features in both places so user will not have to use "old" fuelclient to do some things and the "new" to others. There were no progress with moving old commands to new CLI and I didn't seen plans to do so. IMHO

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

Ihar Hrachyshka wrote: > Chuck, have you forgotten about three more repositories for neutron-*aas? Yeah, if those have fixes they should have been tagged as well. Also we'll want a change to openstack/releases to include 2015.1.2 in release history. -- Thierry Carrez (ttx) signature.asc Desc

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

Le 09/10/2015 11:42, Thierry Carrez a écrit : > 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][stable][release] 2015.1.2

Sean Dague wrote: > I think that whoever sets the tag should also push those fixes. We had > some kilo content bogging down the gate today because of this kind of > failure. Better to time this as close as possible with the tag setting. Right. The ideal process is to push the version bump and cut

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

On 10/14/2015 04:29 AM, Tang Chen wrote: >> >> 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 >> >> >> Currently

[openstack-dev] [Fuel] Proposal to freeze old Fuel CLI

Fuelers, as you know a big effort has been put into making Fuel Client’s CLI better and as a result we got a new fuel2 utility with a new set of commands and options. Some folks still put great effort to move everything that’s left in the old CLI to the new CLI. Every new thing added to the ol

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

Zaro wrote: > We want to let everyone know that there is a big UI change in Gerrit > 2.11. The change screen (CS), which is the main view for a patchset, > has been completely replaced with a new change screen (CS2). While > Gerrit 2.8 contains both old CS and CS2, I believe everyone in > Opensta

[openstack-dev] [ironic] The scenary to rolling upgrade Ironic

Hi guys, I am looking at https://bugs.launchpad.net/ironic/+bug/1502903 which is related to rolling upgrade and here is Jim's patch https://review.openstack.org/#/c/234450 I really have a concern or question about how to do Ironic doing rolling upgrades. It might be my mistake, but I would like

Re: [openstack-dev] [mistral] Team meeting minutes - 10/12/2015

Hi, Mistral guys, In last meeting, we have discussed deeply about Tempest usage in Mistral project and the functional testing mechanism, I have the understanding in terms of functional testing as below, * run_functional_tests.sh is just used locally, will not run tests depend on OpenStack. * in o

  1   2   >