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

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), >

[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

[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

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

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:

[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

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. ―

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'

[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

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

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

[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

[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

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

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

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

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] [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

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)

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

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

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

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

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. > > >

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

[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

[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:

[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.

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] [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.

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

[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] [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

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

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

[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

[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

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] [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

[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

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

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] [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 >

[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

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

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

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] [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 >

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

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)

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

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

[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

[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. *

[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

[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:

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

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

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

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

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

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

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

[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

[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

[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

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

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

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 > wrote: About the maintenance burden, I also consider that

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 >>

[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 __

[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

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

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 []

[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] KILO: neutron port-update --allowed-address-pairs action=clear throws an exception

stable KILO shall I checkout the latest code are you saying this...Also can you please confirm if you have tested this thing at your endand there was no problem... Thanks On Sun, Sep 27, 2015 at 11:29 PM, shihanzhang wrote: > which branch do you use? there is not

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

Le 25/09/2015 16:12, Andrew Laski a écrit : On 09/24/15 at 03:13pm, James Penick wrote: At risk of getting too offtopic I think there's an alternate solution to doing this in Nova or on the client side. I think we're missing some sort of OpenStack API and service that can handle this.

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

which branch do you use? there is not this problem in master branch. At 2015-09-28 13:43:05, "masoom alam" wrote: Can anybody highlight why the following command is throwing an exception: Command# neutron port-update db3113df-14a3-4d6d-a3c5-d0517a134fc3

Re: [openstack-dev] [Fuel][Plugins] add health check for plugins

Hi, Totally agree with you Andrey, other use cases could be : -for Ironic plugin, add test to validate that Ironic is properly deploy -for LMA plugin check that metric and log are properly collect, that elk, nagios or grafana dashboard are accessible -for cinder netapp multi backend, check that

Re: [openstack-dev] [oslo] nominating Brant Knudson for Oslo core

+1 for Brant Victor Le 24/09/2015 19:12, Doug Hellmann a écrit : Oslo team, I am nominating Brant Knudson for Oslo core. As liaison from the Keystone team Brant has participated in meetings, summit sessions, and other discussions at a level higher than some of our own core team members. He

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

I don't see any exception using bellow command root@szxbz:/opt/stack/neutron# neutron port-update 3748649e-243d-4408-a5f1-8122f1fbf501 --allowed-address-pairs action=clear Allowed address pairs must be a list. At 2015-09-28 14:36:44, "masoom alam" wrote: stable

Re: [openstack-dev] [murano] Outreachy: Interest in contributing to open-source

Hi Yolande, welcome to OpenStack and open source! We gladly introduce you with Murano project! Topic 'Implementation of tagging heat stacks, created by murano' is already taken, but we can offer you another one after talking to you about what you are interesting in. You can go to #murano

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

On 28/09, Andreas Jaeger wrote: > On 2015-09-28 11: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

[openstack-dev] [ptls] Asserting that your projects follow at least the base deprecation policy

Hi everyone, Last week at the Technical Committee meeting, following the discussion on this mailing-list a few weeks ago, we finally passed a definition[1] for a standard base deprecation policy for OpenStack projects. [1]

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

On 09/25/2015 08:16 PM, Monty Taylor wrote: > On 09/25/2015 06:37 PM, Chris Hoge wrote: >> >>> On Sep 25, 2015, at 10:12 AM, Andrew Laski >> > wrote: >>> >>> I understand that reasoning, but still am unsure on a few things. >>> >>> The direction seems

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

Please help, its not working: root@openstack-latest-kilo-28-09-2015-masoom:/opt/stack/devstack# neutron port-show 2d1bfe12-7db6-4665-9c98-6b9b8a043af9 +---+-+ | Field | Value

[openstack-dev] [nova] Liberty and Nova Specs, Blueprints and Design Summit for Mitaka

Hi, A quick update on where we are at. Liberty - Its time to give RC1 an good test. We need to keep our eyes out for release blockers, using this tag: https://bugs.launchpad.net/nova/+bugs?field.tag=liberty-rc-potential We will need an new tag on or after 8th October, to include

[openstack-dev] [puppet] weekly meeting #53

Hello! Here's an initial agenda for our weekly meeting, tomorrow at 1500 UTC in #openstack-meeting-4: https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20150929 Feel free to add any additional items you'd like to discuss. If our schedule allows it, we'll make bug triage during

Re: [openstack-dev] [all] Consistent support for SSL termination proxies across all API services

On 09/28/2015 05:01 AM, Julien Danjou wrote: > On Wed, Sep 23 2015, Julien Danjou wrote: > > > […] > >> I'm willing to clear that out and come with specs and patches if that >> can help. :) > > Following-up on myself, I went ahead and I wrote a more complete version > of the current proxy

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

On 09/27/2015 08:43 AM, Doug Hellmann wrote: > Excerpts from Mark Voelker's message of 2015-09-25 20:43:23 +: >> On Sep 25, 2015, at 1:56 PM, Doug Hellmann wrote: >>> >>> Excerpts from Mark Voelker's message of 2015-09-25 17:42:24 +: >> >> Ah. Thanks for bringing

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

On 2015-09-28 11: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

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

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 +: >>> On Sep 25, 2015, at 1:56 PM, Doug Hellmann wrote: Excerpts from Mark

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

Le 28/09/2015 11:23, Duncan Thomas a écrit : The trouble with putting more intelligence in the clients is that there are more clients than just the one we provide, and the more smarts we require in the clients, the more divergence of functionality we're likely to see. Also, bugs and slowly

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

Hi, murano-dashboard works the same way any other horizon dashboard does. I’m not quite sure, what you meant by «combined and showed under one tab», could you please elaborate? If you’re asking about debugging — you can install murano-dashboard locally and configure it to use remote cloud (i.e.

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

As already mentioned, we need to pass [] (an empty list) rather than None as allowed_address_pairs. At the moment it is not supported in Neutron CLI. This review https://review.openstack.org/#/c/218551/ is trying to fix this problem. Akihiro 2015-09-28 15:51 GMT+09:00 shihanzhang

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

IMO those checks should be automated, as we automate pep8 checks on our python code. I agree, that if we have a rule for this, we should follow it, but it's a waste of time reviewing and enforcing this manually. Best regards. Miguel Ángel. Gorka Eguileor wrote: On 26/09, Morgan Fainberg

Re: [openstack-dev] [all][stable][release][horizon] 2015.1.2

On 25/09/15 15:39, Ihar Hrachyshka wrote: > I see you have three people in the horizon-stable-maint team only. > Have you considered expanding the team with more folks? In > neutron, we have five people in the stable-maint group. Good suggestion! In horizon, we just have a very few cores being

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

On 28 September 2015 at 12:35, Sylvain Bauza wrote: > About the maintenance burden, I also consider that patching clients is far > more easier than patching an API unless I missed something. > > I think I very much disagree there - patching a central installation is much, much

[openstack-dev] [mistral] Cancelling team meeting today (09/28/2015)

Mistral Team, We’re cancelling today’s team meeting because a number of key members won’t be able to attend. The next one is scheduled for 5 Oct. Best Regards, Nikolay Makhotkin @Mirantis Inc. __ OpenStack Development

  1   2   >