Re: [openstack-dev] [api][nova][ironic] Microversion API HTTP header

On 06/17/2015 03:35 AM, Ken'ichi Ohmichi wrote: 2015-06-16 21:16 GMT+09:00 Jay Pipes : On 06/16/2015 08:00 AM, Dmitry Tantsur wrote: 16 июня 2015 г. 13:52 пользователь "Jay Pipes" mailto:jaypi...@gmail.com>> написал: > > On 06/16/2015 04:36 AM, Alex Xu wrote: >> >> So if our min_versi

Re: [openstack-dev] [QA] [Ironic] [Inspector] Where should integration tests for non-core projects live now? (Was: Toward 2.0.0 release)

On 06/17/2015 06:54 AM, Ken'ichi Ohmichi wrote: 2015-06-17 12:38 GMT+09:00 Yuiko Takada : Then, as you and Matt and Dimitry talked about this on IRC few days ago, We can add Ironic/Ironic-inspector tests into Tempest still, right? So that I've started to implement a test in Tempest, but I'm fac

[openstack-dev] [Security] the need about implementing a MAC security hook framework for OpenStack

Hi list, I'd like to know the need about implementing a MAC (Mandatory Access Control) security hook framework for OpenStack, just like the Linux Security Module to Linux. It can be used to help construct a security module that mediates the communications between OpenStack nodes and controls dis

[openstack-dev] [neutron] slimming down (the RFE) process for small internal design stuff

A few days ago, I was talking to Rossella, about the need of a RFE for this [1], in this case, it's an internal library/nicety for neutron development. It's not a feature from the user point of view. And it's not a very big change. So, we thought that starting by a simple devref to agree on, an

Re: [openstack-dev] [Openstack-operators] [nova] [neutron] Re: How do your end users use networking?

> On 17 Jun 2015, at 10:56 am, Armando M. wrote: > > > > On 16 June 2015 at 17:31, Sam Morrison > wrote: > We at NeCTAR are starting the transition to neutron from nova-net and neutron > almost does what we want. > > We have 10 “public" networks and 10 “service" n

Re: [openstack-dev] [Magnum] TLS Support in Magnum

Clint, Hi! It’s good to hear from you! On Jun 16, 2015, at 8:58 PM, Clint Byrum mailto:cl...@fewbar.com>> wrote: I don't understand at all what you said there. If my kubernetes minions are attached to a gateway which has a direct route to Magnum, let's say they're at, 192.0.2.{100,101,102}, an

Re: [openstack-dev] [QA] [Ironic] [Inspector] Where should integration tests for non-core projects live now? (Was: Toward 2.0.0 release)

2015-06-17 12:38 GMT+09:00 Yuiko Takada : > > Then, as you and Matt and Dimitry talked about this on IRC few days ago, > We can add Ironic/Ironic-inspector tests into Tempest still, right? > So that I've started to implement a test in Tempest, > but I'm facing another issue. > As you know, Ironic A

[openstack-dev] [Ironic][Horizon][Tuskar-ui] Making a dashboard for Ironic‏

hi folks,I'm planning to propose a new horizon plugin ironic-dashboard to fill the gap that ironic doesn't have horizon support. I know there's a nodes panel on "infrastructure" dashboard handled by tuskar-ui, but it's specifically geared towards TripleO. Ironic needs a separate dashboard to pre

Re: [openstack-dev] [Neutron] Quota enforcement

On Tue, Jun 16, 2015 at 5:17 PM, Kevin Benton wrote: > There seems to be confusion on what causes deadlocks. Can one of you explain > to me how an optimistic locking strategy (a.k.a. compare-and-swap) results > in deadlocks? > > Take the following example where two workers want to update a record

Re: [openstack-dev] [Magnum] TLS Support in Magnum

I don't understand at all what you said there. If my kubernetes minions are attached to a gateway which has a direct route to Magnum, let's say they're at, 192.0.2.{100,101,102}, and Magnum is at 198.51.100.1, then as long as the minions' gateway knows how to find 198.51.100.0/24, and Magnum's gat

Re: [openstack-dev] [QA] [Ironic] [Inspector] Where should integration tests for non-core projects live now? (Was: Toward 2.0.0 release)

Hi, Dmitry, thank you for putting it up, and also Ken'ichi, thank you for your reply. > Will it be possible to run tests on Ironic as well using plugin from > > ironic-inspector? > > Yeah, it will be possible. > but I'm guessing ironic-inspector is optional and Ironic should not > depend on the

Re: [openstack-dev] [Mistral] Proposal for the Resume Feature

Winson, thanks for the etherpad to gather different opinions. Dmitri, I think it's ok we discuss here, make more people get involved, we could use etherpad for summary. On Wed, Jun 17, 2015 at 2:22 AM, W Chan wrote: > Here's the etherpad link. I replied to the comments/feedbacks there. > Please

Re: [openstack-dev] [Magnum] TLS Support in Magnum

Clint, Answering Clint’s question, yes there is a reason all nodes must expose a floating IP address. In a Kubernetes cluster, each minion has a port address space. When an external service contacts the floating IP’s port, the request is routed over the internal network to the correct contain

Re: [openstack-dev] [Solum] Should logs be deleted when we delete an app?

CLIs should get versioned like any other contract and allow for change (not be restricted in stone to what's already out there{). With Solum, we have less to worry about as we are at the early phases of adoption and growth. To someone's earlier point, you can have —non-interactive flags which

Re: [openstack-dev] [api][nova][ironic] Microversion API HTTP header

2015-06-16 21:14 GMT+09:00 Sean Dague : > On 06/16/2015 07:38 AM, Alex Xu wrote: >> >> >> 2015-06-16 18:57 GMT+08:00 Sean Dague > >: >> >> On 06/15/2015 03:45 PM, Kevin L. Mitchell wrote: >> > On Mon, 2015-06-15 at 13:07 -0400, Jay Pipes wrote: >> >> The original

Re: [openstack-dev] [api][nova][ironic] Microversion API HTTP header

2015-06-16 21:16 GMT+09:00 Jay Pipes : > On 06/16/2015 08:00 AM, Dmitry Tantsur wrote: >> >> >> 16 июня 2015 г. 13:52 пользователь "Jay Pipes" > > написал: >> > >> > On 06/16/2015 04:36 AM, Alex Xu wrote: >> >> >> >> So if our min_version is 2.1 and the max_version is

Re: [openstack-dev] [Openstack] What code structure is recommended for a Neutron plugin( L2 and L3)?

On 15 June 2015 at 19:34, Sam Su wrote: > Hi stackers, > > > > I am going to implement a Neutron plugin, however when I checked the > current Neutron code(master) structure, I found there are two way to > organize a Neutron plugin: > > 1. The first one is implement all L2 and L3 functions u

Re: [openstack-dev] [Congress] Mid-cycle sprint

Hi, Tim Is this the oslo.messaging integration task? I’m interested in participating. Actually I am working on a bp to receive notifications from external services in datasource driver at first. I’m ok to change if the direction is to integrate oslo.messaging thoroughly (even replacing DSE). Th

Re: [openstack-dev] [Openstack-operators] [nova] [neutron] Re: How do your end users use networking?

On 16 June 2015 at 17:31, Sam Morrison wrote: > We at NeCTAR are starting the transition to neutron from nova-net and > neutron almost does what we want. > > We have 10 “public" networks and 10 “service" networks and depending on > which compute node you land on you get attached to one of them. >

Re: [openstack-dev] [Openstack-operators] [nova] [neutron] Re: How do your end users use networking?

We at NeCTAR are starting the transition to neutron from nova-net and neutron almost does what we want. We have 10 “public" networks and 10 “service" networks and depending on which compute node you land on you get attached to one of them. In neutron speak we have multiple shared externally rou

Re: [openstack-dev] [Foundation Board] [OpenStack] OpenStack Diversity Working Group - Meeting Information

Roland – Thanks for your comments. Hope you can join us to help move this effort forward. Carol From: Roland Chan [mailto:rol...@aptira.com] Sent: Tuesday, June 16, 2015 4:44 PM To: Barrett, Carol L Cc: Greenberg, Suzy M; foundation-bo...@lists.openstack.org; openst...@lists.openstack.org; OpenS

Re: [openstack-dev] [Solum] Should logs be deleted when we delete an app?

It sounded like the push was, cli's for interactive, if you want to script, use python. My assertion was, developers script in python, users/admins script in shell usually. Not arguing against making the cli user experience more pleasant for interactive users, but realize shell is the way most u

Re: [openstack-dev] [api][nova][ironic] Microversion API HTTP header

2015-06-16 20:52 GMT+09:00 Jay Pipes : > >> but I have the same question with Dmitry. >> If using service names in the header, how to define these name before >> that? >> Current big-tent situation can make duplications between projects like >> X-OpenStack-Container-API-Version or something. >> Pro

Re: [openstack-dev] [api][nova][ironic] Microversion API HTTP header

2015-06-16 6:30 GMT+09:00 Michael Davies : > On Tue, Jun 16, 2015 at 5:15 AM, Kevin L. Mitchell > wrote: >> >> Given the disagreement evinced by the responses to this thread, let me >> ask a question: Would there be any particular problem with using >> "X-OpenStack-API-Version"? > > > Well, perhap

Re: [openstack-dev] [Solum] Should logs be deleted when we delete an app?

Kevin, I agree with your break out, except I think you are missing a 3rd category. 100's of public cloud support specialists, developers, and product management folks use the CLI without scripts every day in supporting the OpenStack services and customers. Using and interacting with the CLI i

[openstack-dev] [neutron][vpnaas] No VPNaaS weekly IRC meeting next week (June 23rd)

As some of us are attending Neutron mid-cycle we are skipping the VPNaaS weekly IRC meeting for next week Tuesday June 23rd. The meeting will resume the week after. As usual please update agenda on the wiki page: https://wiki.openstack.org/wiki/Meetings/VPNaaS before the meeting. See you all on T

Re: [openstack-dev] [Solum] Should logs be deleted when we delete an app?

-1. There are developers and there are users/admins. The former tend to write in python. the latter, shell. Thanks, Kevin From: Keith Bray [keith.b...@rackspace.com] Sent: Tuesday, June 16, 2015 2:42 PM To: OpenStack Development Mailing List (not for usage questio

Re: [openstack-dev] [Neutron] Quota enforcement

There seems to be confusion on what causes deadlocks. Can one of you explain to me how an optimistic locking strategy (a.k.a. compare-and-swap) results in deadlocks? Take the following example where two workers want to update a record: Worker1: "UPDATE items set value=newvalue1 where value=oldva

Re: [openstack-dev] [Neutron] Quota enforcement

On Tue, Jun 16, 2015 at 2:18 PM, Salvatore Orlando wrote: > But zzzeek (Mike Bayer) is coming to our help; as a part of his DBFacade > work, we should be able to treat active/active cluster as active/passive for > writes, and active/active for reads. This means that the write set > certification i

Re: [openstack-dev] [nova] Plan to consolidate FS-style libvirt volume drivers under a common base class

I don't think you need a spec for this (its a refactor). That said, I'd be interested in exploring how you deprecate the old flags. Can you have more than one deprecated name for a single flag? Michael On Wed, Jun 17, 2015 at 7:29 AM, Matt Riedemann wrote: > > > On 6/16/2015 4:21 PM, Matt Riedem

Re: [openstack-dev] Targeting icehouse-eol?

> let's release this last one (codename: Farewell ?) point release. I > can do this next week after we finish pending reviews. Remaining stable/icehouse reviews[1] have -2 or -1 except https://review.openstack.org/176019 which I've asked neutron-stable-maint to review. Matt, anything else before w

[openstack-dev] [OpenStack] OpenStack Diversity Working Group - Meeting Information

The initial meeting for this work group will be: Friday, June 19, 2015 at 18:00 UTC, on IRC: #openstack-meeting The Agenda is: * Introductions * Mission Discussion and definition of Diversity * Discuss proposal to engage a Consultant/Coach to assist this work group *

Re: [openstack-dev] [Solum] Should logs be deleted when we delete an app?

That makes sense Randall.. .a sort of "Novice mode" vs. "Expert mode." I definitely want to see OpenStack to get easier to use, and lower the barrier to entry. If projects only cater to developers, progress will be slower than what it could be. -Keith On 6/16/15 4:52 PM, "Randall Burt" wrote: >

Re: [openstack-dev] [all] [stable] No longer doing stable point releases

On 06/16/2015 12:06 PM, Thierry Carrez wrote: >>> It also removes the stupid encouragement to use all components from the >>> same date. With everything tagged at the same date, you kinda send the >>> message that those various things should be used together. With >>> everything tagged separately,

Re: [openstack-dev] [Solum] Should logs be deleted when we delete an app?

While I agree with what you're saying, the way the OpenStack clients are traditionally written/designed, the CLI *is* the SDK for those users who want to do scripting in a shell rather than in Python. If we go with your suggestion, we'd probably also want to have the ability to suppress those p

Re: [openstack-dev] [Solum] Should logs be deleted when we delete an app?

Isn't that what the SDK is for? To chip in with a Product Management type hat on, I'd think the CLI should be primarily focused on user experience interaction, and the SDK should be primarily targeted for developer automation needs around programmatically interacting with the service. So, I

Re: [openstack-dev] [nova] Plan to consolidate FS-style libvirt volume drivers under a common base class

On 6/16/2015 4:21 PM, Matt Riedemann wrote: The NFS, GlusterFS, SMBFS, and Quobyte libvirt volume drivers are all very similar. I want to extract a common base class that abstracts some of the common code and then let the sub-classes provide overrides where necessary. As part of this, I'm won

Re: [openstack-dev] [devstack] apache wsgi application support

On Tue, 16 Jun 2015, Sean Dague wrote: I was just looking at the patches that put Nova under apache wsgi for the API, and there are a few things that I think are going in the wrong direction. Largely I think because they were copied from the lib/keystone code, which we've learned is kind of the

[openstack-dev] [nova] Plan to consolidate FS-style libvirt volume drivers under a common base class

The NFS, GlusterFS, SMBFS, and Quobyte libvirt volume drivers are all very similar. I want to extract a common base class that abstracts some of the common code and then let the sub-classes provide overrides where necessary. As part of this, I'm wondering if we could just have a single 'moun

[openstack-dev] [Congress] Mid-cycle sprint

Hi all, In the last couple of IRCs we've been talking about running a mid-cycle sprint focused on enabling our message bus to span multiple processes and multiple hosts. The message bus is what allows the Congress policy engine to communicate with the Congress wrappers around external services li

Re: [openstack-dev] [Neutron] Quota enforcement

Some more comments inline. Salvatore On 16 June 2015 at 19:00, Carl Baldwin wrote: > On Tue, Jun 16, 2015 at 12:33 AM, Kevin Benton wrote: > >>Do these kinds of test even make sense? And are they feasible at all? I > >> doubt we have any framework for injecting anything in neutron code under >

Re: [openstack-dev] [Cinder] Volume creation fails in Horizon

On 13:00 Jun 15, Jayanthi, Swaroop wrote: > Hi All, > > I am trying to create a Volume for VMFS with a Volume Type (selected Volume > Type selected has extra_specs).I am receiving an error Volume creation > failed incase if the volume-type has extra-specs. > > Cinder doesn't support Volume

Re: [openstack-dev] [Neutron] Quota enforcement

On 16 June 2015 at 18:49, Carl Baldwin wrote: > On Thu, Jun 11, 2015 at 2:45 PM, Salvatore Orlando > wrote: > > I have been then following a different approach. And a set of patches, > > including a devref one [2], if up for review [3]. This hardly completes > the > > job: more work is required

Re: [openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

Excerpts from Thierry Carrez's message of 2015-06-16 11:45:51 +0200: > Doug Hellmann wrote: > > [...] > > I put together a little script [1] to try to count the previous > > releases for projects, to use that as the basis for their first > > SemVer-based version number. I pasted the output into an

Re: [openstack-dev] [packaging] Adding packaging as an OpenStack project

On 06/15/2015 10:55 AM, James Page wrote: We understand and have communicated from the start of this conversation that we will need to be able to maintain deltas between Debian and Ubuntu - for both technical reasons, in the way the distributions work (think Ubuntu main vs universe), as well as o

Re: [openstack-dev] [oslo.messaging][zeromq] Next step

Gordon, These are all great points for RPC messages (also called "CALL" in oslo messaging). There are similar ambiguous contracts for the other types of messages (CAST and FANOUT). I am worried about the general lack of interest from the community to fix this as it looks like most people assume th

Re: [openstack-dev] [devstack] apache wsgi application support

On 06/16/2015 12:48 PM, Morgan Fainberg wrote: Long term we want to see Keystone move to http:///identity. However the reason for choosing 5000/35357 for ports was compatibility and avoiding breaking horizon. At the time we did the initial change over, sharing the root 80/443 ports with horizon

Re: [openstack-dev] [devstack] apache wsgi application support

On 06/16/2015 12:25 PM, Sean Dague wrote: I was just looking at the patches that put Nova under apache wsgi for the API, and there are a few things that I think are going in the wrong direction. Largely I think because they were copied from the lib/keystone code, which we've learned is kind of th

Re: [openstack-dev] [javascript] [horizon] [merlin] [refstack] Javascript Linting

On Tue, Jun 16, 2015 at 10:22 AM Tripp, Travis S wrote: > I think agreeing on rules is the bigger problem here and I don’t think all > the projects should have to agree on rules. I believe we agree there, mostly. I personally feel there is some benefit to setting some rules, likely published as

Re: [openstack-dev] [kolla] Proposal for changing 1600UTC meeting to 1700 UTC

I'm ok with moving to 16:30 UTC instead of staying at 16:00. I actually prefer it in my evening schedule :) Moving to 16:30 would already be a great improvement to the current schedule and should at least allow me to not miss everything. - harmw Op 12-06-15 om 15:44 schreef Steven Dake (stda

Re: [openstack-dev] [kolla] Proposal for new core-reviewer Harm Waites

Thanks guys, both for all the nice words and the acceptance! harmw Op 16-06-15 om 16:32 schreef Steven Dake (stdake): Its unanimous! Welcome to the core reviewer team Harm! Regards -steve From: Steven Dake mailto:std...@cisco.com>> Reply-To: "OpenStack Development Mailing List (not for usag

Re: [openstack-dev] Getting rid of suds, which is unmaintained, and which we want out of Debian

On Thu, 11 Jun 2015 11:08:55 +0300 Duncan Thomas wrote: > There's only one cinder driver using it (nimble storage), and it seems to > be using only very basic features. There are half a dozen suds forks on > pipi, or there's pisimplesoap that the debian maintainer recommends. None > of the above

Re: [openstack-dev] [Manila] Network path between admin network and shares

Yes. I think this is possible with the HP 3PAR. I'd have to test more to be sure, but if I understand the plan correctly, it'll work. However, there are limited resources for doing this, so it'll only work if resources allow. I'm thinking that the administrator config+startup/setup code wou

Re: [openstack-dev] [Mistral] Proposal for the Resume Feature

Here's the etherpad link. I replied to the comments/feedbacks there. Please feel free to continue the conversation there. https://etherpad.openstack.org/p/mistral-resume __ OpenStack Development Mailing List (not for usage que

Re: [openstack-dev] [oslo.messaging][zeromq] Next step

On 06/12/2015 09:41 PM, Alec Hothan (ahothan) wrote: One long standing issue I can see is the fact that the oslo messaging API documentation is sorely lacking details on critical areas such as API behavior during fault conditions, load conditions and scale conditions. I very much agree, particu

Re: [openstack-dev] [grenade] future direction on partial upgrade support

On 2015-06-16 12:58:18 -0400 (-0400), Sean Dague wrote: [...] > I think the only complexity here is the fact that grenade.sh > implicitly drives stack.sh. Which means one of: > > 1) devstack-gate could build the worker first, then run grenade.sh > > 2) we make it so grenade.sh can execute in part

Re: [openstack-dev] stackforge projects are not second class citizens

In Murano project we do see a positive impact of BigTent model. Since Murano was accepted as a part of BigTent community we had a lot of conversations with potential users. They were driven exactly by the fact that Murano is now "officially" recognized in OpenStack community. It might be a wrong pe

Re: [openstack-dev] [Security] Nominating Travis McPeak for Security CoreSec

On 06/16/2015 05:28 AM, Clark, Robert Graham wrote: I’d like to nominate Travis for a CoreSec position as part of the Security project. - CoreSec team members support the VMT with extended consultation on externally reported vulnerabilities. Travis has been an active member of the Security proje

Re: [openstack-dev] [puppet] (officially) deprecate stable/{grizzly, havana} branches

Matt Fischer wrote: +1 from me for deprecation. I'd also like to know or have an official policy for future deprecations, such as when will we deprecate Icehouse? On Tue, Jun 16, 2015 at 9:50 AM, Emilien Macchi mailto:emil...@redhat.com>> wrote: Hi, Some of our modules have stable/gri

Re: [openstack-dev] [puppet] (officially) deprecate stable/{grizzly, havana} branches

+1 for deprecation -- David Moreau Simard On 2015-06-16 11:54 AM, Emilien Macchi wrote: > Hi, > > Some of our modules have stable/grizzly and stable/havana branches. Some > of them have the CI broken due to rspec issues that would require some > investigation and time if we wanted to fix it. > >

Re: [openstack-dev] [Mistral] Proposal for the Resume Feature

+1 great write-up Winson, I propose we move the discussion to an etherpad, and flash out details there so it won’t get lost in a long thread. Winson would you care to create one and post here? Re: ‘error state’: I think it’s not absolutely necessary: pause/resume can be done without enabling

Re: [openstack-dev] [Solum] Should logs be deleted when we delete an app?

On Jun 15, 2015, at 9:10 PM, Keith Bray mailto:keith.b...@rackspace.com>> wrote: Regardless of what the API defaults to, could we have the CLI prompt/warn so that the user easily knows that both options exist? Is there a precedent within OpenStack for a similar situation? E.g. > solum app de

Re: [openstack-dev] [Glance] [all] Proposal for Weekly Glance Drivers meeting.

FYI, We will be closing the vote on Friday, June 19 at 1700 UTC. On 6/15/15 7:41 PM, Nikhil Komawar wrote: > Hi, > > As per the discussion during the last weekly Glance meeting (14:51:42at > http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-06-11-14.00.log.html > ), we will begin a s

Re: [openstack-dev] [puppet] (officially) deprecate stable/{grizzly, havana} branches

+1 from me for deprecation. I'd also like to know or have an official policy for future deprecations, such as when will we deprecate Icehouse? On Tue, Jun 16, 2015 at 9:50 AM, Emilien Macchi wrote: > Hi, > > Some of our modules have stable/grizzly and stable/havana branches. Some > of them have

Re: [openstack-dev] [javascript] [horizon] [merlin] [refstack] Javascript Linting

I’m copying and pasting from the other thread some info below. I think agreeing on rules is the bigger problem here and I don’t think all the projects should have to agree on rules. We’ve spent a good portion of liberty 1 getting the code base cleaned up to meet the already adopted horizon rules a

Re: [openstack-dev] [all] FYI - dropping non RabbitMQ support in devstack

On 06/16/2015 12:49 PM, Clint Byrum wrote: > Excerpts from Sean Dague's message of 2015-06-16 06:22:23 -0700: >> FYI, >> >> One of the things that came out of the summit for Devstack plans going >> forward is to trim it back to something more opinionated and remove a >> bunch of low use optionality

Re: [openstack-dev] CLI problem

It is weired. I deleted my devstack and redo everything. I am using the same command and everything is fine. Thanks, Regards, On 06/16/2015 01:03 PM, Steve Martinelli wrote: What was the command you used? What was the output? Can you try running it with --debug? More information is needed here

Re: [openstack-dev] CLI problem

What was the command you used? What was the output? Can you try running it with --debug? More information is needed here. It would also probably be quicker to jump on IRC and ask around. Thanks, Steve Martinelli OpenStack Keystone Core "Ali Reza Zamani" wrote on 06/16/2015 12:46:16 PM: > Fr

Re: [openstack-dev] [Neutron] Quota enforcement

On Tue, Jun 16, 2015 at 12:33 AM, Kevin Benton wrote: >>Do these kinds of test even make sense? And are they feasible at all? I >> doubt we have any framework for injecting anything in neutron code under >> test. > > I was thinking about this in the context of a lot of the fixes we have for > othe

[openstack-dev] [grenade] future direction on partial upgrade support

Back when Nova first wanted to test partial upgrade, we did a bunch of slightly odd conditionals inside of grenade and devstack to make it so that if you were very careful, you could just not stop some of the old services on a single node, upgrade everything else, and as long as the old services di

Re: [openstack-dev] [Neutron] Quota enforcement

On Thu, Jun 11, 2015 at 2:45 PM, Salvatore Orlando wrote: > I have been then following a different approach. And a set of patches, > including a devref one [2], if up for review [3]. This hardly completes the > job: more work is required on the testing side, both as unit and functional > tests. >

Re: [openstack-dev] [all] FYI - dropping non RabbitMQ support in devstack

Excerpts from Sean Dague's message of 2015-06-16 06:22:23 -0700: > FYI, > > One of the things that came out of the summit for Devstack plans going > forward is to trim it back to something more opinionated and remove a > bunch of low use optionality in the process. > > One of those branches to be

Re: [openstack-dev] [devstack] apache wsgi application support

Long term we want to see Keystone move to http:///identity. However the reason for choosing 5000/35357 for ports was compatibility and avoiding breaking horizon. At the time we did the initial change over, sharing the root 80/443 ports with horizon was more than "challenging" since horizon neede

[openstack-dev] CLI problem

Hi all, I have a problem in creating the instances. When I create the instances using GUI web interface everything is fine. But when I do it using CLI after spawning it says Error. And the error is: ne __ OpenStack Developmen

Re: [openstack-dev] [neutron] Mechanism drivers and Neutron server forking?

> Right now I'm leaning toward "parent always does nothing" + PluginWorker. > Everything is forked, no special case for workers==0, and explicit > designation of the "only one" case. Of course, it's still early in the day > and I haven't had any coffee. I have updated the patch (https://review.ope

Re: [openstack-dev] [packaging] Adding packaging as an OpenStack project

On 06/16/2015 12:41 PM, Allison Randal wrote: On 06/15/2015 01:43 PM, Paul Belanger wrote: While I agree those points are valid, and going to be helpful, moving under OpenStack (even Stackforge) does also offer the chance to get more test integration upstream (not saying this was the original sc

Re: [openstack-dev] [packaging] Adding packaging as an OpenStack project

On 06/15/2015 01:43 PM, Paul Belanger wrote: > While I agree those points are valid, and going to be helpful, moving > under OpenStack (even Stackforge) does also offer the chance to get more > test integration upstream (not saying this was the original scope). > However, this could also be achieve

[openstack-dev] [Keystone][OSC] Keystone v3 user create --project $projid does not add user to project?

Using admin token credentials with the Keystone v2.0 API and the openstackclient, doing this: # openstack project create bar --enable # openstack user create foo --project bar --enable ... The user will be added to the project. Using admin token credentials with the Keystone v3 API and the op

[openstack-dev] [devstack] apache wsgi application support

I was just looking at the patches that put Nova under apache wsgi for the API, and there are a few things that I think are going in the wrong direction. Largely I think because they were copied from the lib/keystone code, which we've learned is kind of the wrong direction. The first is the fact th

[openstack-dev] [Glance] [all] Proposal for Glance Artifacts Sub-Team meeting.

Hi all, We have planned a fast track development for Glance Artifacts; also it would be our v3 API. To balance pace, knowledge sharing, synchronous discussion on ideas and opinions as well as seeing this great feature through in Liberty: We hereby propose a non-mandatory, open to all, sub-team me

Re: [openstack-dev] [neutron][db] online schema upgrades

On 6/16/15 11:41 AM, Ihar Hrachyshka wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 - - instead of migrating data with alembic rules, migrate it in runtime. There should be a abstraction layer that will make sure that data is migrated into new schema fields and objects, while preservin

Re: [openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

Doug Hellmann wrote: > Excerpts from Thierry Carrez's message of 2015-06-16 11:45:51 +0200: >> We also traditionally "managed" the previously-incubated projects. That >> would add the following to the mix: >> >> barbican 1.0.0 >> designate 1.0.0 >> manila 1.0.0 >> zaqar 1.0.0 >> > > Those didn't h

Re: [openstack-dev] [Ironic] ironic-lib library

Hi, > I haven't paid any attention to ironic-lib; I just knew that we wanted to > have a library of common code so that we didn't cut/paste. I just took a > look[1] and there are files there from 2 months ago. So far, everything is > under ironic_lib (ie, no subdirectories to group things). Going

[openstack-dev] [puppet] (officially) deprecate stable/{grizzly, havana} branches

Hi, Some of our modules have stable/grizzly and stable/havana branches. Some of them have the CI broken due to rspec issues that would require some investigation and time if we wanted to fix it. We would like to know who plan to backport some patches in these branches? If nobody plans to do that

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

On 06/15/2015 08:06 PM, Emilien Macchi wrote: > Hi everyone, > > 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-20150616 > > Please add additiona

[openstack-dev] [neutron][db] online schema upgrades

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi neutron folks, I'd like to discuss a plan on getting support for online db schema upgrades in neutron. *What is it even about?* Currently, any major version upgrade, or master-to-master upgrade, requires neutron-server shutdown. After shutdown,

Re: [openstack-dev] [Solum] Should logs be deleted when we delete an app?

+1 Murali. AFIAK, there is no precedent for what Keith proposes, but that doesn't mean its a bad thing. On Jun 16, 2015, at 12:21 AM, Murali Allada wrote: > I agree, users should have a mechanism to keep logs around. > > I implemented the logs deletion feature after we got a bunch of requests

Re: [openstack-dev] [Murano] Cloud Foundry Service Broker Api in Murano

Here is a draft spec for this: https://review.openstack.org/#/c/192250/ Nikolay Starodubtsev Software Engineer Mirantis Inc. Skype: dark_harlequine1 2015-06-16 13:11 GMT+03:00 Nikolay Starodubtsev : > Hi all, > I've started a work on bp: > https://blueprints.launchpad.net/murano/+spec/clo

Re: [openstack-dev] How does instance's tap device macaddress generate?

On 11.06.2015 18:52, Andreas Scheuring wrote: Maybe this helps (taken from [1]) "Actually there is one way that the MAC address of the tap device affects proper operation of guest networking - if you happen to set the tap device's MAC identical to the MAC used by the guest, you will get errors f

[openstack-dev] [kolla] Add your name and TZ to wiki

Hi all, Steve suggested adding a new table to the Kolla wiki to help us keep track of who's actively working on Kolla along with relevant info such as timezones and IRC names. I'm missing lots of names and timezones so if you'd like to be on this please feel free to update it at https://wik

Re: [openstack-dev] [ceilometer] When do we import aodh?

On Tue, Jun 16 2015, Chris Dent wrote: > 5. anything in tempest to worry about? Yes, we need to adapt and reenable tempest after. > 6. what's that stuff in the "ceilometer" dir? >6.1. Looks like migration artifacts, what about migration in > general? That's a rest of one of the many

[openstack-dev] [Fuel] Improvement of the blueprint specs template

Hi folks! I was reviewing one of specs for Fuel 7.0 and realized the information there is messed up and it’s pretty hard to put it all together. The reason for that is basically that Fuel is a multicomponent project but the template does not consider that — there is a Proposed change section wh

Re: [openstack-dev] [all][requirements] Proposing a slight change in requirements.txt syncing output.

Doug Hellmann wrote: Excerpts from Robert Collins's message of 2015-06-16 11:18:55 +1200: At the moment we copy the global-requirements lines verbatim. So if we have two lines in global-requirements.txt: oslotest>=1.5.1 # Apache-2.0 PyECLib>=1.0.7 # BSD with very diffe

Re: [openstack-dev] [taskflow] Returning information from reverted flow

Dulko, Michal wrote: -Original Message- From: Joshua Harlow [mailto:harlo...@outlook.com] Sent: Friday, June 12, 2015 5:49 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [taskflow] Returning information from reverted flow Dulko, Michal wr

[openstack-dev] [oslo][all] Request from Oslo team for Liberty Cycle

Hello fellow stackers, The Oslo team came up with a handful of requests to the projects that use Oslo-*. Here they are: 0. Check if your project has a Oslo Liaison Please see https://wiki.openstack.org/wiki/CrossProjectLiaisons#Oslo and volunteer for your project. We meet once a week to go over

Re: [openstack-dev] [Ironic] Adopting ironic-lib in Ironic

On 16 June 2015 at 03:12, Dmitry Tantsur wrote: > On 06/16/2015 08:58 AM, Ramakrishnan G wrote: > >> >> Hi All, >> >> Some time back we created a new repository[1] to move all the reusable >> code components of Ironic to a separate library. The branched out code >> has changed and there has been

Re: [openstack-dev] [ceilometer] When do we import aodh?

On Tue, 16 Jun 2015, Julien Danjou wrote: To me the next step is to: 1. Someone cares and review what I've done in the repository 2. import the code into openstack/aodh Assuming that we'll do whatever is required to finish things after moving it under openstack/ then whatever you've done in st

[openstack-dev] [Ironic] ironic-lib library

Hi, I haven't paid any attention to ironic-lib; I just knew that we wanted to have a library of common code so that we didn't cut/paste. I just took a look[1] and there are files there from 2 months ago. So far, everything is under ironic_lib (ie, no subdirectories to group things). Going forward,

Re: [openstack-dev] [kolla] Proposal for new core-reviewer Harm Waites

Its unanimous! Welcome to the core reviewer team Harm! Regards -steve From: Steven Dake mailto:std...@cisco.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Sunday, June 14, 2015 at 10:48 AM To: "OpenStack Developme

Re: [openstack-dev] [javascript] [horizon] [merlin] [refstack] Javascript Linting

Just for the sake of clarity- did the Horizon team discuss the tool selection for JSCS with the greater community? I can't find anything on the dev list. Furthermore, there've been situations before (karma) where a patch was landed without appropriate upstream notifications and/or discussion, which

  1   2   >