[openstack-dev] [manila] [third-party][qa]: Tempest plugin concept: 3rd party CI

Hello Manila team, as discussed in the Manila mid-cycle we want to move forward with the tempest plugin porting. The initial patch is already up and ready for review [1]. For more details please see [2]. Please note that 3rd party CI systems may need to be adapted. All tests are currently moved f

Re: [openstack-dev] [Keystone][Fernet] HA SQL backend for Fernet keys

On Monday 03 August 2015 21:05:00 David Stanek wrote: > On Sat, Aug 1, 2015 at 8:03 PM, Boris Bobrov wrote: > > On Sat, Aug 1, 2015 at 3:41 PM, Clint Byrum wrote: > > > This too is overly complex and will cause failures. If you replace key > > > 0, > > > > > > you will stop validating tokens t

Re: [openstack-dev] [Keystone][Fernet] HA SQL backend for Fernet keys

> On 3 Aug 2015, at 8:02 pm, Sergii Golovatiuk wrote: > > Hi, > > I agree with Bogdan that key rotation procedure should be part of HA solution. These things don’t usually have to be an either/or situation. Why not create one script that does the work and can be called manually if desired but

Re: [openstack-dev] [CI]How to set proxy for nodepool

Hi Xiexs, You are using disk image builder (DIB), so make sure your proxy is set correctly also without the NODEPOOL_ prefix. Those NODEPOOL_ prefixed variables are what would be used when DIB is not used / when the script approach is used with nova/glance (nodepool image-update). I don’t recom

[openstack-dev] [CI]How to set proxy for nodepool

Hi All, When I ran “nodepool image-build ” to create a new image, I got this error message: … INFO nodepool.image.build.dpc: + sudo -H virtualenv /usr/zuul-swift-logs-env INFO nodepool.image.build.dpc: sudo: unable to resolve host fnst01 INFO nodepool.image.build.dpc: + sudo -H /usr/zuul-swift-log

Re: [openstack-dev] 答复: [CI] No image was created after running "nodepoold -d $DAEMON_ARGS"

Hi Ramy, Cc Wienand, Thanks to both of you and your suggestions help me solve this problem. It was really a permission issue: (debug info) +sha256sum --check - +grep: /opt/dib_cache/SHA256SUMS.ubuntu.trusty.amd64: Permission denied Here grep command run as nodepool, but the file was owned by ro

Re: [openstack-dev] [devstack][neutron] How to give nested VM access to outside network?

On 08/03/2015 10:07 PM, Rich Megginson wrote: I'm running devstack in a VM (Fedora 21 host, EL 7.1.x VM) with a static IP address (because dhcp was not working): cat > /etc/sysconfig/network-scripts/ifcfg-eth0

[openstack-dev] [devstack][neutron] How to give nested VM access to outside network?

I'm running devstack in a VM (Fedora 21 host, EL 7.1.x VM) with a static IP address (because dhcp was not working): cat > /etc/sysconfig/network-scripts/ifcfg-eth0

Re: [openstack-dev] [Magnum]horizontal scalability

Adrian, If the reason to avoid leader election is because it is complicated and error prone, this argument may not be true. Leader election is complicated in a pure distributed system in which there is no centralized storage. However, Magnum has a centralized database, so it is possible to impl

Re: [openstack-dev] [magnum][blueprint] magnum-service-list

Cool, Suro! It's great that we finally reach an agreement on this ;-) 2015-08-03 20:43 GMT-04:00 SURO : > Thanks Jay/Kennan/Adrian for chiming in! > > From this, I conclude that we have enough consensus to have 'magnum > service-list' and 'magnum coe-service-list' segregated. I will capture > ext

Re: [openstack-dev] [Neutron][L3] [Large Deployments Team] Representing a networks connected by routers

I hope we can move this idea moving forward. I was disappointed to see the spec abandoned. Some of us from the large deployers group will be at the Ops Meetup. Will there be any representation from Neutron there that we could discuss with more? Thanks, Mike On 8/3/15, 12:27 PM, "Carl Ba

[openstack-dev] [fuel][puppet] The state of collaboration: 7 weeks

Two weeks ago we had a discussion of where things stand in the collaboration between Fuel and Puppet OpenStack projects [0]. [0] http://lists.openstack.org/pipermail/openstack-dev/2015-July/069925.html Things that were good at that point: - number of proposed patch sets Things that needed furth

Re: [openstack-dev] How to use the log server in CI ?

BTW, I did update the documentation a bit to cover recent questions [1]. Let me know if I missed anything. Thanks, Ramy [1] https://github.com/rasselin/os-ext-testing/commit/0d8e4234c226273392391df3693292af43b1d2be From: Tang Chen [mailto:tangc...@cn.fujitsu.com] Sent: Monday, August 03, 2015

Re: [openstack-dev] How to use the log server in CI ?

On 08/04/2015 06:44 AM, Asselin, Ramy wrote: Hi Tang, Sorry the documentation on github is limited. I've been focusing on getting an upstream solution working, and that's where it belongs and should be maintained. I will take a quick look and add some tips as discussed in this thread. Of

Re: [openstack-dev] [Neutron] Common Base class for agents

I hacked up the LB agent and the OVS agent over some coffee - to see if there are pieces that overlap. I believe there are - I'm hoping to extract some code from each agent, into a common class. It's very WIP but I'm hopeful that I'll be able to share some promising results soon. https://review.op

Re: [openstack-dev] [Keystone][Fernet] HA SQL backend for Fernet keys

On Sat, Aug 1, 2015 at 8:03 PM, Boris Bobrov wrote: > On Sat, Aug 1, 2015 at 3:41 PM, Clint Byrum wrote: > > > This too is overly complex and will cause failures. If you replace key 0, > > > you will stop validating tokens that were encrypted with the old key 0. > > > > No. Key 0 is replaced aft

Re: [openstack-dev] [magnum][blueprint] magnum-service-list

Thanks Jay/Kennan/Adrian for chiming in! From this, I conclude that we have enough consensus to have 'magnum service-list' and 'magnum coe-service-list' segregated. I will capture extract of this discussion at the blueprint and start implementation of the same. Kennan, I would request you to

Re: [openstack-dev] [all] Does OpenStack need a common solution for DLM? (was: Re: [Cinder] A possible solution for HA Active-Active)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Aug 3, 2015, at 6:09 PM, Flavio Percoco wrote: On 03/08/15 19:48 +0200, Gorka Eguileor wrote: On Mon, Aug 03, 2015 at 03:42:48PM +, Fox, Kevin M wrote: I'm usually for abstraction layers, but they don't always pay off very well due to cater

Re: [openstack-dev] [magnum][blueprint] magnum-service-list

Hi Suro and Jay, I checked discussion below, and I do believe we also need service-list(for just magnum-api and magnum-conductor), but not so emergent requirement. I also think service-list should not bind to k8s or swarm etc. (can use coe-service etc.) But I have more for below: 1) For k8s or

[openstack-dev] [keystone] policy issues when generating trusts with different clients

hi all, i am doing some work to change sahara to make greater use of keystoneclient.session.Session objects and i am running into a strange error when issuing the trusts. the crux of this issue is that when i create Client objects by passing all the parameters directly to the client, the tru

Re: [openstack-dev] [Neutron] Common Base class for agents

I see this as two tasks: 1) A refactoring to share common code and 2) the addition of another agent following the pattern of the others. I'd prefer that the two tasks not be mixed in the same review because it makes it more difficult to review as I think Kevin eluded to. For me, either could be d

Re: [openstack-dev] How to use the log server in CI ?

Hi Tang, Sorry the documentation on github is limited. I’ve been focusing on getting an upstream solution working, and that’s where it belongs and should be maintained. I will take a quick look and add some tips as discussed in this thread. Of course if you have pull requests, I’m happy to merg

Re: [openstack-dev] 答复: [CI] No image was created after running "nodepoold -d $DAEMON_ARGS"

Hi Xiexs, Definitely make sure you run nodepool commands as nodepool and not root: sudo su - nodepool Before starting nodepool on a fresh install, I usually manually build the image first as it is easier to debug issues: sudo su - nodepool nodepool image-build Ramy -Original Message

Re: [openstack-dev] [CI] Jenkins jobs are not executed when setting up a new CI system.

Hi Tang, I thought I replied about this earlier. There seems to be a regression running jobs directly on master, at least for newer versions of Jenkins. Running on a slave does work. Ramy From: Tang Chen [mailto:tangc...@cn.fujitsu.com] Sent: Monday, July 27, 2015 6:30 PM To: openstack-dev@lis

Re: [openstack-dev] Would people see a value in the cve-check-tool?

Hi Elena, the tool looks very interesting. Maybe try to spread out this proposal also through openstack-security@ ML. BTW, I can't find the wrapper mentioned - am I missing something? Regards, Adam On Mon, Aug 3, 2015 at 11:08 PM, Reshetova, Elena wrote: > Hi, > > > > We would like to ask opin

[openstack-dev] [all] Does OpenStack need a common solution for DLM? (was: Re: [Cinder] A possible solution for HA Active-Active)

On 03/08/15 19:48 +0200, Gorka Eguileor wrote: On Mon, Aug 03, 2015 at 03:42:48PM +, Fox, Kevin M wrote: I'm usually for abstraction layers, but they don't always pay off very well due to catering to the lowest common denominator. Lets clearly define the problem space first. IFF the proble

Re: [openstack-dev] [magnum][blueprint] magnum-service-list

Hi Suro, Yes, I did not see a strong reason for adding "service-list" to show all of magnum system services, but it is nice to have. But I did see a strong reason to rename "service-list" to "coe-service-list" or others which might be more meaningful as I was often asked by someone why does "magn

Re: [openstack-dev] [Cinder] A possible solution for HA Active-Active

On 03/08/15 08:32 -0700, Joshua Harlow wrote: Morgan Fainberg wrote: Lets step back away from tooz. Tooz for the sake of this conversation is as much the same as saying zookeeper or consul or etcd, etc. We should be focused (as both Flavio and Thierry said) on if we need DLM and what it will s

[openstack-dev] [neutron][vpnaas] Next IRC meeting - Tuesday, August 4th.

Will hold another meeting tomorrow. If you have items for the agenda, please update the Wiki. Regards, Paul Michali (pc_m) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lis

Re: [openstack-dev] [nova][oslo][policy] oslo.policy adoption in Nova.

Excerpts from Doug Hellmann's message of 2015-08-03 16:19:31 -0400: > Excerpts from Morgan Fainberg's message of 2015-08-04 06:05:56 +1000: > > > > > On Aug 4, 2015, at 05:49, Doug Hellmann wrote: > > > > > > Excerpts from Sergey Vilgelm's message of 2015-08-03 22:11:50 +0300: > > >>> On Mon, Au

Re: [openstack-dev] [kolla] Mission change suggested by the TC for big tent

On Mon, Aug 3, 2015 at 5:47 PM, Steven Dake (stdake) wrote: > > > On 7/30/15, 4:26 PM, "Doug Hellmann" wrote: > > >Excerpts from Steven Dake (stdake)'s message of 2015-07-30 15:27:15 +: > >> > >> On 7/29/15, 1:23 PM, "Doug Hellmann" wrote: > >> > >> >Excerpts from Steven Dake (stdake)'s mes

Re: [openstack-dev] [stable] [infra] How to auto-generate stable release notes

Perhaps the following can be used? https://github.com/vaab/gitchangelog#gitchangelog That does impose a commit message format, but then any kind of release notes generated from a commit log will require some sort of standard to be maintained (otherwise it's going to be tough to auto-generate

[openstack-dev] Would people see a value in the cve-check-tool?

Hi, We would like to ask opinions if people find it valuable to include a cve-check-tool into the OpenStack continuous integration process? A tool can be run against the package and module dependencies of OpenStack components and detect any CVEs (in future there are also plans to integrate mo

Re: [openstack-dev] [all] [oslo] Suggestion to change verbose=false to true in oslo.log by default

On 7/28/2015 4:28 AM, Dmitry Tantsur wrote: On 07/27/2015 02:11 PM, Sean Dague wrote: Honestly, I think deprecating and removing 'verbose' is probably the best option. INFO is probably the right default behavior, and it's not really "verbose" in any real openstack usage. It is unlikely that an

Re: [openstack-dev] [Keystone] [Horizon] UI for Keystone dynamic policies editing

Hi Timur, Thanks for bringing this up. I think we can borrow some concept from the Mistral Workbook Builder. I like the ability to add items and seeing the preview on the right side. We can re-use that part. The challenging part would be building a Rule expression builder that supports the polic

[openstack-dev] [nova] [FFE] Feature Freeze Exception Request for virtuozzo related features

Hello nova team, On behalf of the team working on Virtuozzo libvirt driver support in nova, I would like to ask for a feature freeze exception for the following two blueprints related to virtuozzo libvirt driver (virt_type=parallels): - virtuozzo instance resize support https://blueprints.l

[openstack-dev] [puppet] weekly meeting #45

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-20150804 Please add additional items you'd like to discuss. If our schedule allows it, we'll make bug triage during the meeting.

Re: [openstack-dev] [nova][oslo][policy] oslo.policy adoption in Nova.

Excerpts from Morgan Fainberg's message of 2015-08-04 06:05:56 +1000: > > > On Aug 4, 2015, at 05:49, Doug Hellmann wrote: > > > > Excerpts from Sergey Vilgelm's message of 2015-08-03 22:11:50 +0300: > >>> On Mon, Aug 3, 2015 at 9:37 PM, Doug Hellmann > >>> wrote: > >>> > >>> Making that func

Re: [openstack-dev] [all] Need volunteers to test coverage 4.0 alpha release

Excerpts from Brant Knudson's message of 2015-08-03 10:32:51 -0500: > On Mon, Aug 3, 2015 at 6:32 AM, Doug Hellmann wrote: > > > Do we have anyone willing to spend some time looking at the > > incompatibilities Ned mentions below to ensure that we have a smooth > > transition when 4.0 moves out o

Re: [openstack-dev] [kolla] Mission change suggested by the TC for big tent

Excerpts from Steven Dake (stdake)'s message of 2015-08-03 15:47:28 +: > > On 7/30/15, 4:26 PM, "Doug Hellmann" wrote: > > >Excerpts from Steven Dake (stdake)'s message of 2015-07-30 15:27:15 +: > >> > >> On 7/29/15, 1:23 PM, "Doug Hellmann" wrote: > >> > >> >Excerpts from Steven Dake

Re: [openstack-dev] [nova][oslo][policy] oslo.policy adoption in Nova.

> On Aug 4, 2015, at 05:49, Doug Hellmann wrote: > > Excerpts from Sergey Vilgelm's message of 2015-08-03 22:11:50 +0300: >>> On Mon, Aug 3, 2015 at 9:37 PM, Doug Hellmann wrote: >>> >>> Making that function public may be the most expedient fix, but the >>> parser was made private for a reaso

Re: [openstack-dev] [stable] [infra] How to auto-generate stable release notes

Excerpts from Robert Collins's message of 2015-08-04 06:43:48 +1200: > On 4 August 2015 at 02:46, Alexis Lee wrote: > > Thierry Carrez said on Mon, Aug 03, 2015 at 02:57:39PM +0200: > >> 1. we can maintain a Changelog document directly in the source code. > >> Rather than being straightly backport

Re: [openstack-dev] [nova][oslo][policy] oslo.policy adoption in Nova.

Excerpts from Sergey Vilgelm's message of 2015-08-03 22:11:50 +0300: > On Mon, Aug 3, 2015 at 9:37 PM, Doug Hellmann wrote: > > > Making that function public may be the most expedient fix, but the > > parser was made private for a reason, so before we expose it we > > should understand why, and i

Re: [openstack-dev] [Cinder] A possible solution for HA Active-Active

> On Aug 4, 2015, at 01:42, Fox, Kevin M wrote: > > I'm usually for abstraction layers, but they don't always pay off very well > due to catering to the lowest common denominator. > > Lets clearly define the problem space first. IFF the problem space can be > fully implemented using Tooz, th

Re: [openstack-dev] [nova] Thoughts on things that don't make freeze cutoffs

On 7/29/15, 2:13 PM, "Matt Riedemann" wrote: >We talked a bit about this at the nova mid-cycle last week but I can't >say I completely remember all of the points made, since I feel like we >talked ourselves into a circle that got us back to more or less 'the >current specs and freeze process is

Re: [openstack-dev] [magnum][blueprint] magnum-service-list

Hi Jay, Thanks for clarifying the requirements further. I do agree with the idea of having 'magnum service-list' and 'magnum coe-service-list' to distinguish that coe-service is a different concept. BUT, in openstack space, I do not see 'service-list' as a standardized function across other A

Re: [openstack-dev] [Cinder] Quobyte Cinder Driver revert?

On 8/3/2015 10:23 AM, Mike Perez wrote: On Fri, Jul 3, 2015 at 9:11 AM, Duncan Thomas wrote: It was discussed on the mailing list, and at the weekly meeting. Mike had had no response on the issue from the listed contact email, and the CI was reporting failure for every patch for two months O

Re: [openstack-dev] [nova] Proposal for an Experiment

Jesse J. CookCompute Team Lead jesse.c...@rackspace.com irc: #compute-eng (gimchi) mobile: 618-530-0659 On 7/20/15, 12:40 PM, "Clint Byr

Re: [openstack-dev] [magnum][blueprint] magnum-service-list

Jay makes a good point here. The service-list output is specific to the “service” abstraction in the COE, not the system services that are part of magnum. The suggested rename from service-list to coe-service-list would make this distinction more clear. Adrian On Jul 30, 2015, at 2:40 AM, Jay

Re: [openstack-dev] [nova][oslo][policy] oslo.policy adoption in Nova.

On Mon, Aug 3, 2015 at 9:37 PM, Doug Hellmann wrote: > Making that function public may be the most expedient fix, but the > parser was made private for a reason, so before we expose it we > should understand why, and if there are alternatives (such as > creating a fixture in oslo.policy to do wha

Re: [openstack-dev] [magnum][blueprint] magnum-service-list

Hi Suro and others, comments on this? Thanks. 2015-07-30 5:40 GMT-04:00 Jay Lau : > Hi Suro, > > In my understanding, even other CoE might have service/pod/rc concepts in > future, we may still want to distinguish the "magnum service-list" with > "magnum coe-service-list". > > service-list is mai

Re: [openstack-dev] [pbr] [stable] [infra] How to generate .Z version increments on stable/liberty commits

On Mon, Aug 3, 2015, at 05:46 AM, Thierry Carrez wrote: > Hi everyone, > > A month ago the stable branch team decided to move away from > synchronized stable point releases and enable continuous stable branch > delivery instead. > > The end goal is that every commit on a stable branch for a "serv

Re: [openstack-dev] [openstack-announce] [release][oslo] tooz release 1.21.0 (liberty)

Hi, Justin, Perhaps you meant to click through to http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-announce and unsubscribe? Let me know if you need help figuring that interface out. Doug Excerpts from Justin Hammond's message of 2015-08-03 18:00:02 +: > FUCK OFF > > From: "dav

Re: [openstack-dev] [stable] [infra] How to auto-generate stable release notes

On 4 August 2015 at 02:46, Alexis Lee wrote: > Thierry Carrez said on Mon, Aug 03, 2015 at 02:57:39PM +0200: >> 1. we can maintain a Changelog document directly in the source code. >> Rather than being straightly backported from master, commits with >> significant changes would be amended to addit

Re: [openstack-dev] [pbr] [stable] [infra] How to generate .Z version increments on stable/liberty commits

On 4 August 2015 at 06:06, Doug Hellmann wrote: > Excerpts from Thierry Carrez's message of 2015-08-03 18:11:53 +0200: >> Jeremy Stanley wrote: >> > On 2015-08-03 14:46:51 +0200 (+0200), Thierry Carrez wrote: >> > [...] >> >> In order to make this work, it looks like we'd require: >> >> >> >> * pb

Re: [openstack-dev] [nova][oslo][policy] oslo.policy adoption in Nova.

Excerpts from Sergey Vilgelm's message of 2015-08-03 19:05:52 +0300: > If i understood correctly, the main difference is that the parse_rule > function is a private now in the oslo.policy library, also Jeffrey Zhang > has changed this function and put into nova.policy module. I offer remove > this

[openstack-dev] [nova] Feature Freeze Exception Request

Hello, I would like to request feature freeze exception for the implementation of Nested Quota Driver for Nova, which does the quota management of nested projects. Blueprint https://blueprints.launchpad.net/nova/+spec/nested-quota-driver-api Addr

Re: [openstack-dev] [Neutron][L3] Representing a networks connected by routers

Kevin, sorry for the delay in response. Keeping up on this thread was getting difficult while on vacation. tl;dr: I think it is worth it to talk through the idea of inserting some sort of a "subnet group thing" in the model to which floating ips (and router external gateways) will associate. It

Re: [openstack-dev] [pbr] [stable] [infra] How to generate .Z version increments on stable/liberty commits

On 2015-08-03 16:42:06 + (+), Ian Cordasco wrote: > Auto-tagging seems to be the least amount of work. That could be > done as a post-commit hook or post-receive (depending on where we > implement it) upstream. Well, not as a git hook but we would likely run it as a CI job in zuul's post p

Re: [openstack-dev] [Cinder] A possible solution for HA Active-Active

For example, to parallel the conversation with databases: "We want a database". Well, that means mongodb, postgres, mysql, berkeleydb, etc "Oh, well, I need it to be a relational db", Well, that means postgresq, mysql, etc "Oh, and I need recursive queries"... that excludes even more.

Re: [openstack-dev] [pbr] [stable] [infra] How to generate .Z version increments on stable/liberty commits

Excerpts from Thierry Carrez's message of 2015-08-03 18:11:53 +0200: > Jeremy Stanley wrote: > > On 2015-08-03 14:46:51 +0200 (+0200), Thierry Carrez wrote: > > [...] > >> In order to make this work, it looks like we'd require: > >> > >> * pbr changes so that it supports a mode where every commit o

Re: [openstack-dev] [openstack-announce] [release][oslo] tooz release 1.21.0 (liberty)

FUCK OFF From: "dava...@gmail.com" mailto:dava...@gmail.com>> Reply-To: "openstack-dev@lists.openstack.org" mailto:openstack-dev@lists.openstack.org>> Date: Monday, August 3, 2015 at 12:50:00PM To: "openstack-annou...@lists.op

Re: [openstack-dev] [Cinder] A possible solution for HA Active-Active

Excerpts from Devananda van der Veen's message of 2015-08-03 08:53:21 -0700: > On Mon, Aug 3, 2015 at 8:41 AM Joshua Harlow wrote: > > > Clint Byrum wrote: > > > Excerpts from Gorka Eguileor's message of 2015-08-02 15:49:46 -0700: > > >> On Fri, Jul 31, 2015 at 01:47:22AM -0700, Mike Perez wrote:

Re: [openstack-dev] [Cinder] A possible solution for HA Active-Active

We'll have a chance to discuss DB mutual exclusion at the API nodes at the Cider mid-cyle, which starts tomorrow. The details, issues, and realistic schedule for that will be a key piece to this whole puzzle, since anything else is seen as a temporary solution. -Original Message- From: G

Re: [openstack-dev] [Cinder] A possible solution for HA Active-Active

On Mon, Aug 03, 2015 at 03:42:48PM +, Fox, Kevin M wrote: > I'm usually for abstraction layers, but they don't always pay off very well > due to catering to the lowest common denominator. > > Lets clearly define the problem space first. IFF the problem space can be > fully implemented using

[openstack-dev] [Infra] Meeting Tuesday August 4th at 19:00 UTC

Hi everyone, The OpenStack Infrastructure (Infra) team is having our next weekly meeting on Tuesday August 4th, at 19:00 UTC in #openstack-meeting Meeting agenda available here: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting (anyone is welcome to to add agenda items) Everyone interest

Re: [openstack-dev] [Cinder] A possible solution for HA Active-Active

On Mon, Aug 03, 2015 at 07:01:45PM +1000, Morgan Fainberg wrote: > Lets step back away from tooz. Tooz for the sake of this conversation is as > much the same as saying zookeeper or consul or etcd, etc. We should be > focused (as both Flavio and Thierry said) on if we need DLM and what it will >

Re: [openstack-dev] [Neutron] Common Base class for agents

I would just de-dup anything that is obvious into a common class to inherit from. Don't go through any major re-factorings because that will just take longer to review and will probably need to be reworked anyway when we spend more time on the modular agent stuff later in the cycle. On Mon, Aug 3,

[openstack-dev] [Manila] Midcycle meetup highlights

Thanks to all of those who attended the midcycle. We had more than 20 attendees this cycle and excellent participation -- also some new faces! My apologies for the Google Hangouts failure. We ended up switching to Webex for the audio/video conferencing and it scaled significantly better. I exp

Re: [openstack-dev] [Cinder] encryption is not supported in ceph volume

On 7/30/2015 1:02 AM, Li, Xiaoyan wrote: Hi all, I created an encryption type, and create a volume in Ceph with the volume type. cinder encryption-type-create But failed to attach it to a VM. The error message shows that no device_path in connection_info. ^[[01;31m2015-07-30 05:55:57.117

Re: [openstack-dev] [designate] and [lbaas] - GSLB API and backend support

Hi Graham, Can we have your GSLB pull request merged to the repo https://github.com/gslb/gslb-specs/pull/1/files ? I would like to send another pull request based on these changes. Regards Kunal > On Jun 30, 2015, at 8:38 AM, Hayes, Graham w

Re: [openstack-dev] [Magnum]horizontal scalability

On Aug 2, 2015, at 7:40 PM, 王华 mailto:wanghua.hum...@gmail.com>> wrote: Hi all, As discussed in the Vancouver Summit, we are going to drop the bay lock implementation. Instead, each conductor will call Heat concurrently and rely on heat for concurrency control. However, I think we need an ap

Re: [openstack-dev] [pbr] [stable] [infra] How to generate .Z version increments on stable/liberty commits

On 8/3/15, 11:11, "Thierry Carrez" wrote: >Jeremy Stanley wrote: >> On 2015-08-03 14:46:51 +0200 (+0200), Thierry Carrez wrote: >> [...] >>> In order to make this work, it looks like we'd require: >>> >>> * pbr changes so that it supports a mode where every commit on the >>> branch increments .

[openstack-dev] [kolla][announce] Announcing the release of Kolla Liberty-2

Hi folks, the Kolla community is pleased to announce the release of the Kolla Liberty 2 milestone. This release fixes 77 bugs and implements 18 blueprints! Our community developed the following notable features: * Source building of containers * Ansible Deployment for core services * High

Re: [openstack-dev] [pbr] [stable] [infra] How to generate .Z version increments on stable/liberty commits

Jeremy Stanley wrote: > On 2015-08-03 14:46:51 +0200 (+0200), Thierry Carrez wrote: > [...] >> In order to make this work, it looks like we'd require: >> >> * pbr changes so that it supports a mode where every commit on the >> branch increments .Z >> >> * infra changes to automatically push the cor

Re: [openstack-dev] [Cinder] A possible solution for HA Active-Active

Devananda van der Veen wrote: On Mon, Aug 3, 2015 at 8:41 AM Joshua Harlow mailto:harlo...@outlook.com>> wrote: Clint Byrum wrote: > Excerpts from Gorka Eguileor's message of 2015-08-02 15:49:46 -0700: >> On Fri, Jul 31, 2015 at 01:47:22AM -0700, Mike Perez wrote: >>> On Mon

Re: [openstack-dev] [nova][oslo][policy] oslo.policy adoption in Nova.

If i understood correctly, the main difference is that the parse_rule function is a private now in the oslo.policy library, also Jeffrey Zhang has changed this function and put into nova.policy module. I offer remove this function from the nova and make a public in the oslo.policy. On Mon, Aug 3,

Re: [openstack-dev] [Cinder] A possible solution for HA Active-Active

On Mon, Aug 3, 2015 at 8:41 AM Joshua Harlow wrote: > Clint Byrum wrote: > > Excerpts from Gorka Eguileor's message of 2015-08-02 15:49:46 -0700: > >> On Fri, Jul 31, 2015 at 01:47:22AM -0700, Mike Perez wrote: > >>> On Mon, Jul 27, 2015 at 12:35 PM, Gorka Eguileor > wrote: > I know we've al

Re: [openstack-dev] How should we expose host capabilities to the scheduler

Dugger, Donald D said on Mon, Aug 03, 2015 at 05:39:49AM +: > Also note that, although many capabilities can be represented by > simple key/value pairs (e.g. the presence of a specific special > instruction) that is not true for all capabilities (e.g. Numa topology > doesn't really fit into thi

[openstack-dev] [Neutron] Common Base class for agents

Hi, I'm planning to add a new ml2 driver and agent to neutron supporting macvtap attachments [1]. Kyle already decided, that this code should land in the neutron tree [2]. The normal approach till now was to copy an existing agent code and modify accordingly, which lead to a lot of duplicated code

Re: [openstack-dev] [kolla] Mission change suggested by the TC for big tent

On 7/30/15, 4:26 PM, "Doug Hellmann" wrote: >Excerpts from Steven Dake (stdake)'s message of 2015-07-30 15:27:15 +: >> >> On 7/29/15, 1:23 PM, "Doug Hellmann" wrote: >> >> >Excerpts from Steven Dake (stdake)'s message of 2015-07-29 20:07:26 >>+: >> >> Doug Hellman of the TC suggested

Re: [openstack-dev] [Cinder] A possible solution for HA Active-Active

I'm usually for abstraction layers, but they don't always pay off very well due to catering to the lowest common denominator. Lets clearly define the problem space first. IFF the problem space can be fully implemented using Tooz, then lets do that. Then the operator can choose. If Tooz cant and

Re: [openstack-dev] [Cinder] A possible solution for HA Active-Active

Clint Byrum wrote: Excerpts from Gorka Eguileor's message of 2015-08-02 15:49:46 -0700: On Fri, Jul 31, 2015 at 01:47:22AM -0700, Mike Perez wrote: On Mon, Jul 27, 2015 at 12:35 PM, Gorka Eguileor wrote: I know we've all been looking at the HA Active-Active problem in Cinder and trying our be

Re: [openstack-dev] [all] Need volunteers to test coverage 4.0 alpha release

On Mon, Aug 3, 2015 at 6:32 AM, Doug Hellmann wrote: > Do we have anyone willing to spend some time looking at the > incompatibilities Ned mentions below to ensure that we have a smooth > transition when 4.0 moves out of alpha? > > Doug > > Seems to work ok with keystone. There were a couple of p

Re: [openstack-dev] [Cinder] A possible solution for HA Active-Active

+1. From: Flavio Percoco [fla...@redhat.com] Sent: Monday, August 03, 2015 12:30 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Cinder] A possible solution for HA Active-Active On 03/08/15 00:49 +02

Re: [openstack-dev] [Cinder] A possible solution for HA Active-Active

Morgan Fainberg wrote: Lets step back away from tooz. Tooz for the sake of this conversation is as much the same as saying zookeeper or consul or etcd, etc. We should be focused (as both Flavio and Thierry said) on if we need DLM and what it will solve. So IMHO part of the problem with just

Re: [openstack-dev] [Cinder] Quobyte Cinder Driver revert?

On Fri, Jul 3, 2015 at 9:11 AM, Duncan Thomas wrote: > It was discussed on the mailing list, and at the weekly meeting. Mike had > had no response on the issue from the listed contact email, and the CI was > reporting failure for every patch for two months > > On 3 Jul 2015 17:33, "Silvan Kaiser"

Re: [openstack-dev] [neutron][lbaas] Horizon support for neutron-lbaas v2

For now, take this code and merge with exiting horizon setup (openstack_dashbord) and restart horizon. With that you will see loadbalancers_v2 panel on the left pane. Thanks, Vivek From: santosh sharma mailto:chitr.praya...@gmail.com>> Reply-To: "OpenStack Development Mailing List (not for usag

Re: [openstack-dev] [glance] Additions and removals for the glance-drivers team

This has been implemented. Thanks all for participation. On 8/3/15 10:14 AM, Nikhil Komawar wrote: > We asked Stuart personally during the recent Glance mid-cycle if he > wanted to join and he said yes. Guess it's appropriate time for > rotation now. > > On 8/1/15 11:44 PM, Flavio Percoco wrote: >

Re: [openstack-dev] [stable] [infra] How to auto-generate stable release notes

Thierry Carrez said on Mon, Aug 03, 2015 at 02:57:39PM +0200: > 1. we can maintain a Changelog document directly in the source code. > Rather than being straightly backported from master, commits with > significant changes would be amended to additionally modify that document. Wouldn't this cause

Re: [openstack-dev] [pbr] [stable] [infra] How to generate .Z version increments on stable/liberty commits

On 2015-08-03 14:46:51 +0200 (+0200), Thierry Carrez wrote: [...] > In order to make this work, it looks like we'd require: > > * pbr changes so that it supports a mode where every commit on the > branch increments .Z > > * infra changes to automatically push the corresponding tag when the > comm

[openstack-dev] [Glance] Artifacts sub team meeting 08/03

Hi, We had a very low turnout to the above meeting today. Hence, we did a very short update and ended it. You may find more details here: http://eavesdrop.openstack.org/meetings/glance_artifacts_sub_team/2015/glance_artifacts_sub_team.2015-08-03-14.10.html -- Thanks, Nikhil _

Re: [openstack-dev] [Keystone][Fernet] HA SQL backend for Fernet keys

Folks As Sergii G. already pointed out if you want this solution to work in production, you should provide common ways of synchronization between different processing entities. Otherwise your "very simple one-script solution" will be prone to errors such as race conditions and others. You need to

Re: [openstack-dev] [glance] Additions and removals for the glance-drivers team

We asked Stuart personally during the recent Glance mid-cycle if he wanted to join and he said yes. Guess it's appropriate time for rotation now. On 8/1/15 11:44 PM, Flavio Percoco wrote: > On 09/07/15 20:37 +0200, Flavio Percoco wrote: >> Greetings, >> >> I'd like to propose Stuart Mclaren for th

Re: [openstack-dev] How should we expose host capabilities to the scheduler

> -Original Message- > From: Dugger, Donald D [mailto:donald.d.dug...@intel.com] > Sent: Monday, August 3, 2015 7:40 AM > To: OpenStack Development Mailing List (not for usage questions) > Subject: [openstack-dev] How should we expose host capabilities to the > scheduler > > Without going

Re: [openstack-dev] [Cinder] A possible solution for HA Active-Active

Agree with Thierry. Let's define requirements. We are trying to solve HA not scale "infinitely" number of cinder instances running. Thanks, Arkady -Original Message- From: Gorka Eguileor [mailto:gegui...@redhat.com] Sent: Monday, August 03, 2015 3:44 AM To: OpenStack Development Mailing L

[openstack-dev] [mistral] Team meeting reminder - 08/03/2015

Hi, This is a reminder that we’ll have a team meeting today at #openstack-meeting at 16.00 UTC. Agenda: - Review action items - Current status (progress, issues, roadblocks, further plans) - Liberty-2 release - Open discussion Add your own items either by replying to this email or

Re: [openstack-dev] [Keystone][Fernet] HA SQL backend for Fernet keys

On Mon, Aug 3, 2015 at 7:03 AM, David Stanek wrote: > > On Mon, Aug 3, 2015 at 7:14 AM, Davanum Srinivas > wrote: > >> agree. "Native HA solution" was already ruled out in several email >> threads by keystone cores already (if i remember right). This is a >> devops issue and should be handled as

[openstack-dev] [stable] [infra] How to auto-generate stable release notes

Hi everyone, A month ago the stable branch team decided to move away from synchronized stable point releases and enable continuous stable branch delivery instead. A side-effect of this decision is that we need to move away from a model where we curate release notes for each stable point release,

Re: [openstack-dev] [neutron][lbaas] Horizon support for neutron-lbaas v2

Hi Vivek, How to get the lbaas v2 UI up with mentioned changelist? Thanks Santosh On Wed, Jul 29, 2015 at 8:24 AM, Jain, Vivek wrote: > Initial code for horizon lbaas v2 dashboard submitted: > > https://review.openstack.org/#/c/206797 > > Thanks, > vivek > > From: "Jain, Vivek" > Reply-To: "O

  1   2   >