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

On 09/14/2015 01:12 PM, Emilien Macchi wrote: > 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-20150915 > > Tomorrow we will make our Spri

Re: [openstack-dev] [Cinder]Behavior when one cinder-volume service is down

On Tue, Sep 15, 2015 at 8:53 AM, Eduard Matei < eduard.ma...@cloudfounders.com> wrote: > Hi, > > Let me see if i got this: > - running 3 (multiple) c-vols won't automatically give you failover > ​correct ​ > - each c-vol is "master" of a certain number of volumes > ​yes ​ > -- if the c-vol is

Re: [openstack-dev] [neutron][L3][QA] DVR job failure rate and maintainability

I couldn't have said it better, Sean. Ryan Moats "Sean M. Collins" wrote on 09/14/2015 05:01:03 PM: > From: "Sean M. Collins" > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 09/14/2015

[openstack-dev] [Policy][Group-based-policy]

Hello , We were exploring group based policy for some project.We could find CLI and REST API documentation for GBP. Do we have separate REST API for GBP which can be called separately ? >From documentation it seems that we can only use CLI , Horizon and Heat. Please point us to CLI or REST API

Re: [openstack-dev] [TripleO] Current meeting timeslot

On 10/09/15 15:12, Derek Higgins wrote: Hi All, The current meeting slot for TripleO is every second Tuesday @ 1900 UTC, since that time slot was chosen a lot of people have joined the team and others have moved on, I like to revisit the timeslot to see if we can accommodate more people at the

Re: [openstack-dev] [puppet] monasca,murano,mistral governance

Emilien, puppet-murano module have a bunch of patches from Alexey Deryugin on review [0], which implements most of all Murano deployment stuff. Murano project was added to OpenStack namespace not so long ago, that's why I suggest to have murano-core rights on puppet-murano as they are till all

Re: [openstack-dev] [nova][neutron][SR-IOV] Hardware changes and shifting PCI addresses

On 09/15/2015 02:25 AM, Daniel P. Berrange wrote: Taking a host offline for maintenance, should be considered equivalent to throwing away the existing host and deploying a new host. There should be zero state carry-over from OpenStack POV, since both the software and hardware changes can

Re: [openstack-dev] [glance] proposed priorities for Mitaka

On 09/15/2015 07:09 PM, stuart.mcla...@hp.com wrote: I've been looking into the existing task-based-upload that Doug mentions: can anyone clarify the following? On a default devstack install you can do this 'task' call: http://paste.openstack.org/show/462919 Yup. That's the one. as an

[openstack-dev] os-cloud-config support for custom .ssh configs

In bug https://bugzilla.redhat.com/show_bug.cgi?id=1252255 is about adding a possibility to have an .ssh directory that is not in ~/.ssh Currently the blocker there is os-cloud-config, that just calls ssh, and ssh will look in the users homedirectory for .ssh/config no matter what. To solve

Re: [openstack-dev] [nova][neutron][devstack] New proposed 'default' network model

We run several clouds where there are multiple external networks. the "just run it in on THE public network" doesn't work. :/ I also strongly recommend to users to put vms on a private network and use floating ip's/load balancers. For many reasons. Such as, if you don't, the ip that gets

Re: [openstack-dev] [Cinder]Behavior when one cinder-volume service is down

Of the two, pacemaker is far, far safer from a cinder PoV - fewer races, fewer problematic scenarios. On 15 September 2015 at 17:59, D'Angelo, Scott wrote: > Eduard, Gorka has done a great job of explaining some of the issues with > Active-Active Cinder-volume services in

Re: [openstack-dev] [Cinder]Behavior when one cinder-volume service is down

I’m just not sure that you can evacuate with the c-vol service for those volume down. Not without the un-safe HA active-active hacks. In our public cloud, if the c-vol service for a backend/volumes is down, we get woken up in the middle of the night and stay at it until we get c-vol back up.

Re: [openstack-dev] [nova][neutron][devstack] New proposed 'default' network model

That's exactly right, and we need to get this merged early in Mitaka. We'll discuss this in a design summit session in Tokyo in fact to ensure it's resourced correctly and continues to address the evolving needs in this space. On Tue, Sep 15, 2015 at 10:47 AM, Doug Wiegley

[openstack-dev] [TripleO] Remove Tuskar from tripleo-common and python-tripleoclient

Hi all, This is partly a heads up for everyone, but also seeking feedback on the direction. We are starting to move to a more general Heat workflow without the need for Tuskar. The CLI is already in a position to do this as we can successfully deploy without Tuskar. Moving forward it will be

Re: [openstack-dev] [oslo] Help with stable/juno branches / releases

Excerpts from Tony Breeds's message of 2015-08-27 08:32:01 +1000: > On Wed, Aug 26, 2015 at 03:11:56PM -0400, Doug Hellmann wrote: > > Tony, > > > > Thanks for digging into this! > > No problem. It seemed like such a simple thing :/ > > > I should be able to help, but right now we're ramping

Re: [openstack-dev] [Cinder]Behavior when one cinder-volume service is down

Hi, Let me see if i got this: - running 3 (multiple) c-vols won't automatically give you failover - each c-vol is "master" of a certain number of volumes -- if the c-vol is "down" then those volumes cannot be managed by another c-vol What i'm trying to achieve is making sure ANY volume is

Re: [openstack-dev] [Cinder]Behavior when one cinder-volume service is down

Eduard, Gorka has done a great job of explaining some of the issues with Active-Active Cinder-volume services in his blog: http://gorka.eguileor.com/ TL;DR: The hacks to use the same hostname or use Pacemaker + VIP are dangerous because of races, and are not recommended for Enterprise

Re: [openstack-dev] [openstack-ansible] Security hardening

Very interesting discussion. The Security project has a published security guide that I believe this would be very appropriate content for, the current guide (for reference) is here: http://docs.openstack.org/sec/ Contributions welcome, just like any other part of the OpenStack docs :) -Rob On

Re: [openstack-dev] [Cinder]Behavior when one cinder-volume service is down

Thanks Scott, But the question remains: if the "hacks" are not recommended then how can i perform Evacuate when the c-vol service of the volumes i need evacuated is "down", but there are two more controller node with c-vol services running? Thanks, Eduard

Re: [openstack-dev] [nova][neutron][devstack] New proposed 'default' network model

On 15 September 2015 at 08:27, Mike Spreitzer wrote: > Monty Taylor wrote on 09/15/2015 11:04:07 AM: > > > a) an update to python-novaclient to allow a named network to be passed > > to satisfy the "you have more than one network" - the nics argument

[openstack-dev] [nova] Liberty-RC1: Identification of release critical bugs (urgent)

We will enter the release candidates period by next week [1], which means we have to identify the bugs which will block us from creating a release candidate. The upcoming nova meeting on Thursday (09/17) will discuss those. The current plan is to release RC1 on next Tuesday (09/22). Everyone,

Re: [openstack-dev] [Fuel] fuel-createmirror "command not found"

Hi Adam, Can you provide a bit more details, e.g. specific error messages and logs? We have a fairly detailed checklist of things to look for when reporting bugs about Fuel: https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Test_and_report_bugs Did you check the bugs about

Re: [openstack-dev] [nova][neutron][devstack] New proposed 'default' network model

On 15 September 2015 at 11:28, Matt Riedemann wrote: > > > On 9/15/2015 10:27 AM, Mike Spreitzer wrote: > >> Monty Taylor wrote on 09/15/2015 11:04:07 AM: >> >> > a) an update to python-novaclient to allow a named network to be passed >> > to

Re: [openstack-dev] [nova][neutron][devstack] New proposed 'default' network model

"Fox, Kevin M" wrote on 09/15/2015 02:57:10 PM: > From: "Fox, Kevin M" > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 09/15/2015 02:59 PM > Subject: Re: [openstack-dev]

Re: [openstack-dev] [nova][neutron][devstack] New proposed 'default' network model

On 15 September 2015 at 10:02, Doug Hellmann wrote: > Excerpts from Armando M.'s message of 2015-09-15 09:30:35 -0700: > > On 15 September 2015 at 08:04, Monty Taylor > wrote: > > > > > Hey all! > > > > > > If any of you have ever gotten drunk with

Re: [openstack-dev] [cinder] LVM snapshot performance issue -- why isn't thin provisioning the default?

On Tue, Sep 15, 2015 at 11:38 AM, Eric Harney wrote: > On 09/15/2015 01:00 PM, Chris Friesen wrote: > > I'm currently trying to work around an issue where activating LVM > > snapshots created through cinder takes potentially a long time. > > (Linearly related to the amount of

Re: [openstack-dev] [nova][neutron][devstack] New proposed 'default' network model

"Fox, Kevin M" wrote on 09/15/2015 02:00:03 PM: > From: "Fox, Kevin M" > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 09/15/2015 02:02 PM > Subject: Re: [openstack-dev]

Re: [openstack-dev] [all][ptl][release] final liberty cycle client library releases needed

Hi Doug, And it would be good to lock in on glance_store (if it applies to this email) 0.9.1 too. (that's on pypi) On 9/14/15 9:26 AM, Kuvaja, Erno wrote: > Hi Doug, > > Please find python-glanceclient 1.0.1 release request > https://review.openstack.org/#/c/222716/ > > - Erno > >>

Re: [openstack-dev] [Ironic] [Inspector] Finishing Liberty (was: final liberty cycle client library releases needed)

2015-09-15 17:36 GMT+02:00 Doug Hellmann : > Excerpts from Dmitry Tantsur's message of 2015-09-15 17:02:52 +0200: > > Hi folks! > > > > As you can see below, we have to make the final release of > > python-ironic-inspector-client really soon. We have 2 big missing parts: >

[openstack-dev] [Congress] PTL candidacy

Hi all, I’m writing to announce my candidacy for Congress PTL for the Mitaka cycle. I’m excited at the prospect of continuing the development of our community, our code base, and our integrations with other projects. This past cycle has been exciting in that we saw several new, consistent

Re: [openstack-dev] [nova][neutron][devstack] New proposed 'default' network model

Thanks Kevin for your answer. My question was different. You mentioned in your email that you run several clouds. That's why I used the word "instance" in my question to refer to each of those clouds. So let me put the question in a different way: in the biggest cloud you run, how many total

Re: [openstack-dev] [oslo][oslo.config] Reloading configuration of service

Excerpts from mhorban's message of 2015-09-15 19:38:58 +0300: > Hi guys, > > I would like to talk about reloading config during reloading service. > Now we have ability to reload config of service with SIGHUP signal. > Right now SIGHUP causes just calling conf.reload_config_files(). > As result

Re: [openstack-dev] [nova][neutron][devstack] New proposed 'default' network model

I'm not quite sure how to read your question. I think it can be taken multiple ways. I'll guess at what you meant though. If I interpreted wrong, please ask again. For the instances that have floating ip's, usually either 1 or 2. One of our clouds has basically a public network directly on the

[openstack-dev] [TripleO] PTL candidacy

Hi TripleO, My name is Dan Prince and I'm running for the Mitaka TripleO PTL. I've been working on TripleO since Grizzly and OpenStack since Bexar. I care deeply about the project and would like to continue the vision of deploying OpenStack w/ OpenStack. TripleO has come a long way over the past

Re: [openstack-dev] [nova][neutron][devstack] New proposed 'default' network model

On Tue, Sep 15, 2015, at 11:00 AM, Fox, Kevin M wrote: > We run several clouds where there are multiple external networks. the > "just run it in on THE public network" doesn't work. :/ Maybe this would be better expressed as "just run it on an existing public network" then? > > I also strongly

Re: [openstack-dev] [nova][neutron][devstack] New proposed 'default' network model

On Tue, Sep 15, 2015 at 5:09 PM, Fox, Kevin M wrote: > Unfortunately, I haven't had enough chance to play with ipv6 yet. > > I still think ipv6 with floating ip's probably makes sense though. > > In ipv4, the floating ip's solve one particular problem: > > End Users want to

[openstack-dev] [all] New Gerrit translations change proposals from Zanata

Hi everyone, Daisy announced to the i18n team last week[0] that we've moved to using Zanata for translations for the Liberty cycle. Everyone should now be using Zanata at https://translate.openstack.org/ for translations. We're just now finishing up the infrastructure side of things with the

Re: [openstack-dev] [cinder] PTL Non-Candidacy

Thanks Mike, It was really a good experience working with you in kilo and liberty. Regards Nikesh On Tue, Sep 15, 2015 at 1:21 PM, Silvan Kaiser wrote: > Thanks Mike! > That was really demanding work! > > 2015-09-15 9:27 GMT+02:00 陈莹 : > >> Thanks

Re: [openstack-dev] [nova][neutron][devstack] New proposed 'default' network model

Ah. Instance of Cloud, not Nova Instance. Gotcha. The biggest currently has about 100 addresses on the public net and maybe about a quoter of those are allocated to instances. the shared private's about 200 and around a 30 or 40 are used. We have a lot of big vm's on that cloud for HPC like

[openstack-dev] [Mistral] Mistral PTL Candidacy

Hi, My name is Renat Akhmerov. I decided to run for Mistral PTL for Mitaka release cycle. This is the first time when I’m doing it officially after Mistral was accepted into Big Tent. In fact, I’ve been driving the project for just a little less than 2 years by now and I've put a lot of my

[openstack-dev] [fuel][fuel-library] modules managed with librarian round 2

Hello! So after our first round of librarian changes for 7.0, it is time to start switching to upstream for more changes. We've had a few updates during the fuel meetings over the last month[0][1]. I have begun to prepare additional reviews to move modules. The current modules available for

Re: [openstack-dev] [nova][neutron][devstack] New proposed 'default' network model

"Armando M." wrote on 09/15/2015 03:50:24 PM: > On 15 September 2015 at 10:02, Doug Hellmann wrote: > Excerpts from Armando M.'s message of 2015-09-15 09:30:35 -0700: ... > As with the Glance image upload API discussion, this is an example > of an

Re: [openstack-dev] [OpenStack-docs] [docs][ptl] Docs PTL Candidacy

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 15/09/15 20:06, Christian Berendt wrote: > On 09/14/2015 04:31 AM, Lana Brindley wrote: >> I'd love to have your support for the PTL role for Mitaka, and >> I'm looking forward to continuing to grow the documentation >> team. > > You have my

Re: [openstack-dev] [nova][neutron][devstack] New proposed 'default' network model

Clark Boylan wrote on 09/15/2015 04:06:26 PM: > > I also strongly recommend to users to put vms on a private network and > > use floating ip's/load balancers. For many reasons. Such as, if you > > don't, the ip that gets assigned to the vm helps it become a pet. you > >

Re: [openstack-dev] [Cinder] PTL Candidacy

Thanks Sean, Vote +1. On Tue, Sep 15, 2015 at 8:36 AM, hao wang wrote: > Thanks Sean, Vote +1. > > 2015-09-14 22:49 GMT+08:00 Sean McGinnis : > > Hello everyone, > > > > I'm announcing my candidacy for Cinder PTL for the Mitaka release. > > > > The

Re: [openstack-dev] [Cinder] PTL Candidacy

Voting is done by formal ballot just before the summit. All Cinder ATCs will be invited to vote. Voting on the mailing list is just noise. On 15 September 2015 at 23:40, Nikesh Kumar Mahalka < nikeshmaha...@vedams.com> wrote: > Thanks Sean, Vote +1. > > On Tue, Sep 15, 2015 at 8:36 AM, hao wang

Re: [openstack-dev] [cinder] LVM snapshot performance issue -- why isn't thin provisioning the default?

Hi Eric, Regarding the default max_over_subscription_ratio, I initially set the default to 1 while working on oversubscription, and changed it to 2 after getting review comments. After it was merged, I got feedback that 2 is too small and 20 is more appropriated, so I changed it to 20. So it

Re: [openstack-dev] [nova][neutron][devstack] New proposed 'default' network model

Unfortunately, I haven't had enough chance to play with ipv6 yet. I still think ipv6 with floating ip's probably makes sense though. In ipv4, the floating ip's solve one particular problem: End Users want to be able to consume a service provided by a VM. They have two options: 1. contact the

[openstack-dev] [Cinder]Behavior when one cinder-volume service is down

Hi, This all started when we were testing Evacuate with our storage driver. We thought we found a bug (https://bugs.launchpad.net/cinder/+bug/1491276) then Scott replied that we should be running cinder-volume service separate from nova-compute. For some internal reasons we can't do that - yet,

Re: [openstack-dev] [all][ptl][release] final liberty cycle client library releases needed

On 09/14/2015 04:18 PM, Doug Hellmann wrote: Excerpts from Doug Hellmann's message of 2015-09-14 08:46:02 -0400: PTLs and release liaisons, In order to keep the rest of our schedule for the end-of-cycle release tasks, we need to have final releases for all client libraries in the next day or

Re: [openstack-dev] [Cinder]Behavior when one cinder-volume service is down

> From: Eduard Matei [mailto:eduard.ma...@cloudfounders.com] > Sent: Tuesday, September 15, 2015 4:04 PM > > Hi, > > This all started when we were testing Evacuate with our storage driver. > We thought we found a bug > (https://bugs.launchpad.net/cinder/+bug/1491276) then Scott replied that > we

Re: [openstack-dev] [Fuel] Nominate Denis Dmitriev for fuel-qa(devops) core

+1 Regards, Tatyana On Tue, Sep 15, 2015 at 12:16 PM, Alexander Kostrikov < akostri...@mirantis.com> wrote: > +1 > > On Mon, Sep 14, 2015 at 10:19 PM, Anastasia Urlapova < > aurlap...@mirantis.com> wrote: > >> Folks, >> I would like to nominate Denis Dmitriev[1] for fuel-qa/fuel-devops core. >>

Re: [openstack-dev] [oslo][versionedobjects][ceilometer] explain the benefits of ceilometer+versionedobjects

On 03/09/2015 4:02 PM, Dan Smith wrote: - do we need to migrate the db to some handle different set of >attributes and what happens for nosql dbs? No, Nova made no schema changes as a result of moving to objects. so i don't really understand how this part works. if i have two collectors --

[openstack-dev] Ceilometer M Midcycle

Hello Everyone, We are setting up a few polls to determine the possibility of meeting face to face for a ceilometer midcycle in Dublin, IE. We'd like to gather for three days to discuss all the work we are currently doing; however, we have access to space for 5 so you could also use that

Re: [openstack-dev] [glance] proposed priorities for Mitaka

Excerpts from Kuvaja, Erno's message of 2015-09-15 09:43:26 +: > > -Original Message- > > From: Doug Hellmann [mailto:d...@doughellmann.com] > > Sent: Monday, September 14, 2015 5:40 PM > > To: openstack-dev > > Subject: Re: [openstack-dev] [glance] proposed priorities for Mitaka > >

Re: [openstack-dev] [glance] proposed priorities for Mitaka

Excerpts from Clint Byrum's message of 2015-09-14 17:06:44 -0700: > Excerpts from Doug Hellmann's message of 2015-09-14 13:46:16 -0700: > > Excerpts from Clint Byrum's message of 2015-09-14 13:25:43 -0700: > > > Excerpts from Doug Hellmann's message of 2015-09-14 12:51:24 -0700: > > > > Excerpts

Re: [openstack-dev] [openstack-ansible] PTL Non-Candidacy

On 09/14/2015 04:02 PM, Kevin Carter wrote: > TL;DR - I'm sending this out to announce that I won't be running for PTL of > the OpenStack-Ansible project in the upcoming cycle. Although I won't be > running for PTL, with community support, I intend to remain an active > contributor just with

Re: [openstack-dev] [TripleO] Current meeting timeslot

On 15/09/15 12:38, Derek Higgins wrote: On 10/09/15 15:12, Derek Higgins wrote: Hi All, The current meeting slot for TripleO is every second Tuesday @ 1900 UTC, since that time slot was chosen a lot of people have joined the team and others have moved on, I like to revisit the timeslot to

Re: [openstack-dev] [glance] proposed priorities for Mitaka

After having some conversations with folks at the Ops Midcycle a few weeks ago, and observing some of the more recent email threads related to glance, glance-store, the client, and the API, I spent last week contacting a few of you individually to learn more about some of the issues confronting

Re: [openstack-dev] [puppet] monasca,murano,mistral governance

On 09/15/2015 07:39 AM, Ivan Berezovskiy wrote: > Emilien, > > puppet-murano module have a bunch of patches from Alexey Deryugin on > review [0], which implements most of all Murano deployment stuff. > Murano project was added to OpenStack namespace not so long ago, that's > why I suggest to

[openstack-dev] [Neutron] PTL Candidacy

Hi everyone, I decided to run for the Neutron PTL position for the Mitaka release cycle. I have been contributing to Neutron since Havana and I am a member of the control plane core review team. During these years I have touched most parts of the Neutron code and in the last cycle my main focus

Re: [openstack-dev] [glance] proposed priorities for Mitaka

Excerpts from Flavio Percoco's message of 2015-09-15 10:54:04 +0200: > On 14/09/15 15:51 -0400, Doug Hellmann wrote: > >Excerpts from Flavio Percoco's message of 2015-09-14 14:41:00 +0200: > >> On 14/09/15 08:10 -0400, Doug Hellmann wrote: > > >> This is definitely unfortunate. I believe a good

Re: [openstack-dev] [Cinder]Behavior when one cinder-volume service is down

On Tue, Sep 15, 2015 at 8:04 AM, Eduard Matei < eduard.ma...@cloudfounders.com> wrote: > Hi, > > This all started when we were testing Evacuate with our storage driver. > We thought we found a bug (https://bugs.launchpad.net/cinder/+bug/1491276) > then Scott replied that we should be running

Re: [openstack-dev] [congress] IRC hangout

On 2015-09-14 17:44:14 + (+), Shiv Haris wrote: > What is the IRC channel where congress folks hangout. I tried > #openstack-congress on freenode but is seems not correct. https://wiki.openstack.org/wiki/IRC has it listed as #congress -- Jeremy Stanley

Re: [openstack-dev] [all][ptl][release] final liberty cycle client library releases needed

Excerpts from Dmitry Tantsur's message of 2015-09-15 16:16:00 +0200: > On 09/14/2015 04:18 PM, Doug Hellmann wrote: > > Excerpts from Doug Hellmann's message of 2015-09-14 08:46:02 -0400: > >> PTLs and release liaisons, > >> > >> In order to keep the rest of our schedule for the end-of-cycle

Re: [openstack-dev] [fuel] [plugin] Release tagging

On Mon, Sep 14, 2015 at 7:44 PM, John Griffith wrote: > > > On Mon, Sep 14, 2015 at 7:27 PM, Davanum Srinivas > wrote: > >> John, >> >> per ACL in project-config: >> >>

[openstack-dev] [all] [ptl] Troubleshooting cross-project communications

Hi all, What can we do to make the cross-project meeting more helpful and useful for cross-project communications? I started with a proposal to move it to a different time, which morphed into an idea to alternate times. But, knowing that we need to layer communications I wonder if we should

<    1   2