[openstack-dev] [Tripleo] Core reviewer update Dec

Hi, like most OpenStack projects we need to keep the core team up to date: folk who are not regularly reviewing will lose context over time, and new folk who have been reviewing regularly should be trusted with -core responsibilities. In this months review: - Ghe Rivero for -core - Jan Prova

Re: [openstack-dev] [Nova] New API requirements, review of GCE

It is not a problem to update the code in given direction when the decision is made. As I understood right now it's not about the code - that's why I'd canceled the code review until the blueprint is accepted - it's more about architecture and procedures such as which tests should be obligatory

Re: [openstack-dev] Package from Debian for Devstack?

On 12/04/2013 04:51 AM, Adam Young wrote: >> Hi, >> >> So the way that the package syncs works from Debian to Ubuntu is that >> a package usually moves from Experimental->Unstable->Testing, Ubuntu >> usually picks the package up in Unstable and gets placed in Universe >> (usually). However that doe

Re: [openstack-dev] [Neutron] Rename 'tenant' to 'project' as per Keystone?

I can speak to the first "project->tenant” part. In the beginning there was Nova and Swift. Nova (NASA) used the term project. Swift (Rackspace) used the term account. When we created Keystone to provide a common auth system, we were also interested in developing a common multi-tenant-accountin

Re: [openstack-dev] [Olso][DB] Remove eventlet from oslo.db

Hey all, Mark, Yes, that's exactly what we were going to do! (and there is a similar class in eventlet itself, Victor is currently trying to run Nova with it applied, so we might end up with no module/class at all, but rather use the one from eventlet instead) Thank you all for your feedback! Ro

Re: [openstack-dev] [OpenStack-dev][cinder][glance] Should glance be installed on cinder only nodes?

Thanks Avishay. I will try to setup a cinder-volume node and test this feature. Regards, Gans On Tue, Dec 3, 2013 at 3:00 PM, Avishay Traeger wrote: > Gans, > No, you don't need to install Glance on Cinder nodes. Cinder will use the > Glance client, which must be installed on the Cinder node

[openstack-dev] [openstack-tc] [barbican] Curious about oslo.messaging (from Incubation Request for Barbican)

Hello folks, I was curious if there is an OpenStack project that would be a good example to follow as we convert Barbican over to oslo messaging. I've been examining existing OpenStack projects such as Ceilometer and Keystone to see how they are utilizing oslo messaging. These projects appear

[openstack-dev] [Neutron][IPv6] Webex Recording of IPv6 / Neutron Sync-up

Hi, guys: We had a great discussion tonight with stackers from Comcast, IBM, HP, Cisco and Nephos6! Here is the debrief of what we discussed during this 1-hr session: 1) Sean from Comcast provided clarification of his short-term and mid-term goals in the proposed blueprint. 2) Da Zhao, Yu Yang,

Re: [openstack-dev] creating a default for oslo config variables within a project?

Excerpts from Sean Dague's message of 2013-12-03 16:05:47 -0800: > On 12/03/2013 06:13 PM, Ben Nemec wrote: > > On 2013-12-03 17:09, Sean Dague wrote: > >> On 12/03/2013 05:50 PM, Mark McLoughlin wrote: > >>> On Tue, 2013-12-03 at 16:23 -0600, Ben Nemec wrote: > On 2013-12-03 15:56, Sean Dague

Re: [openstack-dev] creating a default for oslo config variables within a project?

IIRC nova solved this problem by adding a very simple wrapper utility around the oslo call. Couldn't cinder do the same? Michael On Tue, Dec 3, 2013 at 6:05 PM, Sean Dague wrote: > On 12/03/2013 06:13 PM, Ben Nemec wrote: >> On 2013-12-03 17:09, Sean Dague wrote: >>> On 12/03/2013 05:50 PM, Mark

Re: [openstack-dev] [Neutron] DHCP Agent Reliability

Excerpts from Maru Newby's message of 2013-12-03 19:37:19 -0800: > > On Dec 4, 2013, at 11:57 AM, Clint Byrum wrote: > > > Excerpts from Maru Newby's message of 2013-12-03 08:08:09 -0800: > >> I've been investigating a bug that is preventing VM's from receiving IP > >> addresses when a Neutron

Re: [openstack-dev] [Neutron] DHCP Agent Reliability

On Dec 4, 2013, at 11:57 AM, Clint Byrum wrote: > Excerpts from Maru Newby's message of 2013-12-03 08:08:09 -0800: >> I've been investigating a bug that is preventing VM's from receiving IP >> addresses when a Neutron service is under high load: >> >> https://bugs.launchpad.net/neutron/+bug/11

Re: [openstack-dev] [Neutron] DHCP Agent Reliability

On Dec 4, 2013, at 11:02 AM, Yongsheng Gong wrote: > another way is to have a large agent_down_time, by default it is 9 secs. I don't believe that increasing the timeout by itself is a good solution. Relying on the agent state to know whether to send a notification has simply proven unreliab

[openstack-dev] [Solum] First working group meeting on language packs

Meeting 1 was conducted on Monday and consisted mostly of freeform discussions, clarification, and QA: http://irclogs.solum.io/2013/solum.2013-12-02-17.05.html. The next meeting is Monday, December 9, 2013 1700 UTC. Wiki: https://wiki.openstack.org/wiki/Solum/FeatureBlueprints/BuildingSourceI

Re: [openstack-dev] [Neutron] DHCP Agent Reliability

On Dec 4, 2013, at 1:47 AM, Stephen Gran wrote: > On 03/12/13 16:08, Maru Newby wrote: >> I've been investigating a bug that is preventing VM's from receiving IP >> addresses when a Neutron service is under high load: >> >> https://bugs.launchpad.net/neutron/+bug/1192381 >> >> High load cause

Re: [openstack-dev] [Neutron] DHCP Agent Reliability

Excerpts from Maru Newby's message of 2013-12-03 08:08:09 -0800: > I've been investigating a bug that is preventing VM's from receiving IP > addresses when a Neutron service is under high load: > > https://bugs.launchpad.net/neutron/+bug/1192381 > > High load causes the DHCP agent's status updat

Re: [openstack-dev] [Neutron] Rename 'tenant' to 'project' as per Keystone?

who can tell me the whole story about keystone(or openstack) changes between project->tenant->project? On Wed, Dec 4, 2013 at 9:58 AM, Adam Young wrote: > On 11/26/2013 12:07 PM, Maru Newby wrote: > >> Keystone is almost finished replacing the term 'tenant' with 'project' >> (see recent thread

Re: [openstack-dev] [Neutron] DHCP Agent Reliability

another way is to have a large agent_down_time, by default it is 9 secs. On Wed, Dec 4, 2013 at 7:55 AM, Carl Baldwin wrote: > Stephen, all, > > I agree that there may be some opportunity to split things out a bit. > However, I'm not sure what the best way will be. I recall that Mark > mention

Re: [openstack-dev] [Neutron] Rename 'tenant' to 'project' as per Keystone?

On 11/26/2013 12:07 PM, Maru Newby wrote: Keystone is almost finished replacing the term 'tenant' with 'project' (see recent thread https://www.mail-archive.com/openstack-dev@lists.openstack.org/msg09709.html) and we might want to think about how and when Neutron makes a similar transition.

Re: [openstack-dev] [keystone] Service scoped role definition

I've been thinking about your comment that "nested roles are confusing" What if we backed off and said the following: "Some role-definitions are owned by services. If a Role definition is owned by a service, in role assignment lists in tokens, those roles we be prefixd by the service name.

Re: [openstack-dev] When should things get added to Oslo.Incubator

Jay is right. What we have is probably close enough to what's in Nova to qualify for oslo-incubator. The simplifications seem to me to have general appeal so this code would be more attractive to other projects. One worry I have is that there is still a good deal of magic behavior in this code,

Re: [openstack-dev] [Solum] CLI minimal implementation

I did some streamlining of the etherpad on this: https://etherpad.openstack.org/p/MinimalCLI I agree that required arguments should be positional. The only one that is confusing is the --repo argument to the app create command, which will end up being optional in a subsequent release, so I want

Re: [openstack-dev] creating a default for oslo config variables within a project?

On 12/03/2013 06:13 PM, Ben Nemec wrote: > On 2013-12-03 17:09, Sean Dague wrote: >> On 12/03/2013 05:50 PM, Mark McLoughlin wrote: >>> On Tue, 2013-12-03 at 16:23 -0600, Ben Nemec wrote: On 2013-12-03 15:56, Sean Dague wrote: > This cinder patch - https://review.openstack.org/#/c/48935/ >

Re: [openstack-dev] [keystone] Service scoped role definition

Hi David, I have added my comments underneath line # 97 till line #110, it is mostly aligned with your proposal with some modification. https://etherpad.openstack.org/p/service-scoped-role-definition Thanks for your time, Arvind -Original Message- From: Tiwari, Arvind Sent: Monday

Re: [openstack-dev] [Neutron] DHCP Agent Reliability

Stephen, all, I agree that there may be some opportunity to split things out a bit. However, I'm not sure what the best way will be. I recall that Mark mentioned breaking out the processes that handle API requests and RPC from each other at the summit. Anyway, it is something that has been discu

Re: [openstack-dev] [Olso][DB] Remove eventlet from oslo.db

On Mon, 2013-12-02 at 16:02 +0200, Victor Sergeyev wrote: > Hi folks! > > At the moment I and Roman Podoliaka are working on splitting of > openstack.common.db code into a separate library. And it would be nice to > drop dependency on eventlet before oslo.db is released. > > Currently, there is o

Re: [openstack-dev] creating a default for oslo config variables within a project?

On 2013-12-03 17:09, Sean Dague wrote: On 12/03/2013 05:50 PM, Mark McLoughlin wrote: On Tue, 2013-12-03 at 16:23 -0600, Ben Nemec wrote: On 2013-12-03 15:56, Sean Dague wrote: This cinder patch - https://review.openstack.org/#/c/48935/ Is blocked on failing upgrade because the updated oslo l

Re: [openstack-dev] creating a default for oslo config variables within a project?

On 12/03/2013 05:50 PM, Mark McLoughlin wrote: > On Tue, 2013-12-03 at 16:23 -0600, Ben Nemec wrote: >> On 2013-12-03 15:56, Sean Dague wrote: >>> This cinder patch - https://review.openstack.org/#/c/48935/ >>> >>> Is blocked on failing upgrade because the updated oslo lockutils won't >>> function

Re: [openstack-dev] When should things get added to Oslo.Incubator

On Tue, 2013-12-03 at 22:44 +, Joshua Harlow wrote: > Sure sure, let me not make that assumption (can't speak for them), but > even libraries on pypi have to deal with API instability. Yes, they do ... either by my maintaining stability, bumping their major version number to reflect an incompa

Re: [openstack-dev] creating a default for oslo config variables within a project?

On Tue, 2013-12-03 at 16:23 -0600, Ben Nemec wrote: > On 2013-12-03 15:56, Sean Dague wrote: > > This cinder patch - https://review.openstack.org/#/c/48935/ > > > > Is blocked on failing upgrade because the updated oslo lockutils won't > > function until there is a specific configuration variable

Re: [openstack-dev] When should things get added to Oslo.Incubator

Sure sure, let me not make that assumption (can't speak for them), but even libraries on pypi have to deal with API instability. Just more of suggesting, might as well bite the bullet (if objects folks feel ok with this) and just learn to deal with the pypi method for dealing with API instability

Re: [openstack-dev] When should things get added to Oslo.Incubator

On 12/03/2013 05:30 PM, Mark McLoughlin wrote: On Wed, 2013-12-04 at 10:42 +1300, Robert Collins wrote: Hey - https://review.openstack.org/#/c/57022/7//COMMIT_MSG - I strongly suggested here that reusing the Nova object code is the first step towards an objects library, and that we should be put

Re: [openstack-dev] When should things get added to Oslo.Incubator

On Tue, 2013-12-03 at 22:31 +, Joshua Harlow wrote: > Sure, no one has said it. But it seems to be implied, otherwise these > types of discussions wouldn't occur. Right? You're assuming the Nova objects API is at a point where the maintainers of it feel ready to commit to API stability. Mark.

Re: [openstack-dev] creating a default for oslo config variables within a project?

We can't do that. It used to behave that way, which led to https://bugs.launchpad.net/cinder/+bug/1065531 -Ben On 2013-12-03 16:22, Davanum Srinivas wrote: Should we update oslo-incubator first to? default=os.environ.get("OSLO_LOCK_PATH") or tempfile.mkdtemp() -- dims On Tue, Dec 3, 2013 a

Re: [openstack-dev] When should things get added to Oslo.Incubator

Sure, no one has said it. But it seems to be implied, otherwise these types of discussions wouldn't occur. Right? On 12/3/13 2:25 PM, "Mark McLoughlin" wrote: >On Tue, 2013-12-03 at 22:07 +, Joshua Harlow wrote: > >> Process for process sake imho has been a problem for oslo. > >It's been rei

Re: [openstack-dev] creating a default for oslo config variables within a project?

On 2013-12-03 15:56, Sean Dague wrote: This cinder patch - https://review.openstack.org/#/c/48935/ Is blocked on failing upgrade because the updated oslo lockutils won't function until there is a specific configuration variable added to the cinder.conf. That work around is proposed here - https

Re: [openstack-dev] When should things get added to Oslo.Incubator

On Wed, 2013-12-04 at 10:42 +1300, Robert Collins wrote: > Hey - https://review.openstack.org/#/c/57022/7//COMMIT_MSG - I > strongly suggested here that reusing the Nova object code is the first > step towards an objects library, and that we should be putting it in > olso; there are some reasonable

Re: [openstack-dev] VMware Workstation / Fusion / Player Nova driver

On 12/03/2013 04:59 PM, Alessandro Pilotti wrote: > BTW didn't you want to come to the Hyper-V session in HK to talk about this > (off)topic? :-) Yeah. I'm sorry I couldn't be there. Conflicts at the design summit are both tough and unavoidable. I sometimes have sessions in other tracks that I

Re: [openstack-dev] [Oslo] Layering olso.messaging usage of config

Of course ;-) Another question that¹s come up recently. Python 3.3 support? Will oslo.messaging achieve that? Maybe its a later goal, but it seems like one that is required (and should almost be expected of new libraries imho). Thoughts? Seems to be mainly eventlet that is the blocker for oslo.mes

Re: [openstack-dev] When should things get added to Oslo.Incubator

On 12/03/2013 05:15 PM, Davanum Srinivas wrote: Robert, I believe some code is in Ironic too [1]. The 2 choices are in Oslo are: 1) copy code to oslo-incubator 2) start a new oslo.objects(?) repo In the summit meeting, we have been trying to break existing code into libraries so #1 is probably

Re: [openstack-dev] When should things get added to Oslo.Incubator

On Tue, 2013-12-03 at 22:07 +, Joshua Harlow wrote: > Process for process sake imho has been a problem for oslo. It's been reiterated many times, but again - the only purpose of oslo-incubator is as a place to evolve an API until we're ready to make a commitment to API stability. It's often

Re: [openstack-dev] creating a default for oslo config variables within a project?

Should we update oslo-incubator first to? default=os.environ.get("OSLO_LOCK_PATH") or tempfile.mkdtemp() -- dims On Tue, Dec 3, 2013 at 4:56 PM, Sean Dague wrote: > This cinder patch - https://review.openstack.org/#/c/48935/ > > Is blocked on failing upgrade because the updated oslo lockutils w

Re: [openstack-dev] When should things get added to Oslo.Incubator

Robert, I believe some code is in Ironic too [1]. The 2 choices are in Oslo are: 1) copy code to oslo-incubator 2) start a new oslo.objects(?) repo In the summit meeting, we have been trying to break existing code into libraries so #1 is probably counter-productive. If the code churn in the file

Re: [openstack-dev] [Cinder] Cloning vs copying images

Hi Dmitry, Currently, the GPFS Cinder driver can use GPFS's file cloning mechanism when creating a bootable volume from Glance if the source image is RAW. If the source image is not raw, the driver creates the boot volume by converting the source image to RAW. Regards, Bill Owen billo...@us.ibm

Re: [openstack-dev] When should things get added to Oslo.Incubator

Why not just make it a pypi party library from the start? Call it 'super-objects' or something. Why does it have to be connected to oslo.incubator? Process for process sake imho has been a problem for oslo. Why not just go straight to building a library (does it matter if it's in oslo?) that is

Re: [openstack-dev] VMware Workstation / Fusion / Player Nova driver

> On 03.12.2013, at 21:20, "Russell Bryant" wrote: > >> On 12/03/2013 04:27 AM, Daniel P. Berrange wrote: >>> On Mon, Dec 02, 2013 at 07:23:19PM +, Alessandro Pilotti wrote: >>> >>> On 02 Dec 2013, at 04:52 , Kyle Mestery (kmestery) >>> wrote: >>> This is very cool Alessandro, than

[openstack-dev] creating a default for oslo config variables within a project?

This cinder patch - https://review.openstack.org/#/c/48935/ Is blocked on failing upgrade because the updated oslo lockutils won't function until there is a specific configuration variable added to the cinder.conf. That work around is proposed here - https://review.openstack.org/#/c/52070/3 Howe

Re: [openstack-dev] [Keystone] Store quotas in Keystone

John Dickinson wrote: > How are you proposing that this integrate with Swift's account and container > quotas (especially since there may be hundreds of thousands of accounts and > millions (billions?) of containers in a single Swift cluster)? A centralized > lookup for quotas doesn't really see

[openstack-dev] When should things get added to Oslo.Incubator

Hey - https://review.openstack.org/#/c/57022/7//COMMIT_MSG - I strongly suggested here that reusing the Nova object code is the first step towards an objects library, and that we should be putting it in olso; there are some reasonable concerns about this being experimental but... The Oslo wiki pag

Re: [openstack-dev] Package from Debian for Devstack?

On Tue, Dec 3, 2013 at 3:51 PM, Adam Young wrote: > On 12/02/2013 08:20 PM, Chuck Short wrote: > > > > > On Mon, Dec 2, 2013 at 6:21 PM, Sean Dague wrote: > >> On 12/02/2013 06:15 PM, Adam Young wrote: >> > In order to provide Devstack a better certificate management example, we >> > want to ma

Re: [openstack-dev] Package from Debian for Devstack?

On 12/02/2013 08:20 PM, Chuck Short wrote: On Mon, Dec 2, 2013 at 6:21 PM, Sean Dague > wrote: On 12/02/2013 06:15 PM, Adam Young wrote: > In order to provide Devstack a better certificate management example, we > want to make devstack capable of callin

Re: [openstack-dev] Tool for detecting commonly misspelled words

On 12/03/2013 03:43 PM, Jay S Bryant wrote: > */ > Jay S. Bryant/* >/IBM Cinder Subject Matter Expert & Cinder Core Member/ > Sorry, but ... does your email signature seriously have an image of the OpenStack logo and cinder block in it? I think that was so distracting

Re: [openstack-dev] [savanna] neutron floating IP assignment unexpected

Hi Jon, If AUTO_ASSIGNMENT_ENABLED is disabled, Savanna dashboard asks for floating IP network during node group template creation. Probably you have chosen some network in it. Right value in your case is 'Do not assign floating IPs'. Thanks, Andrew. On Tue, Dec 3, 2013 at 11:38 AM, Jon Maron

Re: [openstack-dev] Tool for detecting commonly misspelled words

On Tue, Dec 3, 2013 at 12:46 PM, John Griffith wrote: > On Tue, Dec 3, 2013 at 11:38 AM, Russell Bryant > wrote: > > On 12/03/2013 09:22 AM, Joe Gordon wrote: > >> HI all, > >> > >> Recently I have seen a few patches fixing a few typos. I would like to > >> point out a really nifty tool to detec

Re: [openstack-dev] Tool for detecting commonly misspelled words

Since I am one of those people that comments on spelling and grammar ... If you use emacs for your coding you can add the following to help catch spelling issues: http://www.emacswiki.org/emacs/FlySpell There is also git-commit-mode: http://www.emacswiki.org/emacs/GitCommitMode which ensures

[openstack-dev] [Neutron][IPv6] Stackers Brainstorming session on Neutron IPv6

Hi, folks: We plan to host a webex meeting tonight at 9pm EST (UTC-5) to have a brainstorming session on Neutron IPv6 readiness. As suggested by Sean Collins, the chair of Neutron IPv6 sub-team, I expand the invitation to this mailer. If you are interested in this topic, please feel free to joi

[openstack-dev] [nova][vmware] VMwareAPI sub-team status update 2013-12-03

Greetings Stackers, In our last IRC meeting for the VMwareAPI sub-team we identified our blueprint priority order for the vmwareapi driver's blueprints... 2 are ready to go in review. The last one we'll have to catch in Icehouse-2. Blueprint priorities *. https://blueprints.launchpad.net/opens

Re: [openstack-dev] [Nova] New API requirements, review of GCE

On 12/03/2013 03:15 PM, Eric Windisch wrote: >> One other issue with the proposed GCE changes is that it uses the custom >> wsgi which we are trying to phase out eventually. Should we be suggesting >> that new APIs use Pecan/WSME? > > Nova isn't using Pecan/WSME for any of its API services. Is No

Re: [openstack-dev] VMware Workstation / Fusion / Player Nova driver

On 12/03/2013 04:27 AM, Daniel P. Berrange wrote: > On Mon, Dec 02, 2013 at 07:23:19PM +, Alessandro Pilotti wrote: >> >> On 02 Dec 2013, at 04:52 , Kyle Mestery (kmestery) >> wrote: >> >>> This is very cool Alessandro, thanks for sharing! Any plans to try and get >>> this >>> nova

Re: [openstack-dev] Tool for detecting commonly misspelled words

On Tue, Dec 3, 2013 at 1:05 PM, Russell Bryant wrote: > On 12/03/2013 01:46 PM, John Griffith wrote: >> On Tue, Dec 3, 2013 at 11:38 AM, Russell Bryant wrote: >>> On 12/03/2013 09:22 AM, Joe Gordon wrote: HI all, Recently I have seen a few patches fixing a few typos. I would like

Re: [openstack-dev] [Nova] New API requirements, review of GCE

> One other issue with the proposed GCE changes is that it uses the custom > wsgi which we are trying to phase out eventually. Should we be suggesting > that new APIs use Pecan/WSME? Nova isn't using Pecan/WSME for any of its API services. Is Nova truly going in this direction? I'd think that con

Re: [openstack-dev] [scheduler] External scheduler design doc + review

On 12/03/2013 11:05 AM, Debojyoti Dutta wrote: > Hi > > I think we should do a review of the design doc review and have rough > consensus (that it should work) followed by running code. …. > > As of now all the design stuff is supposedly in (as per the scheduler > meeting today) > https://etherp

Re: [openstack-dev] [Nova][Schduler] Volunteers wanted for a modest proposal for an external scheduler in our lifetime

On 12/03/2013 03:17 AM, Robert Collins wrote: > The team size was a minimum, not a maximum - please add your names. > > We're currently waiting on the prerequisite blueprint to land before > work starts in earnest; and for the blueprint to be approved (he says, > without having checked to see if i

Re: [openstack-dev] [Nova][Schduler] Volunteers wanted for a modest proposal for an external scheduler in our lifetime

On 12/03/2013 03:17 AM, Robert Collins wrote: > The team size was a minimum, not a maximum - please add your names. > > We're currently waiting on the prerequisite blueprint to land before > work starts in earnest; and for the blueprint to be approved (he says, > without having checked to see if i

Re: [openstack-dev] Tool for detecting commonly misspelled words

On 12/03/2013 02:05 PM, John Griffith wrote: > That being said, I realize people will continue to this sort of thing > (it's very important to get your -1 counts in the review stats) Minor note ... this is part of what the Disagreements stat helps point out. If you come around and +2 something af

Re: [openstack-dev] Tool for detecting commonly misspelled words

On 12/03/2013 01:46 PM, John Griffith wrote: > On Tue, Dec 3, 2013 at 11:38 AM, Russell Bryant wrote: >> On 12/03/2013 09:22 AM, Joe Gordon wrote: >>> HI all, >>> >>> Recently I have seen a few patches fixing a few typos. I would like to >>> point out a really nifty tool to detect commonly misspe

Re: [openstack-dev] Tool for detecting commonly misspelled words

On 12/03/2013 02:05 PM, John Griffith wrote: On Tue, Dec 3, 2013 at 11:54 AM, Nachi Ueno wrote: 2013/12/3 John Griffith : On Tue, Dec 3, 2013 at 11:38 AM, Russell Bryant wrote: On 12/03/2013 09:22 AM, Joe Gordon wrote: HI all, Recently I have seen a few patches fixing a few typos. I would

[openstack-dev] [savanna] neutron floating IP assignment unexpected

Hi, I have the following configuration in savanna.conf: # If set to True, Savanna will use floating IPs to communicate # with instances. To make sure that all instances have # floating IPs assigned in Nova Network set # "auto_assign_floating_ip=True" in nova.conf.If Neutron is # used for networ

Re: [openstack-dev] Tool for detecting commonly misspelled words

On Tue, Dec 3, 2013 at 12:18 PM, Nachi Ueno wrote: > 2013/12/3 John Griffith : >> On Tue, Dec 3, 2013 at 11:54 AM, Nachi Ueno wrote: >>> 2013/12/3 John Griffith : On Tue, Dec 3, 2013 at 11:38 AM, Russell Bryant wrote: > On 12/03/2013 09:22 AM, Joe Gordon wrote: >> HI all, >> >>>

Re: [openstack-dev] Tool for detecting commonly misspelled words

2013/12/3 John Griffith : > On Tue, Dec 3, 2013 at 11:54 AM, Nachi Ueno wrote: >> 2013/12/3 John Griffith : >>> On Tue, Dec 3, 2013 at 11:38 AM, Russell Bryant wrote: On 12/03/2013 09:22 AM, Joe Gordon wrote: > HI all, > > Recently I have seen a few patches fixing a few typos. I

Re: [openstack-dev] Tool for detecting commonly misspelled words

On Tue, Dec 3, 2013 at 10:46 AM, John Griffith wrote: > On Tue, Dec 3, 2013 at 11:38 AM, Russell Bryant > wrote: > > On 12/03/2013 09:22 AM, Joe Gordon wrote: > >> HI all, > >> > >> Recently I have seen a few patches fixing a few typos. I would like to > >> point out a really nifty tool to detec

Re: [openstack-dev] [Nova][Schduler] Volunteers wanted for a modest proposal for an external scheduler in our lifetime

I totally agree on this meta level scheduler aspect. This should separate the placement decision making logic (for resources of any type, but can start on Nova resources) from their actual creation, say VM creation. This way the placement decisions can be relayed to the individual components

Re: [openstack-dev] Tool for detecting commonly misspelled words

On Tue, Dec 3, 2013 at 11:54 AM, Nachi Ueno wrote: > 2013/12/3 John Griffith : >> On Tue, Dec 3, 2013 at 11:38 AM, Russell Bryant wrote: >>> On 12/03/2013 09:22 AM, Joe Gordon wrote: HI all, Recently I have seen a few patches fixing a few typos. I would like to point out a re

Re: [openstack-dev] [horizon] Enhance UX of Launch Instance Form

(Previous mail went out a bit fast) These features could be developed iteratively to improve upon the existing code base: - First allow the modal view system to expand for better usage of screen real-estate combined with responsiveness of the whole popin - Then rework existing menus to simp

Re: [openstack-dev] [horizon] Enhance UX of Launch Instance Form

(Previous mail went out a bit fast) These features could be developed iteratively to improve upon the existing code base: - First allow the modal view system to expand for better usage of screen real-estate combined with responsiveness of the whole popin - Then rework existing menus to simp

Re: [openstack-dev] Tool for detecting commonly misspelled words

2013/12/3 John Griffith : > On Tue, Dec 3, 2013 at 11:38 AM, Russell Bryant wrote: >> On 12/03/2013 09:22 AM, Joe Gordon wrote: >>> HI all, >>> >>> Recently I have seen a few patches fixing a few typos. I would like to >>> point out a really nifty tool to detect commonly misspelled words. So >>>

Re: [openstack-dev] Tool for detecting commonly misspelled words

On Tue, Dec 3, 2013 at 11:38 AM, Russell Bryant wrote: > On 12/03/2013 09:22 AM, Joe Gordon wrote: >> HI all, >> >> Recently I have seen a few patches fixing a few typos. I would like to >> point out a really nifty tool to detect commonly misspelled words. So >> next time you want to fix a typo,

Re: [openstack-dev] [Nova][Schduler] Volunteers wanted for a modest proposal for an external scheduler in our lifetime

I agree with RussellB on this … if the forklift's goal is to just separate the scheduler, there should be no new features etc till the forklift is done and it should work as is with very minor config changes. A scheduler has several features like place resources correctly, for example. Ideally, th

Re: [openstack-dev] Tool for detecting commonly misspelled words

On 12/03/2013 09:22 AM, Joe Gordon wrote: > HI all, > > Recently I have seen a few patches fixing a few typos. I would like to > point out a really nifty tool to detect commonly misspelled words. So > next time you want to fix a typo, instead of just fixing a single one > you can go ahead and fi

Re: [openstack-dev] [nova][heat][[keystone] RFC: introducing "request identification"

On 11/29/13 at 03:56pm, haruka tanizawa wrote: Thank you for your reply. I completely misunderstood. You're correct on request_id and task_id. What I'm planning is a string field that a user can pass in with the request and it will be part of the task representation. That field will have no m

Re: [openstack-dev] Tool for detecting commonly misspelled words

Great tool especially for non-native guys such as me! Thanks Joe Best Nachi 2013/12/3 Sylvain Bauza : > Great tool ! > Just discovered that openstack.common.rpc does have typos, another good > reason to migrate to oslo.messaging.rpc :-) > > -Sylvain > > > 2013/12/3 Joe Gordon >> >> HI all, >> >

Re: [openstack-dev] [openstack-tc] Incubation Request for Barbican

On 12/03/2013 01:26 PM, Russell Bryant wrote: > Unless the requirements change, so far it > looks like this request should be deferred a bit longer. And note that this is just my opinion, and note a statement of position on behalf of the entire TC. We can still officially consider the request at

Re: [openstack-dev] [Solum] CLI minimal implementation

On 12/03/2013 11:45 AM, Jay Pipes wrote: > On 12/03/2013 11:39 AM, Arati Mahimane wrote: >> Randall, I think you are talking about required parameters and we are >> talking about optional ones. >> Please correct me if I am wrong. > > Russell was specifically talking about required parameters being

Re: [openstack-dev] [openstack-tc] Incubation Request for Barbican

On 12/03/2013 11:40 AM, Jarret Raim wrote: > >> I think there's something else you should take under consideration. >> Oslo messaging is not just an OpenStack library. It's the RPC library >> that all projects are relying on and one of the strong goals we have >> in OpenStack is to reduce code and

Re: [openstack-dev] welcoming new committers

On 10/31/2013 11:49 AM, Stefano Maffulli wrote: > Another idea that Tom suggested is to use gerrit automation to send back > to first time committers something in addition to the normal 'your patch > is waiting for review' message. The message could be something like: [...] Tom sent a patch for re

Re: [openstack-dev] [Nova][Schduler] Volunteers wanted for a modest proposal for an external scheduler in our lifetime

On 12/03/2013 07:22 AM, Boris Pavlovic wrote: > Hi all, > > > Finally found a bit time to write my thoughts. > > There are few blockers that make really complex to build scheduler as a > services or even to move main part of scheduler code to separated lib. > We already have one unsuccessfully e

Re: [openstack-dev] [Keystone] Store quotas in Keystone

On Dec 3, 2013 6:49 PM, "John Dickinson" wrote: > > > On Dec 3, 2013, at 8:05 AM, Jay Pipes wrote: > > > On 12/03/2013 10:04 AM, John Dickinson wrote: > >> How are you proposing that this integrate with Swift's account and container quotas (especially since there may be hundreds of thousands of a

Re: [openstack-dev] [openstack-tc] Incubation Request for Barbican

On 2013-12-03 16:43:32 + (+), Jarret Raim wrote: > This is great, thanks for the link. Would there be any objections to > adding this to the github repo I think you meant the "git" repo. What's a gi-thub? http://git.openstack.org/cgit/openstack/oslo.messaging/tree/doc/source/ > > and the

Re: [openstack-dev] [nova][heat][[keystone] RFC: introducing "request identification"

On 11/27/2013 12:45 AM, Takahiro Shida wrote: Hi all, I'm also interested in this issue. > Create a unified request identifier > https://blueprints.launchpad.net/nova/+spec/cross-service-request-id I checked this BP and the following review. https://review.openstack.org/#/c/29480/ There are

Re: [openstack-dev] [Solum] CLI minimal implementation

On Mon, Dec 2, 2013 at 10:09 PM, Adrian Otto wrote: > Sorry, I changed the link. We originally started with hyphenated > noun-verbs but switched to the current proposal upon receipt of advice that > it would be more compatible with the next version of the cliff based CLI > for OpenStack. If I rem

Re: [openstack-dev] [Neutron][LBaaS] Vote required for certificate as first-class citizen - SSL Termination (Revised)

Hi, The primary reason for the "simple" proposal is due to the difficult to reach consensus on how SSL certificates can be stored in OpenStack. As there is currently no "trusted" storage in OpenStack, the "simple" proposal overcomes this by pushing the SSL certificates into the load balancers wh

Re: [openstack-dev] [Keystone] Store quotas in Keystone

On 12/03/2013 11:40 AM, John Dickinson wrote: On Dec 3, 2013, at 8:05 AM, Jay Pipes wrote: On 12/03/2013 10:04 AM, John Dickinson wrote: How are you proposing that this integrate with Swift's account and container quotas (especially since there may be hundreds of thousands of accounts and

Re: [openstack-dev] Plugin Blueprint and ML2 Plugin

On Dec 3, 2013, at 10:13 AM, NAVEEN R K REDDY wrote: > > Hi All, > > I have couple of questions wrt to plugin blueprint and ml2 plugin, > > 1. We are planning to submit the plugin into Openstack Icehouse release. The > question we have is there any deadline for the plugin blueprint submissio

Re: [openstack-dev] Incubation Request for Barbican

On Dec 3, 2013 6:45 PM, "Jarret Raim" wrote: > > > >With the introduction of programs (think: official teams), all > >incubated/integrated projects must belong to an official program... So > >when a project applies for incubation but is not part of an official > >program yet, it de-facto also appl

[openstack-dev] [neutron] [policy] Neutron Policy IRC meeting

Hello everybody, Following up the action items from our last meeting and in preparation for our next IRC meeting on Dec 5th (see below), I have started updating the google document [1]. I have added the tables describing the attributes of new Neutron objects. I will be also working on adding a fe

[openstack-dev] [horizon] Enhance UX of Launch Instance Form

Hi there I read the proposal and related documentation, and intend to start implementing it into horizon. Regards on Wed Nov 20 15:09:05 UTC 2013 C?dric Soulas Wrote > > >Thanks for all the feedback on the "Enhance UX of launch instance form" >subject and its prototype. > >Try the latest versi

Re: [openstack-dev] [Neutron] DHCP Agent Reliability

On 03/12/13 16:08, Maru Newby wrote: I've been investigating a bug that is preventing VM's from receiving IP addresses when a Neutron service is under high load: https://bugs.launchpad.net/neutron/+bug/1192381 High load causes the DHCP agent's status updates to be delayed, causing the Neutron

Re: [openstack-dev] [Solum] CLI minimal implementation

On 12/03/2013 11:39 AM, Arati Mahimane wrote: Randall, I think you are talking about required parameters and we are talking about optional ones. Please correct me if I am wrong. Russell was specifically talking about required parameters being positional arguments. Best, -jay __

Re: [openstack-dev] [Solum] CLI minimal implementation

Roshan, I have added some comments to the Etherpad - https://etherpad.openstack.org/p/MinimalCLI -Arati On 12/3/13 10:27 AM, "Randall Burt" wrote: >I disagree. If a param is required and has no meaningful default, it >should be positional IMO. I think this actually reduces confusion as you >can

Re: [openstack-dev] [openstack-tc] Incubation Request for Barbican

> The API and developer documentation is at >http://docs.openstack.org/developer/oslo.messaging/ This is great, thanks for the link. Would there be any objections to adding this to the github repo and the openstack wiki pages? I spent a bunch of time looking and wasn¹t able to turn this up. Add

  1   2   >