Re: [openstack-dev] [Openstack] Cinder-service connectivity issues

Based on the checkin times in your post, it looks like time is out of sync between your nodes. The one reporting down is reporting time in the future. I would install ntp and make sure the clocks are in sync. Vish On Mar 25, 2015, at 2:33 AM, Kamsali, RaghavendraChari (Artesyn) wrote: > >

Re: [openstack-dev] [nova] Intended behavior for instance.host on reschedule?

I’m pretty sure it has always done this: leave the host set on the final scheduling attempt. I agree that this could be cleared which would free up room for future scheduling attempts. Vish On Mar 3, 2015, at 12:15 AM, Joe Cropper wrote: > Hi Folks, > > I was wondering if anyone can comment

Re: [openstack-dev] [nova] Question about force_host skip filters

If this feature is going to be added, I suggest it gets a different name. Force host is an admin command to force an instance onto a host. If you want to make a user-facing command that respects filters, perhaps something like requested-host might work. In general, however, the name of hosts are

Re: [openstack-dev] [cinder] Fixing stuck volumes - part II

On Feb 11, 2015, at 3:45 PM, D'Angelo, Scott wrote: > At the cinder mid-cycle it was decided that the best way to fix volumes stuck > in ‘attaching’ or ‘detaching’ was NOT to fix the broken reset-state command. > The doc string and help message for reset-state have been modified to warn > the

Re: [openstack-dev] Deprecation of in tree EC2 API in Nova for Kilo release

On Feb 3, 2015, at 6:19 AM, Sean Dague wrote: > On 02/03/2015 08:57 AM, Thierry Carrez wrote: >> Jesse Pretorius wrote: >>> I think that perhaps something that shouldn't be lost site of is that >>> the users using the EC2 API are using it as-is. The only commitment that >>> needs to be made is t

Re: [openstack-dev] [oslo.db] PyMySQL review

On Jan 29, 2015, at 8:57 AM, Roman Podoliaka wrote: > Jeremy, > > I don't have exact numbers, so yeah, it's just an assumption based on > looking at the nova-api/scheduler logs with connection_debug set to > 100. > > But that's a good point you are making here: it will be interesting to > see

Re: [openstack-dev] [oslo.db] PyMySQL review

On Jan 28, 2015, at 4:03 PM, Doug Hellmann wrote: > > > On Wed, Jan 28, 2015, at 06:50 PM, Johannes Erdfelt wrote: >> On Wed, Jan 28, 2015, Clint Byrum wrote: >>> As is often the case with threading, a reason to avoid using it is >>> that libraries often aren't able or willing to assert threa

Re: [openstack-dev] [neutron] high dhcp lease times in neutron deployments considered harmful (or not???)

On Jan 28, 2015, at 9:36 AM, Carl Baldwin wrote: > On Wed, Jan 28, 2015 at 9:52 AM, Salvatore Orlando > wrote: >> The patch Kevin points out increased the lease to 24 hours (which I agree is >> as arbitrary as 2 minutes, 8 minutes, or 1 century) because it introduced >> use of DHCPRELEASE mess

Re: [openstack-dev] [nova] [api] Get servers with limit and IP address filter

On Jan 28, 2015, at 7:05 AM, Steven Kaufer wrote: > Vishvananda Ishaya wrote on 01/27/2015 04:29:50 PM: > > > From: Vishvananda Ishaya > > To: "OpenStack Development Mailing List (not for usage questions)" > > > > Date: 01/27/2015 04:32 PM > >

Re: [openstack-dev] [nova] [api] Get servers with limit and IP address filter

The network info for an instance is cached as a blob of data (neutron has the canonical version in most installs), so it isn’t particularly easy to do at the database layer. You would likely need a pretty complex stored procedure to do it accurately. Vish On Jan 27, 2015, at 2:00 PM, Steven Ka

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

On Jan 26, 2015, at 10:16 PM, Philipp Marek wrote: > Hello Vish, > >> Nova passes ip, iqn, and hostname into initialize_connection. That should >> give you the info you need. > thank you, but that is on the _Nova_ side. > > I need to know that on the Cinder node already: > >>> For that the c

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] [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] [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] [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] [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?

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] [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] [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] 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 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] [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] [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] [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][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] [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] [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] pci pass through turing complete config options?

On Nov 6, 2014, at 7:56 PM, Ian Wienand wrote: > On 10/29/2014 12:42 AM, Doug Hellmann wrote: >> Another way to do this, which has been used in some other projects, >> is to define one option for a list of “names” of things, and use >> those names to make groups with each field > > I've propose

Re: [openstack-dev] TC election by the numbers

On Oct 30, 2014, at 10:41 AM, Zane Bitter wrote: > On 30/10/14 06:22, Eoghan Glynn wrote: >> > IIRC, there is no method for removing foundation members. So there > are likely a number of people listed who have moved on to other > activities and are no longer involved wit

Re: [openstack-dev] [Neutron] Killing connection after security group rule deletion

If you exec conntrack inside the namespace with ip netns exec does it still show both connections? Vish On Oct 23, 2014, at 3:22 AM, Elena Ezhova wrote: > Hi! > > I am working on a bug "ping still working once connected even after related > security group rule is deleted" > (https://bugs.la

Re: [openstack-dev] [qa] "nova get-password" does not seem to work

Get password only works if you have something in the guest generating the encrypted password and posting it to the metadata server. Cloud-init for windows (the primary use case) will do this for you. You can do something similar for ubuntu using this script: https://gist.github.com/vishvananda/400

Re: [openstack-dev] [qa] Cannot start the VM console when VM is launched at Compute node

No this is not expected and may represent a misconfiguration or a bug. Something is returning a 404 when it shouldn’t. You might get more luck running the nova command with —debug to see what specifically is 404ing. You could also see if anything is reporting NotFound in the nova-consoleauth or n

Re: [openstack-dev] [neutron][all] Naming convention for unused variables

On Oct 13, 2014, at 6:28 PM, Angus Lees wrote: > (Context: https://review.openstack.org/#/c/117418/) > > I'm looking for some rough consensus on what naming conventions we want for > unused variables in Neutron, and across the larger OpenStack python codebase > since there's no reason for Neu

Re: [openstack-dev] [kolla] on Dockerfile patterns

On Oct 14, 2014, at 1:12 PM, Clint Byrum wrote: > Excerpts from Lars Kellogg-Stedman's message of 2014-10-14 12:50:48 -0700: >> On Tue, Oct 14, 2014 at 03:25:56PM -0400, Jay Pipes wrote: >>> I think the above strategy is spot on. Unfortunately, that's not how the >>> Docker ecosystem works. >>

Re: [openstack-dev] [kolla] on Dockerfile patterns

On Oct 14, 2014, at 1:21 PM, Lars Kellogg-Stedman wrote: > On Tue, Oct 14, 2014 at 04:06:22PM -0400, Jay Pipes wrote: >> I understand that general feeling, but system administration tasks like >> debugging networking issues or determining and grepping log file locations >> or diagnosing packagin

Re: [openstack-dev] [nova] Resource tracker

On Oct 7, 2014, at 6:21 AM, Daniel P. Berrange wrote: > On Mon, Oct 06, 2014 at 02:55:20PM -0700, Joe Gordon wrote: >> On Mon, Oct 6, 2014 at 6:03 AM, Gary Kotton wrote: >> >>> Hi, >>> At the moment the resource tracker in Nova ignores that statistics that >>> are returned by the hypervisor an

Re: [openstack-dev] [Glance] Granularity of policies

On Oct 6, 2014, at 12:35 PM, Eddie Sheffield wrote: > I encountered an interesting situation with Glance policies. Basically we > have a situation where users in certain roles are not allowed to make certain > calls at all. In this specific case, we don't want users in those roles > listing

Re: [openstack-dev] Quota management and enforcement across projects

The proposal in the past was to keep quota enforcement local, but to put the resource limits into keystone. This seems like an obvious first step to me. Then a shared library for enforcing quotas with decent performance should be next. The quota calls in nova are extremely inefficient right now and

Re: [openstack-dev] [nova] why do we have os-attach-interfaces in the v3 API?

2, 2014, at 2:43 PM, Matt Riedemann wrote: > > > On 10/2/2014 4:34 PM, Vishvananda Ishaya wrote: >> os-attach-interfacees is actually a a forward port of: >> >> http://git.openstack.org/cgit/openstack/nova/tree/nova/api/openstack/compute/contrib/attach_interfaces.p

Re: [openstack-dev] [nova] evacuating boot-from-volume instances with local storage is broken?

On Oct 2, 2014, at 2:05 PM, Chris Friesen wrote: > On 10/02/2014 02:24 PM, Jay Pipes wrote: >> On 10/02/2014 02:29 PM, Chris Friesen wrote: >>> >>> Hi, >>> >>> I'm interested in running "nova evacuate" on an instance that has local >>> storage but was booted from a cinder volume. OpenStack al

Re: [openstack-dev] [nova] why do we have os-attach-interfaces in the v3 API?

os-attach-interfacees is actually a a forward port of: http://git.openstack.org/cgit/openstack/nova/tree/nova/api/openstack/compute/contrib/attach_interfaces.py which is a compute action that is valid for both nova-network and neutron: http://git.openstack.org/cgit/openstack/nova/tree/nova/compu

Re: [openstack-dev] [kolla] Kolla Blueprints

On Oct 1, 2014, at 2:05 PM, Fox, Kevin M wrote: > Has anyone figured out a way of having a floating ip like feature with docker > so that you can have rabbitmq, mysql, or ceph mon's at fixed ip's and be able > to migrate them around from physical host to physical host and still have > them at

Re: [openstack-dev] Help with EC2 Driver functionality using boto ...

It is hard to tell if this is a bug or a misconfiguration from your desctiption. The failure likely generated some kind of error message in nova or glance. If you can track down an error message and a tracback it would be worth submitting as a bug report to the appropriate project. Vish On Oct

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

On Sep 26, 2014, at 1:25 AM, Thierry Carrez wrote: > That said, singling out the test infrastructure (3) and the release > management (2) is a bit unfair to other horizontal efforts, like > Documentation, Translations, or general QA, which also suffer from a > scale issue. The Docs team, in part

Re: [openstack-dev] [infra] Nominating Sean Dague for project-config-core

Based on the amazing work that Sean does across a whole slew of repositories, can we just give him +2 rights on everything? ;) Vish P.S. But seriously, I am truly impressed with how much Sean puts into this project. On Sep 26, 2014, at 8:35 AM, James E. Blair wrote: > I'm pleased to nominate S

Re: [openstack-dev] [neutron][IPv6] Neighbor Discovery for HA

You are going to have to make this as a separate binary and call it via rootwrap ip netns exec. While it is possible to change network namespaces in python, you aren’t going to be able to do this consistently without root access, so it will need to be guarded by rootwrap anyway. Vish On Sep 25, 2

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

On Sep 25, 2014, at 4:01 PM, Robert Collins wrote: > So I guess I'm saying: > >Lets decouple 'what is openstack' from 'what we test together on > every commit'. It seems that this discussion has actually illustrated shortcomings in our answers to 3 separate questions, and people have been

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

On Sep 24, 2014, at 10:55 AM, Zane Bitter wrote: > On 18/09/14 14:53, Monty Taylor wrote: >> Hey all, >> >> I've recently been thinking a lot about Sean's Layers stuff. So I wrote >> a blog post which Jim Blair and Devananda were kind enough to help me edit. >> >> http://inaugust.com/post/108

Re: [openstack-dev] [Nova] Release criticality of bug 1365606 (get_network_info efficiency for nova-network)

complain if we just took all 4 :) Vish On Sep 25, 2014, at 9:44 AM, Vishvananda Ishaya wrote: > To explain my rationale: > > I think it is totally reasonable to be conservative and wait to merge > the actual fixes to the network calls[1][2] until Kilo and have them > go thr

Re: [openstack-dev] [Nova] Release criticality of bug 1365606 (get_network_info efficiency for nova-network)

To explain my rationale: I think it is totally reasonable to be conservative and wait to merge the actual fixes to the network calls[1][2] until Kilo and have them go through the stable/backports process. Unfortunately, due to our object design, if we block https://review.openstack.org/#/c/119521/

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

On Sep 23, 2014, at 8:40 AM, Doug Hellmann wrote: > If we are no longer incubating *programs*, which are the teams of people who > we would like to ensure are involved in OpenStack governance, then how do we > make that decision? From a practical standpoint, how do we make a list of > eligibl

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

On Sep 19, 2014, at 10:14 AM, John Dickinson wrote: > > On Sep 19, 2014, at 5:46 AM, John Griffith > wrote: > >> >> >> On Fri, Sep 19, 2014 at 4:33 AM, Thierry Carrez >> wrote: >> Vishvananda Ishaya wrote: >>> Great writeup. I t

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

On Sep 19, 2014, at 3:33 AM, Thierry Carrez wrote: > Vishvananda Ishaya wrote: >> 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 >

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] 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] [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] [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 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] 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] [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] [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] [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] [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] [Nova] Boot from ISO feature status

+38 (093) 665 14 28 > Skype: max_lobur > > 38, Lenina ave. Kharkov, Ukraine > www.mirantis.com > www.mirantis.ru > > > On Tue, Jul 22, 2014 at 8:57 AM, Vishvananda Ishaya > wrote: > This is somewhat confusing, but long ago the decision was made that booting > from an

Re: [openstack-dev] [nova] vhost-scsi support in Nova

On Jul 24, 2014, at 3:06 AM, Daniel P. Berrange wrote: > On Wed, Jul 23, 2014 at 10:32:44PM -0700, Nicholas A. Bellinger wrote: >> *) vhost-scsi doesn't support migration >> >> Since it's initial merge in QEMU v1.5, vhost-scsi has a migration blocker >> set. This is primarily due to requiring

Re: [openstack-dev] [nova]resize

The resize code as written originally did the simplest possible thing. It converts and copies the whole file so that it doesn’t have to figure out how to sync backing files etc. This could definitely be improved, especially now that there is code in _create_images_and_backing that can ensure that

Re: [openstack-dev] [nova] how scheduler handle messages?

Workers can consume more than one message at a time due to eventlet/greenthreads. The conf option rpc_thread_pool_size determines how many messages can theoretically be handled at once. Greenthread switching can happen any time a monkeypatched call is made. Vish On Jul 21, 2014, at 3:36 AM, fd

Re: [openstack-dev] [Nova] Boot from ISO feature status

This is somewhat confusing, but long ago the decision was made that booting from an ISO image should use the ISO as a root drive. This means that it is only really useful for things like live cds. I believe you could use the new block device mapping code to create an instance that boots from an

Re: [openstack-dev] Virtio-scsi settings nova-specs exception

I will also sponsor this. Vish On Jul 17, 2014, at 2:47 PM, Mike Perez wrote: > As requested from the #openstack-meeting for Nova, I'm posting my > nova-spec exception proposal to the ML. > > Spec: > https://review.openstack.org/#/c/103797/3/specs/juno/virtio-scsi-settings.rst > Code: https:/

Re: [openstack-dev] [nova] fair standards for all hypervisor drivers

On Jul 16, 2014, at 8:28 AM, Daniel P. Berrange wrote: > On Wed, Jul 16, 2014 at 08:12:47AM -0700, Clark Boylan wrote: > >> I am worried that we would just regress to the current process because >> we have tried something similar to this previously and were forced to >> regress to the current p

Re: [openstack-dev] [neutron][all] switch from mysqldb to another eventlet aware mysql client

On Jul 15, 2014, at 3:30 PM, Ihar Hrachyshka wrote: > Signed PGP part > On 14/07/14 22:48, Vishvananda Ishaya wrote: > > > > On Jul 13, 2014, at 9:29 AM, Ihar Hrachyshka > > wrote: > > > >> Signed PGP part On 12/07/14 03:17, Mike Bayer wrote: > >>

Re: [openstack-dev] [neutron][all] switch from mysqldb to another eventlet aware mysql client

On Jul 13, 2014, at 9:29 AM, Ihar Hrachyshka wrote: > Signed PGP part > On 12/07/14 03:17, Mike Bayer wrote: > > > > On 7/11/14, 7:26 PM, Carl Baldwin wrote: > >> > >> > >> On Jul 11, 2014 5:32 PM, "Vishvananda Ishaya" > >> &

Re: [openstack-dev] [neutron][all] switch from mysqldb to another eventlet aware mysql client

I have tried using pymysql in place of mysqldb and in real world concurrency tests against cinder and nova it performs slower. I was inspired by the mention of mysql-connector so I just tried that option instead. Mysql-connector seems to be slightly slower as well, which leads me to believe that th

Re: [openstack-dev] [Neutron] cloud-init IPv6 support

I haven’t heard of anyone addressing this, but it seems useful. Vish On Jul 7, 2014, at 9:15 AM, Nir Yechiel wrote: > AFAIK, the cloud-init metadata service can currently be accessed only by > sending a request to http://169.254.169.254, and no IPv6 equivalent is > currently implemented. Does

Re: [openstack-dev] [nova][libvirt] Suspend via virDomainSave() rather than virDomainManagedSave()

On Jul 6, 2014, at 10:22 PM, Rafi Khardalian wrote: > Hi All -- > > It seems as though it would be beneficial to use virDomainSave rather than > virDomainManagedSave for suspending instances. The primary benefit of doing > so would be to locate the save files within the instance's dedicated

Re: [openstack-dev] [nova] Two questions about 'backup' API

; P.S. So maybe 'backup_name'/'backup_tag' is a better name, but we can't > modify the API for compatibility.. Yes the name is confusing. Vish > > > Thanks. > > WingWJ > > > On Fri, Jun 27, 2014 at 5:20 AM, Vishvananda Ishaya > wrote

Re: [openstack-dev] nova networking API and CLI are poorly documented and buggy

On Jun 14, 2014, at 9:12 AM, Mike Spreitzer wrote: > I am not even sure what is the intent, but some of the behavior looks like it > is clearly unintended and not useful (a more precise formulation of "buggy" > that is not defeated by the lack of documentation). > > IMHO, the API and CLI docu

Re: [openstack-dev] Virtual Interface creation failed

I have seen something like this before with nova-network and it was due to the number of requests the rpc call timeout gets hit for allocate_network. You might need to set your rpc_response_timeout to something greater. I think it defaults to 60 seconds. Vish On Jun 25, 2014, at 6:57 AM, tfre.

Re: [openstack-dev] [nova] should we have a stale data indication in "nova list/show"?

On Jun 26, 2014, at 3:58 AM, Day, Phil wrote: >> -Original Message- >> From: Ahmed RAHAL [mailto:ara...@iweb.com] >> Sent: 25 June 2014 20:25 >> To: openstack-dev@lists.openstack.org >> Subject: Re: [openstack-dev] [nova] should we have a stale data indication in >> "nova list/show"? >>

Re: [openstack-dev] [nova] Why is there a 'None' task_state between 'SCHEDULING' & 'BLOCK_DEVICE_MAPPING'?

Thanks WingWJ. It would also be great to track this in a bug. Vish On Jun 26, 2014, at 5:30 AM, wu jiang wrote: > Hi Phil, > > Ok, I'll submit a patch to add a new task_state(like 'STARTING_BUILD') in > these two days. > And related modifications will be definitely added in the Doc. > > Th

Re: [openstack-dev] [nova] Two questions about 'backup' API

On Jun 26, 2014, at 5:07 AM, wu jiang wrote: > Hi all, > > I tested the 'backup' API recently and got two questions about it: > > 1. Why 'daily' & 'weekly' appear in code comments & novaclient about > 'backup_type' parameter? > > The 'backup_type' parameter is only a tag for this backup(image

Re: [openstack-dev] [Neutron]One security issue about floating ip

when it removes the IP from it's qg- interface it can do a > similar operation. > > -Brian > > On 06/26/2014 03:36 PM, Vishvananda Ishaya wrote: > > I believe this will affect nova-network as well. We probably should use > > something like the linux cutter utili

Re: [openstack-dev] [Neutron]One security issue about floating ip

I believe this will affect nova-network as well. We probably should use something like the linux cutter utility to kill any ongoing connections after we remove the nat rule. Vish On Jun 25, 2014, at 8:18 PM, Xurong Yang wrote: > Hi folks, > > After we create an SSH connection to a VM via its

Re: [openstack-dev] [nova] fastest way to run individual tests ?

This isn’t an officially supported method, but i tend to use: python -m nova.openstack.common.lockutils nosetests for example: python -m nova.openstack.common.lockutils nosetests nova.tests.integrated.test_api_samples:CloudPipeSampleJsonTest.test_cloud_pipe_create I think this is a little bit

Re: [openstack-dev] [Openstack] [Nova] How to confirm I have the right database schema when checkout to another branch?

You need to remove the old .pyc files in the migrate_repo/versions directory. I have an alias in my .gitconfig to allow me to checkout a branch and delete pycs in one command: [alias] cc = !"TOP=$(git rev-parse --show-toplevel); find $TOP -name '*.pyc' -delete; git-checkout” so i can do:

Re: [openstack-dev] [nova] Reducing quota below utilisation

On Jun 17, 2014, at 12:53 PM, Jan van Eldik wrote: > Just > > On 06/17/2014 08:18 PM, Tim Bell wrote: >> We have some projects which are dynamically creating VMs up to their >> quota. Under some circumstances, as cloud administrators, we would like >> these projects to shrink and make room for

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

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] 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

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] 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] [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] 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 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] [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] [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] [Openstack] Question regarding Nova in Havana

the above is correct, what is the ‘exchange’ used Nova Conductor to send > back this response. > > Regards > -Prashant > > > From: Vishvananda Ishaya [mailto:vishvana...@gmail.com] > Sent: Wednesday, April 16, 2014 10:11 AM > To: OpenStack Development Mailing List

Re: [openstack-dev] [Openstack] Question regarding Nova in Havana

The service reference is created in the start method of the service. This happens around line 217 in nova/service.py in the current code. You should be able to do something similar by sending a message to service_create on conductor. It will return an error if the service already exists. Note yo

[openstack-dev] TC candidacy

Hello all, I’d like to announce my candidacy for the Technical Committee election. I was one of the original authors of the Nova project and served as its PTL for the first two years that the position existed. I have also been on the Technical Comittee since its inception. I was also recently ele

Re: [openstack-dev] [oslo] use of the "oslo" namespace package

I dealt with this myself the other day and it was a huge pain. That said, changing all the packages seems like a nuclear option. Is there any way we could change python that would make it smarter about searching multiple locations for namespace packages? Vish On Apr 7, 2014, at 12:24 PM, Doug Hel

  1   2   3   >