Re: [openstack-dev] [oslo] python 2.6 support for oslo libraries

On 10/22/2014 08:15 PM, Doug Hellmann wrote: > The application projects are dropping python 2.6 support during Kilo, and > I’ve had several people ask recently about what this means for Oslo. Because > we create libraries that will be used by stable versions of projects that > still need to run

Re: [openstack-dev] [oslo] proposed summit session topics

Looks good, sorry for missing the meeting! On 10/22/2014 09:11 PM, Doug Hellmann wrote: > > On Oct 20, 2014, at 1:22 PM, Doug Hellmann wrote: > >> After today’s meeting, we have filled our seven session slots. Here’s the >> proposed list, in no particular order. If you think something else nee

Re: [openstack-dev] [Nova] Cells conversation starter

> -Original Message- > From: Andrew Laski [mailto:andrew.la...@rackspace.com] > Sent: 22 October 2014 21:12 > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [Nova] Cells conversation starter > > > On 10/22/2014 12:52 AM, Michael Still wrote

Re: [openstack-dev] [cinder][nova] Are disk-intensive operations managed ... or not?

On Tue, Oct 21, 2014 at 9:17 AM, Duncan Thomas wrote: > For LVM-thin I believe it is already disabled? It is only really > needed on LVM-thick, where the returning zeros behaviour is not done. > > On 21 October 2014 08:29, Avishay Traeger wrote: > > I would say that wipe-on-delete is not necessa

Re: [openstack-dev] [devstack] Enable LVM ephemeral storage for Nova

On Tue, Oct 21, 2014 at 2:48 PM, Dan Genin wrote: > So then it is probably best to leave existing Cinder LVM code in > lib/cinder_backends/lvm alone and create a similar set of lvm scripts for > Nova, > perhaps in lib/nova_backends/lvm? > > Dan > > On 10/21/2014 03:10 PM, Duncan Thomas wrote: >

Re: [openstack-dev] [api] API Workgroup git repository

On Thu, 23 Oct 2014 05:53:21 + Shaunak Kashyap wrote: > Thanks Chris. And am I correct in assuming that no weekly api-wg > meetings are currently going on? I don’t see anything here anyway: > https://wiki.openstack.org/wiki/Meetings. > They haven't started yet. Not sure if we'll be squeezin

Re: [openstack-dev] Taking a break..

Thanks for all the help Chris and all the best. Now on the lookout for another cells core I can harass and pass obscure bugs too. It was always reassuring knowing you’d probably already come across the issue and could point me to a review or git branch with a fix. Cheers, Sam > On 23 Oct 2014

Re: [openstack-dev] [api] API Workgroup git repository

Thanks Chris. And am I correct in assuming that no weekly api-wg meetings are currently going on? I don’t see anything here anyway: https://wiki.openstack.org/wiki/Meetings. Shaunak On Oct 22, 2014, at 10:39 PM, Christopher Yeoh mailto:cbky...@gmail.com>> wrote: On Thu, Oct 23, 2014 at 3:51 P

Re: [openstack-dev] [api] API Workgroup git repository

On Thu, Oct 23, 2014 at 3:51 PM, Shaunak Kashyap < shaunak.kash...@rackspace.com> wrote: > If I have a proposal to make for a guideline, how do I do it? Do I simply > create a gerrit review for a file under > http://git.openstack.org/cgit/openstack/api-wg/tree/guidelines? > > Yes, either additions

Re: [openstack-dev] [api] API Workgroup git repository

If I have a proposal to make for a guideline, how do I do it? Do I simply create a gerrit review for a file under http://git.openstack.org/cgit/openstack/api-wg/tree/guidelines? Shaunak On Oct 22, 2014, at 3:34 PM, Christopher Yeoh wrote: > On Wed, 22 Oct 2014 20:36:27 + > Everett Toews

Re: [openstack-dev] Taking a break..

Thnx, everyone, for the nice comments. Replies to Dan below: On Oct 22, 2014, at 10:52 AM, Dan Smith wrote: >> I won’t have much time for OpenStack, but I’m going to continue to >> hang out in the channels. > > Nope, sorry, veto. I'm the only Core in this project, so I'm sorry: You do not have

Re: [openstack-dev] move deallocate port from after hypervisor driver does detach interface when doing detach_interface

? 2014?10?22? 23:18, Ben Nemec ??: Please don't send review requests to the list. The preferred methods of asking for reviews are discussed in this post: http://lists.openstack.org/pipermail/openstack-dev/2013-September/015264.html Thanks. -Ben hi Ben, thanks for letting me know this. and I'

Re: [openstack-dev] [Nova] Cells conversation starter

I suspect whether cell itself could ease large scale deployment across multiple DC. Although openstack is modularized as separated projects, but top level total solution across projects is needed when considering issues such as scaling, especially coordination between nova and network / metering.

Re: [openstack-dev] [DevStack] Proposal - add support for Markdown for docs

On 2014-10-21 17:00:09 + (+), Jeremy Stanley wrote: > Well, actually that's still in progress. The last bit we need is to > host a redirect somewhere so that devstack.org/(.*) is 301'd to > docs.openstack.org/developer/devstack/$1 instead, and then we change > the DNS address records to poi

[openstack-dev] [Heat] kilo design sessions

Hi all, We prioritized the session in our weekly meeting and I have now pushed them to http://kilodesignsummit.sched.org/overview/type/heat . Let me know if the scheduling works for you. Regards -Angus ___ OpenStack-dev mailing list OpenStack-dev@lists

Re: [openstack-dev] [Nova] Cells conversation starter

> On 23 Oct 2014, at 5:55 am, Andrew Laski wrote: > >> While I agree that N is a bit interesting, I have seen N=3 in production >> >> [central API]-->[state/region1]-->[state/region DC1] >>\->[state/region DC2] >> -->[state/region2 DC] >>

[openstack-dev] [congress] kilo design session

We are scheduled for Monday, 03 Nov, 14:30 - 16:00. I have a conflict with the “Meet the Influencers” talk that runs from 14:30-18:30, plus the GBP session is on Tuesday, 04 Nov, 12:05-12:45. I was thinking we would want to co-located the Congress and GBP talks as much as possible. The BOSH tea

[openstack-dev] [Neutron][LBaaS] Paris Summit talking points

Let's get a list of questions / talking points set up on this etherpad: https://etherpad.openstack.org/p/paris_absentee_talking_points If you can't make it to the summit (like me) then you can put any questions or concerns you have in this document. If you are going to the summit, please take a

Re: [openstack-dev] [openstack][keystone] why is lxml only in test-requirements.txt?

Great question! For some backstory, the community interest in supporting XML has always been lackluster, so the XML translation middleware has been on a slow road of decline. It's a burden for everyone to maintain, and only works for certain API calls. For the bulk of Keystone's documented APIs, X

Re: [openstack-dev] [api] API Workgroup git repository

On Wed, 22 Oct 2014 20:36:27 + Everett Toews wrote: > I notice at the top of the GitHub mirror page [1] it reads, "API > Working Group http://openstack.org” > > Can we get that changed to "API Working Group > https://wiki.openstack.org/wiki/API_Working_Group”? > > That URL would be much mor

Re: [openstack-dev] [api] API Workgroup git repository

On Wed, 22 Oct 2014 14:44:26 -0500 Anne Gentle wrote: > On Wed, Oct 22, 2014 at 2:26 PM, Steve Martinelli > wrote: > > > we could set up a job to publish under docs.o.org/api-wg pretty > > easily - it seems like a good place to start to publish this > > content. > > > > thanks for getting the r

Re: [openstack-dev] [NFV] NFV BoF session for OpenStack Summit Paris

- Original Message - > From: "Steve Gordon" > To: "OpenStack Development Mailing List (not for usage questions)" > > > - Original Message - > > From: "Steve Gordon" > > To: "OpenStack Development Mailing List (not for usage questions)" > > > > > > Hi all, > > > > I took an

[openstack-dev] [Nova] Scheduler / Resource Tracker designated core

Hello. Its clear that the scheduler and resource tracker inside Nova are areas where we need to innovate. There are a lot of proposals in this space at the moment, and it can be hard to tell which ones are being implemented and in which order. I have therefore asked Jay Pipes to act as "designate

Re: [openstack-dev] [oslo] proposed summit session topics

+1 from me as well. -- dims On Wed, Oct 22, 2014 at 5:05 PM, Ben Nemec wrote: > +1 to the proposed schedule from me. > > On 10/22/2014 02:11 PM, Doug Hellmann wrote: >> >> On Oct 20, 2014, at 1:22 PM, Doug Hellmann wrote: >> >>> After today’s meeting, we have filled our seven session slots. Her

Re: [openstack-dev] [oslo] proposed summit session topics

+1 to the proposed schedule from me. On 10/22/2014 02:11 PM, Doug Hellmann wrote: > > On Oct 20, 2014, at 1:22 PM, Doug Hellmann wrote: > >> After today’s meeting, we have filled our seven session slots. Here’s the >> proposed list, in no particular order. If you think something else needs to

Re: [openstack-dev] [api] API Workgroup git repository

Everett, I think the description is managed by this file: https://github.com/openstack-infra/project-config/blob/master/gerrit/projects.yaml - Steve From: Everett Toews To: "OpenStack Development Mailing List (not for usage questions)" , Date: 10/22/2014 04:40 PM Subject:Re:

Re: [openstack-dev] [api] API Workgroup git repository

It is a code change :) Everything is a code change around here. You will want to update the projects.yaml file in openstack-infra/project-config [0]. If you add a 'homepage: https://wiki.openstack.org/wiki/API_Working_Group' key value pair to the api-wg dict there the jeepyb tooling should update t

Re: [openstack-dev] [api] API Workgroup git repository

I notice at the top of the GitHub mirror page [1] it reads, "API Working Group http://openstack.org” Can we get that changed to "API Working Group https://wiki.openstack.org/wiki/API_Working_Group”? That URL would be much more helpful to people who come across the GitHub repo. It's not a code

[openstack-dev] [Neutron][L3][IPAM] No Team Meeting Thursday

I just had a conflict come up. I won't be able to make it to the meeting. I wanted to announce that IPAM is very likely topic for a design session at the summit. I will spend some time reviewing the old etherpads starting here [1] since the topic was set aside early in Juno. Carl [1] https://e

Re: [openstack-dev] [Nova] Automatic evacuate

- Original Message - > On 10/21/2014 07:53 PM, David Vossel wrote: > > > > - Original Message - > >>> -Original Message- > >>> From: Russell Bryant [mailto:rbry...@redhat.com] > >>> Sent: October 21, 2014 15:07 > >>> To: openstack-dev@lists.openstack.org > >>> Subject: Re:

Re: [openstack-dev] [api] API Workgroup git repository

On Wed, Oct 22, 2014 at 2:26 PM, Steve Martinelli wrote: > we could set up a job to publish under docs.o.org/api-wg pretty easily - > it seems like a good place to start to publish this content. > > thanks for getting the repo all setup chris and jay. > > Thanks for setting up the repo. We proba

Re: [openstack-dev] [Neutron][LBaaS][Octavia] Usage Requirements

Hi Jorge, Good discussion so far + glad to have you back :) I am not a big fan of using logs for billing information since ultimately (at least at HP) we need to pump it into ceilometer. So I am envisioning either the amphora (via a proxy) to pump it straight into that system or we collect it o

Re: [openstack-dev] [api] API Workgroup git repository

we could set up a job to publish under docs.o.org/api-wg pretty easily - it seems like a good place to start to publish this content. thanks for getting the repo all setup chris and jay. Thanks, _ Steve Martinelli OpenStack Development - Keystone Cor

Re: [openstack-dev] [api] API Workgroup git repository

Hi Chris On 10/21/2014 11:08 PM, Christopher Yeoh wrote: > The API Workgroup git repository has been setup and you can access it > here. Cool, adding it to the repos to watch. > There is some content there though not all the proposed guidelines from > the wiki page are in yet: > > https://wiki.op

Re: [openstack-dev] [Nova] Cells conversation starter

On 10/22/2014 12:52 AM, Michael Still wrote: Thanks for this. It would be interesting to see how much of this work you think is achievable in Kilo. How long do you see this process taking? In line with that, is it just you currently working on this? Would calling for volunteers to help be meani

Re: [openstack-dev] [oslo] proposed summit session topics

On Oct 20, 2014, at 1:22 PM, Doug Hellmann wrote: > After today’s meeting, we have filled our seven session slots. Here’s the > proposed list, in no particular order. If you think something else needs to > be on the list, speak up today because I’ll be plugging all of this into the > scheduli

Re: [openstack-dev] [neutron] [nfv] VM-based VLAN trunking blueprints

I suppose this BP also has some relevance to such a discussion. https://review.openstack.org/#/c/100278/ / Bob On 2014-10-22 15:42, "Kyle Mestery" wrote: >There are currently at least two BPs registered for VLAN trunk support >to VMs in neutron-specs [1] [2]. This is clearly something that I'

Re: [openstack-dev] [Fuel] Backup of information about nodes.

What is current best practice to restore a failed Fuel node? *Adam Lawson* AQORN, Inc. 427 North Tatnall Street Ste. 58461 Wilmington, Delaware 19801-2230 Toll-free: (844) 4-AQORN-NOW ext. 101 International: +1 302-387-4660 Direct: +1 916-246-2072 On Wed, Oct 22, 2014 at 10:40 AM, Sergii Golov

Re: [openstack-dev] [Nova] Cells conversation starter

On 10/22/2014 03:42 AM, Vineet Menon wrote: On 22 October 2014 06:24, Tom Fifield > wrote: On 22/10/14 03:07, Andrew Laski wrote: > > On 10/21/2014 04:31 AM, Nikola Đipanov wrote: >> On 10/20/2014 08:00 PM, Andrew Laski wrote: >>> One of the big

Re: [openstack-dev] [Nova] Cells conversation starter

On 10/22/2014 12:24 AM, Tom Fifield wrote: On 22/10/14 03:07, Andrew Laski wrote: On 10/21/2014 04:31 AM, Nikola Đipanov wrote: On 10/20/2014 08:00 PM, Andrew Laski wrote: One of the big goals for the Kilo cycle by users and developers of the cells functionality within Nova is to get it to a

Re: [openstack-dev] Taking a break..

Chris, Thanks for your work on cells in OpenStack nova... we're heavily exploiting it to scale out the CERN cloud. Tim > -Original Message- > From: Chris Behrens [mailto:cbehr...@codestud.com] > Sent: 22 October 2014 19:37 > To: OpenStack Development Mailing List (not for usage questio

[openstack-dev] [sahara] team meeting Oct 23 1800 UTC

Hi folks, We'll be having the Sahara team meeting as usual in #openstack-meeting-alt channel. Agenda: https://wiki.openstack.org/wiki/Meetings/SaharaAgenda#Next_meetings http://www.timeanddate.com/worldclock/fixedtime.html?msg=Sahara+Meeting&iso=20141023T18 P.S. The main topic is finalisation o

[openstack-dev] [Manila] command execution refactor plan

Hi, I have these concerns regarding command execution in Manila. I was to propose these to be discussed at the Design Summit. It might be too late for that. Then we can discuss it here -- or at the summit, just informally. Thanks for Valeriy for his ideas about some of the topics below. Driver

[openstack-dev] [oslo] python 2.6 support for oslo libraries

The application projects are dropping python 2.6 support during Kilo, and I’ve had several people ask recently about what this means for Oslo. Because we create libraries that will be used by stable versions of projects that still need to run on 2.6, we are going to need to maintain support for

[openstack-dev] [MagnetoDB] PTL Elections

Hi folks, due to the requirement to have PTL for the program, we're running elections for the MagnetoDB PTL for Kilo cycle. Schedule and policies are fully aligned with official OpenStack PTLs elections. You can find more info in official elections wiki page [0] and the same page for MagnetoDB el

Re: [openstack-dev] Adding new dependencies to stackforge projects

On 2014-10-22 12:31:53 -0400 (-0400), Davanum Srinivas wrote: > fyi, latest update after discussion on #openstack-infra, consensus > seems to be to allow projects to add to g-r. [...] If that's deemed unacceptable for other reasons, the alternative solution which was floated is to tweak setup_pack

Re: [openstack-dev] Taking a break..

Chris, It was great to work with you, best of luck and enjoy this new opportunity. Cheers, Lucas On Wed, Oct 22, 2014 at 6:50 PM, Morgan Fainberg wrote: > Chris, > > Best of luck on the new adventure! Definitely don’t be a stranger! > > Cheers, > Morgan > >> On Oct 22, 2014, at 10:37, Chris Beh

Re: [openstack-dev] Taking a break..

> I won’t have much time for OpenStack, but I’m going to continue to > hang out in the channels. Nope, sorry, veto. Some options to explain your way out: 1. Oops, I forgot it wasn't April 2. I have a sick sense of humor; I'm getting help for it 3. I've come to my senses after a brief break from

Re: [openstack-dev] Taking a break..

Chris, All the best to you on you new adventure. Chris Krelle NobodyCam On Wed, Oct 22, 2014 at 10:37 AM, Chris Behrens wrote: > Hey all, > > Just wanted to drop a quick note to say that I decided to leave Rackspace > to pursue another opportunity. My last day was last Friday. I won’t have > m

Re: [openstack-dev] Taking a break..

Chris, Best of luck on the new adventure! Definitely don’t be a stranger! Cheers, Morgan > On Oct 22, 2014, at 10:37, Chris Behrens wrote: > > Hey all, > > Just wanted to drop a quick note to say that I decided to leave Rackspace to > pursue another opportunity. My last day was last Friday.

Re: [openstack-dev] Taking a break..

Chris, All the best on your next adventure - you'll be missed here! -Deva On Wed, Oct 22, 2014 at 10:37 AM, Chris Behrens wrote: > Hey all, > > Just wanted to drop a quick note to say that I decided to leave Rackspace to > pursue another opportunity. My last day was last Friday. I won’t have m

Re: [openstack-dev] [nova] Pulling nova/virt/hardware.py into nova/objects/

On 10/21/2014 04:51 PM, Dan Smith wrote: The rationale behind two parallel data model hiercharies is that the format the virt drivers report data in, is not likely to be exactly the same as the format that the resoure tracker / scheduler wishes to use in the database. Yeah, and in cases where w

Re: [openstack-dev] [nova] Pulling nova/virt/hardware.py into nova/objects/

On 10/21/2014 05:44 AM, Nikola Đipanov wrote: On 10/20/2014 07:38 PM, Jay Pipes wrote: Hi Dan, Dan, Nikola, all Nova devs, OK, so in reviewing Dan B's patch series that refactors the virt driver's get_available_resource() method [1], I am stuck between two concerns. I like (love even) much of t

Re: [openstack-dev] [Fuel] Backup of information about nodes.

Hi Andrew, Thank you for sharing your ideas. We have similar blueprint where you should be able to save/restore information about your environment https://blueprints.launchpad.net/fuel/+spec/save-and-restore-env-settings For development, it's very useful when you need to create the identical env

[openstack-dev] Taking a break..

Hey all, Just wanted to drop a quick note to say that I decided to leave Rackspace to pursue another opportunity. My last day was last Friday. I won’t have much time for OpenStack, but I’m going to continue to hang out in the channels. Having been involved in the project since day 1, I’m going

Re: [openstack-dev] Time to Samba! :-)

Just for the record, they are watching us!:-O https://aws.amazon.com/blogs/aws/new-aws-directory-service/ Best! Thiago On 16 August 2014 16:03, Martinx - ジェームズ wrote: > Hey Stackers, > > I'm wondering here... Samba4 is pretty solid (up coming 4.2 rocks), I'm > using it on a daily basis as

Re: [openstack-dev] Adding new dependencies to stackforge projects

fyi, latest update after discussion on #openstack-infra, consensus seems to be to allow projects to add to g-r. 131+ All OpenStack projects, regardless of status, may add entries to 132+ ``global-requirements.txt`` for dependencies if the project is going 133+ to run integration tests under a devs

[openstack-dev] [MagnetoDB][api] Monitoring API

Hello Stackers, Here is a first blueprint to discuss for Kilo. I would like to start discussing related to monitoring API in MagnetoDB. I've written Blueprint[1] about this. The goal of this is to create a API for exposing usage statistic for users, external monitoring or billing tools. Pleas

Re: [openstack-dev] [NFV] Meeting minutes and summary for 2014-10-22

On 22 October 2014 16:34, Steve Gordon wrote: > Thanks to those who attended the meeting today, for those who missed in > minutes and the full log are available at these locations: > Apologies for absence. Here is an update from me: We are currently developing the Snabb mechanism driver out-of-

Re: [openstack-dev] [gantt] Scheduler group meeting - cancelled this week INTERNAL

The regular meeting time is Tuesdays at 15:00 UTC/11am EST: https://wiki.openstack.org/wiki/Meetings#Gantt_.28Scheduler.29_team_meeting Generally, we don't do slides for design summit sessions -- we use etherpads instead and the sessions are discussions, not presentations. Next week's meeting

[openstack-dev] [Fuel] Backup of information about nodes.

Hi, everyone. For one project we need to have backup of info about nodes (astute.yaml). In case the Fuel and a Node-n is down. How a bad idea to keep a copy of the astute.yaml file of each node to each node of the cluster? For example: pod_state/node-1.yaml pod_state/node-2.yaml pod_state/node-3.

Re: [openstack-dev] [gantt] Scheduler group meeting - cancelled this week INTERNAL

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/22/2014 10:54 AM, Elzur, Uri wrote: > Will there be a meeting next week? What is the regular time slot for the > meeting? Tuesdays at 1500 UTC in IRC channel: #openstack-meeting https://wiki.openstack.org/wiki/Meetings#Gantt_.28Scheduler.29_tea

Re: [openstack-dev] [kolla] making Daneyon Hansen core

On Wed, Oct 22, 2014 at 08:04:24AM -0700, Steven Dake wrote: > A few weeks ago in IRC we discussed the criteria for joining the core team > in Kolla. I believe Daneyon has met all of these requirements by reviewing > patches along with the rest of the core team and providing valuable > comments, a

Re: [openstack-dev] [gantt] Scheduler group meeting - cancelled this week INTERNAL

Don Will there be a meeting next week? What is the regular time slot for the meeting? I'd like to work w you on a technical slide to use in Paris Do we need to socialize the Gantt topic more? Thx Uri ("Oo-Ree") C: 949-378-7568 From: Dugger, Donald D [mailto:donald.d.dug...@intel.com] Sent: W

Re: [openstack-dev] [Glance][Cinder] The sorry state of cinder's driver in Glance

On 2014-10-22 10:05 AM, John Griffith wrote: Ideas started spreading from there to "Using a Read Only Cinder Volume per image", to "A Glance owned Cinder Volume" that would behave pretty much the current local disk/file-system model (Create a Cinder Volume for Glance, attach it to the Glance Ser

Re: [openstack-dev] [Ironic] disambiguating the term "discovery"

On Tue, Oct 21, 2014 at 6:29 PM, Stuart Fox wrote: > Having written/worked on a few DC automation tools, Ive typically broken > down the process of getting unknown hardware into production in to 4 > distinct stages. > 1) Discovery (The discovery of unknown hardware) > 2) Normalising (Push initial

Re: [openstack-dev] [kolla] making Daneyon Hansen core

Great work Daneyon! Excellent job with neutron and nova-networking! +1 -Ryan - Original Message - From: "Steven Dake" To: "OpenStack Development Mailing List" Sent: Wednesday, October 22, 2014 11:04:24 AM Subject: [openstack-dev] [kolla] making Daneyon Hansen core A few weeks ago in I

Re: [openstack-dev] [all] periodic jobs for master

On 10/22/2014 06:07 AM, Thierry Carrez wrote: Ihar Hrachyshka wrote: [...] For stable branches, we have so called periodic jobs that are triggered once in a while against the current code in a stable branch, and report to openstack-stable-maint@ mailing list. An example of failing periodic job r

Re: [openstack-dev] move deallocate port from after hypervisor driver does detach interface when doing detach_interface

Please don't send review requests to the list. The preferred methods of asking for reviews are discussed in this post: http://lists.openstack.org/pipermail/openstack-dev/2013-September/015264.html Thanks. -Ben On 10/22/2014 02:57 AM, Eli Qiao wrote: > > hi all. > when I am reviewing code of in

Re: [openstack-dev] [TripleO] Removing nova-bm support within os-cloud-config

On 10/20/2014 10:00 PM, Steve Kowalik wrote: > With the move to removing nova-baremetal, I'm concerned that portions > of os-cloud-config will break once python-novaclient has released with > the bits of the nova-baremetal gone -- import errors, and such like. > > I'm also concerned about backward

Re: [openstack-dev] [DevStack] Proposal - add support for Markdown for docs

With some xargs, sed, and pandoc - I now present to you the first attempt at converting the DevStack docs to RST, and making the doc build look similar to other projects. https://review.openstack.org/130241 It is extremely rough, I basically ran everything through Pandoc and cleaned up any errors

[openstack-dev] [kolla] making Daneyon Hansen core

A few weeks ago in IRC we discussed the criteria for joining the core team in Kolla. I believe Daneyon has met all of these requirements by reviewing patches along with the rest of the core team and providing valuable comments, as well as implementing neutron and helping get nova-networking im

Re: [openstack-dev] [neutron] [nfv] VM-based VLAN trunking blueprints

Hi, Great that we can have more focus on this. I'll attend the meeting on Monday and also attend the summit, looking forward to these discussions. Thanks, Erik -Original Message- From: Steve Gordon [mailto:sgor...@redhat.com] Sent: den 22 oktober 2014 16:29 To: OpenStack Development

[openstack-dev] [kolla][tripleo][nova][glance][keystone] announce of Kolla Milestone #1

The Kolla development community would like to announce the release of Kolla Milestone #1. This milestone constitutes two weeks of effort by the developers and is available for immediate download from https://github.com/stackforge/kolla/archive/version-m1.tar.gz. Kolla is a project to containe

Re: [openstack-dev] [Glance][Cinder] The sorry state of cinder's driver in Glance

Replied in inline. On Wed, Oct 22, 2014 at 9:33 PM, Flavio Percoco wrote: > On 10/22/2014 02:30 PM, Zhi Yan Liu wrote: >> Greetings, >> >> On Wed, Oct 22, 2014 at 4:56 PM, Flavio Percoco wrote: >>> Greetings, >>> >>> Back in Havana a, partially-implemented[0][1], Cinder driver was merged >>> in

Re: [openstack-dev] [gantt] Scheduler group meeting - cancelled this week

On Oct 22, 2014, at 8:21 AM, Dugger, Donald D wrote: > Sigh. I've progressed from being challenged by time of day (e.g. timezone) > to being challenged by day of week. Pretty soon I'll be confused about the > year :-) > > Sorry about that. Heh, no worries – I've had a lot worse days! -- E

[openstack-dev] [QA] Meeting Thursday October 23rd at 17:00 UTC

Hi Everyone, Just a quick reminder that the weekly OpenStack QA team IRC meeting will be this Thursday, October 23rd at 17:00 UTC in the #openstack-meeting channel. The agenda for tomorrow's meeting can be found here: https://wiki.openstack.org/wiki/Meetings/QATeamMeeting Anyone is welcome to add

[openstack-dev] [NFV] Meeting minutes and summary for 2014-10-22

Hi all, Thanks to those who attended the meeting today, for those who missed in minutes and the full log are available at these locations: * Meeting ended Wed Oct 22 14:25:30 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) * Minutes: http://eavesdrop.o

Re: [openstack-dev] [neutron] [nfv] VM-based VLAN trunking blueprints

- Original Message - > From: "Kyle Mestery" > To: "OpenStack Development Mailing List (not for usage questions)" > > > There are currently at least two BPs registered for VLAN trunk support > to VMs in neutron-specs [1] [2]. This is clearly something that I'd > like to see us land in Ki

Re: [openstack-dev] [neutron] [nfv] VM-based VLAN trunking blueprints

Kyle, I pointed out the similarity of the two specifications while reviewing them a few months ago (see patch set #4). Ian then approached me on IRC (I'm afraid it's going to be a bit difficult to retrieve those logs), and pointed out that actually the two specifications, in his opinion, try to ad

[openstack-dev] [all] Liaisons for Vulnerability Management Team

Hi everyone, TL;DR: Update https://wiki.openstack.org/wiki/CrossProjectLiaisons#Vulnerability_management Longer version: In the same spirit as the Oslo Liaisons, we are introducing in the Kilo cycle liaisons for the Vulnerability Management Team. Historically we've been trying to rely on a grou

Re: [openstack-dev] [Glance][Cinder] The sorry state of cinder's driver in Glance

On Wed, Oct 22, 2014 at 7:33 AM, Flavio Percoco wrote: > On 10/22/2014 02:30 PM, Zhi Yan Liu wrote: > > Greetings, > > > > On Wed, Oct 22, 2014 at 4:56 PM, Flavio Percoco > wrote: > >> Greetings, > >> > >> Back in Havana a, partially-implemented[0][1], Cinder driver was merged > >> in Glance to

Re: [openstack-dev] [NFV] Meeting today ? 22nd October

- Original Message - > From: "ITAI MENDELSOHN (ITAI)" > To: "OpenStack Development Mailing List (not for usage questions)" > > > Hi all, > > Do we have a meeting today? > I can't see something in the wiki about today... > > Itai Hi Itai, Apologies, yes we do! -Steve > Sent from my

Re: [openstack-dev] [neutron] HA of dhcp agents?

Hi Noel, On 22 October 2014 01:57, Noel Burton-Krahn wrote: > Hi Armando, > > Sort of... but what happens when the second one dies? > You mean, you lost both (all) agents? In this case, yes you'd need to resurrect the agents or move the networks to another available agent. > If one DHCP agent

Re: [openstack-dev] [neutron][stable] metadata agent performance

On Oct 22, 2014, at 12:53 AM, Jakub Libosvar wrote: > On 10/22/2014 02:26 AM, Maru Newby wrote: >> We merged caching support for the metadata agent in juno, and backported to >> icehouse. It was enabled by default in juno, but disabled by default in >> icehouse to satisfy the stable maint requ

Re: [openstack-dev] [Neutron][LBaaS][Octavia] Usage Requirements

Hey Stephen (and Robert), For real-time usage I was thinking something similar to what you are proposing. Using logs for this would be overkill IMO so your suggestions were what I was thinking of starting with. As far as storing logs is concerned I was definitely thinking of offloading these o

[openstack-dev] [neutron] [nfv] VM-based VLAN trunking blueprints

There are currently at least two BPs registered for VLAN trunk support to VMs in neutron-specs [1] [2]. This is clearly something that I'd like to see us land in Kilo, as it enables a bunch of things for the NFV use cases. I'm going to propose that we talk about this at an upcoming Neutron meeting

Re: [openstack-dev] [Glance][Cinder] The sorry state of cinder's driver in Glance

On 10/22/2014 02:30 PM, Zhi Yan Liu wrote: > Greetings, > > On Wed, Oct 22, 2014 at 4:56 PM, Flavio Percoco wrote: >> Greetings, >> >> Back in Havana a, partially-implemented[0][1], Cinder driver was merged >> in Glance to provide an easier and hopefully more consistent interaction >> between gla

[openstack-dev] Generate documentation with Falcon api

Hello everyone, Is it possible to generate documentation while using Falcon API framework? Thanks beforehand & best regards, Romain Ziba. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listin

Re: [openstack-dev] [gantt] Scheduler group meeting - cancelled this week

Sigh. I've progressed from being challenged by time of day (e.g. timezone) to being challenged by day of week. Pretty soon I'll be confused about the year :-) Sorry about that. -- Don Dugger "Censeo Toto nos in Kansa esse decisse." - D. Gale Ph: 303/443-3786 -Original Message- From:

Re: [openstack-dev] [Ironic] [Triple-O] Openstack Onboarding

On 22/10/14 14:40, James Slagle wrote: > On Tue, Oct 21, 2014 at 1:08 PM, Clint Byrum wrote: >> So Tuskar would be a part of that deployment cloud, and would ask you >> things about your hardware, your desired configuration, and help you >> get the inventory loaded. >> >> So, ideally our gate wo

Re: [openstack-dev] Adding new dependencies to stackforge projects

Dear requirements-core folks, Here's the review as promised: https://review.openstack.org/130210 Thanks, dims On Wed, Oct 22, 2014 at 7:27 AM, Davanum Srinivas wrote: > Matt, > > I've submitted a review to remove the gate-nova-docker-requirements > from nova-docker: > > https://review.openstack

Re: [openstack-dev] [gantt] Scheduler group meeting - cancelled this week

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/22/2014 08:03 AM, Dugger, Donald D wrote: > Just a reminder that, as we mentioned last week, no meeting today. The meetings are supposed to be on Tuesday, no? And yeah, no one showed up yesterday. - -- Ed Leafe -BEGIN PGP SIGNATURE- Ve

Re: [openstack-dev] [neutron] HA of dhcp agents?

If you want rescheduling, you need a script to do it. There is a feature for that behavior in Juno, but only for the L3 agent. [1] 1. http://docs.openstack.org/trunk/config-reference/content/networking-options-l3_agent.html On Tue, Oct 21, 2014 at 4:27 PM, Noel Burton-Krahn wrote: > Hi Armand

[openstack-dev] [gantt] Scheduler group meeting - cancelled this week

Just a reminder that, as we mentioned last week, no meeting today. -- Don Dugger "Censeo Toto nos in Kansa esse decisse." - D. Gale Ph: 303/443-3786 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mail

Re: [openstack-dev] [Ironic] [Triple-O] Openstack Onboarding

On Tue, Oct 21, 2014 at 1:08 PM, Clint Byrum wrote: > So Tuskar would be a part of that deployment cloud, and would ask you > things about your hardware, your desired configuration, and help you > get the inventory loaded. > > So, ideally our gate would leave the images we test as part of the > ar

Re: [openstack-dev] [Glance][Cinder] The sorry state of cinder's driver in Glance

Greetings, On Wed, Oct 22, 2014 at 4:56 PM, Flavio Percoco wrote: > Greetings, > > Back in Havana a, partially-implemented[0][1], Cinder driver was merged > in Glance to provide an easier and hopefully more consistent interaction > between glance, cinder and nova when it comes to manage volume im

Re: [openstack-dev] [neutron][stable] metadata agent performance

My understanding is same as from Ihar, and we no longer have the degradation in the latest Icehouse update. There was a degradation in 2014.1.2 [2] but the fix was backported in 2014.1.3 [1]. We don't need to take care of backporting when considering metadata RPC patch. [1] https://review.openstac

Re: [openstack-dev] [Neutron][LBaaS][Octavia] Usage Requirements

> I,d like to start a conversation on usage requirements and have a few > suggestions. I advocate that, since we will be using TCP and HTTP/HTTPS > based protocols, we inherently enable connection logging for load > balancers for several reasons: Just request from the operator side of things: Plea

Re: [openstack-dev] Adding new dependencies to stackforge projects

Matt, I've submitted a review to remove the gate-nova-docker-requirements from nova-docker: https://review.openstack.org/#/c/130192/ I am good with treating the current situation with DSVM jobs as we "bug" if there is consensus. I'll try to dig in, but we may need Dean, Sean etc to help figure i

  1   2   >