[openstack-dev] [picasso] Picasso (FaaS) project release!

Hi all, I’m very pleased to announce a new project, Picasso[1][2] - Functions as a Service (FaaS). The mission is to provide an API for running FaaS on OpenStack, abstracting away the infrastructure layer while enabling simplicity, efficiency and scalability for both developers and operators.

Re: [openstack-dev] [neutron] proposing Ryan Tidwell and Nate Johnston as service LTs

Belated but enthusiastic +1 doug > On Dec 15, 2016, at 4:58 PM, Armando M. wrote: > > Hi neutrinos, > > I would like to propose Ryan and Nate as the go-to fellows for > service-related patches. > > Both are core in their repos of focus, namely neutron-dynamic-routing and

Re: [openstack-dev] [oslo][nova]Accessing nullable, not set versioned object field

From: Dan Smith Sent: 16 December 2016 16:33 >> NotImplementedError: Cannot load 'nullable_string' in the base class >> >> Is this the correct behavior? > > Yes, that's the expected behaviour. Yes. >> Then what is the expected behavior if the field is also defaulted to >>

Re: [openstack-dev] [osc][openstackclient][zun] Collision on the keyword 'container'

From: Steve Martinelli [mailto:s.martine...@gmail.com] Sent: December-20-16 5:09 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [osc][openstackclient][zun] Collision on the keyword 'container' On Tue, Dec 20, 2016 at 4:39 PM, Clay Gerrard

[openstack-dev] [Neutron][networking-sfc] Next networking-sfc meeting on 1/5/2017

All, As many people will be away over the holiday season we will have the next networking-sfc meeting on 1/5/2017. Best wishes for the season. -Louis __ OpenStack Development Mailing List (not for usage questions)

[openstack-dev] [HA] haproxy can't start with manual setup according to the guide

Hi, haproxy can't start because of its listening ports on vip conflicting with openstack services' listening ports on 0.0.0.0. I opened a bug about it: https://bugs.launchpad.net/openstack-manuals/+bug/1649902 Could anyone help to check this? Or any workaround about it such as change

Re: [openstack-dev] [osc][openstackclient][zun] Collision on the keyword 'container'

-Original Message- From: Hongbin Lu Reply: OpenStack Development Mailing List (not for usage questions) Date: December 20, 2016 at 15:01:33 To: OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [osc][openstackclient][zun] Collision on the keyword 'container'

On Tue, Dec 20, 2016 at 3:39 PM, Clay Gerrard wrote: > http://docs.openstack.org/developer/python-openstackclient/command-list.html > The collision of top-level resource names is not new. You see stuff like > "volume create" & "server create" - but also "volume backup

Re: [openstack-dev] [osc][openstackclient][zun] Collision on the keyword 'container'

On Tue, Dec 20, 2016 at 1:00 PM, Hongbin Lu wrote: > > > $ openstack objectstore container > > $ openstack container container > > $ openstack secret container > > > > Thoughts? > This is the closest thing I can see that's somewhat reasonable - with the obvious

Re: [openstack-dev] [osc][openstackclient][zun] Collision on the keyword 'container'

On Tue, Dec 20, 2016 at 4:39 PM, Clay Gerrard wrote: > > On Tue, Dec 20, 2016 at 1:00 PM, Hongbin Lu wrote: > >> >> >> $ openstack objectstore container >> >> $ openstack container container >> >> $ openstack secret container >> >> >> >>

[openstack-dev] [osc][openstackclient][zun] Collision on the keyword 'container'

Hi OpenStackClients Team, I am from the Zun team, and my team encountered a name collision issue when implementing a OSC plugin [1]. We wanted to use the keyword 'container' to represent a linux container used to host a containerized application. In particular, the commands our contributor

[openstack-dev] [tripleo] December 27th - meeting cancelled

We won't hold our weekly meeting on December 27th. Next meeting is schedule on January 3rd. Happy holidays everyone, -- Emilien Macchi __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [osc][openstackclient][zun] Collision on the keyword 'container'

On Tue, Dec 20, 2016 at 3:00 PM, Hongbin Lu wrote: > In the long-term, I am going to propose to follow the style of AWS CLI, that > is prefixing each command with a project name. For example: We have been down this particular path multiple times, and this is not how the

Re: [openstack-dev] [neutron] Where will Neutron go in future?

Hi Zhi, LBaaSv2 as an API will live on. We are in the process of merging that API into the octavia repository to merge the two load balancing projects into one and remove our dependency on the neutron API process/endpoint. Functionally it is our goal to allow the LBaaSv2 API to continue to

Re: [openstack-dev] [networking-sfc] Intermittent database transaction issues, affecting the tempest gate

Hi Bernard, Thanks for the email. I will take a look at this. Xiaodong has been working on tempest test scripts. I will work with Xiaodong on this issue. Cathy -Original Message- From: Bernard Cafarelli [mailto:bcafa...@redhat.com] Sent: Tuesday, December 20, 2016 3:00 AM To:

[openstack-dev] Dec 28 meeting canceled

Hello, Let's cancel meeting at 28 Dec, but 21 Dec and 4 Jan are still on, probably more lightweight but try to be there please. Cheers, Michal __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [heat] A question on the endpoint of Heat

Zane Bitter: Thank you for your replay. I read the codes of Keystone by your reminding. Maybe the following codes can help us understand. Thanks again! https://github.com/openstack/keystone/blob/master/keystone/common/utils.py#L633

Re: [openstack-dev] [FaaS] Function as a service in OpenStack

Hi all, We just released Picasso[1][2], an OpenStack API for Functions as a Service. I think it may be of particular interest to those in this thread, as it's based on IronFunctions, an open-source alternative to Lambda. The mission is to provide an API to run functions on OpenStack. Picasso is

Re: [openstack-dev] [nova] Help: How to make Nova official support AArch64?

On 12/20/2016 7:27 AM, Jay Pipes wrote: On 12/20/2016 12:45 AM, Kevin Zhao wrote: Hello Nova, Greetings from ARM and Linaro :D This is Kevin Zhao from ARM. Nowadays Linaro and other contributors have submitted some patches to Nova community , fixing bugs for Nova running on AArch64.

[openstack-dev] [nova] Nova API sub-team meeting

Hi, It is really close to the holidays. But we didn't say we will cancel the meeting. I will be there if there are people. Thanks __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [kolla] [kolla-kubernetes] Dec 28 meeting canceled

On Wed, Dec 21, 2016 at 8:31 AM, Michał Jastrzębski wrote: > Hello, > > Let's cancel meeting at 28 Dec, but 21 Dec and 4 Jan are still on, > probably more lightweight but try to be there please. > > Cheers, > Michal > >

[openstack-dev] [acceleration]Team Bi-weekly Meeting 2016.12.21 Agenda

Hi Team, Please find the agenda at https://wiki.openstack.org/wiki/Meetings/CyborgTeamMeeting#Next_meeting_:_UTC_1500.2C_Dec_21th Remember that our IRC channel is #openstack-cyborg -- Zhipeng (Howard) Huang Standard Engineer IT Standard & Patent/IT Prooduct Line Huawei Technologies Co,. Ltd

[openstack-dev] [tricircle]agenda of weekly meeting Dec.21

Hello, team, Agenda of Dec.21 weekly meeting: 1. one idea to address VxLAN L2 networking/L3 DVR issue 2. Ocata feature development review 3. Open Discussion How to join: # IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on every Wednesday starting from UTC

[openstack-dev] [tacker] December 28th weekly meeting cancelled

We are skipping next week's Tacker meeting, on Dec 28th [1]. We will resume on Jan 4th. Happy Holidays!! [1] http://eavesdrop.openstack.org/meetings/tacker/2016/tacker.2016-12-21-05.30.log.html __ OpenStack Development

[openstack-dev] [Vitrage] [aodh] Generig alarm help

Hi, I have pushed the first code of the generic alarm to the aodhclient. I encountered an error there in py27 which I don't quite understand why it happens because I have changed all the correct places in the client (maybe I need to have some appropriate code for this in the aodh project

[openstack-dev] [networking-sfc] Intermittent database transaction issues, affecting the tempest gate

Hi everyone, we have an open bug (thanks Igor for the report) on DB transaction issues: https://bugs.launchpad.net/networking-sfc/+bug/1630503 The thing is, I am seeing quite a few tempest gate failures that follow the same pattern: at some point in the test suite, the service gets

Re: [openstack-dev] [nova] [placement] Which service is using port 8778?

Le 20/12/2016 10:20, Chris Dent a écrit : > On Tue, 20 Dec 2016, Sylvain Bauza wrote: > >> Before moving forward and picking yet another port that could trample >> another service, I'd rather prefer first that Senlin jobs would >> temporarely disable the placement-* services so that the gate

Re: [openstack-dev] [nova] [placement] Which service is using port 8778?

Le 20/12/2016 09:12, Sylvain Bauza a écrit : > > > Le 20/12/2016 07:31, Ghanshyam Mann a écrit : >> Changing placement API port to 8780 [1], hope this is not being used by any >> services. >> >> But I am not sure how to check all used port currently as wiki does not >> seems to have all. >>

Re: [openstack-dev] [nova] [placement] Which service is using port 8778?

Le 20/12/2016 09:29, Sylvain Bauza a écrit : > > > Le 20/12/2016 09:12, Sylvain Bauza a écrit : >> >> >> Le 20/12/2016 07:31, Ghanshyam Mann a écrit : >>> Changing placement API port to 8780 [1], hope this is not being used by any >>> services. >>> >>> But I am not sure how to check all used

Re: [openstack-dev] [Cinder] Does cinder use novaclient?

On Tue, 2016-12-20 at 14:44 +0800, lij...@gohighsec.com wrote: > Hi Cinder community, > > Does cinder use novaclient? What's the use of cinder/compute/nova.py? > > I find that there seems to have some problems when construct > novaclient in the file  cinder/compute/nova.py, >  but I think the

Re: [openstack-dev] [nova] [placement] Which service is using port 8778?

Yea, that is also options to disable the placement api in senlin setup. But for long term we should have different ports for each service and should be maintained here - http://docs.openstack.org/newton/config-reference/firewalls-default-ports.html But I have no clue how to confirm the free

Re: [openstack-dev] [nova] [placement] Which service is using port 8778?

On Tue, 20 Dec 2016, Sylvain Bauza wrote: Before moving forward and picking yet another port that could trample another service, I'd rather prefer first that Senlin jobs would temporarely disable the placement-* services so that the gate would be happy, while in the same time we try to identify

Re: [openstack-dev] [all][rdo][kolla] Recommending the RDO tag for the mailing list

On Mon, Dec 19, 2016 at 2:21 PM, Steven Dake (stdake) wrote: > Folks, > > > > I am in favor of using a new tag called [rdo] such that RDO (or its > transitive dependencies) can be discussed and filtered by email clients as > it relates to development topics that affect the

Re: [openstack-dev] [heat] A question on the endpoint of Heat

On 20/12/16 02:29, zengchen wrote: Hi, Heat stackers: May I ask a question about the endpoint of Heat. I see the endpoints of Heat registered to Keystone look like this. 'http://10.229.45.150:8004/v1/$(project_id)s' . My question is that why use '$' instead of '%' as the replacement symbol.

Re: [openstack-dev] [nova] [placement] Which service is using port 8778?

Le 20/12/2016 14:30, Jay Pipes a écrit : > On 12/20/2016 08:03 AM, Sean Dague wrote: >> On 12/20/2016 07:53 AM, Sylvain Bauza wrote: >>> Le 20/12/2016 10:26, Sylvain Bauza a écrit : Le 20/12/2016 10:20, Chris Dent a écrit : > On Tue, 20 Dec 2016, Sylvain Bauza wrote: > >> Before

[openstack-dev] [puppet] Dec 27, Jan 3 meetings canceled

Hey, Given that the next few meetings will be right after some holidays, we're going to go ahead and cancel the meetings on Dec 27 and Jan 3. Our next meeting will be on Jan 10. See you then. Thanks, -Alex __ OpenStack

Re: [openstack-dev] [nova] [placement] Which service is using port 8778?

Le 20/12/2016 10:26, Sylvain Bauza a écrit : > > > Le 20/12/2016 10:20, Chris Dent a écrit : >> On Tue, 20 Dec 2016, Sylvain Bauza wrote: >> >>> Before moving forward and picking yet another port that could trample >>> another service, I'd rather prefer first that Senlin jobs would >>>

Re: [openstack-dev] [nova] [placement] Which service is using port 8778?

On 12/20/2016 07:53 AM, Sylvain Bauza wrote: > > > Le 20/12/2016 10:26, Sylvain Bauza a écrit : >> >> >> Le 20/12/2016 10:20, Chris Dent a écrit : >>> On Tue, 20 Dec 2016, Sylvain Bauza wrote: >>> Before moving forward and picking yet another port that could trample another service,

Re: [openstack-dev] [nova] Help: How to make Nova official support AArch64?

On 12/20/2016 12:45 AM, Kevin Zhao wrote: Hello Nova, Greetings from ARM and Linaro :D This is Kevin Zhao from ARM. Nowadays Linaro and other contributors have submitted some patches to Nova community , fixing bugs for Nova running on AArch64. Now we can successfully running a

Re: [openstack-dev] [tripleo] [ci]

On Fri, Dec 16, 2016 at 9:12 AM, Flavio Percoco wrote: > On 14/12/16 21:44 -0500, Emilien Macchi wrote: > >> On Wed, Dec 14, 2016 at 7:22 PM, Wesley Hayutin >> wrote: >> >>> >>> >>> On Fri, Dec 2, 2016 at 12:04 PM, Wesley Hayutin >>>

Re: [openstack-dev] [all][rdo][kolla] Recommending the RDO tag for the mailing list

Hi Erno, I believe Steven is referring to the recent post regarding issues with CentOS 7.3 [1]. Arguably, that particular email was sent to openstack-dev, openstack-operators as well as rdo-list. I think it's okay to tag things relevant to RDO in openstack-dev but that doesn't mean we're moving

Re: [openstack-dev] [nova] [placement] Which service is using port 8778?

On 12/20/2016 08:03 AM, Sean Dague wrote: On 12/20/2016 07:53 AM, Sylvain Bauza wrote: Le 20/12/2016 10:26, Sylvain Bauza a écrit : Le 20/12/2016 10:20, Chris Dent a écrit : On Tue, 20 Dec 2016, Sylvain Bauza wrote: Before moving forward and picking yet another port that could trample

Re: [openstack-dev] [api][zun] Effective URL for resource actions

On Dec 19, 2016, at 9:34 PM, Qiming Teng wrote: > > Then we should stop identifying actions based on URL. :) > The following URL for representing a 'pause' action is really ugly: > > /containers//pause > > First of all, 'pause' is a verb. I cannot persuade myself

[openstack-dev] [storlets] End of year IRC team meetings

Unless there is some objection we will skip next week's meeting and meet again on Tuesday January 3rd in the usual place and time. Thanks, Eran __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [neutron] Where will Neutron go in future?

Hi Zhi: With the L3 implementation, FWaaS acts on traffic that is seen by the router (we have some issues with DVR) so it is really constrained to N - S. SG will of course see all traffic. Once we have the FWaaS L2 implementation - it opens up the possibilities to be applied on a VM port and

[openstack-dev] Proposing Steve Martinelli for project-team-guide core

Hi everyone, As you probably know, the OpenStack Project Team Guide is a piece of documentation geared towards project teams, to help them navigate the troubled and complex waters of being an official OpenStack team: http://docs.openstack.org/project-team-guide/ Steve Martinelli has been doing

[openstack-dev] [neutron][fwaas] Weekly FWaaS meetings cancelled next 2 weeks.

Hi All: We will skip the weekly FWaaS meetings on Dec 27 and Jan 3 with the Holiday Season. We will start back on Jan 10 as usual. Happy Holidays to all. Thanks Sridar __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [nova] [placement] Which service is using port 8778?

Le 20/12/2016 07:31, Ghanshyam Mann a écrit : > Changing placement API port to 8780 [1], hope this is not being used by any > services. > > But I am not sure how to check all used port currently as wiki does not seems > to have all. > > .. [1] https://review.openstack.org/#/c/412770/ >

Re: [openstack-dev] [all][rdo][kolla] Recommending the RDO tag for the mailing list

Erno, As David mentioned I had certainly not suggested moving all discussion from RDO list. This is why I invited the Kolla community to join rdo-list if they so choose. I think some heads up around “these are issues you may face” is warranted as David’s email [1] points out. It is very

Re: [openstack-dev] [Cinder] Does cinder use novaclient?

Hi Jane, there is also some other uses, I know. In migration[1] when Cinder needs to migrate an attached volume, in some remotefs drivers [2], when Cinder needs to take a snapshot of an attached volume. Both seems to work fine with me. [1] http://bit.ly/2i6m1Pb [2] http://bit.ly/2i6m3GM On

Re: [openstack-dev] OpenStack Dev Digest 10- 16

On 12/19/2016 10:54 PM, Kendall Nelson wrote: Upgrade readiness check in Nova [11] * New, separate service Clarification here, it's not a new separate service, it's a new CLI (nova-status). Right now we're developing it within the nova repo, just like nova-manage. -- Thanks,

Re: [openstack-dev] Proposing Steve Martinelli for project-team-guide core

Excerpts from Thierry Carrez's message of 2016-12-20 16:18:15 +0100: > Hi everyone, > > As you probably know, the OpenStack Project Team Guide is a piece of > documentation geared towards project teams, to help them navigate the > troubled and complex waters of being an official OpenStack team: >