[openstack-dev] [cinder] snapshot and cloning for NFS backend

Hi Devs, The cinder-specs [1] for snapshot and cloning NFS backend submitted by Eric was approved in Kilo but due to nova issue [2] it is not implemented in Kilo and Liberty. I am discussing about this nova bug with nova team for finding possible solutions and Nikola has given some pointers abo

Re: [openstack-dev] [Cinder] [Manila] Will NFS stay with Cinder as a reference implementation?

Cinder provides a block storage abstraction to a vm. Manila provides a filesystem abstraction. The two are very different, and complementary. I see no reason why the nfs related cinder drivers should be removed based on the existence or maturity of manila - manila is not going to suddenly start pro

[openstack-dev] [Neutron] Defeact management

Hi folks, One of the areas I would like to look into during the Mitaka cycle is 'stability' [1]. The team has done a great job improving test coverage, and at the same time increasing reliability of the product. However, regressions are always around the corner, and there is a huge backlog of out

Re: [openstack-dev] [magnum]swarm + compose = k8s?

Would it make sense to ask the opposite of Wanghua's question: should pod/service/rc be deprecated if the user can easily get to the k8s api? Even if we want to orchestrate these in a Heat template, the corresponding heat resources can just interface with k8s instead of Magnum. Ton Ngo, From:

Re: [openstack-dev] [magnum]swarm + compose = k8s?

Also I belive docker compose is just command line tool which doesn’t have any api or scheduling features. But during last Docker Conf hackathon PayPal folks implemented docker compose executor for Mesos (https://github.com/mohitsoni/compose-executor) which can give you pod like experience. ― Ego

Re: [openstack-dev] [magnum]swarm + compose = k8s?

Wanghua, I do follow your logic, but docker-compose only needs the docker API to operate. We are intentionally avoiding re-inventing the wheel. Our goal is not to replace docker swarm (or other existing systems), but to compliment it/them. We want to offer users of Docker the richness of native

[openstack-dev] [election] [tc] TC candidacy -- Let's do this

Greetings Stackers, Some of you I know, some of you I'm meeting for the first time. Through the last 3 years, since I got involved with OpenStack, I've seen it grow and mature, and I want to make sure it continues to as we all raise the bar on what we expect from the not so little cloud engine th

Re: [openstack-dev] [magnum]swarm + compose = k8s?

> From: 王华 > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 09/28/2015 11:34 PM > Subject: [openstack-dev] [magnum]swarm + compose = k8s? > > Hi folks, > > Magnum now exposes service, pod, etc to users in kubernetes coe, but > exposes container in swarm coe. As I

Re: [openstack-dev] [puppet][keystone] Choose domain names with 'composite namevar' or 'meaningless name'?

On 15/09/15 19:55, Sofer Athlan-Guyot wrote: > Gilles Dubreuil writes: > >> On 15/09/15 06:53, Rich Megginson wrote: >>> On 09/14/2015 02:30 PM, Sofer Athlan-Guyot wrote: Hi, Gilles Dubreuil writes: > A. The 'composite namevar' approach: > > keystone_tenant

[openstack-dev] [Cinder] [Manila] Will NFS stay with Cinder as a reference implementation?

Hi folks, I have a question about the file services in OpenStack. As you know there is a generic NFS driver in Cinder and other file system drivers inherit it, while the project Manila is determined to provide the file system service. Will NFS stay with Cinder as the reference implementation f

Re: [openstack-dev] [Openstack-operators] [cinder] [all] The future of Cinder API v1

On Mon, Sep 28, 2015 at 6:19 PM, Mark Voelker wrote: > FWIW, the most popular client libraries in the last user survey[1] other > than OpenStack’s own clients were: libcloud (48 respondents), jClouds (36 > respondents), Fog (34 respondents), php-opencloud (21 respondents), > DeltaCloud (which has

[openstack-dev] [magnum]swarm + compose = k8s?

Hi folks, Magnum now exposes service, pod, etc to users in kubernetes coe, but exposes container in swarm coe. As I know, swarm is only a scheduler of container, which is like nova in openstack. Docker compose is a orchestration program which is like heat in openstack. k8s is the combination of sc

Re: [openstack-dev] [Horizon] Horizon Productivity Suggestion

I agree with Travis that 2-3 minutes is not enough, that may not be even enough to talk about one bug. :) We could save some time if we have someone monitoring the bugs/feature and publish the high priority item into a report - something similar to what Keystone does [1]. Reviewers can look this

Re: [openstack-dev] [Openstack-operators] [neutron] [nova] Nova Network/Neutron Migration Survey - need response from folks currently using Nova Networks in their deployments

On 28 September 2015 at 18:01, Kruithof, Piet wrote: > There has been a significant response to the Nova Network/Neutron > migration survey. However, the responses are leaning heavily on the side > of deployments currently using Neutron. As a result, we would like to have > more representation

Re: [openstack-dev] [Horizon] Horizon Productivity Suggestion

Things always move more quickly at the end of a cycle because people feel release pressure, but I do think this is a good idea. 2 - 3 minutes isn’t very realistic. It would need to be planned for longer. On 9/28/15, 3:57 AM, "Rob Cresswell (rcresswe)" wrote: >Hi folks, > >I¹m wondering if

[openstack-dev] [fuel] Nominate Svetlana Karslioglu for fuel-docs core

I'd like to nominate Svetlana Karslioglu as a core reviewer for the fuel-docs-core team. During the last few months, Svetlana restructured the Fuel QuickStart Guide, fixed a few documentation bugs for Fuel 7.0, and improved the quality of the Fuel documentation through reviews. I believe it's time

Re: [openstack-dev] [murano] Fix order of arguments in assertEqual

Hi 2015-09-29 10:09 GMT+09:00 Ian Wienand : > On 09/24/2015 08:18 PM, Andrey Kurilin wrote: >> >> I agree that wrong order of arguments misleads while debugging errors, BUT >> how we can prevent regression? > > > Spell it out and use keyword args? > > assertEqual(expected="foo", observed=...) >

Re: [openstack-dev] [murano] Fix order of arguments in assertEqual

On 09/24/2015 08:18 PM, Andrey Kurilin wrote: I agree that wrong order of arguments misleads while debugging errors, BUT how we can prevent regression? Spell it out and use keyword args? assertEqual(expected="foo", observed=...) is pretty hard to mess up -i ___

[openstack-dev] [Openstack-operators] [neutron] [nova] Nova Network/Neutron Migration Survey - need response from folks currently using Nova Networks in their deployments

There has been a significant response to the Nova Network/Neutron migration survey. However, the responses are leaning heavily on the side of deployments currently using Neutron. As a result, we would like to have more representation from folks currently using Nova Networks. If you are curren

Re: [openstack-dev] [Openstack-operators] [cinder] [all] The future of Cinder API v1

FWIW, the most popular client libraries in the last user survey[1] other than OpenStack’s own clients were: libcloud (48 respondents), jClouds (36 respondents), Fog (34 respondents), php-opencloud (21 respondents), DeltaCloud (which has been retired by Apache and hasn’t seen a commit in two year

Re: [openstack-dev] [Openstack-operators] [cinder] [all] The future of Cinder API v1

Yeah we’re still using v1 as the clients that are packaged with most distros don’t support v2 easily. Eg. with Ubuntu Trusty they have version 1.1.1, I just updated our “volume” endpoint to point to v2 (we have a volumev2 endpoint too) and the client breaks. $ cinder list ERROR: OpenStack Block

[openstack-dev] [third-party] Reminder of 3rd party ci working group meeting Tuesday at 1700 UTC in #openstack-meeting

Hi, This is a reminder for 3rd party ci operators that there is a working group meeting Tuesday at 1700 UTC in #openstack-meeting The agenda is available here. Please feel free to add additional topics: https://wiki.openstack.org/wiki/Meetings/ThirdParty#Agenda_for_next_Working_Group_meeting T

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

On 2015-09-28 16:27:19 -0500 (-0500), Kyle Mestery wrote: [...] > I should note that as the previous PTL, for the most part I viewed > stats as garbage. Keep in mind I nominated two new core reviewers > whose stats were lowe but who are incredibly important members of > our community [1]. I did thi

Re: [openstack-dev] [Openstack-operators] [cinder] [all] The future of Cinder API v1

Yes, people are probably still using it. Last time I tried to use V2 it didn't work because the clients were broken, and then it went back on the bottom of my to do list. Is this mess fixed? http://lists.openstack.org/pipermail/openstack-operators/2015-February/006366.html On Mon, Sep 28, 2015 at

[openstack-dev] [cinder] [all] The future of Cinder API v1

Hi all, As you may know, we've got 2 APIs in Cinder: v1 and v2. Cinder v2 API was introduced in Grizzly and v1 API is deprecated since Juno. After [1] is merged, Cinder API v1 is disabled in gates by default. We've got a filed bug [2] to remove Cinder v1 API at all. According to Deprecation Pol

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

> On Sep 28, 2015, at 3:00 PM, Assaf Muller wrote: > > > > On Mon, Sep 28, 2015 at 12:40 PM, Zane Bitter > wrote: > On 28/09/15 05:47, Gorka Eguileor wrote: > On 26/09, Morgan Fainberg wrote: > As a core (and former PTL) I just ignored commit message -1s unless ther

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

On Mon, Sep 28, 2015 at 5:29 PM, Kevin Benton wrote: > I think a blanket statement about what people's motivations are is not > fair. We've seen in this thread that some people want to enforce the limit > of 72 chars and it's not about padding their stats. > I took this golden opportunity to kid

[openstack-dev] [fuel][ptl] PTL candidacy

Hi friends, I’d like to raise my hand to send my candidacy for Fuel PTL position for next cycle. Before I go forward with my candidacy, I will remind some facts we’ve been focuses as a team for last six months: - Synchronisation with upstream modules. As a result we have a nice mechanist to syn

Re: [openstack-dev] [Congress] Congress and Monasca Joint Session at Tokyo Design Summit

Hi Fabio: Thanks for reaching out. We should definitely talk at the summit. I don't know if we can devote 1 of the 3 allocated Congress sessions to Monasca, but we'll talk it over during IRC on Wed and let you know. Or do you have a session we could use for the discussion? In any case, I'm conf

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

Excerpts from Kevin Benton's message of 2015-09-28 14:29:14 -0700: > I think a blanket statement about what people's motivations are is not > fair. We've seen in this thread that some people want to enforce the limit > of 72 chars and it's not about padding their stats. > > The issue here is that

Re: [openstack-dev] [all] devstack default worker changes

On 9/28/2015 3:02 PM, Sean Dague wrote: We used to default to using the mysqldb driver in devstack, which is a C binding that is not eventlet aware. This means that any time a db query is executed the entire greenlet is blocked. This behavior meant that in devstack (and in oslo.concurrency) def

Re: [openstack-dev] [lbaas] [octavia] Proposing new meeting time Wednesday 16:00 UTC

Brandon, We had some requests in the past and I just wanted to float the idea on the ML since we are starting a new cycle... Thanks, German On 9/27/15, 10:12 PM, "Brandon Logan" wrote: >Is there a lot of people requesting this meeting change? > >Thanks, >Brandon > >On Fri, 2015-09-25 at 23:58

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

I think a blanket statement about what people's motivations are is not fair. We've seen in this thread that some people want to enforce the limit of 72 chars and it's not about padding their stats. The issue here is that we have a guideline with a very specific number. If we don't care to enforce

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

On Mon, Sep 28, 2015 at 4:00 PM, Assaf Muller wrote: > > > On Mon, Sep 28, 2015 at 12:40 PM, Zane Bitter wrote: > >> On 28/09/15 05:47, Gorka Eguileor wrote: >> >>> On 26/09, Morgan Fainberg wrote: >>> As a core (and former PTL) I just ignored commit message -1s unless there is somethi

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

Excerpts from Morgan Fainberg's message of 2015-09-26 23:36:09 -0700: > As a core (and former PTL) I just ignored commit message -1s unless there is > something majorly wrong (no bug id where one is needed, etc). > > I appreciate well formatted commits, but can we let this one go? This > discus

Re: [openstack-dev] [release][requirements] changes to the requirements-core team

On 09/28/2015 04:16 PM, Doug Hellmann wrote: > It has been a while since we've reviewed the requirements-core team > members. Since it's the end of the cycle, I did a quick scan of the > stats this week and I am proposing some changes based on participation. > > I spoke with Ghe Rivero and Julien

Re: [openstack-dev] [Ironic] Preparing for functional testing in Ironic. Will likely break any in-flight patches.

On Mon, Sep 28, 2015 at 09:00:07PM +, Villalovos, John L wrote: > Just to give a heads up to people. I have proposed the following patch: > https://review.openstack.org/228612 > > This moves the tests in ironic/tests/ to ironic/tests/unit/ > > Likely this patch will break most in-flight patch

Re: [openstack-dev] [release][requirements] changes to the requirements-core team

All sounds good to me. -Rob On 29 September 2015 at 09:16, Doug Hellmann wrote: > It has been a while since we've reviewed the requirements-core team > members. Since it's the end of the cycle, I did a quick scan of the > stats this week and I am proposing some changes based on participation. >

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

On Mon, Sep 28, 2015 at 12:40 PM, Zane Bitter wrote: > On 28/09/15 05:47, Gorka Eguileor wrote: > >> On 26/09, Morgan Fainberg wrote: >> >>> As a core (and former PTL) I just ignored commit message -1s unless >>> there is something majorly wrong (no bug id where one is needed, etc). >>> >>> I app

[openstack-dev] [Ironic] Preparing for functional testing in Ironic. Will likely break any in-flight patches.

Just to give a heads up to people. I have proposed the following patch: https://review.openstack.org/228612 This moves the tests in ironic/tests/ to ironic/tests/unit/ Likely this patch will break most in-flight patches, so rebasing will be required when this patch goes in. If you have any ques

Re: [openstack-dev] [cinder][neutron][all] New third-party-ci testing requirements for OpenStack Compatible mark

The Neutron team also discussed this in Vancouver, you can see the etherpad here [1]. We talked about the idea of creating a validation suite, and it sounds like that's something we should again discuss in Tokyo for the Mitaka cycle. I think a validation suite would be a great step forward for Neut

Re: [openstack-dev] Openvswitch agent unit tests

Generally speaking, testing agent methods that interact with the system heavily with unit tests provide very little, and arguably negative value to the project. Mocking internal methods and asserting that they were called is a clear anti-pattern to my mind. In Neutron-land we prefer to test agent c

[openstack-dev] [Congress] Congress and Monasca Joint Session at Tokyo Design Summit

Tim and Congress folks, I am writing on behalf of the Monasca community and I would like to explore the possibility of holding a joint session during the Tokyo Design Summit. We would like to explore: 1. how to integrate Monasca with Congress so then Monasca can provide metrics, logs and ev

Re: [openstack-dev] [all] devstack default worker changes

This is great news indeed, Sean. :) On 09/28/2015 04:02 PM, Sean Dague wrote: We used to default to using the mysqldb driver in devstack, which is a C binding that is not eventlet aware. This means that any time a db query is executed the entire greenlet is blocked. This behavior meant that in d

Re: [openstack-dev] [glance][nova] how to upgrade from v1 to v2?

Excerpts from Mark Voelker's message of 2015-09-28 19:55:18 +: > On Sep 28, 2015, at 9:03 AM, Doug Hellmann wrote: > > > > Excerpts from John Garbutt's message of 2015-09-28 12:32:53 +0100: > >> On 28 September 2015 at 12:10, Sean Dague wrote: > >>> On 09/27/2015 08:43 AM, Doug Hellmann wrot

[openstack-dev] [fuel] PTL Candidacy

I'd like to announce my candidacy as Fuel PTL for the next cycle. It is our very first election, so we are taking our time to make sure we get everything right. We have extended the nomination period to September 28 [0] to give Fuel contributors more time to learn about the OpenStack governance pr

[openstack-dev] [release][requirements] changes to the requirements-core team

It has been a while since we've reviewed the requirements-core team members. Since it's the end of the cycle, I did a quick scan of the stats this week and I am proposing some changes based on participation. I spoke with Ghe Rivero and Julien Danjou, both of whom have done good work in the past bu

Re: [openstack-dev] [cinder] The Absurdity of the Milestone-1 Deadline for Drivers

On Mon, Sep 28, 2015 at 12:13:04PM -0600, John Griffith wrote: > On Mon, Sep 28, 2015 at 11:29 AM, Ben Swartzlander > wrote: > > > I've always thought it was a bit strange to require new drivers to merge > > by milestone 1. I think I understand the motivations of the policy. The > > main motivati

[openstack-dev] [all] devstack default worker changes

We used to default to using the mysqldb driver in devstack, which is a C binding that is not eventlet aware. This means that any time a db query is executed the entire greenlet is blocked. This behavior meant that in devstack (and in oslo.concurrency) default number of workers for things like API s

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

>I see a clear line between something that handles the creation of all ancillary resources needed to boot a VM and then the creation of the VM itself. I agree. To me the line is the difference between creating a top level resource, and adding a host to that resource. For example, I do expect a to

Re: [openstack-dev] [glance][nova] how to upgrade from v1 to v2?

On Sep 28, 2015, at 9:03 AM, Doug Hellmann wrote: > > Excerpts from John Garbutt's message of 2015-09-28 12:32:53 +0100: >> On 28 September 2015 at 12:10, Sean Dague wrote: >>> On 09/27/2015 08:43 AM, Doug Hellmann wrote: Excerpts from Mark Voelker's message of 2015-09-25 20:43:23 +: >>

[openstack-dev] Openvswitch agent unit tests

Hello, I'm new developer who want to start contributing to neutron. I have some small experience with neutron already but I didn't do anything which I could push to upstream for now. So I searched for some bug on launchpad and I found such bug which I took: https://bugs.launchpad.net/neutron/+bug/

Re: [openstack-dev] [cinder] The Absurdity of the Milestone-1 Deadline for Drivers

On 09/28/2015 02:42 PM, Walter A. Boring IV wrote: On 09/28/2015 10:29 AM, Ben Swartzlander wrote: I've always thought it was a bit strange to require new drivers to merge by milestone 1. I think I understand the motivations of the policy. The main motivation was to free up reviewers to review

[openstack-dev] [ironic] weekly subteam status report

Hi, Following is the subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) (diff with Sep 21) - Open: 135 (-1). 9 new (+2), 36 in progress (-5), 0 critical, 7 high (-5) and 9 incomplete - Nova bugs with Ironic tag: 2

Re: [openstack-dev] [cinder] The Absurdity of the Milestone-1 Deadline for Drivers

On 09/28/2015 10:29 AM, Ben Swartzlander wrote: I've always thought it was a bit strange to require new drivers to merge by milestone 1. I think I understand the motivations of the policy. The main motivation was to free up reviewers to review "other things" and this policy guarantees that for

Re: [openstack-dev] [neutron] congrats to armax!

On 25 September 2015 at 17:03, Ryan Moats wrote: > First, congratulations to armax on being elected PTL for Mitaka. Looking > forward to Neutron improving over the next six months. > > Second thanks to everybody that voted in the election. Hopefully we had > something close to 100% turnout, becau

Re: [openstack-dev] [cinder] The Absurdity of the Milestone-1 Deadline for Drivers

On Mon, Sep 28, 2015 at 12:11 PM, Duncan Thomas wrote: > I can definitely see your logic, but we've a history in cinder of vendors > trying to cram drivers in at the last minute which we very much wanted to > stop dead. I might suggest that the second milestone, rather than the first > might be a

[openstack-dev] [Fuel] Fuel PTL Candidacy

Fuelers I am glad that Fuel is becoming more open as a project and is heading towards Openstack BigTent which should allow our project to scale and become one of the default OpenStack installers not only for a fraction of end users but for a significant amount of OpenStack developers also. Althoug

Re: [openstack-dev] [cinder] The Absurdity of the Milestone-1 Deadline for Drivers

On Mon, Sep 28, 2015 at 11:29 AM, Ben Swartzlander wrote: > I've always thought it was a bit strange to require new drivers to merge > by milestone 1. I think I understand the motivations of the policy. The > main motivation was to free up reviewers to review "other things" and this > policy guar

Re: [openstack-dev] [TripleO] tripleo.org theme

On Mon, 2015-09-28 at 16:04 +, Jeremy Stanley wrote: > On 2015-09-28 09:43:37 -0400 (-0400), James Slagle wrote: > > Would the content of tripleo-docs be exactly the same as what is > > published at http://docs.openstack.org/developer/tripleo-docs/ ? > > > > I think it probably should be, and

Re: [openstack-dev] [cinder] The Absurdity of the Milestone-1 Deadline for Drivers

I can definitely see your logic, but we've a history in cinder of vendors trying to cram drivers in at the last minute which we very much wanted to stop dead. I might suggest that the second milestone, rather than the first might be a better one to dedicate to driver reviews... An interesting thin

Re: [openstack-dev] [Congress] Congress Usecases VM

When I tried to import the image, it gave me an error. Could not create the imported medium '/Users/tim/VirtualBox VMs/Congress_Usecases/Congress_Usecases_SEPT_25_2015-disk1.vmdk' . VMDK: Compressed image is corrupted '/Congress_Usecases_SEPT_25_2015-disk1.vmdk' (VERR_ZIP_CORRUPTED). Tim On

Re: [openstack-dev] [Congress] hands on lab

Hi Alex, I went through the HOL. Some feedback... 1. When starting up, it paused for a while showing the following messages. Maybe that caused the issues I mention below. Waiting for network configuration... Waiting up to 60 more seconds for network configuration... 2. Maybe spell out the fi

Re: [openstack-dev] [TripleO] tripleo.org theme

On Mon, 2015-09-28 at 09:43 -0400, James Slagle wrote: > On Fri, Sep 25, 2015 at 8:34 AM, Dan Prince > wrote: > > It has come to my attention that we aren't making great use of our > > tripleo.org domain. One thing that would be useful would be to have > > the > > new tripleo-docs content displaye

Re: [openstack-dev] [TripleO] tripleo.org theme

On Fri, 2015-09-25 at 12:31 -0500, Ben Nemec wrote: > On 09/25/2015 07:34 AM, Dan Prince wrote: > > It has come to my attention that we aren't making great use of our > > tripleo.org domain. One thing that would be useful would be to have > > the > > new tripleo-docs content displayed there. It wou

Re: [openstack-dev] [Fuel] Code review process in Fuel and related issues

Hi Mike, thanks, now it's clear. On Thu, Sep 3, 2015 at 9:19 AM, Mike Scherbakov wrote: > Thank you all for the feedback. > > > Dims - > > > 1) I'd advise to codify a proposal in fuel-specs under a 'policy' > directory > > I think it's great idea and I'll do it. > > > > 2) We don't have SME term

[openstack-dev] [cinder] The Absurdity of the Milestone-1 Deadline for Drivers

I've always thought it was a bit strange to require new drivers to merge by milestone 1. I think I understand the motivations of the policy. The main motivation was to free up reviewers to review "other things" and this policy guarantees that for 75% of the release reviewers don't have to revie

Re: [openstack-dev] [puppet] Moving puppet-ceph to the Openstack big tent

On 09/28/2015 08:31 AM, David Moreau Simard wrote: > puppet-ceph currently lives in stackforge [1] which is being retired > [2]. puppet-ceph is also mirrored on the Ceph Github organization [3]. > This version of the puppet-ceph module was created from scratch and > not as a fork of the (then) upst

[openstack-dev] [ironic] [javascript] ironic-webclient seeks more reviewers and contributors

Hey everyone! The ironic webclient is finally moving forward again, however we're at that odd stage where most of the ironic team is Awesome Python and Hardware types, and we're lacking reviewers able to keep an eye on our Angular Javascript code. In the interest of not creating an echo chamber ov

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

I'd like to submit my candidacy for the TC Election. I've been involved with OpenStack since the beginning of the Folsom release. We may have worked together on parts of Nova, Tempest, DevStack, Grenade, or in generally debugging failures in the upstream gate in OpenStack. Or from things like the

Re: [openstack-dev] [all] Proposed Mitaka release schedule

Excerpts from Ivan Kolodyazhny's message of 2015-09-28 17:41:46 +0300: > Hi Thierry, > > Thank you for sharing this information with us so early. One > comment/question from me about FinalClientLibraryRelease: > > Could we make client release at least one week later after M-3 milestone? > It will

[openstack-dev] [puppet][murano] Launchpad project created

Hi all, as you know murano started creating puppet manifests. They are located at the corresponding repository [1] And this is just a notification, that the separate project [2]to track puppet-related activities is

Re: [openstack-dev] [devstack] Is there a way to configure devstack for one flat external network using Kilo, Neutron?

On Mon, Sep 28, 2015 at 7:08 AM, Mike Spreitzer wrote: > Is there a way to configure devstack to install Neutron such that there is > just one network and that is an external network and Nova can create Compute > Instances on it, using projects of Kilo vintage? Mike, this might help, I have a scr

[openstack-dev] [Designate] Topics for Design Summit

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi All, Just a reminder that this etherpad is still nearly empty :). https://etherpad.openstack.org/p/designate-design-summit-tokyo Can we try and get a few more topics so we can talk about it on Wednesday? Thanks, Graham - -- Graham Hayes Softw

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

On 28/09/15 05:47, Gorka Eguileor wrote: On 26/09, Morgan Fainberg wrote: As a core (and former PTL) I just ignored commit message -1s unless there is something majorly wrong (no bug id where one is needed, etc). I appreciate well formatted commits, but can we let this one go? This discussion

Re: [openstack-dev] [fuel] PTL & Component Leads elections

> On 18 Sep 2015, at 04:39, Sergey Lukjanov wrote: > > > Time line: > > PTL elections > * September 18 - September 28, 21:59 UTC: Open candidacy for PTL position > * September 29 - October 8: PTL elections Just a reminder that we have a deadline for candidates today. Regards, -- Tomasz 'Zen'

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

On 09/28/15 at 10:19am, Sean Dague wrote: On 09/28/2015 10:11 AM, Andrew Laski wrote: On 09/28/15 at 08:50am, Monty Taylor wrote: On 09/28/2015 07:58 AM, Sylvain Bauza wrote: Specifically, I want "nova boot" to get me a VM with an IP address. I don't want it to do fancy orchestration - I wa

Re: [openstack-dev] KILO: neutron port-update --allowed-address-pairs action=clear throws an exception

Are you reading our reply comments? At the moment, there is no way to set allowed-address-pairs to an empty list by using neutron CLI. When action=clear is passed, type=xxx, list=true and specified values are ignored and None is sent to the server. Thus you cannot set allowed-address-pairs to [] wi

[openstack-dev] [Infra] Meeting Tuesday September 29th at 19:00 UTC

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

Re: [openstack-dev] [TripleO] tripleo.org theme

On 2015-09-28 09:43:37 -0400 (-0400), James Slagle wrote: > Would the content of tripleo-docs be exactly the same as what is > published at http://docs.openstack.org/developer/tripleo-docs/ ? > > I think it probably should be, and be updated on every merged commit. > If that's not the case, I thin

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Greetings Stackers! I'm announcing my candidacy for the Technical Committee Elections. Those of you who have been involved in OpenStack most likely know me, as I was part of the original team from Rackspace that created OpenStack in 2010. For the pa

Re: [openstack-dev] [murano] Murano code flow for custom development and combining murano with horizon in devstack

Hi 1) adding [murano] would definitely suffice 2) Seems that you want to combine some of the murano panels under your own dashboard, right? (I do not really see why would you want to do that, but still). I believe that it is possible. You can look at muranodashboard/dashboard.py file. It defin

[openstack-dev] [puppet] Moving puppet-ceph to the Openstack big tent

Hi, puppet-ceph currently lives in stackforge [1] which is being retired [2]. puppet-ceph is also mirrored on the Ceph Github organization [3]. This version of the puppet-ceph module was created from scratch and not as a fork of the (then) upstream puppet-ceph by Enovance [4]. Today, the version b

Re: [openstack-dev] [Barbican][Security] Automatic Certificate Management Environment

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Rob, I agree that the ACME standard is very interesting, but I'm also pretty new to it. And by pretty new I mean I just started reading it after I saw your email. :) There has been interest in adding support for Let's Encrypt as a Barbican back

Re: [openstack-dev] [murano] Murano code flow for custom development and combining murano with horizon in devstack

Thanks Kirill. Would adding "[murano]” to the subject line suffice or pls let me know if there is a separate mailing list for murano? Let me try to clarify what I am asking over here. So we have all these panels - 'Compute', 'Network', etc on Horizon dashboard. If I add another panel like 'Exampl

[openstack-dev] [ceilometer] OpenStack Telemetry user survey

Hello, The OpenStack Telemetry (aka Ceilometer) team would like to collect feedback and information from its user base in order to drive future improvements to the project. To do so, we have developed a survey. It should take about 15min to complete. Questions are fairly technical, so please

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

On 09/26/2015 12:04 AM, Joshua Harlow wrote: +1 from me, although I thought heat was supposed to be this thing? Maybe there should be a 'warm' project or something ;) Or we can call it 'bbs' for 'building block service' (obviously not bulletin board system); ask said service to build a set of b

[openstack-dev] [nova][infra] Intel NFV CI, testing hugepages, numa topology, cpu pinning

Hi cores et al, As discussed briefly with Jay Pipes in Vancouver, we were about to provide CI and tests for features such as: hugepages, cpu pinning, numa topology. We since worked on NFV CI here at Intel. The work on the CI and tests is now completed. A few details about the CI and tests. * CI

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

Le 28/09/2015 16:19, Sean Dague a écrit : On 09/28/2015 10:11 AM, Andrew Laski wrote: On 09/28/15 at 08:50am, Monty Taylor wrote: On 09/28/2015 07:58 AM, Sylvain Bauza wrote: Specifically, I want "nova boot" to get me a VM with an IP address. I don't want it to do fancy orchestration - I w

[openstack-dev] [election] [tc] Candidacy for Technical Committee

Hi all, I'm writing to let you know I would like to run for Technical Committee again this term. Here is my candidacy statement for your review. I have worked at Rackspace on the OpenStack collection of projects for five years now, working primarily on documentation. Rackspace is one of the foun

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

> From: Monty Taylor > To: Sylvain Bauza , "OpenStack Development > Mailing List (not for usage questions)" > Date: 09/28/2015 09:54 AM > Subject: Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how > to handle AZ bug 1496235?) > > ... > Specifically, I want "nova boot" to get me a VM w

Re: [openstack-dev] [all] Proposed Mitaka release schedule

Hi Thierry, Thank you for sharing this information with us so early. One comment/question from me about FinalClientLibraryRelease: Could we make client release at least one week later after M-3 milestone? It will give us more chances to have features landed into the client if they were merged lat

[openstack-dev] [devstack] Is there a way to configure devstack for one flat external network using Kilo, Neutron?

Is there a way to configure devstack to install Neutron such that there is just one network and that is an external network and Nova can create Compute Instances on it, using projects of Kilo vintage? Thanks, Mike __ Open

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

Hi, We have weekly Nova API meeting this week. The meeting is being held Tuesday UTC1200. In other timezones the meeting is at: EST 08:00 (Tue) Japan 21:00 (Tue) China 20:00 (Tue) United Kingdom 13:00 (Tue) The proposed agenda and meeting details are here: https://wiki.openstack.org/wiki/Meeti

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

On 09/28/2015 10:11 AM, Andrew Laski wrote: > On 09/28/15 at 08:50am, Monty Taylor wrote: >> On 09/28/2015 07:58 AM, Sylvain Bauza wrote: >> >> Specifically, I want "nova boot" to get me a VM with an IP address. I >> don't want it to do fancy orchestration - I want it to not need fancy >> orchestr

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

On 09/28/15 at 08:50am, Monty Taylor wrote: On 09/28/2015 07:58 AM, Sylvain Bauza wrote: Le 28/09/2015 12:35, Duncan Thomas a écrit : On 28 September 2015 at 12:35, Sylvain Bauza mailto:sba...@redhat.com>> wrote: About the maintenance burden, I also consider that patching clients is

[openstack-dev] [all] Proposed Mitaka release schedule

Hi everyone, You can find the proposed release schedule for Mitaka here: https://wiki.openstack.org/wiki/Mitaka_Release_Schedule That places the end release on April 7, 2016. It's also worth noting that in an effort to maximize development time, this schedule reduces the time between Feature Fre

Re: [openstack-dev] KILO: neutron port-update --allowed-address-pairs action=clear throws an exception

This is even not working: root@openstack-latest-kilo-28-09-2015-masoom:/opt/stack/devstack/accrc/admin# neutron port-update e5b05961-e5d0-481b-bbd0-2ce4bbd9ea64 --allowed-address-pairs type=list [] action=clear AllowedAddressPair must contain ip_address root@openstack-latest-kilo-28-09-2015-mas

Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how to handle AZ bug 1496235?)

On 09/28/2015 07:58 AM, Sylvain Bauza wrote: Le 28/09/2015 12:35, Duncan Thomas a écrit : On 28 September 2015 at 12:35, Sylvain Bauza mailto:sba...@redhat.com>> wrote: About the maintenance burden, I also consider that patching clients is far more easier than patching an API unless

Re: [openstack-dev] [glance] [infra] [neutron] [swift] [trove] [zaqar] [murano] [docs] Outreachy: selecting a project to contribute to

Hi Twinkle, Welcome! Please join us in #openstack-opw channel on irc.freenode.org. We can chat about different projects and helping you get started with OpenStack. Best, Victoria 2015-09-26 11:19 GMT-03:00 Anne Gentle : > Hi Twinkle, > > Welcome! Thanks for your interest. If you have time, sto

  1   2   >