Re: [openstack-dev] [nova] [infra] The same SRIOV / NFV CI failures missed a regression, why?

>-Original Message- >From: Monty Taylor [mailto:mord...@inaugust.com] >Sent: Saturday, March 26, 2016 3:27 PM >To: openstack-dev@lists.openstack.org >Subject: Re: [openstack-dev] [nova] [infra] The same SRIOV / NFV CI failures >missed a regression, why? > >On 03/25/2016 03:52 PM, J

[openstack-dev] [FUEL] Timeout of deployment is exceeded & Fuel does not autodetect my hardware.

Bonjour, Hello. I'm trying to deploy the basic 3 nodes architecture to learn OpenStack: 1 controller and 2 compute nodes. After several hours of deployment, I got this error 'Timeout of deployment is exceeded.'. So I tried to redeploy it but without success. I have installed Fuel 7.0 with lau

Re: [openstack-dev] [tricircle] playing tricircle with two node configuration

Very good. Cheers, S - Original Message - From: "joehuang" To: "Yipei Niu" , "Vega Cai" Cc: "OpenStack Development Mailing List (not for usage questions)" , ski...@redhat.com Sent: Thursday, March 31, 2016 5:07:24 PM Subject: RE: [openstack-dev] [tricircle] playing tricircle with two n

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

Kevin, I am not directly answering your question, but from the perspective of Kolla, our upgrades are super simple because we don't make a big mess in the first place to upgrade from. In my experience, this is the number one problem with upgrades – everyone makes a mess of the first deployment

Re: [openstack-dev] [TripleO] PLUMgrid Neutron Integration for stable/mitaka

On Thu, Mar 31, 2016 at 10:24:26AM +0500, Qasim Sarfraz wrote: >Hi TripleO Folks, >As Mitaka branch was cut few days ago, I would like a request for backport >for PLUMgrid Neutron integration patch [1]. The patch has been in progress >for a while and adds support for enabling PLUMgr

[openstack-dev] [Heat] Re-evaluate conditions specification

Hi all, As the patches for conditions support are incoming, I've found something in the code (and the spec) I'm not really happy with. We're creating a new top-level section in the template called "conditions" which holds names that can be reused for conditionally creating resource. While it's fi

Re: [openstack-dev] meeting topics for 3/31/2016 networking-sfc project IRC meeting

Hi, I would like to talk about modifying the chain to include port pair group (#1537023) and about effects of having port security disabled. Cheers Prithiv From: Cathy Zhang mailto:cathy.h.zh...@huawei.com>> Date: Thursday 31 March 2016

Re: [openstack-dev] [nova] API priorities in Newton

2016-03-31 5:36 GMT+08:00 Matt Riedemann : > > > On 3/30/2016 2:26 PM, Sean Dague wrote: > >> During the Nova API meeting we had some conversations about priorities, >> but this feels like the thing where a mailing list conversation is more >> inclusive to get agreement on things. I think we need

Re: [openstack-dev] [telemetry] Rescheduling IRC meetings

On Thu, Mar 31 2016, liusheng wrote: > Another personal suggestion: > > maybe we can have a weekly routine mail thread to present the things need to > be > discussed or need to be notified. The mail will also list the topics posted in > meeting agenda and ask to Telemetry folks if a online IRC m

Re: [openstack-dev] [FUEL] Timeout of deployment is exceeded & Fuel does not autodetect my hardware.

Hi Samer, On Thu, Mar 31, 2016 at 10:18 AM, Samer Machara < samer.mach...@telecom-sudparis.eu> wrote: > Bonjour, Hello. > > I'm trying to deploy the basic 3 nodes architecture to learn OpenStack: > 1 controller and 2 compute nodes. After several hours of deployment, I got > this error 'Timeout

Re: [openstack-dev] [Fuel] [RDO] Volunteers needed

Aleksandra, You are right, we need to split this task into several smaller work items. For the start, I have created BP [1]. Let's discuss this on Fuel IRC meeting [2] today. I have put this topic to the agenda. And this is a great idea to put this task into the list for interns. I'll certainly d

Re: [openstack-dev] [murano] Fw:Extending API via Plugins

I’d like to add my 2 cents for this: It’s really hard to read through the changes on pastes. May I ask you to submit it on gerrit for review as a WIP patch? This would allow us to give you proper feedback. I +1 Serg’s idea to add a formal spec for this change. May I ask you to submit one to mur

Re: [openstack-dev] [Heat] Re-evaluate conditions specification

On Thu, Mar 31, 2016 at 10:40:33AM +0200, Thomas Herve wrote: > Hi all, > > As the patches for conditions support are incoming, I've found > something in the code (and the spec) I'm not really happy with. We're > creating a new top-level section in the template called "conditions" > which holds na

Re: [openstack-dev] [nova][cinder] Fix nova swap volume (updating an attached volume) function

This [1] adds tests for swap volume with admin and non-admin case. I want to check behaviour with current code so not adding Depends-On on your fix. Once we have gate results then feel free to add Depends-On or I will add. I think virt driver does not do attach/detach but we can re-verify that on

[openstack-dev] [Fuel] New version of fuel-devops (2.9.20)

Hi All, We are going to update the 'fuel-devops' framework on our product CI to the version 2.9.20. Changes since 2.9.17: * Fixes: - Fixes related to time synchronization issues: [1], [2], [10] - Fix for 'dos.py create' CLI command [4] - Use 0644 access mode for libvirt volumes created by fuel-

[openstack-dev] [horizon] - oAuth tab proposal

Hi all, I would like to propose a new tab in "Access and security" web page. As you know, keystone offers an OAUTH plugin for authentication. This means that third party applications could access to OpenStack cloud resources using OAUTH. Now, this is possible using the CLI but there is nothing

Re: [openstack-dev] [Fuel] New version of fuel-devops (2.9.20)

I’ve just tried to look up for fuel-devops on PyPi and found nothing. Let’s set up everything to let OpenStack CI release this package to PyPi and start publish releases there. Also it’s better to use openstack-announce to announce new releases. - romcheg > 31 бер. 2016 р. о 11:52 Dennis Dmi

Re: [openstack-dev] [fuel] Component Leads Elections

Hi, I'm not sure if it's a right place to continue this discussion, but if there are doubts that such role is needed, we should not wait for another half a year to drop it. Also I'm not sure if a single engineer (or two engineers) can handle majority of upcoming patches + specs + meetings around

Re: [openstack-dev] [nova] API priorities in Newton

On Wed, 30 Mar 2016, Matt Riedemann wrote: - POC of Gabbi for additional API validation I'm assuming cdent would be driving this, and he's also working on the resource providers stuff for the scheduler, but might be a decent side project for him to stay sane. As Jay points out Sergey Nikit

Re: [openstack-dev] [Fuel] [Shotgun] Decoupling Shotgun from Fuel

Hi, Problems which I see with current Shotgun are: 1. Luck of parallelism, so it's not going to fetch data fast enough from medium/big clouds. 2. There should be an easy way to run it manually (it's possible, but there is no ready-to-use config), it would be really helpful in case if Nailgun/Astut

Re: [openstack-dev] [FUEL] Timeout of deployment is exceeded & Fuel does not autodetect my hardware.

Hi, According to logs I see manifest /etc/puppet/modules/osnailyfacter/modular/ceilometer/controller.pp was exceeded. However, at the same time I don't see any puppet.logs from primary-controllers :\ Though analysing other tasks like database.pp it was executed for 10 minutes when it usually tak

Re: [openstack-dev] [nova][cinder] Fix nova swap volume (updating an attached volume) function

I *think* it is significantly semanticist different to do detach, attach; with swap volume, no events are generated in the guest; that is why it is dangerous to expose to the tenant - if the volume contents is not identical, you get weird corruption as the guess flushes caches. I think this call o

Re: [openstack-dev] [FUEL] Timeout of deployment is exceeded & Fuel does not autodetect my hardware.

Hi, Sergii Here is the bug: https://bugs.launchpad.net/fuel/+bug/1564312 with the diagnostic snapshot. - Original Message - Sergii Golovatiuk sgolovatiuk at mirantis.com Thu Mar 31 09:09:39 UTC 2016 * Previous message: [openstack-dev] [FUEL] Timeout of deployment is exceeded &

[openstack-dev] [Nova] No rejoin-stack.sh script in my setup

Hi everyone, Could you give any help to my question here, please. http://stackoverflow.com/questions/36268822/no-rejoin-stack-sh-script-in-my-setup I'm blocked with the same problem since 10 days. Any help is considered. Regards, -- Ouadï Belmokhtar *Permanent Professor at EMSI-Rabat* *PhD Ca

Re: [openstack-dev] [telemetry] Rescheduling IRC meetings

Hi All, +1 on the on demand meeting schedule. Maybe we can also have some news flash mails week to summarize the progress in our sub-modules when we don't have the meeting. Just to keep people up to date. Will we already skip the today's meeting? Thanks, /Ildikó > -Original Message-

[openstack-dev] [TC] TC Candidacy

I am Dean Troyer and would like to nominate myself as a candidate for re-election to the Technical Committee. I have a bit of history with OpenStack: I was early contributor to DevStack, I started Grenade to perform basic upgrade testing, and I started the OpenStackClient project. I currently work

Re: [openstack-dev] [nova] API priorities in Newton

On 03/30/2016 05:27 PM, Andrew Laski wrote: > > > On Wed, Mar 30, 2016, at 04:47 PM, Adam Young wrote: >> On 03/30/2016 04:16 PM, Andrew Laski wrote: >>> >>> On Wed, Mar 30, 2016, at 03:54 PM, Matt Riedemann wrote: On 3/30/2016 2:42 PM, Andrew Laski wrote: > > On Wed, Mar 30, 20

Re: [openstack-dev] [nova] API priorities in Newton

On 03/31/2016 04:55 AM, Alex Xu wrote: > > > 2016-03-31 5:36 GMT+08:00 Matt Riedemann > As discussed in IRC today, first steps (I think) are removing the > deprecated 'osapi_v21.enabled' option in newton so v2.1 can't be > disabled. > > And we need to think about logging a warni

Re: [openstack-dev] [Nova] No rejoin-stack.sh script in my setup

On 31/03/16 12:10, Ouadï Belmokhtar wrote: > Hi everyone, > > Could you give any help to my question here, please. > > http://stackoverflow.com/questions/36268822/no-rejoin-stack-sh-script-in-my-setup > > I'm blocked with the same problem since 10 days. Any help is considered. I think the recommen

Re: [openstack-dev] [release] proposed newton schedule

Doug Hellmann wrote: The proposed release schedule for Newton is available at http://releases.openstack.org/newton/schedule.html Please note that we will be using Thursdays for deadlines next cycle (that is, for the Feature Freeze at Newton-3 in week R-5 the deadline is Sept 8). Let us know her

Re: [openstack-dev] [Heat] Re-evaluate conditions specification

On Thu, Mar 31, 2016 at 10:40 AM, Thomas Herve wrote: > Hi all, > > As the patches for conditions support are incoming, I've found > something in the code (and the spec) I'm not really happy with. We're > creating a new top-level section in the template called "conditions" > which holds names that

Re: [openstack-dev] [Heat] Re-evaluate conditions specification

On Thu, Mar 31, 2016 at 11:39 AM, Qiming Teng wrote: > On Thu, Mar 31, 2016 at 10:40:33AM +0200, Thomas Herve wrote: >> Hi all, >> >> As the patches for conditions support are incoming, I've found >> something in the code (and the spec) I'm not really happy with. We're >> creating a new top-level

[openstack-dev] [Fuel][Swarm blocker] Release data contain liberty name on mitaka packages

Folks, There is a bug that is tagged as a swarm blocker [1] and two patches that fix it. One of them is for nailgun [2] and another one is for fuel-library [3]. The reason I write here is that those patches seem to fix the issue but they will never pass tests on the CI when they are tested apar

Re: [openstack-dev] [telemetry] Rescheduling IRC meetings

ie. the new PTL should checkpoint with subteam leads regularly to review spec status or identify missing resources on high-priority items? as some feedback, re: news flash mails, we need a way to promote roadmap backlog items better. i'm not sure anyone looks at Road Map page... maybe we need t

[openstack-dev] 答复: [Heat] Re-evaluate conditions specification

The conditions function has been requested for a long time, and there have been several previous discussions, which all ended up in debating the implementation, and no result. https://review.openstack.org/#/c/84468/3/doc/source/template_guide/hot_spec.rst https://review.openstack.org/#/c/153771/1

[openstack-dev] [Glance] Mitaka RC2 available

A new release candidate was rolled for Glance to include the greatest and latest of the work of the I18N translations team ! You can find the RC2 source code tarball at: https://tarballs.openstack.org/glance/glance-12.0.0.0rc2.tar.gz Unless release-critical issues are found that warrant a last

[openstack-dev] [puppet] away 2 days, next week

I'll be away next week, Tuesday and Wednesday for personal reasons, with very rare Internet access. Denis Egorenko (degorenko on IRC) will handle the PTL role during this time, and lead the weekly meeting. If anything happens and someone needs Puppet OpenStack PTL decision on something, we can tru

[openstack-dev] [Barbican] Mitaka RC2 available

Due to one release-critical issue spotted in Barbican during RC1 testing, a new release candidate was created for Mitaka. You can find the RC2 source code tarball at: https://tarballs.openstack.org/barbican/barbican-2.0.0.0rc2.tar.gz Unless new release-critical issues are found that warrant a

Re: [openstack-dev] [Nova] No rejoin-stack.sh script in my setup

Hi, rejoin-stack.sh has been removed 14 days ago by https://review.openstack.org/#/c/291453/ You should use the "screen" command now. (e.g screen -R) On Thu, Mar 31, 2016 at 1:06 PM, Ouadï Belmokhtar < ouadi.belmokh...@gmail.com> wrote: > Hi everyone, > > Could you give any help to my question h

Re: [openstack-dev] [nova] Is the Intel SRIOV CI running and if so, what does it test?

>-Original Message- >From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] >Sent: Wednesday, March 30, 2016 4:22 PM >To: OpenStack Development Mailing List (not for usage questions) > >Cc: Feng, Shaohe >Subject: [openstack-dev] [nova] Is the Intel SRIOV CI running and if so, wh

[openstack-dev] [Trove] Mitaka RC2 available

Due to one release-critical issue spotted in Trove during RC1 testing, a new release candidate was created for Mitaka. You can find the RC2 source code tarball at: https://tarballs.openstack.org/trove/trove-5.0.0.0rc2.tar.gz Unless new release-critical issues are found that warrant a last-minu

Re: [openstack-dev] [telemetry] Rescheduling IRC meetings

On Thu, Mar 31 2016, Ildikó Váncsa wrote: > +1 on the on demand meeting schedule. Maybe we can also have some news flash > mails week to summarize the progress in our sub-modules when we don't have the > meeting. Just to keep people up to date. That sounds a good idea. If anyone is motivated to d

[openstack-dev] [Ironic][Neutron] Integration status

Hello Community, I'm happy to announce that new experimental job 'ironic-multitenant-network' is stabilized and working. This job allows to test Ironic multitenancy patches at the gates with help of networking-generic-switch [1]. Unfortunately depends-on doesn't work for python-ironicclient [2] si

[openstack-dev] [Sahara] Mitaka RC2 available

Due to one release-critical issue spotted in Sahara during RC1 testing, a new release candidate was created for Mitaka. You can find the RC2 source code tarballs at: https://tarballs.openstack.org/sahara/sahara-4.0.0.0rc2.tar.gz https://tarballs.openstack.org/sahara-dashboard/sahara-dashboard-4

Re: [openstack-dev] [docs] [api] Oh Swagger, where art thou?

Some more details on progress, because this is getting closer every day. There is now an api-ref target on the Nova project. The entire work in progress stream has been rebased into 2 patches to a top level api-ref/ directory structure in the Nova tree - https://review.openstack.org/#/q/status:ope

[openstack-dev] [Nova] Mitaka RC3 available

Due to new release-critical issues spotted in Nova during RC2 testing, a new release candidate was created for Mitaka. You can find the RC3 source code tarball at: https://tarballs.openstack.org/nova/nova-13.0.0.0rc3.tar.gz Unless new release-critical issues are found that warrant a last-minut

[openstack-dev] [Heat] Mitaka RC3 available

Due to new release-critical issues spotted in Heat during RC2 testing, a new release candidate was created for Mitaka. You can find the RC3 source code tarball at: https://tarballs.openstack.org/heat/heat-6.0.0.0rc3.tar.gz Unless new release-critical issues are found that warrant a last-minute

Re: [openstack-dev] [nova] API priorities in Newton

2016-03-31 19:21 GMT+08:00 Sean Dague : > On 03/31/2016 04:55 AM, Alex Xu wrote: > > > > > > 2016-03-31 5:36 GMT+08:00 Matt Riedemann > > As discussed in IRC today, first steps (I think) are removing the > > deprecated 'osapi_v21.enabled' option in newton so v2.1 can't be > > disable

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

On Thu, Mar 31, 2016 at 12:12 AM, Fox, Kevin M wrote: > The main issue is one of upgradability, not stability. We all know tripleo > is stable. Tripleo cant do upgrades today. We're looking for ways to get > there. So "upgrading" to ansible isnt nessisary for sure since folks > deploying tripleo t

Re: [openstack-dev] [all] Austin Design Summit track layout

OK, please find attached the final layout. Changes: - Swapped Oslo and Stable fishbowl sessions on Thursday afternoon. - Swapped Fuel and Swift workroom sessions on Thursday afternoon This will be pushed to the official schedule ASAP and then PTLs will be able to tweak titles and descriptions f

Re: [openstack-dev] [Ironic][Neutron] Integration status

On Thu, Mar 31, 2016 at 03:37:53PM +0300, Vasyl Saienko wrote: > Hello Community, > > I'm happy to announce that new experimental job > 'ironic-multitenant-network' is stabilized and working. This job allows to > test Ironic multitenancy patches at the gates with help of > networking-generic-switc

Re: [openstack-dev] 答复: [Heat] Re-evaluate conditions specification

> The conditions function has been requested for a long time, and there have > been several previous discussions, which all ended up in debating the > implementation, and no result. > https://review.openstack.org/#/c/84468/3/doc/source/template_guide/hot_spec.rst > https://review.openstack.org/#/c/

Re: [openstack-dev] [Fuel][library] CI gate for regressions detection in deployment data

It is time for update! The previous idea with the committed state and automatic cross-repo merge hooks in zuul seems too complex to implement. So, the "CI gate for blah blah" magically becomes now a manual helper tool for reviewers/developers, see the docs update [0], [1]. You may start using it r

Re: [openstack-dev] [telemetry] Rescheduling IRC meetings

Hi Gordon, > > ie. the new PTL should checkpoint with subteam leads regularly to review spec > status or identify missing resources on high-priority > items? I would say anything that we feel as useful information to people who read this mailing list. In this sense features that got implemente

Re: [openstack-dev] [docs] [api] Oh Swagger, where art thou?

On Thu, Mar 31, 2016 at 08:43:29AM -0400, Sean Dague wrote: > Some more details on progress, because this is getting closer every day. > > There is now an api-ref target on the Nova project. The entire work in > progress stream has been rebased into 2 patches to a top level api-ref/ > directory st

Re: [openstack-dev] [nova][neutron] What to do about booting into port_security_enabled=False networks?

On Wed, Mar 30, 2016 at 09:46:45PM -0500, Matt Riedemann wrote: > > > On 3/30/2016 5:55 PM, Armando M. wrote: > > > > > >On 29 March 2016 at 18:55, Matt Riedemann >> wrote: > > > > > > > >On 3/29/2016 4:44 PM, Armando M. wrote: > > > > > > > >On 29

Re: [openstack-dev] [docs] [api] Oh Swagger, where art thou?

On 03/31/2016 09:43 AM, Jim Rollenhagen wrote: > On Thu, Mar 31, 2016 at 08:43:29AM -0400, Sean Dague wrote: >> Some more details on progress, because this is getting closer every day. >> >> There is now an api-ref target on the Nova project. The entire work in >> progress stream has been rebased i

Re: [openstack-dev] [TripleO] tripleo-quickstart import

On 03/30/2016 02:16 PM, Paul Belanger wrote: > On Tue, Mar 29, 2016 at 08:30:22PM -0400, John Trowbridge wrote: >> Hola, >> >> With the approval of the tripleo-quickstart spec[1], it is time to >> actually start doing the work. The first work item is moving it to the >> openstack git. The spec ta

Re: [openstack-dev] [nova] Is the Intel SRIOV CI running and if so, what does it test?

As approved in [1] we've added Nova-Macvtap job as part of Mellanox Nova non-voting CI Our wiki page is [2] [1] http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack-nova.2016-03-30.log.html [2] https://wiki.openstack.org/wiki/ThirdPartySystems/Mellanox_CI Best Regards Lenny

Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core Reviewer

+1 On Tue, Mar 29, 2016 at 12:07 PM, Steven Dake (stdake) wrote: > Hey folks, > > Consider this proposal a +1 in favor of Vikram joining the core reviewer > team. His reviews are outstanding. If he doesn’t have anything useful to > add to a review, he doesn't pile on the review with more –1s wh

Re: [openstack-dev] 答复: [Heat] Re-evaluate conditions specification

On Thu, Mar 31, 2016 at 2:25 PM, Huangtianhua wrote: > The conditions function has been requested for a long time, and there have > been several previous discussions, which all ended up in debating the > implementation, and no result. > https://review.openstack.org/#/c/84468/3/doc/source/templat

Re: [openstack-dev] [nova][cinder] Fix nova swap volume (updating an attached volume) function

On 3/31/2016 5:58 AM, Duncan Thomas wrote: I *think* it is significantly semanticist different to do detach, attach; with swap volume, no events are generated in the guest; that is why it is dangerous to expose to the tenant - if the volume contents is not identical, you get weird corruption as

Re: [openstack-dev] [kolla][vote] Just make Mitaka deploy Liberty within the Liberty branch

So, a plan. My idea about this backport is to: 1. We write Mitaka code deploying Liberty, just liberty (remove deploy_liberty nonsense from patchset above) 2. We mark this code as Kolla 1.1.0 effectively deprecating what we call liberty today 3. Most of bugs found in master/stable-mitaka will als

Re: [openstack-dev] [nova] Is the Intel SRIOV CI running and if so, what does it test?

On 03/31/2016 08:31 AM, Znoinski, Waldemar wrote: > > > >-Original Message- > >From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] > >Sent: Wednesday, March 30, 2016 4:22 PM > >To: OpenStack Development Mailing List (not for usage questions) > > > >Cc: Feng, Shaohe > >Subject

Re: [openstack-dev] [Sahara][QA] Notes about the move of the Sahara Tempest API test to sahara-tests

On Sunday 20 of March 2016 21:07:06 Luigi Toscano wrote: > Hi, Small update on the plan: > > as discussed in the last (two) Sahara meetings, I'm working on moving the > Tempest API tests from the Tempest repository to the new sahara-tests > repository, which contains only (non-tempest) scenario t

Re: [openstack-dev] [nova] Is the Intel SRIOV CI running and if so, what does it test?

On 03/31/2016 10:34 AM, Anita Kuno wrote: > On 03/31/2016 08:31 AM, Znoinski, Waldemar wrote: >> >> >> >-Original Message- >> >From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] >> >Sent: Wednesday, March 30, 2016 4:22 PM >> >To: OpenStack Development Mailing List (not for usage q

Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes?

Egor, I agree with what you said, but I think we need to address the problem that some clouds are lack of public IP addresses. It is not uncommon that a private cloud is running without public IP addresses, and they already figured out how to route traffics in and out. In such case, a bay doesn

[openstack-dev] [Fuel] CI may be broken for about 2 hours

We’ve organized a tiger team in order to merge two patches with a series of patches [1,2] in order to fix a swarm blocker. Our plan is the following: 1) Merge [1] and [2] 2) Trigger a build 3) Upload the new ISO to the CI system while it lasses the BVT 4) If the BVT is fine, switch the CI system

Re: [openstack-dev] [magnum] Discuss the blueprint"support-private-registry"

Ricardo, Thanks for the willingness to implement the blueprint. I am looking forward to reviewing the implementation. Best regards, Hongbin From: Ricardo Rocha [mailto:rocha.po...@gmail.com] Sent: March-30-16 10:59 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re:

Re: [openstack-dev] [networking guide meeting] Meeting Tomorrow!

Hello Folks, Friendly reminder email that we have our networking guide team meeting in few minutes #openstack-meeting Matt will be chairing the meeting. Thanks, Edgar __ OpenStack Development Mailing List (not for usage q

Re: [openstack-dev] 答复: [Heat] Re-evaluate conditions specification

On Thu, Mar 31, 2016 at 09:21:43AM -0400, Rabi Mishra wrote: > If I understand the suggestion correctly, the only relation it has with > conditions is, > conditions are nothing but variables(boolean). > > conditions: { > 'for_prod': {equals: [{get_param: env_type}, 'prod']} > } > > would

Re: [openstack-dev] [horizon] - oAuth tab proposal

Could you put up a blueprint for discussion? We have a weekly meeting to review blueprints: https://wiki.openstack.org/wiki/Meetings/HorizonDrivers The blueprint template is here: https://blueprints.launchpad.net/horizon/+spec/template Thanks! Rob On 31 Mar 2016, at 10:57, Marcos Fermin Lobo

[openstack-dev] [tempest] Implementing tempest test for Keystone federation functional tests

Hi all, I'm working on resource federation at the Massachusetts Open Cloud. We want to implement functional test on the k2k federation, which requires authentication with both a local keystone and a remote keystone (in a different cloud installation). It also requires a K2K/SAML assertion exchange

Re: [openstack-dev] [fuel] Component Leads Elections

Hi fuelers, only few hours left until period of self-nomination will be closed, but so far we don't have neither consensus regarding how to proceed further nor candidates. I've increased period of self-nomination for another week (until April 7, 23:59 UTC) and expect to have decision about how we

[openstack-dev] [Neutron] Mitaka RC3 available

Due to release-critical issues spotted in Neutron during RC2 testing, a new release candidate was created for Mitaka. You can find the RC3 source code tarballs at: https://tarballs.openstack.org/neutron/neutron-8.0.0.0rc3.tar.gz https://tarballs.openstack.org/neutron-lbaas/neutron-lbaas-8.0.0.0rc3

Re: [openstack-dev] [tempest] Implementing tempest test for Keystone federation functional tests

On Thu, Mar 31, 2016 at 11:38:55AM -0400, Minying Lu wrote: > Hi all, > > I'm working on resource federation at the Massachusetts Open Cloud. We want > to implement functional test on the k2k federation, which requires > authentication with both a local keystone and a remote keystone (in a > diffe

Re: [openstack-dev] [docs] [api] Oh Swagger, where art thou?

On Thu, Mar 31, 2016 at 09:50:48AM -0400, Sean Dague wrote: > On 03/31/2016 09:43 AM, Jim Rollenhagen wrote: > > On Thu, Mar 31, 2016 at 08:43:29AM -0400, Sean Dague wrote: > >> Some more details on progress, because this is getting closer every day. > >> > >> There is now an api-ref target on the

Re: [openstack-dev] [nova] API priorities in Newton

2016-03-30 12:26 GMT-07:00 Sean Dague : > > One other issue that we've been blocking on for a while has been > Capabilities discovery. Some API proposed adds like live resize have > been conceptually blocked behind this one. Once upon a time there was a > theory that JSON Home was a thing, and woul

Re: [openstack-dev] [nova] API priorities in Newton

2016-03-30 12:54 GMT-07:00 Matt Riedemann : >>> - Microversion Testing in Tempest (underway) > > How much coverage do we have today? This could be like novaclient where > people just start hacking on adding tests for each microversion (assuming > gmann would be working on this). Yeah, gmann is wor

Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes?

Hongbin, It's correct, I was involved in two big OpenStack private cloud deployments and we never had public ips.In such case Magnum shouldn't create any private networks, operator need to provide network id/name or it should use default  (we used to have networking selection logic in scheduler)

Re: [openstack-dev] [magnum] Are Floating IPs really needed for all nodes?

A few things: Public IPs and Floating IPs are not the same thing. Some clouds have public IPs. Some have floating ips. Some have both. I think it's important to be able to have magnum work with all of the above. If the cloud does not require using a floating IP (as most do not) to get external

[openstack-dev] Floating IPs and Public IPs are not equivalent

Just a friendly reminder to everyone - floating IPs are not synonymous with Public IPs in OpenStack. The most common (and growing, thank you to the beta of the new Dreamcompute cloud) configuration for Public Clouds is directly assign public IPs to VMs without requiring a user to create a floa

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

Ideally it can roll the services one instance at a time while doing the appropriate load balancer stuff to make it seamless. Our experience has been even though services should retry, they dont always do it right. So better to do it with the lb proper if you can. Between ansible/container orches

Re: [openstack-dev] [Heat] Re-evaluate conditions specification

My initial reaction is that sounds good, but how is it different then params, or maybe a hidden param? Maybe they are conditionally assigned? Conditional params would be awesome too though. If param 1 is not set, then param 2 is required... Thanks, Kevin From:

Re: [openstack-dev] 答复: [Heat] Re-evaluate conditions specification

+1. This sounds good. The lack of any conditionals at all has caused a lot of pain. Thanks, Kevin From: Huangtianhua Sent: Thursday, March 31, 2016 5:25:29 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] 答复: [Heat] Re-

[openstack-dev] [release][horizon] Horizon Mitaka RC2 available

Due to release-critical issues spotted in Horizon during RC1 testing, a new release candidate was created for Mitaka. You can find the RC2 source code tarball at: https://tarballs.openstack.org/horizon/horizon-9.0.0.0rc2.tar.gz Unless new release-critical issues are found that warrant a last-minu

[openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer team

Hi all, Eli Qiao has been consistently contributed to Magnum for a while. His contribution started from about 10 months ago. Along the way, he implemented several important blueprints and fixed a lot of bugs. His contribution covers various aspects (i.e. APIs, conductor, unit/functional tests,

Re: [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer team

+1 from me for Eli Thanks, Dims On Thu, Mar 31, 2016 at 2:18 PM, Hongbin Lu wrote: > Hi all, > > > > Eli Qiao has been consistently contributed to Magnum for a while. His > contribution started from about 10 months ago. Along the way, he implemented > several important blueprints and fixed a lot

Re: [openstack-dev] [TC] TC Non-candidancy

Excerpts from Robert Collins's message of 2016-03-31 15:56:33 +1300: > Hi everyone - I'm not submitting my hat for the ring this cycle - I > think its important we both share the work, and bring more folk up > into the position of having-been-on-the-TC. I promise to still hold > strong opinions wea

Re: [openstack-dev] [neutron] OVSDB native interface as default in gate jobs

On Tue, Mar 29, 2016, at 07:34 PM, Kevin Benton wrote: > I'm not aware of any issues. Perhaps you can propose a patch to just > change > the default in Neutron to that interface and people can -1 if there are > any > concerns. Yes, please do. This is one of the nice things about pre merge testing,

[openstack-dev] PTL communication of offline time

I proposed a resolution to the TC regarding PTL leave of absences, outlining a workflow of communication: https://review.openstack.org/#/c/290141/ The proposal was struck down in favour of a change to the Project Team Guide: https://review.openstack.org/#/c/293170/ I recently was contacted by a PT

Re: [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer team

+1 for Eli Ton Ngo, From: Hongbin Lu To: "OpenStack Development Mailing List (not for usage questions)" Date: 03/31/2016 11:21 AM Subject:[openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer team Hi all, Eli Qiao has been consistent

[openstack-dev] [security] threat analysis, tags, and the road ahead

hey all, at the most recent ossp meeting[1], there was some extended discussion about threat analysis and the work that is being done to push this forward. in this discussion, there were several topics brought up around the process for doing these analyses on current projects and how the ossp

[openstack-dev] [election][tc] TC Candidacy

Friends, Colleagues, and Fellow Community Members, lend me your ears (or eyes as the case may be). I am pleased to submit for your consideration my candidacy for the technical committee (TC). You may know me from such projects as Keystone, and the “From Camera to Couch” segment of Jonathan Bryce’

Re: [openstack-dev] [kolla][tc] [security] threat analysis, tags, and the road ahead

Including tc and kolla Michael, Sounds good. I'll get the governance changes rolling for debate at the next TC meeting. Note I added this cross project topic for discussion Tuesday at summit (last item in the list) https://etherpad.openstack.org/p/newton-cross-project-sessions Regards, -steve

[openstack-dev] [all] Cross Project Session proposals due by Apr 2nd

Reminder that cross project session proposals are due by Apr 2nd - https://etherpad.openstack.org/p/newton-cross-project-sessions We've got 15 proposals at this point, and I expect a bunch to come in later this week. Also, if you aren't sure whether or not your proposal is "cross project enough",

Re: [openstack-dev] Floating IPs and Public IPs are not equivalent

On 03/31/2016 01:23 PM, Monty Taylor wrote: > Just a friendly reminder to everyone - floating IPs are not synonymous > with Public IPs in OpenStack. > > The most common (and growing, thank you to the beta of the new > Dreamcompute cloud) configuration for Public Clouds is directly assign > public

[openstack-dev] [tc][election] TC Candidacy

Hi Everyone, I'd like to submit my candidacy for the OpenStack Technical Committee. I've been involved with OpenStack since the Folsom cycle. In that time I've worked on a lot of varied parts of OpenStack. During this time I have started and led several key initiatives and projects (mostly center

[openstack-dev] [election][tc] Not Running for Re-Election

All- I wanted to drop a note to let everyone know that I will not seek re-election to the TC for this cycle. I’ve really enjoyed working with everyone in our community through the TC the past three years. I’m super excited by the candidates who are running where they’ll lead our community. I’

[openstack-dev] [fuel][ConfigDB] Separating node and cluster serialized data

One of the problems we've faced with trying to plug-in ConfigDB is trying to separate the cluster attributes from the node attributes in the serialized output (ie astute.yaml) I started talking with Alex S about how we could separate them after astute.yaml is prepared trying to ensure which was wh

  1   2   >