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

Kris, On Sep 30, 2015, at 4:26 PM, Kris G. Lindgren mailto:klindg...@godaddy.com>> wrote: We are looking at deploying magnum as an answer for how do we do containers company wide at Godaddy. I am going to agree with both you and josh. I agree that managing one large system is going to be a pa

[openstack-dev] [QA] Meeting Thursday October 1st at 9:00 UTC

Hi everyone, Please reminder that the weekly OpenStack QA team IRC meeting will be Thursday, October 1st at 9:00 UTC in the #openstack-meeting channel. The agenda for the meeting can be found here: https://wiki.openstack.org/wiki/Meetings/QATeamMeeting Anyone is welcome to add an item to the agen

Re: [openstack-dev] [TripleO] Defining a public API for tripleo-common

On 2015-09-30 01:08, Dougal Matthews wrote: > Hi, > > What is the standard practice for defining public API's for OpenStack > libraries? As I am working on refactoring and updating tripleo-common I have > to grep through the projects I know that use it to make sure I don't break > anything. >

Re: [openstack-dev] Do not modify (or read) ERROR_ON_CLONE in devstack gate jobs

hi, you removed networking-midonet tempest jobs for the reason. [1] i want to revive them. but i'm not sure what methods are acceptable or not. can you explain a little? i did some research of other repos. - networking-ovn seems to use a raw "git clone" command to fetch openvswitch repo - networ

Re: [openstack-dev] [neutron] pypi packages for networking sub-projects

Hi Armando and Kyle, Thanks for your reply. Yes, the codes are not ready for release yet. The code size is not small and we are working hard on getting the codes ready as soon as possible. Cathy From: Kyle Mestery [mailto:mest...@mestery.com] Sent: Wednesday, September 30, 2015 6:40 PM To: Ope

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

Hi folks, I've just setup the voting system and you should start receiving email with topic "Poll: Fuel PTL Elections Fall 2015". NOTE: Please, don't forward this email, it contains *personal* unique token for the voting. Thanks. On Wed, Sep 30, 2015 at 3:28 AM, Vladimir Kuklin wrote: > +1 to

[openstack-dev] [Horizon] Selenium is now green - please pay attention to it

Hi folks, Selenium tests "gate-horizon-selenium-headless" are now green in master again. Please pay attention if it goes red. I will probably notice, but if I don't, and you can't figure out what's going on, please feel free to get in touch with me (r1chardj0n3s on IRC in #openstack-horizon, or e

Re: [openstack-dev] [kolla] new yaml format for all.yml, need feedback

On Wed, Sep 30, 2015 at 11:24 PM, Jeff Peeler wrote: > The patch I just submitted[1] modifies the syntax of all.yml to use > dictionaries, which changes how variables are referenced. The key > point being in globals.yml, the overriding of a variable will change > from simply specifying the variab

Re: [openstack-dev] [nova] how to address boot from volume failures

On Sep 30, 2015, at 14:45, Andrew Laski wrote: > > I have a slight preference for #1. Nova is not buggy here novaclient is so I > think we should contain the fix there. > > Is using the v2 API an option? That should also allow the 3 extra parameters > mentioned in #2. +1. I have put up http

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

Thanks for summarizing this Mark. What's the best way to get feedback about this to the TC? I'd love to see some of the items which I think are common sense for anyone who can't just blow away devstack and start over to get added for consideration. On Tue, Sep 29, 2015 at 11:32 AM, Mark Voelker w

Re: [openstack-dev] Announcing Liberty RC1 availability in Debian

On 30/09/15 19:58, Thomas Goirand wrote: Hi everyone! 1/ Announcement === I'm pleased to announce, in advance of the final Liberty release, that Liberty RC1 not only has been fully uploaded to Debian Experimental, but also that the Tempest CI (which I maintain and is a package only

[openstack-dev] [fuel] Fuel 7.0 is released

We are proud to announce the release of Fuel 7.0, deployment and management tool for OpenStack. This release introduces support for OpenStack 2015.1.0 (Kilo) and continues to improve Fuel's pluggability and flexibility: - Fuel plugins now can reserve their own VIP addresses, define their own no

Re: [openstack-dev] [neutron] pypi packages for networking sub-projects

On Wed, Sep 30, 2015 at 8:26 PM, Armando M. wrote: > > > On 30 September 2015 at 16:02, Cathy Zhang > wrote: > >> Hi Kyle, >> >> >> >> Is this only about the sub-projects that are ready for release? I do not >> see networking-sfc sub-project in the list. Does this mean we have done the >> pypi r

Re: [openstack-dev] [neutron] pypi packages for networking sub-projects

On 30 September 2015 at 16:02, Cathy Zhang wrote: > Hi Kyle, > > > > Is this only about the sub-projects that are ready for release? I do not > see networking-sfc sub-project in the list. Does this mean we have done the > pypi registrations for the networking-sfc project correctly or it is not >

Re: [openstack-dev] [all] Liberty release - what is the correct version - 2015.2.0, 8.0.0 or 12.0.0?

On 2015-10-01 10:54:20 +1000 (+1000), Richard Jones wrote: [...] > I believe that if we are moving to semver, then 12.0.0 is > appropriate. Each project participating in the release is following semver independently, with the first digit indicating the number of OpenStack integrated releases in wh

Re: [openstack-dev] [all] Liberty release - what is the correct version - 2015.2.0, 8.0.0 or 12.0.0?

This thread http://lists.openstack.org/pipermail/openstack-dev/2015-May/065211.html (carries on http://lists.openstack.org/pipermail/openstack-dev/2015-June/065278.html) May help. On 1 October 2015 at 13:54, Richard Jones wrote: > Hi all, > > Historically OpenStack releases are versioned .

[openstack-dev] [all] Liberty release - what is the correct version - 2015.2.0, 8.0.0 or 12.0.0?

Hi all, Historically OpenStack releases are versioned .N as documented in the Release Naming wiki page[1]. The Liberty Release Schedule[2] has the version 2015.2.0. However, in Horizon land, I've been informed that OpenStack is moving to semver. I can't find any information about this move exc

Re: [openstack-dev] [Fuel][PTL] PTL Candidates Q&A Session

Vladimir, we may mix technical direction / tech debt roadmap and process, political, and people management work of PTL. PTL definition in OpenStack [1] reflects many things which PTL becomes responsible for. This applies to Fuel as well. I'd like to reflect some things here which I'd expect PTL d

[openstack-dev] [Cinder] New driver submission deadline

This message is for all new vendors looking to add a new Cinder driver in the Mitaka release as well as any existing vendors that need to add a new protocol/driver to what is already in tree. There has been some discussion on the mailing list and in the IRC channel about changes to our policy arou

Re: [openstack-dev] [Manila] CephFS native driver

Is there any plan to merge those branches to master? Or is there anything needs to be done more? Shinobu - Original Message - From: "Ben Swartzlander" To: "OpenStack Development Mailing List (not for usage questions)" Sent: Saturday, September 26, 2015 9:27:58 AM Subject: Re: [openstac

Re: [openstack-dev] [Neutron] Release of a neutron sub-project

Kyle, We referenced arista's setup/config files when we setup the pypi for our plugin. So if it is ok for Arista, then it would be ok for ale-omniswitch too, i believe. You said Arista was ok when you did in google, instead of pypi search, in another email. So can you pls. check again ale-omniswit

Re: [openstack-dev] [puppet] [infra] split integration jobs

Emillien, What image is being used to spawn the image? We see 300 sec as a good timeout time in fuel with a cirros image. The time can usually be substantially cut if the image is of any size using ceph for ephemeral... On Wed, Sep 30, 2015 at 4:37 PM Jeremy Stanley wrote: > On 2015-09-30 17:14

Re: [openstack-dev] [puppet] should puppet-neutron manage third party software?

Makes sense to me. Opened a bug to track the migration of agents/n1kv_vem.pp out of puppet-neutron during the M-cycle: https://bugs.launchpad.net/puppet-neutron/+bug/1501535 Thanks. Steven Hillman On 9/29/15, 9:23 AM, "Emilien Macchi" wrote: >My suggestion: > >* patch master to send deprecatio

Re: [openstack-dev] [puppet] [infra] split integration jobs

On 2015-09-30 17:14:27 -0400 (-0400), Emilien Macchi wrote: [...] > I like #3 but we are going to consume more CI resources (that's why I > put [infra] tag). [...] I don't think adding one more job is going to put a strain on our available resources. In fact it consumes just about as much to run a

Re: [openstack-dev] [puppet] should puppet-neutron manage third party software?

On 09/29/2015 12:23 PM, Emilien Macchi wrote: > My suggestion: > > * patch master to send deprecation warning if third party repositories > are managed in our current puppet-neutron module. > * do not manage third party repositories from now and do not accept any > patch containing this kind of

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

We are looking at deploying magnum as an answer for how do we do containers company wide at Godaddy. I am going to agree with both you and josh. I agree that managing one large system is going to be a pain and pas experience tells me this wont be practical/scale, however from experience I also

Re: [openstack-dev] [magnum] New Core Reviewers

+1 for both. Welcome! From: Davanum Srinivas [mailto:dava...@gmail.com] Sent: September-30-15 7:00 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] New Core Reviewers +1 from me for both Vilobh and Hua. Thanks, Dims On Wed, Sep 30, 2015 a

Re: [openstack-dev] [neutron] pypi packages for networking sub-projects

Hi Kyle, Is this only about the sub-projects that are ready for release? I do not see networking-sfc sub-project in the list. Does this mean we have done the pypi registrations for the networking-sfc project correctly or it is not checked because it is not ready for release yet? Thanks, Cathy

Re: [openstack-dev] [magnum] New Core Reviewers

+1 from me for both Vilobh and Hua. Thanks, Dims On Wed, Sep 30, 2015 at 6:47 PM, Adrian Otto wrote: > Core Reviewers, > > I propose the following additions to magnum-core: > > +Vilobh Meshram (vilobhmm) > +Hua Wang (humble00) > > Please respond with +1 to agree or -1 to veto. This will be deci

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

Totally get it, And its interesting the boundaries that are being pushed, Also interesting to know the state of the world, and the state of magnum and the state of COE systems. I'm somewhat surprised that they lack multi-tenancy in any kind of manner (but I guess I'm not to surprised, its a featu

[openstack-dev] [puppet] prepare 5.2.0 and 6.1.0 releases

Hi, I would like to organize a "release day" sometimes soon, to release 5.2.0 (Juno) [1] and 6.1.0 (Kilo) [2]. Also, we will take the opportunity of that day to consolidate our process and bring more documentation [3]. If you have backport needs, please make sure they are all sent in Gerrit, so

[openstack-dev] [magnum] New Core Reviewers

Core Reviewers, I propose the following additions to magnum-core: +Vilobh Meshram (vilobhmm) +Hua Wang (humble00) Please respond with +1 to agree or -1 to veto. This will be decided by either a simple majority of existing core reviewers, or by lazy consensus concluding on 2015-10-06 at 00:00 U

Re: [openstack-dev] [ops] Operator Local Patches

Is the purge deleted a replacement for nova-manage db archive-deleted? It hasn't worked for several cycles and so I assume it's abandoned. On Sep 30, 2015 4:16 PM, "Matt Riedemann" wrote: > > > On 9/29/2015 6:33 PM, Kris G. Lindgren wrote: > >> Hello All, >> >> We have some pretty good contributi

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

Hello People! I am tossing one of my hats into the ring to run for TC. Yes, I believe you could call me a "diversity candidate" as I'm not much of a developer any more, but I think my skills would be a great addition to the excellent people who are on the TC (past and present). My background: I

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

Joshua, If you share resources, you give up multi-tenancy. No COE system has the concept of multi-tenancy (kubernetes has some basic implementation but it is totally insecure). Not only does multi-tenancy have to “look like” it offers multiple tenants isolation, but it actually has to deliver th

Re: [openstack-dev] Announcing Liberty RC1 availability in Debian

On 09/30/2015 07:25 PM, Jordan Pittier wrote: > We are not used to reading "thanks" messages from you :) So I enjoy this > email even more ! I am well aware that I do have the reputation within the community to complain too much. I'm the world champion of starting monster troll thread by mistake.

Re: [openstack-dev] [Large Deployments Team][Performance Team] New informal working group suggestion

Hello, Thanks Dina for bringing up this great idea. My team at Intel is working with Performance testing so far so we will be likely to be part of that project. The performance aspect at large scale is an obstacle for enterprise deployments. For that reason Win The Enterprise

Re: [openstack-dev] [ops] Operator Local Patches

On 9/29/2015 6:33 PM, Kris G. Lindgren wrote: Hello All, We have some pretty good contributions of local patches on the etherpad. We are going through right now and trying to group patches that multiple people are carrying and patches that people may not be carrying but solves a problem that

[openstack-dev] [Fuel] Remove nova-network as a deployment option in Fuel?

Hi team, where do we stand with it now? I remember there was a plan to remove nova-network support in 7.0, but we've delayed it due to vcenter/dvr or something which was not ready for it. Can we delete it now? The early in the cycle we do it, the easier it will be. Thanks! -- Mike Scherbakov #mi

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

Yes, sfc without nsh is what I am looking into and I am thinking ovn can have a better approach. I did an implementation of sfc around nsh that used ovs & flows from custom ovs-agent back in mar-may. I added fields in ovs agent to send additional info for actions as well. Neutron side was quite tr

Re: [openstack-dev] [nova] how to address boot from volume failures

On 09/30/15 at 05:03pm, Sean Dague wrote: Today we attempted to branch devstack and grenade for liberty, and are currently blocked because in liberty with openstack client and novaclient, it's not possible to boot a server from volume using just the volume id. That's because of this change in no

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

Wouldn't that limit the ability to share/optimize resources then and increase the number of operators needed (since each COE/bay would need its own set of operators managing it)? If all tenants are in a single openstack cloud, and under say a single company then there isn't much need for manag

[openstack-dev] [puppet] [infra] split integration jobs

Hello, Today our Puppet OpenStack Integration jobs are deploying: - mysql / rabbitmq - keystone in wsgi with apache - nova - glance - neutron with openvswitch - cinder - swift - sahara - heat - ceilometer in wsgi with apache Currently WIP: - Horizon - Trove The status of the jobs is that some te

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

On 09/30/2015 04:09 PM, Murali R wrote: > Russel, > > For instance if I have a nsh header embedded in vxlan in the incoming > packet, I was wondering if I can transfer that to geneve options > somehow. This is just as an example. I may have header other info either > in vxlan or ip that needs to e

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

On 09/30/2015 11:43 AM, Sofer Athlan-Guyot wrote: Gilles Dubreuil writes: On 30/09/15 03:43, Rich Megginson wrote: On 09/28/2015 10:18 PM, Gilles Dubreuil wrote: 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 0

[openstack-dev] [nova] how to address boot from volume failures

Today we attempted to branch devstack and grenade for liberty, and are currently blocked because in liberty with openstack client and novaclient, it's not possible to boot a server from volume using just the volume id. That's because of this change in novaclient - https://review.openstack.org/#/c/

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

On 09/25/2015 05:00 PM, Ryan Brown wrote: > I believe the 72 limit is derived from 80-8 (terminal width - tab width) If I'm not mistaking, 72 is because of the email format limitation. Thomas __ OpenStack Development Mailin

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

Joshua, The tenancy boundary in Magnum is the bay. You can place whatever single-tenant COE you want into the bay (Kubernetes, Mesos, Docker Swarm). This allows you to use native tools to interact with the COE in that bay, rather than using an OpenStack specific client. If you want to use the O

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

Adrian Otto wrote: Thanks everyone who has provided feedback on this thread. The good news is that most of what has been asked for from Magnum is actually in scope already, and some of it has already been implemented. We never aimed to be a COE deployment service. That happens to be a necessity t

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

Russel, For instance if I have a nsh header embedded in vxlan in the incoming packet, I was wondering if I can transfer that to geneve options somehow. This is just as an example. I may have header other info either in vxlan or ip that needs to enter the ovn network and if we have generic ovs comm

[openstack-dev] [tripleo] How to selectively enable new services?

Hi all, So I wanted to start some discussion on $subject, because atm we have a couple of patches adding support for new services (which is great!): Manila: https://review.openstack.org/#/c/188137/ Sahara: https://review.openstack.org/#/c/220863/ So, firstly I am *not* aiming to be any impedimen

Re: [openstack-dev] [neutron] pypi packages for networking sub-projects

Hey Kyle, I have updated the ownership of networking-l2gw. I have +1'd your patch. As soon as it merges the ACLs for the L2GW project will be fine as well. Thanks for confirming about the networking-arista. With this both of these packages should be good to go. Thanks -Sukhdev On Wed, Sep 30,

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

Hi folks, I'd like to propose my candidacy for the technical committee elections. I've been involved in OpenStack for around ~four~ years now, working to help integrate it into various Yahoo! systems and infrastructure. I've been involved with integration and creation (and maturation) of many pr

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

On 09/30/2015 03:29 PM, Murali R wrote: > Russell, > > Are any additional options fields used in geneve between hypervisors at > this time? If so, how do they translate to vxlan when it hits gw? For > instance, I am interested to see if we can translate a custom header > info in vxlan to geneve he

Re: [openstack-dev] [neutron] pypi packages for networking sub-projects

Sukhdev, you're right, for some reason that one didn't show up in a pypi search on pypi itself, but does in google. And it is correctly owned [1]. [1] https://pypi.python.org/pypi/networking_arista On Wed, Sep 30, 2015 at 2:21 PM, Sukhdev Kapur wrote: > Hey Kyle, > > I am bit confused by this.

Re: [openstack-dev] [neutron] pypi packages for networking sub-projects

Kyle, I have taken care of this for networking-infoblox. Please let me know if anything else is necessary. Thanks, John On Sep 30, 2015, at 2:55 PM, Kyle Mestery mailto:mest...@mestery.com>> wrote: Folks: In trying to release some networking sub-projects recently, I ran into an issue [1] wh

Re: [openstack-dev] [neutron + ovn] Does neutron ovn plugin support to setup multiple neutron networks for one container?

Russell, Are any additional options fields used in geneve between hypervisors at this time? If so, how do they translate to vxlan when it hits gw? For instance, I am interested to see if we can translate a custom header info in vxlan to geneve headers and vice-versa. And if there are flow commands

Re: [openstack-dev] [neutron] pypi packages for networking sub-projects

Hey Kyle, I am bit confused by this. I just checked networking-arista and see that the co-owner of the project is openstackci I also checked the [1] and [2] and the settings for networking-arista are correct as well. What else is missing which make you put networking-arista in the second category

Re: [openstack-dev] [kolla] new yaml format for all.yml, need feedback

Also in favor is it lands before Liberty. But I don't want to see a format change straight into Mitaka. Sam Yaple On Wed, Sep 30, 2015 at 1:03 PM, Steven Dake (stdake) wrote: > I am in favor of this work if it lands before Liberty. > > Regards > -steve > > > On 9/30/15, 10:54 AM, "Jeff Peeler"

Re: [openstack-dev] [kolla] proposing Michal Jastrzebski (inc0) for core reviewer

Thanks everyone! I really appreciate this and I hope to help to make kolla even better project than it is right now (and right now it's pretty cool;)). We have great community, very diverse and very dedicated. It's pleasure to work with all of you and let's keep up with great work in following

[openstack-dev] [cinder] [Sahara] Block Device Driver updates

Hi team, I know that Block Device Driver (BDD) is not popular in Cinder community. The main issues were: * driver is not good maintained * it doesn't feet minimum features set * there is no CI for it * it's not a Cinder way/it works only when instance and volume are created on the same host * etc

Re: [openstack-dev] [Neutron] Release of a neutron sub-project

On Tue, Sep 29, 2015 at 8:04 PM, Kyle Mestery wrote: > On Tue, Sep 29, 2015 at 2:36 PM, Vadivel Poonathan < > vadivel.openst...@gmail.com> wrote: > >> Hi, >> >> As per the Sub-Project Release process - i would like to tag and release >> the following sub-project as part of upcoming Liberty releas

[openstack-dev] [neutron] pypi packages for networking sub-projects

Folks: In trying to release some networking sub-projects recently, I ran into an issue [1] where I couldn't release some projects due to them not being registered on pypi. I have a patch out [2] which adds pypi publishing jobs, but before that can merge, we need to make sure all projects have pypi

Re: [openstack-dev] [glance] Models and validation for v2

Agree with you. That's why I am asking about reasoning. Perhaps, we need to realize how to get rid of this in glanceclient. Best regards, Kairat Kushaev On Wed, Sep 30, 2015 at 7:04 PM, Jay Pipes wrote: > On 09/30/2015 09:31 AM, Kairat Kushaev wrote: > >> Hi All, >> In short terms, I am wonderi

Re: [openstack-dev] [kolla] proposing Michal Jastrzebski (inc0) for core reviewer

Michal, The vote was unanimous. Welcome to the Kolla Core Reviewer team. I have added you to the appropriate gerrit group. Regards -steve From: Steven Dake mailto:std...@cisco.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack

Re: [openstack-dev] [kolla] new yaml format for all.yml, need feedback

I am in favor of this work if it lands before Liberty. Regards -steve On 9/30/15, 10:54 AM, "Jeff Peeler" wrote: >The patch I just submitted[1] modifies the syntax of all.yml to use >dictionaries, which changes how variables are referenced. The key >point being in globals.yml, the overriding o

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

Hi David, Exactly what Tim mentioned in his email – there are 2 VMs. The VM that I published has a README file in the home directory when you login with the credentials vagrant/vagrant. Looking forward to your feedback. -Shiv From: Tim Hinrichs [mailto:t...@styra.com] Sent: Wednesday, Septe

[openstack-dev] [kolla] new yaml format for all.yml, need feedback

The patch I just submitted[1] modifies the syntax of all.yml to use dictionaries, which changes how variables are referenced. The key point being in globals.yml, the overriding of a variable will change from simply specifying the variable to using the dictionary value: old: api_interface: 'eth0'

Re: [openstack-dev] [stable][glance] glance-stable-maint group refresher

Thank you for your confidence in me folks! I I'll be happy to maintain the stability of our project and continue working on its improvements. Best regards, Mike On Wed, Sep 30, 2015 at 4:28 PM, Nikhil Komawar wrote: > > > On 9/30/15 8:46 AM, Kuvaja, Erno wrote: > > Hi all, > > > > I’d like to p

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

Gilles Dubreuil writes: > On 30/09/15 03:43, Rich Megginson wrote: >> On 09/28/2015 10:18 PM, Gilles Dubreuil wrote: >>> >>> 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-G

Re: [openstack-dev] [openstack-ansible] Proposing Steve Lewis (stevelle) for core reviewer

+1 from me as well -- Dave Wilde Sent with Airmail On September 30, 2015 at 03:51:48, Jesse Pretorius (jesse.pretor...@gmail.com) wrote: Hi everyone, I'd like to propose that Steve Lewis (stevelle) be added as a core reviewer. He has made an effort to consis

Re: [openstack-dev] Announcing Liberty RC1 availability in Debian

On Wed, Sep 30, 2015 at 1:58 PM, Thomas Goirand wrote: > Hi everyone! > > 1/ Announcement > === > > I'm pleased to announce, in advance of the final Liberty release, that > Liberty RC1 not only has been fully uploaded to Debian Experimental, but > also that the Tempest CI (which I mai

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

Hi David, There are 2 VM images for Congress that we're working on simultaneously: Shiv's and Alex's. 1. Shiv's image is to help new people understand some of the use cases Congress was designed for. The goal is to include a bunch of use cases that we have working. 2. Alex's image is the one we

Re: [openstack-dev] Infra needs Gerrit developers

I am definitely interested in helping out with this as I feel the pain of gerrit, particularly around text entry... Not a huge fan of Java but might be able to take on some low-hanging fruit once I've had a chance to tackle the JJB 2.0 API. Maybe this is the wrong place to discuss, but is there a

Re: [openstack-dev] [election][TC] TC Candidacy

Mike - Congrats on your new position! Looking forward to working with you. Carol -Original Message- From: Mike Perez [mailto:thin...@gmail.com] Sent: Wednesday, September 30, 2015 1:55 AM To: OpenStack Development Mailing List Subject: [openstack-dev] [election][TC] TC Candidacy Hi all!

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

On 09/30/2015 12:11 PM, Mike Perez wrote: On 13:29 Sep 28, 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" an

Re: [openstack-dev] [kolla] proposing Michal Jastrzebski (inc0) for core reviewer

Looks like he passed 3 already, but here's another +1 :) Steven Dake (stdake) schreef op 2015-09-30 00:20: Hi folks, I am proposing Michal for core reviewer. Consider my proposal as a +1 vote. Michal has done a fantastic job with rsyslog, has done a nice job overall contributing to the project

Re: [openstack-dev] [openstack-ansible] Proposing Steve Lewis (stevelle) for core reviewer

+1 from me -- Kevin Carter IRC: cloudnull From: Jesse Pretorius Sent: Wednesday, September 30, 2015 3:51 AM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [openstack-ansible] Proposing Steve Lewis (stevelle) for core reviewer Hi everyone, I'd

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

I think I'm seeing similar errors, but I'm not certain. With the OVA I downloaded last night, when I run "./rejoin-stack.sh", I get "Couldn't find ./stack-screenrc file; have you run stack.sh yet?" Concerning the original page with setup instructions, at https://docs.google.com/document/d/1isp

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

Thanks everyone who has provided feedback on this thread. The good news is that most of what has been asked for from Magnum is actually in scope already, and some of it has already been implemented. We never aimed to be a COE deployment service. That happens to be a necessity to achieve our more

Re: [openstack-dev] [kolla] proposing Michal Jastrzebski (inc0) for core reviewer

On Tue, Sep 29, 2015 at 6:20 PM, Steven Dake (stdake) wrote: > Hi folks, > > I am proposing Michal for core reviewer. Consider my proposal as a +1 vote. > Michal has done a fantastic job with rsyslog, has done a nice job overall > contributing to the project for the last cycle, and has really imp

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

On 13:29 Sep 28, 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 75%

Re: [openstack-dev] [kolla] proposing Michal Jastrzebski (inc0) for core reviewer

Way to go Michal! +1 -Ryan - Original Message - From: "Swapnil Kulkarni" To: "OpenStack Development Mailing List (not for usage questions)" Sent: Wednesday, September 30, 2015 5:00:27 AM Subject: Re: [openstack-dev] [kolla] proposing Michal Jastrzebski (inc0) for core reviewer On W

Re: [openstack-dev] [nova] live migration in Mitaka

On 09/30/2015 06:03 AM, Koniszewski, Pawel wrote: From: Murray, Paul (HP Cloud) [mailto:pmur...@hpe.com] - migrate suspended instances I'm not sure I understand this correctly. When user calls 'nova suspend' I thought that it actually "hibernates" VM and saves memory state to disk [2][3]. In

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

Hello Developers and Community, I would like to submit my candidacy for the TC election. I have been involved in OpenStack activities since April 2011, when I became part one of the founders of the networking project known as Quantum at that time. I have been a core reviewer for Neutron since Nov

Re: [openstack-dev] [glance] Models and validation for v2

On 09/30/2015 09:31 AM, Kairat Kushaev wrote: Hi All, In short terms, I am wondering why we are validating responses from server when we are doing image-show, image-list, member-list, metadef-namespace-show and other read-only requests. AFAIK, we are building warlock models when receiving respon

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

+1 Hongbin. From perspective of Solum, which hopes to use Magnum for its application container scheduling requirements, deep integration of COEs with OpenStack services like Keystone will be useful. Specifically, I am thinking that it will be good if Solum can depend on Keystone tokens to deplo

Re: [openstack-dev] [murano] suggestion on commit message title format for the murano-apps repository

lets discuss in more details how it should be I have prepared a draft. please take a look https://review.openstack.org/#/c/229477/ 2015-09-25 13:16 GMT+03:00 Kirill Zaitsev : > Looks reasonable to me! Could you maybe document that on HACKING.rst in > the repo? We could vote on the commit itse

Re: [openstack-dev] [heat] Convergence: Detecting and handling worker failures

Clint Byrum wrote: Excerpts from Anant Patil's message of 2015-09-30 00:10:52 -0700: Hi, One of remaining items in convergence is detecting and handling engine (the engine worker) failures, and here are my thoughts. Background: Since the work is distributed among heat engines, by some means he

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

On 9/29/2015 11:00 PM, Monty Taylor wrote: *waving hands wildly at details* ... I believe that the real win is if Magnum's control plan can integrate the network and storage fabrics that exist in an OpenStack with kube/mesos/swarm. Just deploying is VERY meh. I do not care - it's not interes

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

On 29/09/15 12:05, Ihar Hrachyshka wrote: On 25 Sep 2015, at 16:44, Ihar Hrachyshka wrote: Hi all, releases are approaching, so it’s the right time to start some bike shedding on the mailing list. Recently I got pointed out several times [1][2] that I violate our commit message requirement

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

+1 from me as well. I think what makes Magnum appealing is the promise to provide container-as-a-service. I see coe deployment as a helper to achieve the promise, instead of the main goal. Best regards, Hongbin From: Jay Lau [mailto:jay.lau@gmail.com] Sent: September-29-15 10:57 PM To: Ope

Re: [openstack-dev] [heat] Convergence: Detecting and handling worker failures

On Wed, 2015-09-30 at 02:29 -0700, Clint Byrum wrote: > Excerpts from Anant Patil's message of 2015-09-30 00:10:52 -0700: > > Hi, > > > > One of remaining items in convergence is detecting and handling engine > > (the engine worker) failures, and here are my thoughts. > > > > Background: Since th

Re: [openstack-dev] [heat] Convergence: Detecting and handling worker failures

On 30-Sep-15 14:59, Clint Byrum wrote: > Excerpts from Anant Patil's message of 2015-09-30 00:10:52 -0700: >> Hi, >> >> One of remaining items in convergence is detecting and handling engine >> (the engine worker) failures, and here are my thoughts. >> >> Background: Since the work is distributed a

Re: [openstack-dev] [heat] Convergence: Detecting and handling worker failures

On 30-Sep-15 18:13, Ryan Brown wrote: > On 09/30/2015 03:10 AM, Anant Patil wrote: >> Hi, >> >> One of remaining items in convergence is detecting and handling engine >> (the engine worker) failures, and here are my thoughts. >> >> Background: Since the work is distributed among heat engines, by so

[openstack-dev] [glance] Models and validation for v2

Hi All, In short terms, I am wondering why we are validating responses from server when we are doing image-show, image-list, member-list, metadef-namespace-show and other read-only requests. AFAIK, we are building warlock models when receiving responses from server (see [0]). Each model requires s

Re: [openstack-dev] [stable][glance] glance-stable-maint group refresher

On 9/30/15 8:46 AM, Kuvaja, Erno wrote: > > Hi all, > > > > I’d like to propose following changes to glance-stable-maint team: > > 1) Removing Zhi Yan Liu from the group; unfortunately he has > moved on to other ventures and is not actively participating our > operations anymore. > +1 (alw

Re: [openstack-dev] [TripleO] Defining a public API for tripleo-common

On 09/30/2015 03:15 PM, Ryan Brown wrote: On 09/30/2015 04:08 AM, Dougal Matthews wrote: Hi, What is the standard practice for defining public API's for OpenStack libraries? As I am working on refactoring and updating tripleo-common I have to grep through the projects I know that use it to make

Re: [openstack-dev] [TripleO] Defining a public API for tripleo-common

On 09/30/2015 04:08 AM, Dougal Matthews wrote: Hi, What is the standard practice for defining public API's for OpenStack libraries? As I am working on refactoring and updating tripleo-common I have to grep through the projects I know that use it to make sure I don't break anything. The API wor

[openstack-dev] [fuel][shotgun] do we still use subs?

Hello fuelers, My question is related to shotgun tool[1] which will be invoked in order to generate the diagnostic snapshot. It has possibilities to substitute particular sensitive data such as credentials/hostnames/IPs/etc with meaningless values. It's done by Subs [2] object driver. However, i

  1   2   >