Re: [openstack-dev] [oslo] usage patterns for oslo.config

Hi Alistair, Modules can register their own options and there is no need to call reload_config_files. The config files are parsed and values stored in case the option is later declared. The only time you need to reload files is if you add new config files in the new module. See the example code

Re: [openstack-dev] [cinder] Bug#1231298 - size parameter for volume creation

On Aug 8, 2014, at 6:55 AM, Dean Troyer wrote: > On Fri, Aug 8, 2014 at 12:36 AM, Ganapathy, Sandhya > wrote: > This is to discuss Bug #1231298 – > https://bugs.launchpad.net/cinder/+bug/1231298 > > ... > Conclusion reached with this bug is that, we need to modify cinder client in > order

Re: [openstack-dev] [all] The future of the integrated release

On Aug 13, 2014, at 5:07 AM, Daniel P. Berrange wrote: > On Wed, Aug 13, 2014 at 12:55:48PM +0100, Steven Hardy wrote: >> On Wed, Aug 13, 2014 at 11:42:52AM +0100, Daniel P. Berrange wrote: >>> On Thu, Aug 07, 2014 at 03:56:04AM -0700, Jay Pipes wrote: >>> By ignoring stable branches, leaving it

Re: [openstack-dev] [oslo] Issues with POSIX semaphores and other locks in lockutils

This may be slightly off-topic but it is worth mentioning that the use of threading.Lock[1] which was included to make the locks thread safe seems to be leading to a deadlock in eventlet[2]. It seems like we have rewritten this too many times in order to fix minor pain points and are adding risk

Re: [openstack-dev] Criteria for giving a -1 in a review

On Aug 21, 2014, at 9:42 AM, Adam Young wrote: > On 08/21/2014 12:34 PM, Dolph Mathews wrote: >> >> On Thu, Aug 21, 2014 at 11:21 AM, Daniel P. Berrange >> wrote: >> On Thu, Aug 21, 2014 at 05:05:04PM +0100, Matthew Booth wrote: >> > "I would prefer that you didn't merge this." >> > >> > i.e.

Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

On Sep 4, 2014, at 3:24 AM, Daniel P. Berrange wrote: > Position statement > == > > Over the past year I've increasingly come to the conclusion that > Nova is heading for (or probably already at) a major crisis. If > steps are not taken to avert this, the project is likely to lo

Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

On Sep 4, 2014, at 8:33 AM, Daniel P. Berrange wrote: > On Thu, Sep 04, 2014 at 01:36:04PM +, Gary Kotton wrote: >> Hi, >> I do not think that Nova is in a death spiral. I just think that the >> current way of working at the moment is strangling the project. I do not >> understand why we nee

Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

On Sep 5, 2014, at 4:12 AM, Sean Dague wrote: > On 09/05/2014 06:40 AM, Nikola Đipanov wrote: >> >> >> Just some things to think about with regards to the whole idea, by no >> means exhaustive. > > So maybe the better question is: what are the top sources of technical > debt in Nova that we n

Re: [openstack-dev] Thoughts on OpenStack Layers and a Big Tent model

Great writeup. I think there are some great concrete suggestions here. A couple more: 1. I think we need a better name for Layer #1 that actually represents what the goal of it is: Infrastructure Services? 2. We need to be be open to having other Layer #1s within the community. We should allow

Re: [openstack-dev] battling stale .pyc files

On Sep 15, 2014, at 4:34 AM, Lucas Alvares Gomes wrote: > So, although I like the fix proposed and I would +1 that idea, I'm > also not very concerned if most of the people don't want that. Because > as you just said we can fix it locally easily. I didn't set it to my > .local but the way I do n

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

On Nov 15, 2013, at 8:28 AM, Russell Bryant wrote: > Greetings, > > We've talked a lot about requirements for new compute drivers [1]. I > think the same sort of standards shold be applied for a new third-party > API, such as the GCE API [2]. > > Before we can consider taking on a new API, it

[openstack-dev] [nova] [QA] Triaging Bugs during Review

Hi Everyone, I tend to follow merges and look for valuable havana backports. A few bug fixes have merged recently where the associated bug is untriaged (i.e. the severity is listed as 'Unknown'). I assume that reviewers of a bugfix patch are viewing the associated bugs. It makes sense for core-rev

Re: [openstack-dev] [nova] [QA] Triaging Bugs during Review

On Nov 26, 2013, at 2:26 PM, Mark McLoughlin wrote: > On Tue, 2013-11-26 at 13:06 -0800, Vishvananda Ishaya wrote: >> Hi Everyone, >> >> I tend to follow merges and look for valuable havana backports. A few bug >> fixes have merged recently where the associated

Re: [openstack-dev] problems with rabbitmq on HA controller failure...anyone seen this?

On Nov 29, 2013, at 9:24 PM, Chris Friesen wrote: > On 11/29/2013 06:37 PM, David Koo wrote: >> On Nov 29, 02:22:17 PM (Friday), Chris Friesen wrote: >>> We're currently running Grizzly (going to Havana soon) and we're >>> running into an issue where if the active controller is ungracefully >>>

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

Very cool stuff! Seeing your special glance properties for iso and floppy connections made me think of something. They seem, but it would be nice if they were done in a way that would work in any hypervisor. I "think" we have sufficient detail in block_device_mapping to do essentially the same

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

On Dec 2, 2013, at 9:12 AM, Russell Bryant wrote: > On 12/02/2013 10:59 AM, Gary Kotton wrote: >> I think that this is certainly different. It is something that we we want >> and need a user facing API. >> Examples: >> - aggregates >> - per host scheduling >> - instance groups >> >> Etc. >> >>

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

On Dec 2, 2013, at 11:40 AM, Alessandro Pilotti wrote: > > On 02 Dec 2013, at 20:54 , Vishvananda Ishaya wrote: > >> Very cool stuff! >> >> Seeing your special glance properties for iso and floppy connections made me >> think >> of something. They

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

On Dec 2, 2013, at 12:38 PM, Russell Bryant wrote: > On 12/02/2013 03:31 PM, Vishvananda Ishaya wrote: >> >> On Dec 2, 2013, at 9:12 AM, Russell Bryant >> wrote: >> >>> On 12/02/2013 10:59 AM, Gary Kotton wrote: >>>> I think that this is cert

Re: [openstack-dev] [Neutron] Interfaces file format, was [Tempest] Need to prepare the IPv6 environment for static IPv6 injection test case

Hi Ian, The rendered network template was a legacy item that got stuck onto the config drive so we could remove file injection. It is not intended that this is the correct way to do net config. We have intended in the past to put a generic form of network info into the metadata service and conf

Re: [openstack-dev] [heat] [glance] Heater Proposal

On Dec 5, 2013, at 12:42 PM, Andrew Plunk wrote: >> Excerpts from Randall Burt's message of 2013-12-05 09:05:44 -0800: >>> On Dec 5, 2013, at 10:10 AM, Clint Byrum >>> wrote: >>> Excerpts from Monty Taylor's message of 2013-12-04 17:54:45 -0800: > Why not just use glance? >

Re: [openstack-dev] [heat] [glance] Heater Proposal

On Dec 6, 2013, at 10:07 AM, Georgy Okrokvertskhov wrote: > Hi, > > I am really inspired by this thread. Frankly saying, Glance for Murano was a > kind of sacred entity, as it is a service with a long history in OpenStack. > We even did not think in the direction of changing Glance. Spendin

Re: [openstack-dev] [heat] [glance] Heater Proposal

On Dec 6, 2013, at 10:38 AM, Clint Byrum wrote: > Excerpts from Jay Pipes's message of 2013-12-05 21:32:54 -0800: >> On 12/05/2013 04:25 PM, Clint Byrum wrote: >>> Excerpts from Andrew Plunk's message of 2013-12-05 12:42:49 -0800: > Excerpts from Randall Burt's message of 2013-12-05 09:05:44

Re: [openstack-dev] [neutron] Questions on logging setup for development

On Dec 6, 2013, at 2:09 PM, Paul Michali wrote: > Hi, > > For Neutron, I'm creating a module (one of several eventually) as part of a > new blueprint I'm working on, and the associated unit test module. I'm in > really early development, and just running this UT module as a standalone > scri

Re: [openstack-dev] Novnc switch to sockjs-client instead of websockify

This seems like a great choice, assuming that we can verify that it works properly. Vish On Dec 31, 2013, at 10:33 PM, Thomas Goirand wrote: > Hi, > > I was wondering if it would be possible for NoVNC to switch from > websockify to sockjs-client, which is available here: > > https://github.c

Re: [openstack-dev] [nova] where to expose network quota

On Jan 6, 2014, at 12:47 AM, Yaguang Tang wrote: > Hi all, > > Now Neutron has its own quota management API for network related > items(floating ips, security groups .etc) which are also manged by Nova. > when using nova with neutron as network service, the network related quota > items are

Re: [openstack-dev] [Gantt] Looking for some answers...

On Jan 6, 2014, at 11:02 AM, Jay Pipes wrote: > Hello Stackers, > > I was hoping to get some answers on a few questions I had regarding the > Gantt project [1]. Specifically, here are my queries: > > 1) Why was Nova forked to the http://github.com/openstack/gantt > repository? Forking Nova jus

Re: [openstack-dev] [Gantt] Looking for some answers...

SAP for it to be valuable outside of nova. Vish > > > > Best regards, > Boris Pavlovic > > > > > On Mon, Jan 6, 2014 at 11:30 PM, Vishvananda Ishaya > wrote: > > On Jan 6, 2014, at 11:02 AM, Jay Pipes wrote: > > > Hello Stackers, > >

Re: [openstack-dev] Proposal for instance-level snapshots in Nova

On Jan 6, 2014, at 3:50 PM, Jon Bernard wrote: > Hello all, > > I would like to propose instance-level snapshots as a feature for > inclusion in Nova. An initial draft of the more official proposal is > here [1], blueprint is here [2]. > > In a nutshell, this feature will take the existing cr

Re: [openstack-dev] [nova][neutron][ipv6]Hairpinning in libvirt, once more

The logic makes sense to me here. I’m including Evan Callicoat in this response in case he has any comments on the points you make below. Vish On Jan 7, 2014, at 4:57 AM, Ian Wells wrote: > See Sean Collins' review https://review.openstack.org/#/c/56381 which > disables hairpinning when Neut

Re: [openstack-dev] Proposal for instance-level snapshots in Nova

On Jan 14, 2014, at 2:10 PM, Jon Bernard wrote: > > >> As you’ve defined the feature so far, it seems like most of it could >> be implemented client side: >> >> * pause the instance >> * snapshot the instance >> * snapshot any attached volumes > > For the first milestone to offer crash-consi

Re: [openstack-dev] [oslo] dependency analysis for graduating more oslo libraries

On Jan 15, 2014, at 6:40 AM, Doug Hellmann wrote: > > > > On Wed, Jan 15, 2014 at 6:51 AM, Victor Sergeyev > wrote: > Hello All. > > As for lockutils - a few days ago I wondered why we used custom oslo module > instead of lockfile library [1]. AFAIK, it must be due to this bug [2] > (ple

Re: [openstack-dev] instance migration strangeness in devstack

This is probably more of a usage question, but I will go ahead and answer it. If you are writing to the root drive you may need to run the sync command a few times to make sure that the data has been flushed to disk before you kick off the migration. The confirm resize step should be deleting t

Re: [openstack-dev] [gantt] Sync up patches

On Jan 16, 2014, at 6:46 AM, Joe Gordon wrote: > > > > On Wed, Jan 15, 2014 at 1:29 PM, Dugger, Donald D > wrote: > My thought was to try and get some parallel effort going, do the resync as a > continuing task as suffer a little ongoing pain versus a large amount of pain > at the end. G

Re: [openstack-dev] instance migration strangeness in devstack

errors in syslog. > > I have been able to successfully migrate a Qcow2 backed instance. > Dan > > On 01/16/2014 03:18 AM, Vishvananda Ishaya wrote: >> This is probably more of a usage question, but I will go ahead and answer it. >> >> If you are writing to the

Re: [openstack-dev] question of vcpu-memory-hotplug progress

On Jan 15, 2014, at 7:36 PM, Wangshen (Peter) wrote: > Hi, all > We are interesting in vcpu-memory-hotplug under this link: > https://blueprints.launchpad.net/nova/+spec/vcpu-memory-hotplug > And we have already finished vcpu hotplug and done the basic tests. > > But this blueprint seems not b

Re: [openstack-dev] [nova] how is resource tracking supposed to work for live migration and evacuation?

On Jan 16, 2014, at 1:12 PM, Chris Friesen wrote: > Hi, > > I'm trying to figure out how resource tracking is intended to work for live > migration and evacuation. > > For a while I thought that maybe we were relying on the call to > ComputeManager._instance_update() in > ComputeManager.pos

Re: [openstack-dev] Proposal for instance-level snapshots in Nova

On Jan 16, 2014, at 1:28 PM, Jon Bernard wrote: > * Vishvananda Ishaya wrote: >> >> On Jan 14, 2014, at 2:10 PM, Jon Bernard wrote: >> >>> >>> >>>> As you’ve defined the feature so far, it seems like most of it could >>>&

Re: [openstack-dev] [Nova] why don't we deal with "claims" when live migrating an instance?

On Jan 16, 2014, at 9:41 PM, Jiang, Yunhong wrote: > I noticed the BP has been approved, but I really want to understand more on > the reason, can anyone provide me some hints? > > In the BP, it states that “For resize, we need to confirm, as we want to give > end user an opportunity to roll

Re: [openstack-dev] question of vcpu-memory-hotplug progress

On Jan 18, 2014, at 12:03 AM, Wangshen (Peter) wrote: >> -Original Message- >> From: Vishvananda Ishaya [mailto:vishvana...@gmail.com] >> Sent: Friday, January 17, 2014 1:01 AM >> To: OpenStack Development Mailing List (not for usage questions) >> Cc:

Re: [openstack-dev] [Neutron] Relationship between Neutron LBaaS and Libra

On Jan 19, 2014, at 8:19 AM, Clint Byrum wrote: > Excerpts from Thomas Herve's message of 2014-01-19 01:52:56 -0800: >> >>> Hi, >>> >>> I haven’t read through those (need to go spend time with family so replying >>> quickly) but given the dates the planning phases for Quantum/Neutron LBaaS >>>

Re: [openstack-dev] Havana Release V3 Extensions and new features to quota

Hi Vinod, Sorry for the top post, but there is a lot that needs to be done across projects to make the idea of domains and trees actually work. One of the issues which you mention below is the idea of quotas. I was just having a discussion with some folks in IRC about this very issue, and there

[openstack-dev] Hierarchicical Multitenancy Discussion

Hi Everyone, I apologize for the obtuse title, but there isn't a better succinct term to describe what is needed. OpenStack has no support for multiple owners of objects. This means that a variety of private cloud use cases are simply not supported. Specifically, objects in the system can only

Re: [openstack-dev] [nova][ec2-api]cmd "euca-describle-address" will return error. someone can help me?

Hi! Nice find, this is a bug. I have reported it along with instructions for fixing here: https://bugs.launchpad.net/nova/+bug/1273837 Vish On Jan 21, 2014, at 6:20 PM, li zheming wrote: > hi all: >I used euca2tool3.1.10 to test ec2 api.but when I do cmd > "euca-describle-address", it r

Re: [openstack-dev] [Nova] bp proposal: discovery of peer instances through metadata service

ces by the key_name used to launch the instance instead of security group. I don’t think it occurred to us to use security groups at the time. Note we also provided the number of cores, but this was for convienience because the mpi implementation didn’t support discovering number of cores. Code below

Re: [openstack-dev] Proposed Logging Standards

On Jan 27, 2014, at 6:57 PM, Christopher Yeoh wrote: > On Tue, Jan 28, 2014 at 12:55 AM, Sean Dague wrote: > On 01/27/2014 09:07 AM, Macdonald-Wallace, Matthew wrote: > > Hi Sean, > > > > I'm currently working on moving away from the "built-in" logging to use > > log_config= and the python log

Re: [openstack-dev] [nova]Why not allow to create a vm directly with two VIF in the same network

On Jan 24, 2014, at 6:33 AM, CARVER, PAUL wrote: > I agree that I’d like to see a set of use cases for this. This is the second > time in as many days that I’ve heard about a desire to have such a thing but > I still don’t think I understand any use cases adequately. > > In the physical worl

Re: [openstack-dev] Proposal for instance-level snapshots in Nova

On Jan 24, 2014, at 9:05 AM, Jon Bernard wrote: > * Vishvananda Ishaya wrote: >> >> On Jan 16, 2014, at 1:28 PM, Jon Bernard wrote: >> >>> * Vishvananda Ishaya wrote: >>>> >>>> On Jan 14, 2014, at 2:10 PM, Jon Bernard wrote: >>&

Re: [openstack-dev] [Nova] [Barbican] nova-cert information

I would not want to use nova-cert for something like this. It was a minimum viable option for supporting the ec2 upload bundle use case which requires certs to work. We also managed to get it working for our hacky vpn solution long ago, but it is definitely not a best practices case. Perhaps cer

Re: [openstack-dev] question of vcpu-memory-hotplug progress

On Jan 22, 2014, at 7:27 PM, Wangshen (Peter) wrote: >> -Original Message- >> From: Vishvananda Ishaya [mailto:vishvana...@gmail.com] >> Sent: Wednesday, January 22, 2014 2:26 AM >> To: OpenStack Development Mailing List (not for usage questions) >> Cc:

Re: [openstack-dev] Havana Release V3 Extensions and new features to quota

On Jan 29, 2014, at 3:55 AM, Vinod Kumar Boppanna wrote: > Dear Vishvananda, > > Sorry for very late reply. I was stupid not to follow your reply (i had > messed it some how). > > Actually, i am confused after seeing your mail. In the last two weeks, i was > doing some testing (creating us

Re: [openstack-dev] Hierarchicical Multitenancy Discussion

refer 1600 UTC. > > Florent Flament > > ----- Original Message - > From: "Vishvananda Ishaya" > To: "OpenStack Development Mailing List (not for usage questions)" > > Sent: Tuesday, January 28, 2014 7:35:15 PM > Subject: [openstack-dev] Hierarchicical M

Re: [openstack-dev] [Nova] bp proposal: discovery of peer instances through metadata service

could offer a filter on security groups > as well if this is useful. We might well also allow selection by > instance tags. The approach allows this, though I would like to keep > it as simple as possible at first (share with other instances in > project or don't share) > > Just

Re: [openstack-dev] Hierarchicical Multitenancy Discussion

the 2100 meeting. Thanks! Vish On Jan 29, 2014, at 7:59 AM, Vishvananda Ishaya wrote: > I apologize for the confusion. The Wiki time of 2100 UTC is the correct time > (Noon Pacific time). We can move tne next meeting to a different day/time > that is more convienient for Europe.

Re: [openstack-dev] [Nova][Neutron] nova-network in Icehouse and beyond

On Jan 29, 2014, at 10:45 AM, Dan Smith wrote: >> I was thinking for the upgrade process that we could leverage the port >> attach/detach BP done by Dan Smith a while ago. This has libvirt support >> and there are patches pending approval for Xen and Vmware. Not sure about >> the other drivers.

Re: [openstack-dev] [nova]Why not allow to create a vm directly with two VIF in the same network

On Jan 30, 2014, at 6:26 AM, CARVER, PAUL wrote: > Vishvananda Ishaya wrote: > > >In testing I have been unable to saturate a 10g link using a single VM. Even > >with multiple streams, > >the best I have been able to do (using virtio and vhost_net is about 7.8g. >

Re: [openstack-dev] Hierarchicical Multitenancy Discussion

Thanks Soren, you are correct! Yay Timezones Vish On Jan 30, 2014, at 10:39 AM, Soren Hansen wrote: > 2100 UTC is 1 PM Pacific. :-) > > Den 29/01/2014 17.01 skrev "Vishvananda Ishaya" : > I apologize for the confusion. The Wiki time of 2100 UTC is the correct time >

[openstack-dev] [keystone][nova] Re: Hierarchicical Multitenancy Discussion

al Multitenancy Meeting on Friday at 1600 UTC to discuss. Vish On Jan 28, 2014, at 10:35 AM, Vishvananda Ishaya wrote: > Hi Everyone, > > I apologize for the obtuse title, but there isn't a better succinct term to > describe what is needed. OpenStack has no support for multiple

Re: [openstack-dev] [keystone][nova] Re: Hierarchicical Multitenancy Discussion

logically fits in hierarchicical model. > Absolutely no (or minimal) changes to services (Nova, Swift ) > > ### Cons ### > Most of the changes is needed in Keystone and its data model (Domain, Roles). > Some change required in OSLO policy engine for policy evaluation. > Service

Re: [openstack-dev] [keystone][nova] Re: Hierarchicical Multitenancy Discussion

gt; service whether an action is authorized for a given token? So I threw out the idea the other day that quota enforcement should perhaps be done by gantt. Quotas seem to be a scheduling concern more than anything else. > > Florent Flament > > > > - Original Message

Re: [openstack-dev] [keystone][nova] Re: Hierarchicical Multitenancy Discussion

ave the > time to help with implementation, however. Come to the meeting on friday! 1600 UTC Vish > > - Chris > > > > On Feb 3, 2014, at 1:58 PM, Vishvananda Ishaya wrote: > >> Hello Again! >> >> At the meeting last week we discussed some options ar

Re: [openstack-dev] Hierarchicical Multitenancy Discussion

On Feb 5, 2014, at 6:54 AM, Florent Flament wrote: > Vish: > > I agree that having roles associated with projects may complicate > policy rules (although we may find ways to simplify the syntax?). It > may be a sound choice to stick to a single scope for a given token. > > +1 for your quotas

Re: [openstack-dev] [Nova] RFC: Generate API sample files from API schemas

On Feb 6, 2014, at 5:38 AM, Kenichi Oomichi wrote: > > Hi, > > I'd like to propose one idea that autogenerates API sample files from API > schema for Nova v3 API. > > We are working on API validation for v3 API, the works require API schema > which is defined with JSONSchema for each API. On

Re: [openstack-dev] Asynchrounous programming: replace eventlet with asyncio

On Feb 7, 2014, at 8:21 AM, Jesse Noller wrote: > > On Feb 7, 2014, at 1:51 AM, Chris Behrens wrote: > >> >> On Feb 6, 2014, at 11:07 PM, Joshua Harlow wrote: >> >>> +1 >>> >>> To give an example as to why eventlet implicit monkey patch the world isn't >>> especially great (although it's

Re: [openstack-dev] Asynchrounous programming: replace eventlet with asyncio

On Feb 7, 2014, at 10:25 AM, Yuriy Taraday wrote: > Hello, Vish! > > I hope you can provide some historical data. > > On Fri, Feb 7, 2014 at 9:37 PM, Vishvananda Ishaya > wrote: > To be clear, since many people weren’t around in ye olde days, nova started > usi

Re: [openstack-dev] [Nova] modify_image_attribute() in ec2_api is broken in Nova

This looks like a bug to me. It would be great if you could report it on launchpad. Vish On Feb 11, 2014, at 7:49 PM, wu jiang wrote: > Hi all, > > I met some problems when testing an ec2_api:'modify_image_attribute()' in > Nova. > I found the params send to Nova, are not suitable to match i

Re: [openstack-dev] Hierarchicical Multitenancy Discussion

Hi Vinod! I think you can simplify the roles in the hierarchical model by only passing the roles for the authenticated project and above. All roles are then inherited down. This means it isn’t necessary to pass a scope along with each role. The scope is just passed once with the token and the p

Re: [openstack-dev] OpenStack-dev Digest, Vol 22, Issue 39

jA2. So it is necessary to walk up the tree to find the full list of roles. Vish > > Regards, > Vinod Kumar Boppanna > ____ > Message: 21 > Date: Fri, 14 Feb 2014 10:13:59 -0800 > From: Vishvananda Ishaya > To: "OpenStack Develo

[openstack-dev] [keystone][nova]Hierarchical Multitenancy Meeting

Hi Everyone, I will be on a plane during the Multitenancy Meeting on Friday. You are welcome to have the meeting without me. Otherwise, we can just continue the excellent discussion we have been having on the Mailing list. Thanks, Vish signature.asc Description: Message signed with OpenPGP us

Re: [openstack-dev] Hierarchical Multitenancy and resource ownership

On Feb 18, 2014, at 11:31 AM, Martin, JC wrote: > > I see a lot of good things happening on the hierarchical multi tenancy > proposal that Vish made a while back. > > However, the focus so far is on roles and quota but could not find any > discussion related to resource ownership. > > Is th

Re: [openstack-dev] [Nova] Including Domains in Nova

Hi Henrique I disagree with the idea that the other services should use domains. They need a concept of hierarchical ownership which we have been discussiong. Domains is one way of representing such an ownership hierarchy but i think it is too limited. The POC code I created for hierarchical m

Re: [openstack-dev] [all][keystone] Increase of USER_ID length maximum from 64 to 255

On Mar 3, 2014, at 6:48 AM, Jay Pipes wrote: > On Sun, 2014-03-02 at 12:05 -0800, Morgan Fainberg wrote: >> Having done some work with MySQL (specifically around similar data >> sets) and discussing the changes with some former coworkers (MySQL >> experts) I am inclined to believe the move from

Re: [openstack-dev] [Nova] Concrete Proposal for Keeping V2 API

This seems like a reasonable and well thought out approach but It feels like we are removing our ability to innovate. I know we are worried about maintaining multiple APIs, but I’m still leaning towards putting the v3 API out and just keeping v2 around for a long time. Yes, its a maintenance burde

Re: [openstack-dev] [Nova] Concrete Proposal for Keeping V2 API

On Mar 4, 2014, at 9:10 AM, Russell Bryant wrote: > > Thank you all for your participation on this topic. It has been quite > controversial, but the API we expose to our users is a really big deal. > I'm feeling more and more confident that we're coming through this with > a much better underst

Re: [openstack-dev] [all][keystone] Increase of USER_ID length maximum from 64 to 255

On Mar 3, 2014, at 11:32 AM, Jay Pipes wrote: > On Mon, 2014-03-03 at 11:09 -0800, Vishvananda Ishaya wrote: >> On Mar 3, 2014, at 6:48 AM, Jay Pipes wrote: >> >>> On Sun, 2014-03-02 at 12:05 -0800, Morgan Fainberg wrote: >>>> Having done some work with MyS

Re: [openstack-dev] [OpenStack-dev][Nova] Migration stuck - resize/migrating

Migrate/resize uses scp to copy files back and forth with the libvirt driver. This shouldn’t be necessary with shared storage, but it may still need ssh configured between the user that nova is running as in order to complete the migration. It is also possible that there is a bug in the code pat

Re: [openstack-dev] [nova] Undead DB objects: ProviderFirewallRule and InstanceGroupPolicy?

AFAIK they are relics. Vish On Nov 13, 2014, at 7:20 AM, Matthew Booth wrote: > There are 3 db apis relating to ProviderFirewallRule: > provider_fw_rule_create, provider_fw_rule_get_all, and > provider_fw_rule_destroy. Of these, only provider_fw_rule_get_all seems > to be used. i.e. It seems th

Re: [openstack-dev] [Nova][Neutron] Error message when Neutron network is running out of IP addresses

It looks like this has not been reported so a bug would be great. It looks like it might be as easy as adding the NoMoreFixedIps exception to the list where FixedIpLimitExceeded is caught in nova/network/manager.py Vish On Nov 18, 2014, at 8:13 AM, Edgar Magana wrote: > Hello Community, > >

Re: [openstack-dev] [cinder] [qa] which core team members are diving into - http://status.openstack.org/elastic-recheck/#1373513

On Nov 25, 2014, at 7:29 AM, Matt Riedemann wrote: > > > On 11/25/2014 9:03 AM, Matt Riedemann wrote: >> >> >> On 11/25/2014 8:11 AM, Sean Dague wrote: >>> There is currently a review stream coming into Tempest to add Cinder v2 >>> tests in addition to the Cinder v1 tests. At the same time t

Re: [openstack-dev] [Nova] Spring cleaning nova-core

ople for their contributions over the years: > > * cbehrens: Chris Behrens > * vishvananda: Vishvananda Ishaya Thank you Michael. I knew this would happen eventually. I am around and I still do reviews from time to time, so everyone feel free to ping me on irc if there are specific review

Re: [openstack-dev] [Nova][Neutron] out-of-tree plugin for Mech driver/L2 and vif_driver

On Dec 11, 2014, at 2:41 AM, Daniel P. Berrange wrote: > On Thu, Dec 11, 2014 at 09:37:31AM +0800, henry hly wrote: >> On Thu, Dec 11, 2014 at 3:48 AM, Ian Wells wrote: >>> On 10 December 2014 at 01:31, Daniel P. Berrange >>> wrote: So the problem of Nova review bandwidth is a

Re: [openstack-dev] [Neutron] UniqueConstraint for name and tenant_id in security group

On Dec 11, 2014, at 8:00 AM, Henry Gessau wrote: > On Thu, Dec 11, 2014, Mark McClain wrote: >> >>> On Dec 11, 2014, at 8:43 AM, Jay Pipes >> > wrote: >>> >>> I'm generally in favor of making name attributes opaque, utf-8 strings that >>> are entirely user-defined a

Re: [openstack-dev] Reason for mem/vcpu ratio in default flavors

Probably just a historical artifact of values that we thought were reasonable for our machines at NASA. Vish On Dec 11, 2014, at 8:35 AM, David Kranz wrote: > Perhaps this is a historical question, but I was wondering how the default > OpenStack flavor size ratio of 2/1 was determined? Accord

Re: [openstack-dev] [Neutron] UniqueConstraint for name and tenant_id in security group

On Dec 11, 2014, at 1:04 PM, Jay Pipes wrote: > On 12/11/2014 04:01 PM, Vishvananda Ishaya wrote: >> >> On Dec 11, 2014, at 8:00 AM, Henry Gessau wrote: >> >>> On Thu, Dec 11, 2014, Mark McClain wrote: >>>> >>>>> On Dec 11, 20

Re: [openstack-dev] [qa] Question about "nova boot --min-count "

I suspect you are actually failing due to not having enough room in your cloud instead of not having enough quota. You will need to make instance sizes with less cpus/ram/disk or change your allocation ratios in the scheduler. Vish On Dec 13, 2014, at 8:43 AM, Danny Choi (dannchoi) wrote: >

Re: [openstack-dev] [qa] How to delete a VM which is in ERROR state?

I have seen deadlocks in libvirt that could cause this. When you are in this state, check to see if you can do a virsh list on the node. If not, libvirt is deadlocked, and ubuntu may need to pull in a fix/newer version. Vish On Dec 12, 2014, at 2:12 PM, pcrews wrote: > On 12/09/2014 03:54 PM,

Re: [openstack-dev] [glance] Option to skip deleting images in use?

A simple solution that wouldn’t require modification of glance would be a cron job that lists images and snapshots and marks them protected while they are in use. Vish On Dec 16, 2014, at 3:19 PM, Collins, Sean wrote: > On Tue, Dec 16, 2014 at 05:12:31PM EST, Chris St. Pierre wrote: >> No, I'

Re: [openstack-dev] [qa] How to delete a VM which is in ERROR state?

Maybe I'm observing the same on SLC6 where I can't even "kill" libvirtd > process. > > Belmiro > > On Tue, Dec 16, 2014 at 12:01 AM, Vishvananda Ishaya > wrote: > I have seen deadlocks in libvirt that could cause this. When you are in this > state, check

Re: [openstack-dev] [nova] Setting MTU size for tap device

It makes sense to add it to me. Libvirt sets the mtu from the bridge when it creates the tap device, but if you are creating it manually you might need to set it to something else. Vish On Dec 17, 2014, at 10:29 PM, Ryu Ishimoto wrote: > Hi All, > > I noticed that in linux_net.py, the method

Re: [openstack-dev] [OpenStack-dev][nova-net]Floating ip assigned as /32 from the start of the range

Floating ips are always added to the host as a /32. You will need one ip on the compute host from the floating range with the /16 prefix (which it will use for natting instances without floating ips as well). In other words you should manually assign an ip from 10.100.130.X/16 to each compute node

Re: [openstack-dev] [cinder] [nova] [scheduler] Nova node name passed to Cinder

Nova passes ip, iqn, and hostname into initialize_connection. That should give you the info you need. Vish On Jan 26, 2015, at 3:21 AM, Philipp Marek wrote: > Hello everybody, > > I'm currently working on providing DRBD as a block storage protocol. > For that the cinder volume driver needs to

Re: [openstack-dev] [nova] Proposal: remove the server groups feature

On Apr 25, 2014, at 2:25 PM, Chris Behrens wrote: > > On Apr 25, 2014, at 2:15 PM, Jay Pipes wrote: > >> Hi Stackers, >> >> When recently digging in to the new server group v3 API extension >> introduced in Icehouse, I was struck with a bit of cognitive dissonance >> that I can't seem to sha

Re: [openstack-dev] [Cinder] Question about the magic "100M" when creating zero-size volume

This was added long ago to support testing environments without a lot of disk space. Vish On Apr 29, 2014, at 12:12 AM, Zhangleiqiang (Trump) wrote: > Hi, all: > > I find in some of the cinder backend volume drivers, there are codes in > create_volume as follows: > >

Re: [openstack-dev] [Cinder] Question about synchronized decoration usage in cinder-volume

On Apr 26, 2014, at 2:56 AM, Zhangleiqiang (Trump) wrote: > Hi, all: > > I find almost all of the @utils.synchronized decoration usage in > cinder-volume (cinder.volume.manager / cinder.volume.drivers.*) with an > "external=True" param. Such as > cinder.volume.manager.VolumeManager:at

Re: [openstack-dev] Hierarchicical Multitenancy Discussion

w field so > we can have both information sent. I'm not sure which is the best option for > us but i would think that sending both for now would keep the compatibility > and we could still use the names for display porpuse > > > On Sun, Mar 16, 2014 at 9:18 AM, Jay Pipes w

Re: [openstack-dev] [Cinder] Question about storage backend capacity expansion

On May 14, 2014, at 12:14 AM, Zhangleiqiang (Trump) wrote: > Hi, all: > I meet a requirement in my OpenStack environment which initially uses > one LVMISCSI backend. Along with the usage, the storage is insufficient, so I > want to add a NFS backend to the exists Cinder. > > The

Re: [openstack-dev] Multiple instances of Keystone

Keystone has specifically avoided including multiple process patches because they want to encourage apache + mod_wsgi as the standard way of scaling the keystone api. Vish On May 13, 2014, at 9:34 PM, Aniruddha Singh Gautam wrote: > Hi, > > Hope you are doing well… > > I was working on t

Re: [openstack-dev] [nova] nova default quotas

Are you aware that there is already a way to do this through the cli using quota-class-update? http://docs.openstack.org/user-guide-admin/content/cli_set_quotas.html (near the bottom) Are you suggesting that we also add the ability to use just regular quota-update? I’m not sure i see the need

Re: [openstack-dev] [nova] nova default quotas

oved from Nova now. > > Phil > > > Sent from Samsung Mobile > > > Original message ---- > From: Vishvananda Ishaya > Date:27/05/2014 19:24 (GMT+00:00) > To: "OpenStack Development Mailing List (not for usage questions)" > Subject: Re:

Re: [openstack-dev] [nova] nova default quotas

to add this functionality to nova. > > https://review.openstack.org/#/c/94519/ > > > -Original Message- > From: Vishvananda Ishaya [mailto:vishvana...@gmail.com] > Sent: Tuesday, May 27, 2014 5:11 PM > To: OpenStack Development Mailing List (not for usa

Re: [openstack-dev] [Nova]Passing flat_injected flag through instance metadata

We have discussed this a bunch in the past, and the right implementation here is to put the network configuration in a standard format (json?) in both the config drive and metadata. cloud-init can be modified to read from that format and write out a proper /etc/network/interfaces (or appropriat

  1   2   3   >