Re: [openstack-dev] [charms] Project mascot

I like the idea of the Kraken... though I think I like the giant squid over an octopus, but either one is in the same vein :-) On Mon, Jul 18, 2016 at 1:27 AM, James Page wrote: > Hi All > > As an approved project, we need to provide some ideas for a project mascot > for

[openstack-dev] [trove] no weekly meeting next week

We won't have our weekly meeting next week as we are going to be meeting anyway for our virtual mid-cycle. Thanks, -amrith __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] Mascot/logo for your project

Heidi, The Trove team came up with several logo options. The result of a vote was decisive: 1. Stingray [1] 2. A Clam with a Pearl in it. [2] I have heard of no one else wanting to use the Stingray so I would like to request that the foundation consider that our preference. Among the

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

On Wed, 2016-07-20 at 21:24 +0300, Duncan Thomas wrote: > On 20 July 2016 at 19:57, James Bottomley < > james.bottom...@hansenpartnership.com> wrote: > > > > > OK, I accept your analogy, even though I would view currency as the > > will to create and push patches. > > > > The problem you

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

And maybe this raises an interesting defininition mismatch in the conversation. There is archetectural stuff like, do we support 7 different web frameworks, or do we standardize on flask... python vs go. Theres also the architectural stuff at the, what interactive surface do you expose to

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

On Wed, 2016-07-20 at 18:18 +, Fox, Kevin M wrote: > I wish it was so simple. Its not. > > There is a good coding practice: > "The code is done, not when there is nothing more to add, but nothing > more to remove" > > Some of the more mature projects are in this mode of thinking now. >

[openstack-dev] [tacker] No weekly meeting next week - July 26th, 2016

As we are hosting our newton midcycle meetup next week [1], I'm cancelling our regular weekly irc meeting. Please continue to reach out to the team in #tacker IRC to flag any issues / reviews. - Sridhar [1] https://etherpad.openstack.org/p/tacker-newton-midcycle

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

I would argue Linus, yes. As he's constantly stepping up when a subsistem tries and breaks something for a user or creates a user facing mess and says, no, subsystem, no. breaking userspace is unacceptable, or, we're not adding support for an api we have to support forever thats very poorly

Re: [openstack-dev] Mascot/logo for your project

Hi Julien, The logos are offered on a per-project basis, based on the Yaml file that listed 57 projects approved by the TC. Thanks for asking me to clarify! Cheers, Heidi Joy __ Heidi Joy Tretheway Senior Marketing Manager, OpenStack Foundation 503 816 9769 | skype: heidi.tretheway

[openstack-dev] App Catalog IRC meeting Thursday July 21st

Join us Thursday for our weekly meeting, scheduled for July 21st at 17:00UTC in #openstack-meeting-3 The agenda can be found here, and please add to if you want to discuss something with the Community App Catalog team: https://wiki.openstack.org/wiki/Meetings/app-catalog Tomorrow we will be

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

Duncan Thomas wrote: On 20 July 2016 at 19:57, James Bottomley > wrote: OK, I accept your analogy, even though I would view currency as the will to create and push patches. The problem you

Re: [openstack-dev] Mascot/logo for your project

Hi Heidi, The Watcher team cames up with several mascot options, here is the list ordered by preference : 1. jelly fish 2. eagle 3. bee 4. hammer head shark Thanks, Antoine On Wed, Jul 20, 2016 at 9:01 PM, Amrith Kumar wrote: > Heidi, > > > > The Trove team came up with

[openstack-dev] Freezer - tmp_file issue

Hi! I’m rather new at this so let me know if this is the wrong place to ask for a change. I was trying to run the Freezer code without the trickle executable but with a configuration file. It wouldn’t run. So, I took a look and it appears that if you do not have a trickle executable but

[openstack-dev] [devstack] libvirt/qemu source install plugin.

Hi I recently had the need to test a feature (vhost-user reconnect) that was commit to the qemu source tree a few weeks ago. As there has been no release since then I needed to build from source so to that end I wrote a small devstack plugin to do just that. I was thinking of opening a review

[openstack-dev] [kolla] repo split

Hello. The repo split discussion that started at summit was brought up again at the midcycle. The discussion was focused around splitting the Docker containers and Ansible code into two separate repos [1]. One of the main opponents to the split is backports. Backports will need to be done by

[openstack-dev] [fuel-octane] Nominate Sergey Abramov to fuel-octane core

Hello, I would like to nominate Sergey Abramov to fuel-octane core due to his significant contribution to the project [1] and [2]. Best regards, Ilya Kharin. [1] http://stackalytics.com/report/contribution/fuel-octane/90 [2] http://stackalytics.com/?release=all=fuel-octane=marks_id=sabramov

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

> -Original Message- > From: Jay Pipes [mailto:jaypi...@gmail.com] > Sent: Wednesday, July 20, 2016 7:16 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage > Capabilities with ResourceProvider > > On 07/13/2016 01:37 PM,

Re: [openstack-dev] [nova][glance] snapshots are broken by default with newton and glance v2

On 7/18/2016 4:41 AM, Erno Kuvaja wrote: On Mon, Jul 18, 2016 at 5:19 AM, Nikhil Komawar wrote: Thanks Matt. I've scheduled for a release of the client this week. On 7/16/16 4:09 AM, Matt Riedemann wrote: This is more of a heads up than anything. Our internal CI is

Re: [openstack-dev] Mascot/logo for your project

On 19/07/16 12:26, gordon chung wrote: On 19/07/16 03:50 AM, Julien Danjou wrote: Heidi, could you confirm that it is a mascot per team or per project? Honestly, I don't think it'll suit us to have only one mascot/logo. It's gonna be hard to use a logo marked "Telemetry" as a branding for

Re: [openstack-dev] [kolla] repo split

+1 I was reluctant to repo split by Newton timeframe as it was crucial time to our project, people will start using it, and I didn't want to cause needless confusion. Now time is right imho. On 20 July 2016 at 15:48, Ryan Hallisey wrote: > Hello. > > The repo split

Re: [openstack-dev] FPGA as a dynamic nested resources

Roman Dobosz wrote on 2016/07/20 15:25:28: > From: Roman Dobosz > To: "OpenStack Development Mailing List (not for usage questions)" > > Cc: Ed Leafe > Date: 2016/07/20 15:30 > Subject: Re:

Re: [openstack-dev] [Horizon] Angular action services and initScope

You all sort of touched on what I am about to reiterate:   1. The scope was intended to be used as a way to propagate events up and down the chain (from table controller to step controller) since there was no real way to share information between controllers (remember that a modal dialog launches

Re: [openstack-dev] [cinder] [nova] os-brick privsep failures and an upgrade strategy?

On 07/12/2016 06:25 AM, Matt Riedemann wrote: We probably aren't doing anything while Sean Dague is on vacation. He's back next week and we have the nova/cinder meetups, so I'm planning on talking about the grenade issue in person and hopefully we'll have a plan by the end of next week to move

Re: [openstack-dev] [tc][all] Plugins for all

On 07/18/2016 06:49 AM, Dmitry Tantsur wrote: On 07/17/2016 11:04 PM, Jay Pipes wrote: On 07/14/2016 12:21 PM, Hayes, Graham wrote: A lot of the effects are hard to see, and are not insurmountable, but do cause projects to re-invent the wheel. For example, quotas - there is no way for a

Re: [openstack-dev] [Horizon] On testing...

I'm not sure if (3) was the thing we agreed upon (and if it will help us to detect issues in Horizon) but the rest of options definitely make sense to me. Also there is 5. Parallelize integration tests. On Wed, Jul 20, 2016 at 4:28 PM Richard Jones wrote: > Hi folks, >

Re: [openstack-dev] FPGA as a dynamic nested resources

Roman Dobosz wrote on 2016/07/20 02:03:28: > From: Roman Dobosz > To: openstack-dev > Date: 2016/07/20 02:07 > Subject: [openstack-dev] FPGA as a dynamic nested resources > > Hi all, > > Some time ago Jay

Re: [openstack-dev] Mascot/logo for your project

https://en.wikipedia.org/wiki/Platypus#/media/File:Wild_Platypus_4.jpg :) Thanks, Kevin From: Zane Bitter [zbit...@redhat.com] Sent: Wednesday, July 20, 2016 2:32 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] Mascot/logo for your

[openstack-dev] [Congress] Congress horizon plugin - congressclient/congress API auth issue - help

Hi all, I've been working on Policy UI (Horizon): Unable to get policies list (devstack) (https://bugs.launchpad.net/congress/+bug/1602837) for the past 3 days. Anusha is correct - it's an authentication problem, but I have not been able to fix it. I grabbed the relevant code in congress.py from

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

Excerpts from Fox, Kevin M's message of 2016-07-20 20:12:48 +: > And maybe this raises an interesting defininition mismatch in the > conversation. > > There is archetectural stuff like, do we support 7 different web frameworks, > or do we standardize on flask... python vs go. > Yeah meh,

Re: [openstack-dev] [nova][glance] snapshots are broken by default with newton and glance v2

Thanks Matt. The bug looked very descriptive so, I commented my thoughts there https://bugs.launchpad.net/python-glanceclient/+bug/1596602 On 7/20/16 4:18 PM, Matt Riedemann wrote: > On 7/18/2016 4:41 AM, Erno Kuvaja wrote: >> On Mon, Jul 18, 2016 at 5:19 AM, Nikhil Komawar >>

Re: [openstack-dev] [Horizon] On testing...

On 21 July 2016 at 10:13, Timur Sufiev wrote: > I'm not sure if (3) was the thing we agreed upon (and if it will help us > to detect issues in Horizon) but the rest of options definitely make sense > to me. > I think that's reasonable - moving the tests to tempest will

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

On Wed, 2016-07-20 at 20:01 +, Fox, Kevin M wrote: > I would argue Linus, yes. As he's constantly stepping up when a > subsistem tries and breaks something for a user or creates a user > facing mess and says, no, subsystem, no. breaking userspace is > unacceptable, or, we're not adding support

[openstack-dev] [Horizon] On testing...

Hi folks, Sorry I didn't make the meeting this morning :-( We touched on testing at the mid-cycle and again it came up in the meeting this morning. We identified two issues: 1. Our integration test suite cannot grow to too many more tests because they take too long to run (and get auto-killed).

Re: [openstack-dev] [kolla] repo split

-0 (My vote doesn't count). We had endless problems keeping containers and orchestration in sync when we had two repos. I am really impressed that Mitaka ansible can orchestrate Liberty containers. That really speaks volumes. And I understand there is a stable ABI now, but surely at some

Re: [openstack-dev] [TripleO] Delorean fail blocks CI for stable branches

On Wed, Jul 20, 2016 at 7:49 PM, Sagi Shnaidman wrote: > How then it worked before? Can you show me the patch that broke this > functionality in delorean? It should be about 15 Jul when jobs started to > fail. commented in lp > How then master branch works? It also runs on

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

2016-07-20 11:43 GMT-07:00 Mooney, Sean K : > > > > -Original Message- > > From: Jay Pipes [mailto:jaypi...@gmail.com] > > Sent: Wednesday, July 20, 2016 7:16 PM > > To: openstack-dev@lists.openstack.org > > Subject: Re: [openstack-dev] [Nova] [RFC]

Re: [openstack-dev] [Horizon] Angular action services and initScope

Thanks for the response, Thai! Before I get into addressing your specifics below, I've put up a proof of concept patch that modifies images create-volume to remove the need for scope: https://review.openstack.org/#/c/345145 On 21 July 2016 at 08:23, Thai Q Tran wrote: >

Re: [openstack-dev] FPGA as a dynamic nested resources

On Wed, 20 Jul 2016 10:07:12 +0100 "Daniel P. Berrange" wrote: Hey Daniel, thanks for the feedback. > > Thoughts? > > I'd suggest you'll increase your chances of success with nova design > approval if you focus on implementing a really simple usage scheme for > FPGA as the

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

2016-07-20 11:08 GMT-07:00 Jay Pipes : > On 07/18/2016 01:45 PM, Matt Riedemann wrote: > >> On 7/15/2016 8:06 PM, Alex Xu wrote: >> >>> >>> Actually I still think aggregates isn't good for Manage Caps, just as I >>> said in previous reply about Aggregates. One of reason is

[openstack-dev] [tripleo] moving tripleo-ci/test-environments into THT

Hi, We're currently using tripleo-ci to store our test-environments files (ie: multinode.yaml, etc). To make it compatible with our different versions of TripleO, we have 2 options: * Duplicate templates and use bash conditionals in tripleo-ci scripts to select which one we want at each release.

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

On 07/18/2016 01:45 PM, Matt Riedemann wrote: On 7/15/2016 8:06 PM, Alex Xu wrote: Actually I still think aggregates isn't good for Manage Caps, just as I said in previous reply about Aggregates. One of reason is just same with #2 you said :) And It's totally not managable. User is even no way

Re: [openstack-dev] [Nova] [RFC] ResourceProviderTags - Manage Capabilities with ResourceProvider

On 07/13/2016 01:37 PM, Ed Leafe wrote: On Jul 11, 2016, at 6:08 AM, Alex Xu wrote: For example, the capabilities can be defined as: COMPUTE_HW_CAP_CPU_AVX COMPUTE_HW_CAP_CPU_SSE COMPUTE_HV_CAP_LIVE_MIGRATION COMPUTE_HV_CAP_LIVE_SNAPSHOT (

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

I wish it was so simple. Its not. There is a good coding practice: "The code is done, not when there is nothing more to add, but nothing more to remove" Some of the more mature projects are in this mode of thinking now. (which is mostly good, really). They don't want to add features unless

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

On 20 July 2016 at 19:57, James Bottomley < james.bottom...@hansenpartnership.com> wrote: > > OK, I accept your analogy, even though I would view currency as the > will to create and push patches. > > The problem you describe: getting the recipients to listen and accept > your patches, is also a

Re: [openstack-dev] [PyCharm] [all] Revoking pycharm licences for non-active users

On Tue, May 17, 2016 at 4:22 PM, Swapnil Kulkarni wrote: > Hello All, > > As part of the JetBrains Community support OpenStack (active) > developers get access to community edition of PyCharm tool. From the > management perspective I am facing issue to allocate licences to new

Re: [openstack-dev] [horizon] Plugin stability, failing tests etc.

Hi, testing against stable release of horizon doesn't have any sense of me. when you have tests running against master and them are almost always passing it's much easier to found commit that caused a failure and fix the problem that it's introduced. anyway, it's great news that FF is moved a

Re: [openstack-dev] [oslo.db] [CC neutron] CIDR overlap functionality and constraints

On Tue, Jul 19 2016, Mike Bayer wrote: Hi Mike, > We've developed a system by which CIDR math, such as that of detecting region > overlaps, can be performed on a MySQL database within queries [1] [2]. This > feature makes use of a custom stored function I helped to produce which > provides

[openstack-dev] [TripleO] Delorean fail blocks CI for stable branches

HI, we have a problem with delorean build of stable branches in TripleO CI[1], and it seems like a rpm specs problem. It can be reproducible easily [2] Please, help with solution to this problem, all info is in the bug[1] Alan, if you think we use dlrn wrong, please point me out which line is

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

On Tue, Jul 19 2016, Clint Byrum wrote: > Perhaps if we form and start working together as a group, we can disect > why nothing happened, build consensus on the most important thing to do > next, and actually fix some architectural problems. The social structure > that teams have is a huge part

[openstack-dev] [new][documentation] openstackdocstheme 1.4.0 release

We are pleased to announce the release of: openstackdocstheme 1.4.0: OpenStack Docs Theme With source available at: http://git.openstack.org/cgit/openstack/openstackdocstheme Please report issues through launchpad: http://bugs.launchpad.net/openstack-manuals For more details, please

Re: [openstack-dev] [TripleO] Delorean fail blocks CI for stable branches

> git clone https://git.openstack.org/openstack/tripleo-heat-templates > cd tripleo-heat-templates/ > git checkout -b stable/mitaka origin/stable/mitaka ^ this is manually switching to the stable source branch > sed -i -e "s%distro=.*%distro=rpm-mitaka%" projects.ini > sed -i -e

Re: [openstack-dev] [oslo.db] [CC neutron] CIDR overlap functionality and constraints

Mike, On Tue, Jul 19, 2016 at 7:40 AM, Mike Bayer wrote: > Note that I use the term "function" and not "procedure" to stress that this > is not a "stored procedure" in the traditional sense of performing complex > business logic and persistence operations - this CIDR function

Re: [openstack-dev] FPGA as a dynamic nested resources

On Tue, 19 Jul 2016 15:51:26 -0700 Ed Leafe wrote: > >> Why would a VM program the slot? Wouldn’t it usually be at the > >> host level? > > > > Are there no cases where a VM might want to download a proprietary > > program into an FPGA? > > That doesn’t sound right to me, but

[openstack-dev] [monasca] Monasca Mid-Cycle Minutes

Notes for Monasca July Mid Cycle 2016 Minutes July 19 from 10:30am PDT to Dimensions Names/Values resources This blueprint needs to be updated. The PATCH part needs to be updated. The new URL is metrics/dimensions/names/values The use case is driven by Grafana and is part of the templating. In

Re: [openstack-dev] [horizon] Plugin stability, failing tests etc.

Yes, it would mean changing your requirements after a release. So, for example you might run two gate tests: - A voting Horizon-stable/milestone test, (or both) - A non-voting Horizon-master test That gives you a lot of control over making your tests passing (multiple patches to make the

[openstack-dev] [Monasca] Virtual Mid Cycle Coordinates - July 20

>Monasca Mid Cycle Day 2 >July 20 2016 >7am to noon PDT > >Webex > > >Join WebEx meeting: >https://cisco.webex.com/ciscosales/j.php?MTID=m84f9f81d7c1c171be6365716522 >d >e15e > >Meeting number: 205 141 519 >Meeting password: 8VyzUiyr > >Join by phone >+1-408-525-6800 Call-in toll number

Re: [openstack-dev] [Magnum] Does Docker-Swarm not support inter-node/vm inter-container networking ?

Hi Greg, We should have patches in the next few weeks and the target is to have this functionality in the Newton cycle. Ton Ngo, From: "Waines, Greg" To: "OpenStack Development Mailing List (not for usage questions)"

[openstack-dev] [requirements] Project Mascot

Hello, We had a discussion about project mascot for requirements team today at the team meeting. Some of the options mentioned are added to [1]. If you have any option, please add to the list. Also do not forget to provide preference. We will finalize the mascot on Monday July 25. [1]

Re: [openstack-dev] [Glare][Heat][TripleO] Heat artifact type

On Wed, Jul 20, 2016 at 5:12 AM, Qiming Teng wrote: > On Tue, Jul 19, 2016 at 06:44:06PM +0300, Oleksii Chuprykov wrote: > > Hello! > > > > Today it was announced that Glare is ready for public review > >

Re: [openstack-dev] [heat][yaql] Heat map replacement options

On 19/07/16 11:04, Steven Hardy wrote: On Fri, Jul 15, 2016 at 10:25:39AM +0100, Steven Hardy wrote: Hi all, I'm trying to figure out the cleanest way to do a replacement of values in a mapping (json parameter) in a heat template, e.g: ServiceNetMap: type: json default:

Re: [openstack-dev] [devstack] How to enable SSL in devStack?

Andrey Pavlov wrote: Hi, When I ran devstack with SSL I found a bug and tried to fix it - https://review.openstack.org/#/c/242812/ But no one agree with me. Try to apply this patch - it may help. Also there is a chance that new bugs present in devstack that prevented to install it with SSL.

Re: [openstack-dev] [devstack] How to enable SSL in devStack?

Hi, When I ran devstack with SSL I found a bug and tried to fix it - https://review.openstack.org/#/c/242812/ But no one agree with me. Try to apply this patch - it may help. Also there is a chance that new bugs present in devstack that prevented to install it with SSL. Regards, Andrey. On Wed,

Re: [openstack-dev] [neutron][qos] Egress minimum bandwidth assurance

Hello Ihar: Please, take a look to https://review.openstack.org/#/c/318531/. >> does it mean you want to set some queues on ports that have no qos policy >> attached? That’s exactly what I'm doing, because the unique way to shape traffic in OvS is at the end of the datapath. In other words,

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

Clint Byrum wrote: [...] But what I thought what the TC's job was, was benevolent dictators, which each subproject (or subsystem in linux terms) are required to give up final say to, so that sometimes the projects have to sacrifice a bit so that the whole can flourish and those benevolent

Re: [openstack-dev] [tricircle] A new contributor

Hi, team, Welcome Xiulin to join the team. Best Regards Chaoyi Huang ( joehuang ) From: Shinobu Kinjo [shinobu...@gmail.com] Sent: 20 July 2016 15:49 To: OpenStack Development Mailing List (not for usage questions) Cc: yinxiulin Subject: [openstack-dev]

Re: [openstack-dev] [storlets] IRC meeting times

Hi Eran, 08:00 UTC is good for me. I'm ok with Tuesday. Thank you, Takashi -Original Message- From: e...@itsonlyme.name [mailto:e...@itsonlyme.name] Sent: Wednesday, July 20, 2016 2:28 AM To: OpenStack Development Mailing List (not for usage questions)

[openstack-dev] how to attach a physical disk to a qemu instance?

hi: I want attach a physical disk to a qemu instance in devstack environment,But these methods have some problem. Method 1: step1 reference http://ronaldevers.nl/2012/10/14/adding-a-physical-disk-kvm-libvirt.html virsh edit instance-0001 you add the disk to

[openstack-dev] [tricircle] A new contributor

Hi Team, Please welcome a new contributor (CCed) for the Tricircle project. Cheers, Shinobu -- Email: shin...@linux.com shin...@redhat.com __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] FPGA as a dynamic nested resources

On Tue, Jul 19, 2016 at 08:03:28PM +0200, Roman Dobosz wrote: > Hi all, > > Some time ago Jay Pipes published etherpad[1] with ideas around > modelling nested resources, taking NUMA as an example. I was also > encouraged ;) to start this thread, on last Nova scheduler meeting. > > I was read

Re: [openstack-dev] FPGA as a dynamic nested resources

On Tue, 19 Jul 2016 12:40:50 -0700 Ed Leafe wrote: > > It can identified 3 levels of FPGA resources, which can be nested one > > on the others: > > > > 1. Whole FPGA. If used discrete FPGA, than even today it might be pass > > through to the VM. > Can you explain why this would

Re: [openstack-dev] [Fuel] Nominate Alexey Stepanov for fuel-qa and fuel-devops core

+1 On Mon, Jul 18, 2016 at 3:14 PM, Dmitry Tyzhnenko wrote: > +1 > > On Fri, Jul 15, 2016 at 4:41 PM, Artem Panchenko > wrote: > >> +1 >> >> >> On 15.07.16 16:25, Tatyana Leontovich wrote: >> >> +1 >> >> On Fri, Jul 15, 2016 at 4:08 PM,

[openstack-dev] [horizon] Plugin stability, failing tests etc.

Hey all, So we've had a few issues with plugin stability recently, and its apparent that many plugins are building off Horizon master as a dependency. I would really advise against this. A more manageable development process may be to: - Base stable plugins against a stable release of Horizon

Re: [openstack-dev] [horizon] Plugin stability, failing tests etc.

On 20/07/2016 10:16, Rob Cresswell wrote: > Hey all, > > So we've had a few issues with plugin stability recently, and its > apparent that many plugins are building off Horizon master as a > dependency. I would really advise against this. A more manageable > development process may be to: > > -

Re: [openstack-dev] [Magnum] Does Docker-Swarm not support inter-node/vm inter-container networking ?

Thanks Ton, When is the Docker libnetwork functionality forecasted to be available ? Greg. From: Ton Ngo Reply-To: "openstack-dev@lists.openstack.org" Date: Tuesday, July 19, 2016 at 6:58 PM To: "openstack-dev@lists.openstack.org"

Re: [openstack-dev] [Glare][Heat][TripleO] Heat artifact type

FWIW, option 2 is almost required unless we plan to be able to bundle multiple environments with a single template. While having a single environment for a single template can be useful, the even *more* useful scenario (and the primary one driving the development of environments initially) is

[openstack-dev] [searchlight] Thursday July 21 meeting cancelled

Due to our midcycle hangout today [0], we are cancelling the searchlight IRC meeting tomorrow (Thursday July 21). [0] https://etherpad.openstack.org/p/searchlight-newton-hangout __ OpenStack Development Mailing List (not for

Re: [openstack-dev] [TripleO] Delorean fail blocks CI for stable branches

On Wed, Jul 20, 2016 at 2:29 PM, Alan Pevec wrote: > > git clone https://git.openstack.org/openstack/tripleo-heat-templates > > cd tripleo-heat-templates/ > > git checkout -b stable/mitaka origin/stable/mitaka > > ^ this is manually switching to the stable source branch > > >

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

On Wed, 2016-07-20 at 11:58 +0200, Julien Danjou wrote: > On Tue, Jul 19 2016, Clint Byrum wrote: > > > Perhaps if we form and start working together as a group, we can > > disect why nothing happened, build consensus on the most important > > thing to do next, and actually fix some

Re: [openstack-dev] [devstack] How to enable SSL in devStack?

Rob Crittenden wrote: Andrey Pavlov wrote: Hi, When I ran devstack with SSL I found a bug and tried to fix it - https://review.openstack.org/#/c/242812/ But no one agree with me. Try to apply this patch - it may help. Also there is a chance that new bugs present in devstack that prevented to

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

Excerpts from James Bottomley's message of 2016-07-20 08:31:34 -0700: > So this is where the Open Source method takes over. Change is produced > by those people who most care about it because they're invested. To > take your Cinder example, you're unlikely to find them within Cinder > because

Re: [openstack-dev] [TripleO] Delorean fail blocks CI for stable branches

How then it worked before? Can you show me the patch that broke this functionality in delorean? It should be about 15 Jul when jobs started to fail. How then master branch works? It also runs on patched repo and succeeds. I don't think we can use this workaround, each time this source file will

Re: [openstack-dev] OpenStack Kolla - External Ceph

We use ceph with cinder and glance. I don't see a reason not to. We do not set nova to use it for anything but cinder volumes though. The reason being, if you set it up that way, your users have no way of opting out of the potential performance hit if using no local storage for non pets. If

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

+1 to the finding of a middle ground. The problem I've seen with your suggested OpenSource solution is the current social monetary system of OpenStack makes it extremely difficult. Each project currently prints its own currency. Reviews. It takes quite a few Reviews (time/effort) on a project

Re: [openstack-dev] [TripleO] Delorean fail blocks CI for stable branches

>> ^ ... --local here keeps local checkout untouched, so you end up with >> default rpm-master in distro git checkout. >> If you remove --local it will reset local checkouts to the branches >> specified in projects.ini >> > Alan, > I don't want to reset local checkouts and reset branches - I need

Re: [openstack-dev] [TripleO] Delorean fail blocks CI for stable branches

> as a quickfix in tripleo.sh you could patch dlrn and set local=True in correction, patch local=False there while running dlrn command with --local to keep source checkout as-is __ OpenStack Development Mailing List (not

Re: [openstack-dev] [horizon] Plugin stability, failing tests etc.

On 20/07/2016 15:13, Rob Cresswell wrote: > Yes, it would mean changing your requirements after a release. So, for > example you might run two gate tests: > > - A voting Horizon-stable/milestone test, (or both) > - A non-voting Horizon-master test > > That gives you a lot of control over making

Re: [openstack-dev] OpenStack Kolla - External Ceph

On Wed, Jul 6, 2016 at 1:47 AM, Steven Dake (stdake) wrote: > > At this point, I feel we are going a direction in which we try to wrap > everything anybody could possibly want to configure with Kolla by making > extensive use of global.yml. We would have to introduce flags

Re: [openstack-dev] [tc][all] Big tent? (Related to Plugins for all)

On Wed, 2016-07-20 at 16:08 +, Fox, Kevin M wrote: > +1 to the finding of a middle ground. Thanks ... I have actually been an enterprise architect (I just keep very quiet about it when talking Open Source). > The problem I've seen with your suggested OpenSource solution is the > current

Re: [openstack-dev] [horizon] Plugin stability, failing tests etc.

Kirill: The failures are just as visible, since the cores still control merging anyway. The only difference is that if it takes a few days to fix something in upstream Horizon, you needn't block your own content in the meantime. Later in the release cycle (around N-3, for example) cores could

[openstack-dev] [new][glance] glance_store 0.14.0 release (newton)

We are psyched to announce the release of: glance_store 0.14.0: OpenStack Image Service Store Library This release is part of the newton release series. With source available at: http://git.openstack.org/cgit/openstack/glance_store With package available at:

Re: [openstack-dev] [Glare][Heat][TripleO] Heat artifact type

I have a preference towards option 2 as well. I usually use templates with all the logic in it, and an environment file with just the specific parameters defined for launching an instance of the template so I can repeatedly deploy/delete/redeploy it. I've got a good template set I think that

Re: [openstack-dev] [horizon] Plugin stability, failing tests etc.

Initially I don’t think I like the idea of making master-horizon job non-voting for murano-dashboard. Here are some reasons:  1) We would still need to fix murano-dashboard to work with master horizon (since we would need to be released together) 2) The breakage would be less

Re: [openstack-dev] FPGA as a dynamic nested resources

On Jul 20, 2016, at 2:07 AM, Daniel P. Berrange wrote: > For FPGA, I'd like to see an initial proposal that assumed the FPGA > is pre-programmed & pre-divided into a fixed number of slots and simply > deal with this. This is similar to how we dealt with PCI SR-IOV initially