Re: [Openstack] VM can't ping self floating IP after a snapshot is taken

That's great, thank you for your efforts. Can you make a backport for essex? Sent from my iPhone On Aug 24, 2012, at 7:15 PM, heut2008 wrote: > I have fixed it here https://review.openstack.org/#/c/11925/ > > 2012/8/25 Sam Su : >> Hi, >> >> I also reported this bug: >> https://bugs.launchp

Re: [Openstack] [Nova] Instance Type Extra Specs clarifications

Folsom also supports setting key values for things like capabilities via host aggregates. There is a filter[1] that matches the extra specs by exact comparison just like was done for capabilities before the last patch. The new extra specs matching should be added to it. These capabilities can be

Re: [Openstack] VM can't ping self floating IP after a snapshot is taken

That'll work! Looks good to me. I can't review it on Gerrit but good job. Beat me to it :) On 08/24/2012 09:15 PM, heut2008 wrote: I have fixed it here https://review.openstack.org/#/c/11925/ 2012/8/25 Sam Su : Hi, I also reported this bug: https://bugs.launchpad.net/nova/+bug/1040255

Re: [Openstack] VM can't ping self floating IP after a snapshot is taken

I have fixed it here https://review.openstack.org/#/c/11925/ 2012/8/25 Sam Su : > Hi, > > I also reported this bug: > https://bugs.launchpad.net/nova/+bug/1040255 > > If someone can combine you guys solution and get a perfect way to fix this > bug, that will be great. > > BRs, > Sam > > > On Th

Re: [Openstack] [Nova] Instance Type Extra Specs clarifications

There are two entry points 1) the filters 2) the flavors From a UI perspective it feels safer to let the user select extra spec keys and values from drop-down lists (of pre-defined/registered keys and respective values) to avoid typographic errors This would then introduce a dependency, with nee

Re: [Openstack] [Nova] Instance Type Extra Specs clarifications

Patrick, That's a good point. I think the issue is already being discussed at https://bugs.launchpad.net/nova/+bug/1039386 as Don Dugger pointed out. That being said, as answers to some of your questions: yes, any key/value pair can be used and it is user's (in this case, system admin's) respo

Re: [Openstack] [Nova] Instance Type Extra Specs clarifications

Hi Joseph and All, You are pointing the root cause of my question. The question is about how to specify capabilities for a compute node so that they can be compared with the extra specs. I think how to define extra specs in a flavor is clear enough. So, some capabilities are standard and are ge

[Openstack] OpenStack Community Weekly Newsletter (Aug 17-24)

Highlights of the week OpenStack at CloudOpen OpenStack is a protagonist of CloudOpen, the only conference providing a collaboration and education space dedicated to advancing the open cloud. Next week, from Aug 29

Re: [Openstack] Cannot create snapshots of instances running not on the controller

Actually it looks like a different error. For some reason container format is being sent in as none on the second node. Is it possible the original image that you launched the vm from has been deleted? For some reason it can't determine the container format. If not, can you also make sure that

Re: [Openstack] [openstack-dev] Discussion about where to put database for bare-metal provisioning (review 10726)

I would investigate changing the capabilities to key off of something other than hostname. It looks from the table structure like compute_nodes could be have a many-to-one relationship with services. You would just have to use a little more than hostname. Perhaps (hostname, hypervisor_hostname)

[Openstack] Quantum vs. Nova-network in Folsom

tl;dr both Quantum and nova-network will be core and fully supported in Folsom. Hi folks, Thierry, Vish and I have been spending some talking about OpenStack networking in Folsom, and in particular the availability of nova-network now that Quantum is a core project. We wanted to share our curre

Re: [Openstack] [nova] Meeting Notes

Thanks Vishy, these meeting notes are super helpful IMHO. On Aug 24, 2012, at 5:25 PM, "Vishvananda Ishaya" wrote: > Hello Everyone, > > We had another productive nova meeting yesterday. I've included the summary > below. > > Vish > > Meeting summary > --- > > * http://wiki.o

[Openstack] [nova] Meeting Notes

Hello Everyone, We had another productive nova meeting yesterday. I've included the summary below. Vish Meeting summary --- * http://wiki.openstack.org/Meetings/Nova (vishy, 21:01:14) * Role Call (vishy, 21:01:34) * LINK: Agenda: http://wiki.openstack.org/Meetings/Nova (vishy

Re: [Openstack] OpenStack and IGMP

Hi Juris, Some more detail would be useful here. It sounds like you're trying to use multicast, for which IGMP is a control protocol. Is it that you're trying to run nova VMs and make sure they can participate in multicast groups? Basic flat Nova networking connects VMs directly to a physical n

Re: [Openstack] What is the most commonly used Hypervisor and toolset combination?

Boris-Michel Deschenes wrote: > John, > > Sorry for my late response.. > > It would be great to collaborate, like I said, I prefer to keep the libvirt > layer as it works great with openstack and many other techs (collectd, > virt-manager, etc.), the virsh tool is also very useful for us. > > You

Re: [Openstack] What is the most commonly used Hypervisor and toolset combination?

Sorry for the delayed response. Boris-Michel Deschenes wrote: > That would be great Jim, > > I've built a cloud that uses CentOS+libvirt+Xen 4.1.3 to do GPU passthrough > and I just love to be able to use libvirt with Xen, this setup makes a lot of > sense to me since our main, bigger cloud is t

[Openstack] quantum-rootwrap

https://review.openstack.org/#/c/11524/ Patches posted. Review solicited. Thanks in advance... ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help :

Re: [Openstack] [openstack-dev] Discussion about where to put database for bare-metal provisioning (review 10726)

 Vish,  I've tested your code and did more testing. There are a couple of problems. 1. host name should be unique. If not, any repetitive updates of new capabilities with the same host name are simply overwritten. 2. We cannot generate arbitrary host names on the fly.   The scheduler (I tested f

Re: [Openstack] VM can't ping self floating IP after a snapshot is taken

Hi, I also reported this bug: https://bugs.launchpad.net/nova/+bug/1040255 If someone can combine you guys solution and get a perfect way to fix this bug, that will be great. BRs, Sam On Thu, Aug 23, 2012 at 9:27 PM, heut2008 wrote: > this bug has been filed here https://bugs.launchpad.net

Re: [Openstack] [Nova] Instance Type Extra Specs clarifications

Patrick, Once a new item (key and value pair) is added to the capabilities, it can be compared against extra_specs. The extra_specs can be populated in instance_type_extra_specs table. The items in the extra_specs can start with one of the keywords for operations such as ">=" and "s==". For exa

Re: [Openstack] [Quantum] Running plugin tests with tox

Maru Newby writes: > Hi Salvatore, > > I see you're working on getting plugins testable with tox: > > https://review.openstack.org/#/c/11922/ > > What about keeping the plugins isolated for testing purposes? I have > been unable to work on it yet, but I was thinking it might be a good > idea to

Re: [Openstack] [Quantum] Running plugin tests with tox

Hi Maru, whether plugins should be packaged or not with the main quantum service is a "recurrent" question on this mailing list - and I am afraid I don't have answer to it! Pro and cons of separating the plugins from the main repository have been discussed on the mailing list and on the IRC channe

Re: [Openstack] [Nova] Instance Type Extra Specs clarifications

Patrick- We've enhanced `nova-manage' to manipulate the `extra_specs' entries, c.f. https://blueprints.launchpad.net/nova/+spec/update-flavor-key-value, You can add an `extra_specs' key/value pair to a flavor with the command: nova-manage instance_type add_key m1.humongous cpu

Re: [Openstack] [Nova] Instance Type Extra Specs clarifications

Parick, We are using the feature in Bare-metal machine provisioning. Some keys are automatically generated by nova-compute. For example, "hypervisor_type", "hypervisor_version", etc. fields are automatically put into capabilities by nova-compute (in the case of libvirt). So, you don't need to

[Openstack] [Quantum] Running plugin tests with tox

Hi Salvatore, I see you're working on getting plugins testable with tox: https://review.openstack.org/#/c/11922/ What about keeping the plugins isolated for testing purposes? I have been unable to work on it yet, but I was thinking it might be a good idea to move the plugins out of the main t

[Openstack] [Nova] Instance Type Extra Specs clarifications

Hi, Could someone give a practical overview of how configuring and using the instance type extra specs extension capability introduced in Folsom? If how extending an instance type is relatively clear. Eg.: #nova-manage instance_type set_key --name= --key --value <'s== x86_64'> The principles o

Re: [Openstack] keystone installed by devstack redirect http request

Keystone doesn't return 301's (ever). However, your 301 response headers show: Server: BlueCoat-Security-Appliance I'm guessing that wasn't installed by devstack :) -Dolph On Fri, Aug 24, 2012 at 3:03 AM, Lu, Lianhao wrote: > Hi gang, > > I used the devstack to install a "all-one-one" dev

Re: [Openstack] Default rules for the 'default' security group

2012/8/24 Gabriel Hurley > I traced this through the code at one point looking for the same thing. > As it stands, right now there is **not** a mechanism for customizing the > default security group’s rules. It’s created programmatically the first > time the rules for a project are retrieved wit

[Openstack] OpenStack and IGMP

Hi all, Do you have any experience configuring OpenStack to work with IGMP traffic? If I have IGMP server and appropriate network infrastructure, what is the best way to bound it with one of OpenStack's private networks? ___ Mailing list: https://launch

[Openstack] Coming up: PTL and TC elections

Hi everyone, As the Foundation Board of Directors election is closing, we have new elections coming up for the OpenStack technical contributors: the PTL and TC elections. The process we'll follow lives at: http://wiki.openstack.org/Governance/TCElectionsFall2012 TL;DR summary: * The election pro

[Openstack] Able to ping/ssh from source group VM to the target group VM using public IP when both the VMs are hosted on same compute node

Hi, I am working with multi-node environment and tried the following steps: 1. Create a source group and a target group. a. nova secgroup-create srcsecgrp "Source Security Group" b. nova secgroup-create tgtsecgrp "Target Security Group" 2. Spawn VMs in both the groups separ

[Openstack] keystone installed by devstack redirect http request

Hi gang, I used the devstack to install a "all-one-one" develop environment, but the keystone service seemed not working for me. The host OS is Ubuntu 12.04 with a statically assigned IP address 192.168.79.201. Since this host is in the internal network, I have to use a gateway(with 2 NICs of

Re: [Openstack] Nova Folsom-3

Hi- Thanks for the reply, While installing from the source, will it not be copied from the source to /etc/nova .directory. I see that, /etc/nova directory itself is not created. On Fri, Aug 24, 2012 at 12:51 PM, Ritesh Nanda wrote: > Hello Trinath, > > If you are installing it from source, it

Re: [Openstack] Cannot create snapshots of instances running not on the controller

Hi Vish, I had already a setting: glance_api_servers=10.0.0.1:9292 i've also tried to add glance_host=10.0.0.1 but i got the same error.. Also, after changing configuration and restarting nova-compute restarts all instances, is that normal? Best Alessandro Il giorno 23/ago/2012, alle ore 2