[openstack-dev] [Tricircle] LinuxCon+Container Con (Tokyo )

Does anybody from community is attending the tokyo event. Its from Jul 13-15 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://list

Re: [openstack-dev] Reg: Configuration Management tool for Openstack.

Hi, If you just started your journey for OpenStack, I recommend you to try "Packstack". With Packstack, you could deploy your OpenStack cluster simply with an all-in-one mode to play with. If you wish to add more nodes later, by giving the appropriate configurations in the answer file, your

Re: [openstack-dev] [Tricircle] LinuxCon+Container Con (Tokyo )

When? Cheers, S On Tue, Mar 8, 2016 at 5:43 PM, Khayam Gondal wrote: > Does anybody from community is attending the tokyo event. Its from Jul 13-15 > > __ > OpenStack Development Mailing List (not for usage questions) > Unsu

[openstack-dev] [L2-Gateway] Install and Configuration issue

Hi, I am trying to get the L2GW plugin working with my openstack setup. I did the installation from the git repo using setup.py install. I am having trouble getting the Neutron-server to take the plugin though. Here is the config line from the neutron.conf: # Plugins core_plugin = neutron.plugins.

Re: [openstack-dev] Reg: Configuration Management tool for Openstack.

Hi, Since I think Ansible is the best config management tool, you should try the openstack-ansible installer, or our Ansible based one: https://github.com/DoclerLabs/openstack Br, György > -Original Message- > From: cool dharma06 [mailto:cooldharm...@gmail.com] > Sent: 2016 március 7, h

Re: [openstack-dev] Reg: Configuration Management tool for Openstack.

Good post! http://docs.openstack.org/developer/openstack-ansible/install-guide/index.html So ansible?, I'm puppeter though... Cheers, S On Tue, Mar 8, 2016 at 7:49 PM, Gyorgy Szombathelyi wrote: > Hi, > > Since I think Ansible is the best config management tool, you should try the > openstack

Re: [openstack-dev] [Tricircle] LinuxCon+Container Con (Tokyo )

July 13,2015 to July 15,2015 in Tokyo Japan. http://events.linuxfoundation.org/events/linuxcon-japan Let me know if anyone is interested. Especially from Tricircle community. On Tue, Mar 8, 2016 at 3:28 PM, Shinobu Kinjo wrote: > When? > > Cheers, > S > > On Tue, Mar 8, 2016 at 5:43 PM, Khayam

Re: [openstack-dev] [Neutron][LBaaS]Removing LBaaS v1 - are weready?

Same with Radware. Hence my proposal. -Original Message- From: Vijay Venkatachalam [mailto:vijay.venkatacha...@citrix.com] Sent: Tuesday, March 08, 2016 3:42 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron][LBaaS]Removing LBaaS v1

[openstack-dev] [nova] Standardized executable return codes/logging conventions?

I'm working on a fix [1] for bug #1538227, "Failed `nova-manage db sync` returns exitcode of 0" [2]. Having done this, I've noted that there seems to be no consistent policy around (a) what return codes to use (if any), and (b) whether to use logging or printing. Are there any guidelines on this in

Re: [openstack-dev] [Neutron][LBaaS]Removing LBaaS v1 - are weready?

So this looks like only a database migration, right? -Original Message- From: Eichberger, German [mailto:german.eichber...@hpe.com] Sent: Tuesday, March 08, 2016 12:28 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Neutron][LBaaS]Removing

Re: [openstack-dev] [Tricircle] LinuxCon+Container Con (Tokyo )

If you want anyone to joint this linuxcon to present the Tricle, let me know. IMHO I could -; Cheers, S On Tue, Mar 8, 2016 at 8:09 PM, Khayam Gondal wrote: > July 13,2015 to July 15,2015 in Tokyo Japan. > http://events.linuxfoundation.org/events/linuxcon-japan > > Let me know if anyone is inter

[openstack-dev] [all] [api] Reminder: WSME is not being actively maintained

Last summer Lucas Gomes and I were press ganged into becoming core on WSME. Since then we've piecemeal been verifying bug fixes and generally trying to keep things moving. However, from the beginning we both agreed that WSME is _not_ a web framework that we should be encouraging. Though it looks

[openstack-dev] [OpenStack-Dev][All] Api development question

Hi all, I am working on a feature for share access in manila. For that lets say for creating the entity, I created client and server counterpart. I am stuck as my client request is not able to reach server resource I have created for it. This is client server log http://paste.openstack.org/show

Re: [openstack-dev] [packstack] Update packstack core list

> Hi, > > [post originally sent on RDO-list but I've been told I should use this > channel] > > I've looked at packstack core-list [1] and I suggest we revisit to keep > only active contributors [2] in the core members list. > > The list seems super big comparing to who is actually active on the

Re: [openstack-dev] [Tricircle] LinuxCon+Container Con (Tokyo )

Thanks Khayam for the info Shinobu do you have any initial thoughts on what you would like to present ? :) On Tue, Mar 8, 2016 at 7:19 PM, Shinobu Kinjo wrote: > If you want anyone to joint this linuxcon to present the Tricle, let me > know. > IMHO I could -; > > Cheers, > S > > On Tue, Mar 8,

Re: [openstack-dev] [all] [api] Reminder: WSME is not being actively maintained

Is there an estimate of how much work/time it would take to refactor the library to slowly satisfy those three points? Also, do we already have clear ideas on where we want to get? While the three points are clear from a general point of view, what does each of those points really mean? Which parts

Re: [openstack-dev] [all] [api] Reminder: WSME is not being actively maintained

On Tue, 8 Mar 2016, Stéphane Bisinger wrote: Is there an estimate of how much work/time it would take to refactor the library to slowly satisfy those three points? No, that is the biggest reason I'm calling it unmaintained. Neither Lucas nor I have the time nor interest in being the people who

Re: [openstack-dev] [tc] Leadership training proposal/info

On 07/03/16 23:44 -0800, Colette Alexander wrote: On Fri, Mar 4, 2016 at 12:54 PM, Colette Alexander wrote: Current status, btw is 5 TC members as a 'yes' for going on April 21/22  - the Thurs/Fri before the summit. 4 additional people have mentioned they're interested, but unable to

Re: [openstack-dev] [all] [api] Reminder: WSME is not being actively maintained

Which projects in OpenStack actually use WSME at this time? Best, -jay On 03/08/2016 07:10 AM, Chris Dent wrote: On Tue, 8 Mar 2016, Stéphane Bisinger wrote: Is there an estimate of how much work/time it would take to refactor the library to slowly satisfy those three points? No, that is the

Re: [openstack-dev] [all] [api] Reminder: WSME is not being actively maintained

On Tue, 8 Mar 2016, Jay Pipes wrote: Which projects in OpenStack actually use WSME at this time? sdague and I were just talking about this and using codesearch.openstack.org the list is something like (but probably not completely accurate): aodh blazar ceilometer cerberus

Re: [openstack-dev] [all] [api] Reminder: WSME is not being actively maintained

24 instances as shown by codesearch: http://codesearch.openstack.org/?q=%5E(wsme%7CWSME)&i=nope&files=%5E.*requirements.txt&repos= -- Dims On Tue, Mar 8, 2016 at 7:41 AM, Jay Pipes wrote: > Which projects in OpenStack actually use WSME at this time? > > Best, > -jay > > On 03/08/2016 07:10 AM, C

Re: [openstack-dev] [fuel][plugins] Should we maintain example plugins?

Igor, I agree with folks, that we have to fix plugin. You didn't mention any real reasons, why we should change workflow with example-plugin right now in the middle of release. If we are keeping support of the example plugin in 9.0 it should work from box w/o any black magic in other places. Nast

Re: [openstack-dev] [Heat] Dealing with nonexistent resources during resource-list / stack-delete

Hello, On 03/07/2016 04:48 PM, Zane Bitter wrote: On 04/03/16 04:35, Johannes Grassler wrote: [Uncaught client exceptions in resource plugins' add_dependencies() methods] Yes, you're right and this sucks. That's not the only problem we've had in this area recently - for example there was also:

Re: [openstack-dev] [Performance] Let's have next meeting on March 15th

Just a reminder: we won't have a meeting today! Happy Women's Day! Cheers, Dina On Tue, Mar 1, 2016 at 7:54 PM, Dina Belova wrote: > Folks, > > due to the schedule our next meeting > is going to happen > on March 8th, that's International

Re: [openstack-dev] [OpenStack-Dev][All] Api development question

"Not found" means API you request is not registered. AFAICS, you register "access_groups", but request "access-groups". Diff in symbols "_" and "-". On Tue, Mar 8, 2016 at 1:34 PM, wrote: > > > > > Hi all, > > > > I am working on a feature for share access in manila. > > For that lets say for cr

Re: [openstack-dev] [nova] Standardized executable return codes/logging conventions?

On Tue, Mar 8, 2016, at 06:16 AM, Finucane, Stephen wrote: > I'm working on a fix [1] for bug #1538227, "Failed `nova-manage db > sync` returns exitcode of 0" [2]. Having done this, I've noted that > there seems to be no consistent policy around (a) what return codes to > use (if any), and (b) wh

Re: [openstack-dev] [nova] How to fix the wrong usage of 'format' jsonschema keyword in server create API

2016-03-07 21:10 GMT+08:00 Jay Pipes : > On 03/07/2016 08:05 AM, Alex Xu wrote: > >> 2016-03-07 19:23 GMT+08:00 Sean Dague > >: >> >> On 03/07/2016 01:18 AM, Alex Xu wrote: >> > Hi, >> > >> > Due to this regression bughttps://launchpad.net/bugs/1552888, >> fo

[openstack-dev] [keystone] Single Sign On integration research

Hi, as you may know currently Keystone supports Single Sign-On (SSO) and as I think it is one of the most interesting features in Keystone. I've done research on Single Sign-On in Keystone. Practically I just tried to set up Keystone in 2 different configuration. As a result of my research I have 2

Re: [openstack-dev] [Kolla] DocImpact in reviews

I don't think we can really expect new contributors to understand all the magic flags. This isn't a typical problem - typically DocImpact is used correctly. But it is the responsibility of the core reviewers to make sure that new contributors aren't needlessly wasting time by triggering triage

Re: [openstack-dev] [keystone] Single Sign On integration research

Awesome blogs, Kseniya, thank you for sharing this! :) -jay On 03/08/2016 09:12 AM, Kseniya Tychkova wrote: Hi, as you may know currently Keystone supports Single Sign-On (SSO) and as I think it is one of the most interesting features in Keystone. I've done research on Single Sign-On in Keystone

Re: [openstack-dev] [keystone] Single Sign On integration research

Good job Kseniya :) A. On Tue, Mar 8, 2016 at 3:21 PM, Jay Pipes wrote: > Awesome blogs, Kseniya, thank you for sharing this! :) > -jay > > On 03/08/2016 09:12 AM, Kseniya Tychkova wrote: > >> Hi, >> as you may know currently Keystone supports Single Sign-On (SSO) and as >> I think it is one of

Re: [openstack-dev] [nova] Identifying Mitaka release blockers

On 3 March 2016 at 13:10, Markus Zoeller wrote: > We have now 11-15 days left [1] until it is planned to release the first > release candidate. To provide a stable release, we need to identify the > potential release blockers. Bugs which potentially block the release > should be tagged with "mitak

Re: [openstack-dev] [keystone] Single Sign On integration research

Looks great! I only have one suggestion for the ECP blog. We actually have keystoneauth plugins for ECP [1]. Instead of issuing a request in your example, you may be able to just use the federated auth plugin. [1] https://github.com/openstack/keystoneauth/blob/35cad4a2ef00339eb31d80458bafaada41a5

[openstack-dev] [neutron] Last chance to finish changes affecting DB schema for Mitaka

By tomorrow we intend to tag the heads of all the neutron alembic branches with the MITAKA label [1][2][3][4]. If you have a patch that adds an alembic migration and you want to get it in Mitaka you must be associated with a targeted BP/RFE/bug [5] and get your code merged by tomorrow (Wednesday,

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

n > #openstack-meeting4. > > https://wiki.openstack.org/wiki/Meetings/PuppetOpenStack > > As usual, free free to bring topics in this etherpad: > https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20160308 > > We'll also have open discussion for bugs & revie

Re: [openstack-dev] [kolla][vote] exception for backporting upgrades to liberty/stable

On Mon, Mar 7, 2016 at 11:00 AM, Sam Yaple wrote: > > Obviously I am +1 on committing to a stable _stable_ branch. And that has > always required Z upgrades. Luckily the work we did in master is also usable > for z upgrades. Without the ability to perform an update after a > vulnerability, we have

[openstack-dev] [keystone] Using multiple token formats in a one openstack cloud

Keystone supports both tokens and ec2 credentials simultaneously, but as far as I can tell, will only do a single token format (uuid, pki/z, fernet) at a time. Is it possible or advisable to configure keystone to issue multiple token formats? For example, I could configure two keystone servers,

Re: [openstack-dev] [Heat] Dealing with nonexistent resources during resource-list / stack-delete

Hello, On 03/07/2016 04:48 PM, Zane Bitter wrote: On 04/03/16 04:35, Johannes Grassler wrote: [Uncaught client exceptions in resource plugins' add_dependencies() methods] In the meantime, we need to find and squash every instance of this problem wherever we can like you said. It might also b

[openstack-dev] Interface detach results in incorrect DHCP6 functioning on higher-index interfaces

I'm using the latest Devstack installed as a standalone, and testing the interface detach functionality through the Horizon GUI. In my case, I have a special Linux image with DHCP and DHCPv6 enabled on all interfaces. Here is my config: - Two separate subnets, 'private', with DHCP enabled, and '

Re: [openstack-dev] [all] [api] Reminder: WSME is not being actively maintained

Excerpts from Chris Dent's message of 2016-03-08 11:25:48 +: > > Last summer Lucas Gomes and I were press ganged into becoming core on > WSME. Since then we've piecemeal been verifying bug fixes and generally > trying to keep things moving. However, from the beginning we both agreed > that WSM

Re: [openstack-dev] [Heat] Dealing with nonexistent resources during resource-list / stack-delete

On 08/03/16 10:40, Johannes Grassler wrote: Hello, On 03/07/2016 04:48 PM, Zane Bitter wrote: On 04/03/16 04:35, Johannes Grassler wrote: [Uncaught client exceptions in resource plugins' add_dependencies() methods] In the meantime, we need to find and squash every instance of this problem whe

Re: [openstack-dev] [keystone] Using multiple token formats in a one openstack cloud

This would be complicated to setup. How would the Openstack services validate the token? Which keystone node would they use? A better question is why would you want to do this? On Tue, Mar 8, 2016 at 8:45 AM, rezroo wrote: > Keystone supports both tokens and ec2 credentials simultaneously, but a

Re: [openstack-dev] [Congress] Issue with glancev2 datasource driver

Hi Masahito, The debug log is attached. Thanks, Bryan Sullivan > From: muroi.masah...@lab.ntt.co.jp > Date: Wed, 24 Feb 2016 10:41:17 +0900 > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [Congress] Issue with glancev2 datasource driver > > Hi Bryan, > > Could you show me

[openstack-dev] [trove][stable] proboscis tests randomly failing in stable branches; bug 1538506

This is a call for help on resolving bug 1538506 [1] where the proboscis tests randomly fail on the stable branches with something like: TypeError: create() got an unexpected keyword argument 'slave_of' Craig Vyvial has a proposed stable/kilo change [2] but it has some issues, at least from me

Re: [openstack-dev] [Heat] Dealing with nonexistent resources during resource-list / stack-delete

Hello, On 03/08/2016 04:57 PM, Zane Bitter wrote: On 08/03/16 10:40, Johannes Grassler wrote: On 03/07/2016 04:48 PM, Zane Bitter wrote: On 04/03/16 04:35, Johannes Grassler wrote: [Uncaught client exceptions in resource plugins' add_dependencies() methods] In the meantime, we need to find a

Re: [openstack-dev] [keystone] Using multiple token formats in a one openstack cloud

The basic idea is to let the openstack clients decide what sort of token optimization to use - for example, while a normal client uses uuid tokens, some services like heat or magnum may opt for pki tokens for their operations. A service like nova, configured for PKI will validate that token wit

Re: [openstack-dev] [keystone] Using multiple token formats in a one openstack cloud

On 03/08/2016 11:06 AM, Matt Fischer wrote: This would be complicated to setup. How would the Openstack services validate the token? Which keystone node would they use? A better question is why would you want to do this? On Tue, Mar 8, 2016 at 8:45 AM, rezroo > wr

Re: [openstack-dev] [keystone] Using multiple token formats in a one openstack cloud

This type of configuration is not supported as Matt highlighted. What problem are you trying to solve with having the multiple token formats? Before we discuss if it would be a good idea, we need to know what problem you are solving. On Tue, Mar 8, 2016 at 8:06 AM, Matt Fischer wrote: > This wou

Re: [openstack-dev] [keystone] Using multiple token formats in a one openstack cloud

On Tue, Mar 8, 2016 at 10:58 AM, Adam Young wrote: > On 03/08/2016 11:06 AM, Matt Fischer wrote: > > This would be complicated to setup. How would the Openstack services > validate the token? Which keystone node would they use? A better question > is why would you want to do this? > > On Tue, Mar

Re: [openstack-dev] [trove][stable] proboscis tests randomly failing in stable branches; bug 1538506

On 3/8/2016 10:17 AM, Matt Riedemann wrote: This is a call for help on resolving bug 1538506 [1] where the proboscis tests randomly fail on the stable branches with something like: TypeError: create() got an unexpected keyword argument 'slave_of' Craig Vyvial has a proposed stable/kilo change

Re: [openstack-dev] [Heat] Dealing with nonexistent resources during resource-list / stack-delete

On 08/03/16 08:03, Johannes Grassler wrote: Hello, On 03/07/2016 04:48 PM, Zane Bitter wrote: On 04/03/16 04:35, Johannes Grassler wrote: [Uncaught client exceptions in resource plugins' add_dependencies() methods] Yes, you're right and this sucks. That's not the only problem we've had in thi

Re: [openstack-dev] [trove][stable] proboscis tests randomly failing in stable branches; bug 1538506

Matt, As I just said in my earlier reply to you, Craig has been away for some time and I'll look into this. I don't know that we need to revert the change or take the route you propose. There may be a much simpler solution. I'll propose a change for your review. -amrith > -Original Messa

Re: [openstack-dev] [Neutron][LBaaS]Removing LBaaS v1 - are weready?

Does it work with DVR though? Probably would with Octavia since they are just vm's. Thanks, Kevin From: Eichberger, German [german.eichber...@hpe.com] Sent: Monday, March 07, 2016 4:11 PM To: OpenStack Development Mailing List (not for usage questions) Sub

[openstack-dev] [oslo] oslo.messaging dispatching into private/protected methods?

Hi all, As I was working through https://review.openstack.org/#/c/288719/ for kevin benton to do some things with in neutron it came to my understanding that this code (the dispatcher code that is) can dispatch into nearly arbitrary callables of any object (or that is what it looks like it ca

Re: [openstack-dev] [Neutron][LBaaS]Removing LBaaS v1 - are we ready?

Excerpts from Samuel Bercovici's message of 2016-03-02 07:06:30 -0800: > 2. HEAT Support - will it be ready in Mitaka? Side note, please remember, Heat is not an acronym. __ OpenStack Development Mailing List (not for us

Re: [openstack-dev] [tripleo] CI jobs failures

On 7 March 2016 at 18:22, Ben Nemec wrote: > On 03/07/2016 11:33 AM, Derek Higgins wrote: >> On 7 March 2016 at 15:24, Derek Higgins wrote: >>> On 6 March 2016 at 16:58, James Slagle wrote: On Sat, Mar 5, 2016 at 11:15 AM, Emilien Macchi wrote: > I'm kind of hijacking Dan's e-mail but

Re: [openstack-dev] [tripleo] CI jobs failures

On 03/08/2016 11:58 AM, Derek Higgins wrote: > On 7 March 2016 at 18:22, Ben Nemec wrote: >> On 03/07/2016 11:33 AM, Derek Higgins wrote: >>> On 7 March 2016 at 15:24, Derek Higgins wrote: On 6 March 2016 at 16:58, James Slagle wrote: > On Sat, Mar 5, 2016 at 11:15 AM, Emilien Macchi

[openstack-dev] [horizon] [searchlight] Horizon, Search, and Composability

Hello everybody, At the Horizon mid-cycle we had a lot of discussion on UI composability and searchability. Matt and Tyr provided a short presentation and demo at the mid-cycle. This morning I gave a more detailed presentation and demo via hangouts on air regarding Searchlight and Horizon. The

Re: [openstack-dev] [kolla][vote] Proposing Alicja Kwasniewska for core reviewer

The vote is unanimous. Welcome to the core reviewer team Alicja! Ping me when you get online next and our timezone overlaps, and I'll walk you through the differences in the gerrit interface you should know. I have made appropriate changes in gerrit. Regards -steve From: Steven Dake mailto:s

Re: [openstack-dev] [kolla][vote] exception for backporting upgrades to liberty/stable

Exceptions can always be rationalized which is one reason exceptions are evil among many. The facts however speak for themselves. If we don't have a way to introduce new content in liberty when CVEs are fixed, stable/liberty is just as flawed as the data loss problem which was the original tri

Re: [openstack-dev] [trove][stable] proboscis tests randomly failing in stable branches; bug 1538506

Matt, The correct solution for liberty is that we should fix the tests. Here's why I believe that this is the case. In pertinent part, the backtrace from your bug includes: 2016-01-27 07:02:06.777 | File "/home/jenkins/workspace/periodic-trove-python27-liberty/trove/tests/api/replication.py",

Re: [openstack-dev] [Neutron][LBaaS]Removing LBaaS v1 - are weready?

Yes, it’s Database only — though we changed the agent driver in the DB from V1 to V2 — so if you bring up a V2 with that database it should reschedule all your load balancers on the V2 agent driver. German On 3/8/16, 3:13 AM, "Samuel Bercovici" wrote: >So this looks like only a database mi

Re: [openstack-dev] [kolla][vote] exception for backporting upgrades to liberty/stable

Another tricky situation.. Given that changes to Docker were the cause of the first two backports I'd consider those to not be exceptions, but necessary adaptations that Kolla has to deal with. Unfortunately, this case seems more like an exception. But, I'm not opposed to a necessary exceptio

Re: [openstack-dev] [trove][stable] proboscis tests randomly failing in stable branches; bug 1538506

On 3/8/2016 12:35 PM, Amrith Kumar wrote: Matt, The correct solution for liberty is that we should fix the tests. Here's why I believe that this is the case. In pertinent part, the backtrace from your bug includes: 2016-01-27 07:02:06.777 | File "/home/jenkins/workspace/periodic-trove-pyth

Re: [openstack-dev] [trove][stable] proboscis tests randomly failing in stable branches; bug 1538506

On 3/8/2016 12:52 PM, Matt Riedemann wrote: On 3/8/2016 12:35 PM, Amrith Kumar wrote: Matt, The correct solution for liberty is that we should fix the tests. Here's why I believe that this is the case. In pertinent part, the backtrace from your bug includes: 2016-01-27 07:02:06.777 | File

Re: [openstack-dev] [trove][stable] proboscis tests randomly failing in stable branches; bug 1538506

See below. > -Original Message- > From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] > Sent: Tuesday, March 08, 2016 1:53 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [trove][stable] proboscis tests randomly > failing in stable branches; bug 1538506 > >

Re: [openstack-dev] [trove][stable] proboscis tests randomly failing in stable branches; bug 1538506

Matt, See inline below. -amrith > -Original Message- > From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] > Sent: Tuesday, March 08, 2016 2:00 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [trove][stable] proboscis tests randomly > failing in stable bran

Re: [openstack-dev] [tripleo] CI jobs failures

On Tue, Mar 8, 2016 at 12:58 PM, Derek Higgins wrote: > We discussed this at today's meeting but never really came to a > conclusion except to say most people wanted to try it. The main > objection brought up was that we shouldn't go dropping the nonha job, > that isn't what I was proposing so let

Re: [openstack-dev] [keystone] Using multiple token formats in a one openstack cloud

I don't think your example is right: "PKI will validate that token without going to any keystone server". How would it track revoked tokens? I'm pretty sure that they still get validated, they are stored in the DB even. I also disagree that there are different use cases. Just switch to fernet and

Re: [openstack-dev] [qa] Tempest removal of tempest.api.compute.test_authorization

On 02/16/2016 03:38 PM, Matthew Treinish wrote: > On Tue, Feb 09, 2016 at 07:41:18PM -0500, Sean Dague wrote: >> As proposed in this patch - https://review.openstack.org/#/c/271467/ >> >> These tests do some manipulation of the request URI to attempt to >> request Nova resources owned by a differen

[openstack-dev] [neutron][release] Releasing python-neutronclient 4.1.2?

Hi folks, There's a feature or two that are pending to be delivered in Mitaka [1,2], and those involve changes to both the server and client sides. Ideally we'd merge both sides in time for Mitaka RC and that implies that we would be able to release a new version of the client including changes [3

Re: [openstack-dev] [kolla][vote] exception for backporting upgrades to liberty/stable

The vote was not exactly unanimous. I counted the following: 1.1.0 Steven Dake +1 Paul Bourke +1 Martin Andre +1 Michal Rostecki -1 Jeff Peeler +1 Ryan Hallisey +1 Michal Rosteki -1 Michal Jasterzebski -1 Since there are 6 votes in favor out of the 11 person core review team, 1.1.0 will include

Re: [openstack-dev] [release] mitaka-3 development milestone

On Fri, Mar 4, 2016 at 11:49 AM, Thierry Carrez wrote: > Hello everyone, > > The last milestone of the Mitaka development cycle, "mitaka-3", is now > reached. Some OpenStack projects following the milestone-based release > schedule took the opportunity to publish a development artifact, which > c

[openstack-dev] [magnum] SELinux is temporarily disabled due to bug 1551648

Hi team, FYI. In short, we have to temporarily disable SELinux [1] due to bug 1551648 [2]. SELinux is an important security features for Linux kernel. It improves isolation between neighboring containers in the same host. In before, Magnum had it turned on in each bay node. However, we have to

Re: [openstack-dev] {openstack-dev][tc] Leadership training proposal/info

On 3/1/2016 4:41 PM, Colette Alexander wrote: Hello Stackers, This is the continuation of an ongoing conversation within the TC about encouraging the growth of leadership skills within the community that began just after the Mitaka summit last year[1]. After being asked by lifeless to do a bit

[openstack-dev] [ceilometer] Could not get ceilometer events for instances running on demo tenant

I have a single node configuration for devstack liberty working and I want to record all the *ceilometer events* like compute.instance.start, compute.instance.end, compute.instance.update etc occurred recently. I am unable to get any event occurred for instances running for demo project i.e when I

Re: [openstack-dev] {openstack-dev][tc] Leadership training proposal/info

On Tue, Mar 8, 2016 at 12:27 PM, Matt Riedemann wrote: > >> > So is this for only current TC members? What about people that aren't on > the TC? > > I asked in this in today's TC meeting but figured I'd ask here where it's > more global. Because of limited space in the class, and because of the

Re: [openstack-dev] [TripleO] core members for tripleo-ui

On Mon, 2016-02-29 at 18:32 +0100, Ana Krivokapic wrote: > On Mon, Feb 29, 2016 at 4:27 PM, Dan Prince > wrote: > > > > There is a new projects for the ui called tripleo-ui. As most of > > the > > existing TripleO core members aren't going to be reviewing UI > > specific > > patches is seems reas

Re: [openstack-dev] [trove][stable] proboscis tests randomly failing in stable branches; bug 1538506

On 3/8/2016 1:18 PM, Amrith Kumar wrote: Matt, See inline below. -amrith -Original Message- From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] Sent: Tuesday, March 08, 2016 2:00 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [trove][stable] proboscis tes

[openstack-dev] [neutron] no upgrades meeting on March 14

Hi all, a lot of subteam folks will take part in the code sprint in Brno next Mon-Wed, so we’ll cancel the next meeting. Next meeting will occur March 21. Ihar __ OpenStack Development Mailing List (not for usage questio

Re: [openstack-dev] [all] [api] Reminder: WSME is not being actively maintained

On 08/03/2016 6:25 AM, Chris Dent wrote: > > Last summer Lucas Gomes and I were press ganged into becoming core on > WSME. Since then we've piecemeal been verifying bug fixes and generally > trying to keep things moving. However, from the beginning we both agreed > that WSME is _not_ a web framew

Re: [openstack-dev] [release] mitaka-3 development milestone

Corey Bryant wrote: neutron 8.0.0.0b3: https://tarballs.openstack.org/neutron/neutron-8.0.0.0b3.tar.gz https://tarballs.openstack.org/neutron-fwaas/neutron-fwaas-8.0.0.0b3.tar.gz https://tarballs.openstack.org/neutron-lbaas/neutron-lbaas-8.0.0.0b3.tar.gz https://tarballs.open

Re: [openstack-dev] {openstack-dev][tc] Leadership training proposal/info

Excerpts from Colette Alexander's message of 2016-03-01 14:41:01 -0800: > Hello Stackers, > > This is the continuation of an ongoing conversation within the TC about > encouraging the growth of leadership skills within the community that began > just after the Mitaka summit last year[1]. After bei

Re: [openstack-dev] [kolla][vote] Proposing Alicja Kwasniewska for core reviewer

Thank you! I really appreciate being a part of Kolla project and now also core reviewers team! It is a pleasure to work with you guys. Thank you all for your support and help (especially for all -1 ;) ), wouldn't be here without you! Kind regards, Alicja PS best present for Women's Day ever! :

Re: [openstack-dev] [all] [api] Reminder: WSME is not being actively maintained

Excerpts from gordon chung's message of 2016-03-08 21:22:11 +: > > On 08/03/2016 6:25 AM, Chris Dent wrote: > > > > Last summer Lucas Gomes and I were press ganged into becoming core on > > WSME. Since then we've piecemeal been verifying bug fixes and generally > > trying to keep things moving

Re: [openstack-dev] [neutron][release] Releasing python-neutronclient 4.1.2?

Excerpts from Armando M.'s message of 2016-03-08 12:49:16 -0700: > Hi folks, > > There's a feature or two that are pending to be delivered in Mitaka [1,2], > and those involve changes to both the server and client sides. Ideally we'd > merge both sides in time for Mitaka RC and that implies that w

[openstack-dev] [horizon] Proposal to add Diana Whitten to horizon-core

I propose adding Diana Whitten[1] to horizon-core. Diana is an active reviewer, contributor and community member. Over the past couple of releases, Diana has driven extensive changes around theme-ability in Horizon and drastically increased the standardization of our use of bootstrap. During this

[openstack-dev] [kolla][release] Announcing Kolla Mitaka-3 milestone release \o/

Fellow OpenStackers, The Kolla community is pleased to announce the release of Mitaka milestone #3. Angus Salkeld has agreed to be our release manager for the kolla-mesos repository. As an aside, we held our midcycle during mitaka-3 development, for which the notes can be found here: https

[openstack-dev] [neutron][taas] Proposal of Dashboard for TaaS

Thanks Soichi and Kaz for your work on implementing Horizon (dashboard) support for TaaS. The proposal (with screen shots) discussed in our recent IRC meeting look very nice. Here are some additional suggestions for improvement. 1. General a. When a port is being selected (for a t

Re: [openstack-dev] {openstack-dev][tc] Leadership training proposal/info

On Tue, Mar 8, 2016 at 1:37 PM, Doug Hellmann wrote: > > > As I understood it when this course was originally proposed, the > idea was to have a few folks already in leadership positions go > take the training and evaluate it. Then, assuming the evaluation > was good, we would offer it to (or at

Re: [openstack-dev] {openstack-dev][tc] Leadership training proposal/info

On Tue, Mar 8, 2016 at 2:34 PM, Colette Alexander < colettealexan...@gmail.com> wrote: > So I laid out some of the questions I think the community could benefit > from alignment on in the etherpad I started already[0], but one of the > things that really struck me when talking to various members o

Re: [openstack-dev] [neutron][release] Releasing python-neutronclient 4.1.2?

On 8 March 2016 at 15:07, Doug Hellmann wrote: > Excerpts from Armando M.'s message of 2016-03-08 12:49:16 -0700: > > Hi folks, > > > > There's a feature or two that are pending to be delivered in Mitaka > [1,2], > > and those involve changes to both the server and client sides. Ideally > we'd >

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On Mon, Mar 7, 2016 at 9:52 PM, Richard Jones wrote: > We've solved *most* of the issues around releasing new xstatic packages, > documented here[1] (and related documentation). > > We have one final issue that's blocking us, which is that during the > xstatic release there will be a point at whi

Re: [openstack-dev] [trove][stable] proboscis tests randomly failing in stable branches; bug 1538506

On 3/8/2016 3:17 PM, Matt Riedemann wrote: On 3/8/2016 1:18 PM, Amrith Kumar wrote: Matt, See inline below. -amrith -Original Message- From: Matt Riedemann [mailto:mrie...@linux.vnet.ibm.com] Sent: Tuesday, March 08, 2016 2:00 PM To: openstack-dev@lists.openstack.org Subject: Re:

Re: [openstack-dev] [horizon] Proposal to add Diana Whitten to horizon-core

big +1 from me. She made a lot of contribution in making theming better for horizon and also prevented potential issues through reviews. Thanks for all the hard work, Diana. -Lin On Tue, Mar 8, 2016 at 2:06 PM, David Lyle wrote: > I propose adding Diana Whitten[1] to horizon-core. > > Diana is

Re: [openstack-dev] [Heat] Dealing with nonexistent resources during resource-list / stack-delete

On 09/03/16 05:41, Johannes Grassler wrote: Hello, On 03/08/2016 04:57 PM, Zane Bitter wrote: On 08/03/16 10:40, Johannes Grassler wrote: On 03/07/2016 04:48 PM, Zane Bitter wrote: On 04/03/16 04:35, Johannes Grassler wrote: [Uncaught client exceptions in resource plugins' add_dependencies()

Re: [openstack-dev] [horizon] Proposal to add Diana Whitten to horizon-core

+1, no questions asked. It is rare to find somebody with the passion that Diana has shown. From: Lin Hua Cheng mailto:os.lch...@gmail.com>> Reply-To: OpenStack List mailto:openstack-dev@lists.openstack.org>> Date: Tuesday, March 8, 2016 at 3:48 PM To: OpenStack List mailto:openstack-dev@lists.o

Re: [openstack-dev] [horizon] Proposal to add Diana Whitten to horizon-core

+1 we need Diana's perspective, knowledge and enthusiasm On 9 March 2016 at 10:03, Tripp, Travis S wrote: > +1, no questions asked. It is rare to find somebody with the passion that > Diana has shown. > > From: Lin Hua Cheng mailto:os.lch...@gmail.com>> > Reply-To: OpenStack List openstack-dev@

Re: [openstack-dev] [keystone] [horizon] [qa] keystone versionless endpoints and v3

On Tue, Feb 23, 2016 at 8:49 PM, Jamie Lennox wrote: > > > On 18 February 2016 at 10:50, Matt Fischer wrote: > >> I've been having some issues with keystone v3 and versionless endpoints >> and I'd like to know what's expected to work exactly in Liberty and beyond. >> I thought with v3 we used ve

Re: [openstack-dev] [Horizon][app-catalog] How do we move forward with xstatic releases?

fyi, we are planning on using the xstatic packages for the app catalog website so we can share as much code as possible with horizon and the app catalog horizon plugin. So it will affect the app catalog too, not just horizon. Thanks, Kevin From: David Lyle [dkly.

  1   2   >