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

On Tue, Sep 15, 2015 at 3:09 PM, Fox, Kevin M wrote: > DNS is preferable, since humans don't remember ip's very well. IPv6 is much > harder to remember then v4 too. > > DNS has its own issues, mostly, its usually not very quick to get a DNS entry > updated. At our site (and

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

On 09/15/2015 11:33 AM, Dougal Matthews wrote: > 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

[Openstack] Admin guide

Hi Friends, I wan to learn the each project detailed manner. please send me some links or pdf files admin guide in that doc complete info of openstack should be operated. like neutron,swift,cinder etc. Thank you, Venkatesh.k ___ Mailing list:

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

I am not a neutron developer, but an operator and a writer of cloud apps. Yes, it is sort of a philosophical issue, and I have stated my side of why I think the extra complexity is worth it. Feel free to disagree. But either way I don't think we can ignore the complexity. There are three

Re: [Openstack] To remove particular project

Don't remove Oslo. You don't even really need to remove cinderclient, but if it makes you feel better, that's OK. You'll probably also need to remove the endpoint and service from Keystone to avoid confusion later -Erik On Sep 15, 2015 8:55 PM, "venkatesh kotipalli"

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

Thanks Sumit. Actually I also did the same thing using --debug option with CLI to find the REST requests and responses. Thanks for the help . Will get back to you if required. Regards, Sagar On Sep 15, 2015 11:59 PM, "Sumit Naiksatam" wrote: > Hi Sagar, > > GBP has a

Re: [Openstack] To remove particular project

++ removing the endpoint and service from Keystone was my first thought as well. You could probably remove the package without the dependencies using 'rpm --nodeps' but I'd just stick to removing the service from the catalog via Keystone. Thanks, Steve Martinelli OpenStack Keystone Core

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

Hi Kevin, On 2015-09-15 8:33 PM, Fox, Kevin M wrote: > I am not a neutron developer, but an operator and a writer of cloud apps. So far, I'm only an operator and heavy cloud apps user (if you can call Vagrant an app). =) > Yes, it is sort of a philosophical issue, and I have stated my side >

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

On Tue, Sep 15, 2015 at 12:52:40PM -0400, Doug Hellmann wrote: > I've created the branches for oslo.utils and oslotest, as requested. > There are patches up for each to update the .gitreview file, which will > make it easier to land the patches to update whatever requirements > settings need to

[Openstack-operators] [ops-guide] Ops/Arch Guide specialty team meeting time

Hi everyone, Currently our weekly meeting is held on Thursday 1500 UTC, with fairly poor attendance. Here are some options to cater for different timezones: 1. Every Thursday 2130 UTC (to suit US and APAC timezones)2. Every Thursday at alternating times to cater for timezones - US: Thursday

Re: [Openstack-operators] User Survey - Deadline Sept 25th

Copy and Paste Error Strikes Again! The deadline is (as the subject says): ***September 25 at 23:59 UTC***. That is next Friday - get on it :) http://www.openstack.org/user-survey Regards, Tom On 16/09/15 11:40, Tom Fifield wrote: Hi all, If you run OpenStack, build apps on it, or have

Re: [Openstack-operators] [ops-guide] Ops/Arch Guide specialty team meeting time

Darren, Thanks for putting this together. I vote for Option 1 and 3. On Tue, Sep 15, 2015 at 11:21 PM, darren chan wrote: > Hi everyone, > > Currently our weekly meeting is held on Thursday 1500 UTC, with fairly > poor attendance. Here are some options to cater for

[openstack-dev] [horizon] PTL Candidacy

I would like to announce my candidacy for Horizon PTL for Mitaka. I've been contributing to Horizon since the Grizzly cycle and I've had the honor of serving as PTL for the past four cycles. Over the past couple of releases, our main goal has been to position Horizon for the future while

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

> > I'm currently trying to work around an issue where activating LVM > > snapshots created through cinder takes potentially a long time. [[ thick LVM snapshot performance problem ]] > > Given the above, is there any reason why we couldn't make thin > > provisioning the default? > > My intention

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

> On Sep 15, 2015, at 4:11 PM, Mathieu Gagné wrote: > >> On 2015-09-15 2:00 PM, 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. :/ >> >> I also strongly recommend to

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

Sean, Thank you very much for writing this, DVR indeed need to get more attention, it's a very cool and usefull feature, especially in large-scale. In Juno, it firstly lands to Neutron, through the development of Kilo and Liberty, it's getting better and better, we have used it in our

[Openstack-operators] User Survey - Deadline Sept 25th

Hi all, If you run OpenStack, build apps on it, or have customers with OpenStack deployments, please take a few minutes to respond to the latest User Survey or pass it along to your friends. Since 2013, the user survey has provided significant insight into what people are deploying and how

Re: [Openstack-operators] Tokyo Summit Ops Design Summit Tracks - Agenda Brainstorming

Last chance to provide your ideas for our design summit track. So far we are lacking: * Lightning talks * Working Groups * General Sessions Starting next week we're going to prepare the draft agenda for circulation and discussion. So, get in now. What would you like to discuss with fellow ops

Re: [Openstack] help openvswitch network configuration problems

Hi, In your screen shot I see the IP is still on eth2 port. When you add the eth2 to br-ex OVS bridge, you need to move the IP of eth2 to br-ex for the connectivity to work. Regards, Akash From: "applyhhj" To: "openstack" Date:

[openstack-dev] Barbican : Unable to run barbican CURL commands after starting/restarting barbican using the service file

Hi All, I am Unable to run barbican CURL commands after starting/restarting barbican using the service file. Used below command to run barbican service file : (wheel)[root@controller-01 service]# systemctl restart barbican-api.service When I tried executing the command to create the secret , I

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

Mike, We were enabled to do some great things under your leadership. Cinder has greatly benefited from your time as a PTL. Thanks for all you have done! Jay On 09/14/2015 11:15 AM, Mike Perez wrote: Hello all, I will not be running for Cinder PTL this next cycle. Each cycle I ran was for

[Openstack] User Survey - Deadline Sept 25th

Hi all, If you run OpenStack, build apps on it, or have customers with OpenStack deployments, please take a few minutes to respond to the latest User Survey or pass it along to your friends. Since 2013, the user survey has provided significant insight into what people are deploying and how

Re: [Openstack] User Survey - Deadline Sept 25th

Copy and Paste Error Strikes Again! The deadline is (as the subject says): ***September 25 at 23:59 UTC***. That is next Friday - get on it :) http://www.openstack.org/user-survey Regards, Tom On 16/09/15 11:40, Tom Fifield wrote: Hi all, If you run OpenStack, build apps on it, or have

Re: [Openstack] [Swift] Mount options with xfs - why nobarrier recommended?

On 16/09/15 06:54, Chris Friesen wrote: > On 09/15/2015 01:16 AM, Clay Gerrard wrote: >> Idk about a chestnut, but there's this: >> >> http://lists.openstack.org/pipermail/openstack-operators/2011-October/000297.html >> > > That advice isn't quite accurate. It says "Enabling barriers >

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

On 2015-09-15 18:00:03 + (+), 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. :/ Is this for a public servive provider? If so, do you expect your users to have some premonition which tells

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

On 09/15/2015 06:30 PM, Armando M. wrote: On 15 September 2015 at 08:04, Monty Taylor > wrote: Hey all! If any of you have ever gotten drunk with me, you'll know I hate floating IPs more than I hate being stabbed in the face with

Re: [Openstack] Admin guide

Those are available at docs.openstack.org Mike Smith Principal Engineer / Cloud Team Lead Overstock.com On Sep 15, 2015, at 5:19 PM, venkatesh kotipalli > wrote: Hi Friends, I

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

Yup. And Designate works very well. :) But DNSaaS is not always an option to "the powers that be" floating ip's are a much easier sell. Also Designate does have a restriction of wanting to manage a whole domain itself. When you have existing infrastructure you want your vms to merge into,

[openstack-dev] [searchlight] PTL Candidacy

Hello friends, We are now going into our first official PTL election for Searchlight and I would be honored if you’ll allow me to continue serving in the PTL role. Searchlight became a new project in Liberty after being split out from its initial experimental days in Glance. Since then we’ve

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

On 15 September 2015 at 16:01, Monty Taylor wrote: > On 09/15/2015 06:16 PM, Armando M. wrote: > >> >> >> On 15 September 2015 at 08:27, Mike Spreitzer > > wrote: >> >> Monty Taylor

[openstack-dev] [all][elections] Last hours for PTL candidate announcements

A quick reminder that we are in the last hours for PTL candidate announcements. If you want to stand for PTL, don't delay, follow the instructions on the wikipage and make sure we know your intentions: https://wiki.openstack.org/wiki/PTL_Elections_September_2015 Make sure your candidacy have

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

On 09/15/2015 06:16 PM, Armando M. wrote: 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

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

On 09/15/2015 08:28 PM, 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 satisfy the "you have more than one network" - the

[openstack-dev] [Neutron] PTL Candidacy

I would like to propose my candidacy for the Neutron PTL. If you are reading this and you know me, then you probably know what I have been up to up until now, what I have done for the project, and what I may continue to do. If you do not know me, and you are still interested in reading, then I

[Openstack] To remove particular project

Hi All, I have installed all the projects successfully. But now I would like to remove only one of the projects. (eg: cinder). May I have the procedure to remove only one project. I have tried from controll node to remove only a cinder project (yum remove openstack-cinder python-cinderclient

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

Let me rephrase that to be more explicit. Certain organizations, for various reasons, require people in the process chain to actually make dns changes... No amount of automation can easily address that issue. Hopefully that can change in time. But stuff as simple as letting users launch vm's

[openstack-dev] [Barbican] Providing service user read access to all tenant's certificates

Hi, Is there a way to provide read access to a certain user to all secrets/containers of all project/tenant's certificates? This user with universal "read" privilege's will be used as a service user by LBaaS plugin to read tenant's certificates during LB

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

On 15 September 2015 at 16:08, Monty Taylor wrote: > On 09/15/2015 06:30 PM, Armando M. wrote: > >> >> >> On 15 September 2015 at 08:04, Monty Taylor > > wrote: >> >> Hey all! >> >> If any of you have ever gotten

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

+1 From: Monty Taylor [mord...@inaugust.com] Sent: Tuesday, September 15, 2015 4:33 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [nova][neutron][devstack] New proposed 'default' network model On 09/15/2015 08:28 PM, Matt Riedemann

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

On 15 September 2015 at 14:04, Mike Spreitzer wrote: > "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: >

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

On 15 September 2015 at 15:11, Mathieu Gagné wrote: > On 2015-09-15 2:00 PM, 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. :/ > > > > I also strongly recommend to users to

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

Hi all, If I can attempt to summarize this thread: “We want simple networks with VMs” Ok, in progress, start here: https://blueprints.launchpad.net/neutron/+spec/get-me-a-network “It should work with multiple networks” Same

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

On 2015-09-15 7:44 PM, Armando M. wrote: > > > On 15 September 2015 at 15:11, Mathieu Gagné > wrote: > > On 2015-09-15 2:00 PM, Fox, Kevin M wrote: > > We run several clouds where there are multiple external networks. the > "just run

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

Sorry, didn’t mean that to come down as a triple pile-on, with me doing it twice. My bad, I’m sorry. Thanks, doug > On Sep 15, 2015, at 6:11 PM, Mathieu Gagné wrote: > > On 2015-09-15 8:06 PM, Doug Wiegley wrote: >> >> “Neutron doesn’t get it and never will.” >> >> I’m

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

On 09/16/2015 02:06 AM, Doug Wiegley wrote: Hi all, If I can attempt to summarize this thread: “We want simple networks with VMs” Ok, in progress, start here: https://blueprints.launchpad.net/neutron/+spec/get-me-a-network \o/ “It should work with multiple networks” Same spec, click

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

Monty, The architectural changes to the installation guide for Liberty [1] support booting VMs on both the public/external/provider and private/project/self-service networks. Also, we should consider including similar "hybrid" scenarios in the networking guide [2] so deployers don't have to

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

On 2015-09-15 6:49 PM, Doug Wiegley wrote: > > >> On Sep 15, 2015, at 4:11 PM, Mathieu Gagné wrote: >> >>> On 2015-09-15 2:00 PM, Fox, Kevin M wrote: >>> We run several clouds where there are multiple external networks. the "just >>> run it in on THE public network"

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

On 2015-09-15 8:06 PM, Doug Wiegley wrote: > > “Neutron doesn’t get it and never will.” > > I’m not sure how all ‘yes’ above keeps translating to this old saw, but > is there any tiny chance we can stop living in the past and instead > focus on the use cases that we want to solve? > I

Re: [Openstack] Admin guide

There are lots of great documentation at http://docs.openstack.org The Cloud Administrator Guide seems to be what you are looking for. Enjoy! Sent from my BlackBerry 10 smartphone. *From: *venkatesh kotipalli *Sent: *Wednesday, September 16, 2015 07:24 *To: *Openstack@lists.openstack.org

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

On 2015-09-15 2:00 PM, 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. :/ > > I also strongly recommend to users to put vms on a private network and use > floating ip's/load balancers. For many

Re: [openstack-dev] [Ceilometer] How to enable devstack plugins

On Tue, 15 Sep 2015, Zhai, Edwin wrote: I saw some patches from Chris Dent to enable functions in devstack/*. But it conflicts with devstack upstream so that start each ceilometer service twice. Is there any official way to setup ceilometer as devstack plugin? What I've been doing is

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

Thanks Mike! That was really demanding work! 2015-09-15 9:27 GMT+02:00 陈莹 : > Thanks Mike. Thank you for doing a great job. > > > > From: sxmatch1...@gmail.com > > Date: Tue, 15 Sep 2015 10:05:22 +0800 > > To: openstack-dev@lists.openstack.org > > Subject: Re:

Re: [openstack-dev] [tempest] Is there a sandbox project how to use tempest test plugin interface?

Am 14.09.2015 um 10:01 schrieb Lajos Katona : > Hi Matthew, > > Finally I made it working, so now I have a dummy plugin. > > Few questions, remarks: > - For me it was little hard to merge my weak knowledge from python packaging > with the documentation for tempest

Re: [Openstack] [Swift] Mount options with xfs - why nobarrier recommended?

Idk about a chestnut, but there's this: http://lists.openstack.org/pipermail/openstack-operators/2011-October/000297.html -Clay On Mon, Sep 14, 2015 at 10:18 PM, Chris Friesen wrote: > On 09/14/2015 08:59 PM, Mark Kirkwood wrote: > >> Hi, >> >> Sorry if this is a

[openstack-dev] [fuel] [plugin] Release tagging - possible problem

Hi John, To put a tag, you need to: - be a member of release group (that has Push Signed Tag rights) - and you are https://review.openstack.org/#/admin/groups/956,members - use gpg key using console gnupg - you might have missed this. -- Best regards, Irina

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

Kyle – I see a Good and a Sad things here, The Good one being, you lighted the path for new PTL to come up. The Sad thing is we are missing your leadership. Hope you still lead the team in dotted line. ☺ - Trinath From: Irena Berezovsky [mailto:irenab@gmail.com] Sent: Sunday, September

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

Thanks Mike. Thank you for doing a great job. > From: sxmatch1...@gmail.com > Date: Tue, 15 Sep 2015 10:05:22 +0800 > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [cinder] PTL Non-Candidacy > > Thanks Mike ! Your help is very important to me to get started in > cinder and

Re: [openstack-dev] [ironic] [tripleo] [kolla] Possible to support multiple compute drivers?

>I'm no Neutron expert, but I suspect that one could use either the LinuxBridge *or* the OVS ML2 mechanism driver for the L2 agent, along with a single flat provider network for your baremetal nodes. If it's a baremetal node, it wouldn't be running an agent at all, would it? On Mon, Sep 14, 2015

[OpenStack-Infra] vcsrepo upstream

Dear all, Actually openstack-infra/system-config is using the openstack-infra/puppet-vcsrepo module for handling git repositories. With Jeremy and Clark we found an issue related this vcsrepo module which is a fork of original puppetlabs-vcsrepo, but not follow the upstream. I made a little poc

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

Hi Sagar, GBP has a single REST API interface. The CLI, Horizon and Heat are merely clients of the same REST API. There was a similar question on this which I had responded to in a different mailer: http://lists.openstack.org/pipermail/openstack/2015-September/013952.html and I believe you are

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

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 satisfy the "you have more than one network" - the nics argument is > still useful for more

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

On Mon, Sep 14, 2015 at 2:46 PM, Sofer Athlan-Guyot wrote: > Morgan Fainberg writes: > > > On Mon, Sep 14, 2015 at 1:53 PM, Rich Megginson > > wrote: > > > > > > On 09/14/2015 02:30 PM, Sofer Athlan-Guyot wrote: > > > >

Re: [Openstack] [Swift] Mount options with xfs - why nobarrier recommended?

On 09/15/2015 01:16 AM, Clay Gerrard wrote: Idk about a chestnut, but there's this: http://lists.openstack.org/pipermail/openstack-operators/2011-October/000297.html That advice isn't quite accurate. It says "Enabling barriers effectively turns all writes into Write-Through operations, so

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

Hi Emilien, I don't think Murano team needs to be core on a Puppet module ether, current scheme was implemented per your proposal [1] and I am happy that we are ready to move Murano to the same scheme that is used with other projects. I've updated ACL for puppet-murano project:

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

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 me, you'll know I hate floating > > IPs more than I hate being stabbed in the face with a

[openstack-dev] [ironic] [tripleo] Deprecating the bash ramdisk

Hi all, We have a spec[0] for deprecating our bash ramdisk during Liberty, so we can remove it in Mitaka and have everything using IPA. The last patch remaining[1] is to mark it deprecated in disk-image-builder. This has been sitting with 4x +2 votes for 3 weeks or so now. Is there any reason we

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

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 alternative to the traditional image upload (the bytes are

Re: [openstack-dev] [openstack-ansible][compass] Support of Offline Install

Jesse, thanks for the information! I will look into this. The proxy server and local repo option might just work for us. On Tue, Sep 15, 2015 at 2:53 AM Jesse Pretorius wrote: > On 15 September 2015 at 05:36, Weidong Shao wrote: > >> Compass,

Re: [openstack-dev] [ironic] [tripleo] Deprecating the bash ramdisk

On Tue, Sep 15, 2015 at 1:05 PM, Jim Rollenhagen wrote: > Hi all, > > We have a spec[0] for deprecating our bash ramdisk during Liberty, so we > can remove it in Mitaka and have everything using IPA. > > The last patch remaining[1] is to mark it deprecated in >

Re: [OpenStack-Infra] vcsrepo upstream

On Tue, Sep 15, 2015 at 06:09:45PM +, Marton Kiss wrote: > Dear all, > > Actually openstack-infra/system-config is using the > openstack-infra/puppet-vcsrepo module for handling git repositories. > > With Jeremy and Clark we found an issue related this vcsrepo module which > is a fork of

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

Sounds like a useful idea if projects can plug-in themselves into the reloading process. I definitely think there needs to be a way for services to plug-in to this, although I'm not quite sure it will be sufficient at the current time though. An example of why: -

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

On Tue, Sep 15, 2015 at 9:04 AM, Derek Higgins wrote: > > > 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

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

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 data that differs between the original volume and the snapshot.) On one system I tested it took about one minute per 25GB of

[openstack-dev] [Solum] PTL Candidacy

Hi, I would like to announce my candidacy for the PTL position of Solum for Mitaka. In my view the challenges in front of us are twofold, which I have outlined below. I believe that I will be able to help us take concrete steps towards addressing these challenges in this cycle. Our first

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

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 data that differs between the > original volume and the snapshot.) On one system

Re: [Openstack-operators] [tags] ease of upgrade

Michal/Grzegorz/Will – Can you pls work with Dave to make sure all of the Liberty improvements are included? Dave: The Enterprise WG has been focused on rolling upgrades and developed tracker for our work from Kilo to Liberty to Mitaka. You can find the info here:

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

Most projects let you specify a name, and only force you to use a uuid IFF there is a conflict, leaving it up to the user to decide if they want the ease of use of names and being careful to name things, or having to use uuid's and not. Neutron also has the odd wrinkle in that if your a cloud

Re: [openstack-dev] [neutron][lbaas] Is SSL offload config possible using non "admin" tenant?

There is not really good documentation for this yet… When I say Neutron-LBaaS tenant, I am maybe using the wrong word — I guess the user that is configured as the service-account in neutron.conf. The user will hit the ACL API themselves to set up the ACLs on their own secrets/containers, we

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

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: [snip] The task upload process you're referring to is the one that uses the `import` task, which allows you to download an image

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

On 14/09/15 16:46 -0400, Doug Hellmann wrote: 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 from Flavio Percoco's message of 2015-09-14 14:41:00 +0200: > > On 14/09/15 08:10 -0400, Doug Hellmann

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

+1 On Mon, Sep 14, 2015 at 10:19 PM, Anastasia Urlapova wrote: > Folks, > I would like to nominate Denis Dmitriev[1] for fuel-qa/fuel-devops core. > > Dennis spent three months in Fuel BugFix team, his velocity was between > 150-200% per week. Thanks to his efforts we

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

> -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 > > Excerpts from Kuvaja, Erno's message of 2015-09-14 15:02:59 +: > > >

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

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

Re: [openstack-dev] [openstack-ansible][compass] Support of Offline Install

On 15 September 2015 at 05:36, Weidong Shao wrote: > Compass, an openstack deployment project, is in process of using osad > project in the openstack deployment. We need to support a use case where > there is no Internet connection. The way we handle this is to split the >

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

On Mon, Sep 14, 2015 at 09:34:31PM -0400, Jay Pipes wrote: > On 09/10/2015 05:23 PM, Brent Eagles wrote: > >Hi, > > > >I was recently informed of a situation that came up when an engineer > >added an SR-IOV nic to a compute node that was hosting some guests that > >had VFs attached. Unfortunately,

Re: [openstack-dev] [all] Base feature deprecation policy

Sean Dague wrote: > On 09/08/2015 03:32 PM, Doug Hellmann wrote: >> Excerpts from Sean Dague's message of 2015-09-08 14:11:48 -0400: >>> On 09/08/2015 01:07 PM, Doug Hellmann wrote: Excerpts from Dean Troyer's message of 2015-09-08 11:20:47 -0500: > On Tue, Sep 8, 2015 at 9:10 AM, Doug

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

On 14 September 2015 at 22:02, 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

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

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 support. Thanks for your great work during the current cycle. Christian. -- Christian Berendt Cloud

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

On 15/09/15 10:59, Ihar Hrachyshka wrote: >> On 11 Sep 2015, at 23:12, Kyle Mestery wrote: >> >> I'm writing to let everyone know that I do not plan to run for Neutron PTL >> for a fourth cycle. Being a PTL is a rewarding but difficult job, as Morgan >> recently put it in

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

On Thu, Sep 10, 2015 at 06:53:06PM -0230, Brent Eagles wrote: > Hi, > > I was recently informed of a situation that came up when an engineer > added an SR-IOV nic to a compute node that was hosting some guests that > had VFs attached. Unfortunately, adding the card shuffled the PCI > addresses

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

Rich Megginson writes: >>> This seems to be the hardest part - I still cannot figure out how to >>> use "compound" names with Puppet. >> I don't get this point. what is "2 or more resource could exists" and >> how it relates to compound names ? > > I would like to uniquely

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

> On 11 Sep 2015, at 23:12, Kyle Mestery wrote: > > I'm writing to let everyone know that I do not plan to run for Neutron PTL > for a fourth cycle. Being a PTL is a rewarding but difficult job, as Morgan > recently put it in his non-candidacy email [1]. But it goes

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

On 15/09/15 02:46 +0200, Monty Taylor wrote: On 09/15/2015 02:06 AM, Clint Byrum wrote: 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:

Re: [openstack-dev] [glance] tasks (following "proposed priorities for Mitaka")

On 14/09/15 16:09 -0400, Doug Hellmann wrote: Excerpts from Monty Taylor's message of 2015-09-14 20:41:38 +0200: On 09/14/2015 04:58 PM, Brian Rosmaita wrote: [snip] If "glance import-from http://example.com/my-image.qcow2' always worked, and in the back end generated a task with the task

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

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: 1. Introspection rules support. I'm working on it: https://review.openstack.org/#/c/223096/ This required a substantial requirement, so that our

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

This is a very interesting proposal and one I believe is needed. I¹m currently looking at hardening the controller nodes from unwanted access and discovered that every time the controller node is booted/rebooted, it flushes the iptables and writes only those rules that neutron believes should be

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

Excerpts from Sergey Lukjanov's message of 2015-09-15 18:12:23 +0300: > We're in a good shape with sahara client. 0.11.0 is the final minor release > for it. Constraints are up to date. Thanks, Sergey! We appreciate you and the rest of the Sahara team staying on track with the work needed for the

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

Hi all, One solution to this was a neutron spec that was added for a “get me a network” api, championed by Jay Pipes, which would auto-assign a public network on vm boot. It looks like it was resource starved in Liberty, though: https://blueprints.launchpad.net/neutron/+spec/get-me-a-network

Re: [openstack-dev] [Ironic] [Inspector] Finishing Liberty

On 09/15/2015 05:02 PM, Dmitry Tantsur wrote: 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: 1. Introspection rules support. I'm working on it: https://review.openstack.org/#/c/223096/ This

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

Excerpts from Renat Akhmerov's message of 2015-09-15 18:11:58 +0300: > > > On 15 Sep 2015, at 17:45, Doug Hellmann wrote: > > > > We would like for the schedule to be the same for everyone. We need the > > final versions for all libraries this week, so we can update > >

  1   2   >