Re: [Openstack-doc-core] How should we mark up nova-* services?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It's possible for the xslts to add quotes around words marked up with an element. When it does this, the quotes are locale-specific (i.e. if the xml:lang=fr you get French-style quotes). So systemitem class=servicenova-volume/systemitem would become nova-volume in English and «nova-volume» in French. If that's a convention you'd like to use, let me know and I can configure the xslts to do that. David On 05/17/2012 05:32 AM, Razique Mahroua wrote: Actually it uses eg nova-volume is... I think 90% of the doc uses that convention. But it could be great to have a convention for it yes :) On Thu, 17 May 2012 05:21:40 +0200, David Cramer david.cra...@rackspace.com wrote: You probably want: systemitem class=service http://www.docbook.org/tdg5/en/html/systemitem.html The things to think about in deciding whether to mark something like this up are: 1) Do I want to be able to have this thing formatted in a particular way? E.g. monospace, bold. 2) Do I want to be able to do something else later (index, cross reference, etc) with this term? If either are true, then you should have a policy of marking it up and agree on a tag to use. Typing systemitem class=service probably seems cumbersome, but I can add to oxygen a shortcut so that it feels like there's really a service tag. I.e. you press enter to pull up the context completion window, start typing systemitem...it autocompletes and you pick systemitem-service from thei list. Or we could even add a service tag to the schema. David On 05/16/2012 09:37 PM, Lorin Hochstein wrote: Hey Razique: No, I was thinking specifically when the user *doesn't* have to type it. For example, this sentence involving nova-volume: The nova-volume service is responsible for managing attachable block storage devices. Take care, Lorin -- Lorin Hochstein Lead Architect - Cloud Services Nimbis Services, Inc. www.nimbisservices.com https://www.nimbisservices.com/ On May 16, 2012, at 3:28 AM, Razique Mahroua wrote: Hey Lorin :) You mean when the user has to type it ? Lorin Hochstein mailto:lo...@nimbisservices.com 16 mai 2012 05:04 Hi folks: What tag should we use for marking up Linux service names like nova-api and nova-network? Should we use command, or literal, or something else? Take care, Lorin -- Lorin Hochstein Lead Architect - Cloud Services Nimbis Services, Inc. www.nimbisservices.com https://www.nimbisservices.com/ -- Nuage Co - Razique Mahroua razique.mahr...@gmail.com image.jpg -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPtPD5AAoJEMHeSXG7afUhLfkH/i0UF7CJQ7AOAYzZaC1lod/l ZpKPTGlndaIeFYsx5HBr2G4w+ePXea9aRZU+DUcnuRVHPAtbaKQHAhqjDwvz1iTk 2mJdP6Z9CfzzZtiYzNO/M2TovDs2SRB6q8a7DNxgCGFIiIJChnCPE96ba5gHtLVQ FYeMWgTdCmONzWF1YVaCL6NDa6OWmop/HoPbaqZzL1w+CK1pZGW4/h+FlUZh/hIp s1RmYmfMyhFbWjByVmlUuZDNPcBFVPvljvRCv9v7D0pBGCS7nILbqYNe0/B5wPda mKlpB3UePF04lOqkOtdBW2MyUtHYMyZHURJpTNzhaVH3ukvUAvE9LqWkI80xdyk= =rv4k -END PGP SIGNATURE- -- Mailing list: https://launchpad.net/~openstack-doc-core Post to : openstack-doc-core@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-doc-core More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Compute] nova-compute does not show up as :-) in nova-manage service list
Thanks a lot Joe! Since yesterday I had this issue with nova-compute and after I synchronized the clock on the servers and restart nova-compute on the server with the issue it works great. Thanks a lot! Gabriel From: Joseph Heck he...@me.com To: Gurjar, Unmesh unmesh.gur...@nttdata.com Cc: openstack@lists.launchpad.net openstack@lists.launchpad.net Sent: Wednesday, May 16, 2012 6:41 PM Subject: Re: [Openstack] [Compute] nova-compute does not show up as :-) in nova-manage service list A completely separate potential cause - make sure the time is synchronized between the various hosts. I significant discrepancy there (over 30 seconds I think), will also result in the services thinking they're offline. -joe (this one from hard experience) On May 16, 2012, at 6:48 AM, Gurjar, Unmesh wrote: Restarting libvirt service seemed to resolve the issue for me in the past. Thanks Regards, Unmesh Gurjar | Lead Engineer | Vertex Software Private Ltd. | w. +91.20.6604.1500 x 379 | m. +91.982.324.7631 | unmesh.gur...@nttdata.com | Follow us on Twitter@NTTDATAAmericas From: Leander Bessa Beernaert [mailto:leande...@gmail.com] Sent: Wednesday, May 16, 2012 5:54 PM To: Day, Phil Cc: Gurjar, Unmesh; openstack@lists.launchpad.net Subject: Re: [Openstack] [Compute] nova-compute does not show up as :-) in nova-manage service list I tried 'virsh list', and the command hangs. At first i thought it was because of KVM, since the vm does not support it. I remember having the same problem with diablo, but it would only result in error when the instance was being launched on the compute service. So i changed libvirt_type=kvm to libvirt_type=qemu. However, the problem still remains: virsh list still hangs and compute refuses to leave the state XXX. On Wed, May 16, 2012 at 12:51 PM, Day, Phil philip@hp.com wrote: So the things to check are: - Is the nova-compute service running ? If not the nova-compute.log should show why its failing - If it is running then it probably means that its getting stuck on some long running issue (e.g as down loading an image, problems talking to libvirt, slow response from the DB, etc). XXX in this case means that its slow in updating its services entry rather than failed as such Phil From: openstack-bounces+philip.day=hp@lists.launchpad.net [mailto:openstack-bounces+philip.day=hp@lists.launchpad.net] On Behalf OfLeander Bessa Beernaert Sent: 16 May 2012 12:19 To: Gurjar, Unmesh Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] [Compute] nova-compute does not show up as :-) in nova-manage service list Shouldn't nova-network and nova-scheduler also fail then, since they share the same config file? If so, that's not what's happening with me, only the compute service is listed as XXX. On Wed, May 16, 2012 at 12:10 PM, Gurjar, Unmesh unmesh.gur...@nttdata.com wrote: Hi Leander, The issue is the Compute is not updating its heartbeat (services table in the nova database), which is causing this. You probably need to check database connection string in the nova.conf on the Compute host and the db connection from the Compute host is working. Thanks Regards, Unmesh Gurjar | Lead Engineer | Vertex Software Private Ltd. | w. +91.20.6604.1500 x 379 | m. +91.982.324.7631 | unmesh.gur...@nttdata.com | Follow us on Twitter@NTTDATAAmericas From: openstack-bounces+unmesh.gurjar=nttdata@lists.launchpad.net [mailto:openstack-bounces+unmesh.gurjar=nttdata@lists.launchpad.net]On Behalf Of Leander Bessa Beernaert Sent: Wednesday, May 16, 2012 4:30 PM To: openstack@lists.launchpad.net Subject: [Openstack] [Compute] nova-compute does not show up as :-) in nova-manage service list Hello, I can't get nova-compute to show up as :-) under 'nova-manager service list'. I've checked the logs and can't find any error or warning. I'm using the default packages shipped with ubuntu 12.04 and have installed everything in a virtual machine. Regards, Leander __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding
Re: [Openstack] SAN and Fibrechannel with OpenStack
Hi Wolfgang, latest versions of our distro supports NFS as backend storage for instances, volumes and images. Basically a zone shares the same NFS mountpoint for instances and another mountpoint for volumes, and I guess it does not differ a lot from what you want to do with FC or iSCSI. It's in our immediate roadmap to use FC and iSCSI instead of NFS, but may be you can give a try to our NFS stuff until then ;-) Cheers -- Diego Parrilla http://www.stackops.com/*CEO* *www.stackops.com | * diego.parri...@stackops.com** | +34 649 94 43 29 | skype:diegoparrilla* * http://www.stackops.com/ * * On Wed, May 16, 2012 at 11:05 AM, Wolfgang Hennerbichler wolfgang.hennerbich...@risc-software.at wrote: dear openstack godfathers; I do plan to migrate from crappy vmware and some ibm based cloud stack to openstack and kvm. here's the thing: I am lucky enough to have decent hardware, all the compute nodes are interconnected via fibre channel. so I don't want and don't need iscsi. do you think I can make it with something like clvm? I read through the docs of openstack, but I am not really sure now if I can make clvm fly without hacking around in openstack (and nova-volume) too much, especially when it comes to live migration and so on... I realize OpenStack was not built for SAN and FC, but I would really like to hear your opinions on that. Thanks, Wolfgang -- DI (FH) Wolfgang Hennerbichler Software Development Unit Advanced Computing Technologies RISC Software GmbH A company of the Johannes Kepler University Linz __**_ Mailing list: https://launchpad.net/~**openstackhttps://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~**openstackhttps://launchpad.net/~openstack More help : https://help.launchpad.net/**ListHelphttps://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Problems with dnat
Hello everyone, i've this problem, vm can connect to internet but cannot receive traffic when i assign them a floating ip, these are the iptables rules created by nova-network -P PREROUTING ACCEPT -P INPUT ACCEPT -P OUTPUT ACCEPT -P POSTROUTING ACCEPT -N nova-api-OUTPUT -N nova-api-POSTROUTING -N nova-api-PREROUTING -N nova-api-float-snat -N nova-api-snat -N nova-compute-OUTPUT -N nova-compute-POSTROUTING -N nova-compute-PREROUTING -N nova-compute-float-snat -N nova-compute-snat -N nova-network-OUTPUT -N nova-network-POSTROUTING -N nova-network-PREROUTING -N nova-network-float-snat -N nova-network-snat -N nova-postrouting-bottom -A PREROUTING -j nova-network-PREROUTING -A PREROUTING -j nova-compute-PREROUTING -A PREROUTING -j nova-api-PREROUTING -A OUTPUT -j nova-network-OUTPUT -A OUTPUT -j nova-compute-OUTPUT -A OUTPUT -j nova-api-OUTPUT -A POSTROUTING -j nova-network-POSTROUTING -A POSTROUTING -j nova-compute-POSTROUTING -A POSTROUTING -j nova-api-POSTROUTING -A POSTROUTING -j nova-postrouting-bottom -A nova-api-snat -j nova-api-float-snat -A nova-compute-snat -j nova-compute-float-snat -A nova-network-OUTPUT -d MY_FLOATING_IP/32 -j DNAT --to-destination 192.168.4.2 -A nova-network-POSTROUTING -s 192.168.4.0/24 -d MY_PUBLIC_IP/32 -j ACCEPT -A nova-network-POSTROUTING -s 192.168.4.0/24 -d 10.128.0.0/24 -j ACCEPT -A nova-network-POSTROUTING -s 192.168.4.0/24 -d 192.168.4.0/24 -m conntrack ! --ctstate DNAT -j ACCEPT -A nova-network-PREROUTING -d 169.254.169.254/32 -p tcp -m tcp --dport 80 -j DNAT --to-destination MY_PUBLIC_IP:8775 -A nova-network-PREROUTING -d MY_FLOATING_IP/32 -j DNAT --to-destination 192.168.4.2 -A nova-network-float-snat -s 192.168.4.2/32 -j SNAT --to-source MY_FLOATING_IP -A nova-network-snat -j nova-network-float-snat -A nova-network-snat -s 192.168.4.0/24 -j SNAT --to-source MY_PUBLIC_IP -A nova-postrouting-bottom -j nova-network-snat -A nova-postrouting-bottom -j nova-compute-snat -A nova-postrouting-bottom -j nova-api-snat and this my nova.conf --dhcpbridge_flagfile=/etc/nova/nova.conf --dhcpbridge=/usr/bin/nova-dhcpbridge --logdir=/var/log/nova --state_path=/var/lib/nova --lock_path=/run/lock/nova --allow_admin_api=true --use_deprecated_auth=false --auth_strategy=keystone --scheduler_driver=nova.scheduler.simple.SimpleScheduler --s3_host=MY_PUBLIC_IP --ec2_host=MY_PUBLIC_IP --rabbit_host=MY_PUBLIC_IP --cc_host=MY_PUBLIC_IP --nova_url=http://MY_PUBLIC_IP:8774/v1.1/ --routing_source_ip=MY_PUBLIC_IP --glance_api_servers=MY_PUBLIC_IP:9292 --image_service=nova.image.glance.GlanceImageService --iscsi_ip_prefix=192.168.4 --sql_connection=mysql://novadbadmin:mydbpassword@192.168.3.1/nova --ec2_url=http://MY_PUBLIC_IP:8773/services/Cloud --keystone_ec2_url=http://MY_PUBLIC_IP:5000/v2.0/ec2tokens --api_paste_config=/etc/nova/api-paste.ini --libvirt_type=kvm --libvirt_use_virtio_for_bridges=true --start_guests_on_host_boot=true --resume_guests_state_on_host_boot=true # vnc specific configuration --novnc_enabled=true --novncproxy_base_url=http://MY_PUBLIC_IP:6080/vnc_auto.html --vncserver_proxyclient_address=MY_PUBLIC_IP --vncserver_listen=MY_PUBLIC_IP # network specific settings --network_manager=nova.network.manager.FlatDHCPManager --public_interface=eth0 --flat_interface=eth2 --flat_network_bridge=br100 --fixed_range=192.168.4.0/24 --network_size=254 --flat_network_dhcp_start=192.168.4.1 --flat_injected=False --force_dhcp_release=true --iscsi_helper=tgtadm --connection_type=libvirt --root_helper=sudo nova-rootwrap --verbose=true with tcpdump i correctly see the syn packets on the eth0 (public interface) but can't see them on br100 or eth2 so they're not correctly dnatted. I've tried with both ip_forward enabled and disabled. Best Alessandro ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [metering] Do we need an API and storage?
On 05/16/2012 11:00 PM, Francis J. Lacoste wrote: I'm now of the opinion that we exclude storage and API from the metering project scope. Let's just focus on defining a metering message format, bus, and maybe a client-library to make it easy to write metering consumers. That way we avoid building a lot of things that we only _think will be useful_ for potential billing integration. Only writing/delivering such an integration component would prove that we built at least something that is useful. Hi, I'm a little reluctant to question the whole approach because I'm engaged in it :-) It's scary to contemplate the idea of throwing away some of the work done but I welcome the challenge. Better lose a few days work than keep going in the wrong direction. Are you proposing that such a library would then be integrated in whatever billing system someone has in mind ? For instance Dough https://github.com/lzyeval/dough trystack.org billing https://github.com/trystack/dash_billing nova-billing https://github.com/griddynamics/nova-billing Would depend on this library and rely on its API to collect what they need. The same would be done by proprietary billing systems ? Regarding the relevance of the metrics exposed by the API, I made sure they match the need of the eNovance sales. I'm quite sure Nicolas checked for Canonical and Doug did the same regarding the needs of Dreamhost. I'm confident that the information is actualy useful, at least in these practical cases. Getting rid of the storage imposes a constraint on the billing system : it must make 100% sure that once a message is consumed it will be reliably archived. It also adds a constraint on the chosen bus : it must be able to retain all messages for as long as a consumer needs, which may be days or weeks. Or it adds a constraint on the billing system which must make 100% sure it will consume all relevant messages the bus at all times before they expire. I have no strong feelings about exposing a bus for everyone to use instead of a REST API. I tend to prefer the REST API because it is an established standard for OpenStack. Could you expand on why a bus would be significantly better than a REST API in this specific case ? Cheers -- Loïc Dachary Chief Research Officer // eNovance labs http://labs.enovance.com // ✉ l...@enovance.com ☎ +33 1 49 70 99 82 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [metering] Do we need an API and storage?
On 05/17/2012 11:13 AM, Loic Dachary wrote: On 05/16/2012 11:00 PM, Francis J. Lacoste wrote: I'm now of the opinion that we exclude storage and API from the metering project scope. Let's just focus on defining a metering message format, bus, and maybe a client-library to make it easy to write metering consumers. That way we avoid building a lot of things that we only _think will be useful_ for potential billing integration. Only writing/delivering such an integration component would prove that we built at least something that is useful. Hi, I'm a little reluctant to question the whole approach because I'm engaged in it :-) It's scary to contemplate the idea of throwing away some of the work done but I welcome the challenge. Better lose a few days work than keep going in the wrong direction. Are you proposing that such a library would then be integrated in whatever billing system someone has in mind ? For instance Dough https://github.com/lzyeval/dough trystack.org billing https://github.com/trystack/dash_billing nova-billing https://github.com/griddynamics/nova-billing Would depend on this library and rely on its API to collect what they need. The same would be done by proprietary billing systems ? Regarding the relevance of the metrics exposed by the API, I made sure they match the need of the eNovance sales. I'm quite sure Nicolas checked for Canonical and Doug did the same regarding the needs of Dreamhost. I'm confident that the information is actualy useful, at least in these practical cases. Getting rid of the storage imposes a constraint on the billing system : it must make 100% sure that once a message is consumed it will be reliably archived. It also adds a constraint on the chosen bus : it must be able to retain all messages for as long as a consumer needs, which may be days or weeks. Or it adds a constraint on the billing system which must make 100% sure it will consume all relevant messages the bus at all times before they expire. I have no strong feelings about exposing a bus for everyone to use instead of a REST API. I tend to prefer the REST API because it is an established standard for OpenStack. Could you expand on why a bus would be significantly better than a REST API in this specific case ? Thanks for challenging our thought process, Francis, it is a great sanity check :) I do have a few use cases where a REST API is better than a bus: * Private clouds: Users are unlikely to want to activate a complete billing system but still want to be able top provide to their users some metrics of their uses. The REST API plus some scripts would allow them to do this without too much pain. * Metric of usage on GUI: It might be usefull to provide a quick way to assess usage in almost real time to users as part of an extension of Horizon for example. The REST API would allow for such data to be extracted dynamically without having to run a full billing tool in real time. * In house billing tools: about half of the ISPs I surveyed are running some form of a customized ERP system to handle the billing for their customers. They need to be able to produce CSVs on a weekly basis to feed their custom billing solutions. Integrating a bus would be much more complex than the script that would issue request to the rest API. * Auditability/Non repudiability: if the messages go from the queue to some unknown DB, how do you solve, in a generic way, coherent audit check and ensure non-repudiability? I do not mean to totally discard Francis' bus idea though, and think that we should allow for (a not necessarily db-less integration but) direct queue attachment model for billing systems. I do think that for all the above reasons, plus the simplification of testing of the overall system, the REST API must remain part of this project. Nick signature.asc Description: OpenPGP digital signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Dashboard] Can't access images/snapshots
I have no trouble from the command line. One thing i find peculiar is that i haven't installed swift and nova-volume yet and they show up as enabled services in the dashboard. Is that normal? On Wed, May 16, 2012 at 11:39 PM, Sébastien Han han.sebast...@gmail.comwrote: Hi, Do you also have an error when retrieving from the command line? ~Cheers! On Wed, May 16, 2012 at 5:38 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello, I keep running into this error when i try to list the images/snapshot in dashboard: http://paste.openstack.org/show/17820/ This is my local_settings.py file: http://paste.openstack.org/show/17822/ , am i missing something? Regards, Leander ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Compute] nova-compute does not show up as :-) in nova-manage service list
I agree on that one, but here every service runs in the same VM. I think it's a libvirt configuration, which need to be updated. I'll try to dig later On Wed, 16 May 2012 17:41:31 +0200, Joseph Heck he...@me.com wrote: A completely separate potential cause - make sure the time is synchronized between the various hosts. I significant discrepancy there (over 30 seconds I think), will also result in the services thinking they're offline. -joe (this one from hard experience) On May 16, 2012, at 6:48 AM, Gurjar, Unmesh wrote: Restarting libvirt service seemed to resolve the issue for me in the past. Thanks Regards, Unmesh Gurjar | Lead Engineer | Vertex Software Private Ltd. | w. +91.20.6604.1500 x 379 | m. +91.982.324.7631 | unmesh.gur...@nttdata.com | Follow us on Twitter@NTTDATAAmericas From: Leander Bessa Beernaert [mailto:leande...@gmail.com] Sent: Wednesday, May 16, 2012 5:54 PM To: Day, Phil Cc: Gurjar, Unmesh; openstack@lists.launchpad.net Subject: Re: [Openstack] [Compute] nova-compute does not show up as :-) in nova-manage service list I tried 'virsh list', and the command hangs. At first i thought it was because of KVM, since the vm does not support it. I remember having the same problem with diablo, but it would only result in error when the instance was being launched on the compute service. So i changed libvirt_type=kvm to libvirt_type=qemu. However, the problem still remains: virsh list still hangs and compute refuses to leave the state XXX. On Wed, May 16, 2012 at 12:51 PM, Day, Phil philip@hp.com wrote: So the things to check are: - Is the nova-compute service running ? If not the nova-compute.log should show why its failing - If it is running then it probably means that its getting stuck on some long running issue (e.g as down loading an image, problems talking to libvirt, slow response from the DB, etc). XXX in this case means that its slow in updating its services entry rather than failed as such Phil From: openstack-bounces+philip.day=hp@lists.launchpad.net [mailto:openstack-bounces+philip.day=hp@lists.launchpad.net] On Behalf OfLeander Bessa Beernaert Sent: 16 May 2012 12:19 To: Gurjar, Unmesh Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] [Compute] nova-compute does not show up as :-) in nova-manage service list Shouldn't nova-network and nova-scheduler also fail then, since they share the same config file? If so, that's not what's happening with me, only the compute service is listed as XXX. On Wed, May 16, 2012 at 12:10 PM, Gurjar, Unmesh unmesh.gur...@nttdata.com wrote: Hi Leander, The issue is the Compute is not updating its heartbeat (services table in the nova database), which is causing this. You probably need to check database connection string in the nova.conf on the Compute host and the db connection from the Compute host is working. Thanks Regards, Unmesh Gurjar | Lead Engineer | Vertex Software Private Ltd. | w. +91.20.6604.1500 x 379 | m. +91.982.324.7631 | unmesh.gur...@nttdata.com | Follow us on Twitter@NTTDATAAmericas From: openstack-bounces+unmesh.gurjar=nttdata@lists.launchpad.net [mailto:openstack-bounces+unmesh.gurjar=nttdata@lists.launchpad.net]On Behalf Of Leander Bessa Beernaert Sent: Wednesday, May 16, 2012 4:30 PM To: openstack@lists.launchpad.net Subject: [Openstack] [Compute] nova-compute does not show up as :-) in nova-manage service list Hello, I can't get nova-compute to show up as :-) under 'nova-manager service list'. I've checked the logs and can't find any error or warning. I'm using the default packages shipped with ubuntu 12.04 and have installed everything in a virtual machine. Regards, Leander __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding __ Disclaimer:This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Understanding Integration Bridge and MACs
Hi. Sorry for delayed replay. Now precreated VM image is available for easy evaluation. It is announced on ryu-de...@lists.sourceforge.net, I site it for sure. I hope you can get successful result. From: FUJITA Tomonori fujita.tomonori@... Subject: pre-configured VM image file for OpenStack environment with Ryu Hi, We created a VM image file that enables you to easily set up multi-node Nova environment with Ryu in your desktop machine: https://github.com/osrg/ryu/wiki/RYU-OpenStack-environment-VM-image-file-HOWTO Enjoy! On Sun, May 13, 2012 at 07:42:14PM -0500, Salman Malik wrote: Hi Dan and Others, I am trying to understand the actions taken by Ryu when the new instance sends DHCP discover message to dnsmasq. When I launch new instannce it keeps on sending discover messages and controller keeps on dropping these messages. But looking at the traffic I couldn't exactly map which MAC address belonged to which entity. Can someone help me with my understanding of the MAC addresses. Using ifconfig , ovs-ofctl show br-int and ovs-ofctl snoop br-int (output shown after MAC addresses), I know exactly about some MAC addresses and can't figure out some of them: Interfaces |HWAddress |IP-addr - eth0|08:00:27:7a:ff:65|10.0.3.15 eth1|08:00:27:16:d5:09 | 10.0.0.10 plugged into br-int gw-82bd3a73-dc|fa:16:3e:49:57:1b |10.0.0.1 plugged into br-int (this is the --listen-address of my two dnsmasqs) br-int |08:00:27:16:d5:09 | why doesn't bridge have no IP ? new-instance |02:d8:47:48:35:26 == MAC address of newly launched instance? (see output below) Unkown |fa:16:3e:5e:02:17 ==Seemingly unknown MAC address(which is related to the new instance?) Unkown |33:33:00:00:00:16 == MAC address related to multicast ? Questions: 1. What is gw-82bd3a73-dc interface ? 2. I am kind of unsure why br-int is so useful? 3. Why doesn't br-int don't have any IP address? 4. Why do we need to plugin a compute node's interface to br-int? (so that guest instances on remote host can communicate with each other?) 5. What is the relationship b/w 02:d8:47:48:35:26 and fa:16:3e:5e:02:17 MAC addresses in the following output? = Output of : ovs-ofctl snoop br-int = OFPT_ECHO_REQUEST (xid=0x0): 0 bytes of payload OFPT_ECHO_REPLY (xid=0x0): 0 bytes of payload OFPT_PORT_STATUS (xid=0x0): ADD: 7(tap76127847-b1): addr:02:d8:47:48:35:26 config: 0 state: LINK_DOWN current:10MB-FD COPPER OFPT_FLOW_MOD (xid=0x491662da): DEL priority=0 buf:0x0 actions=drop OFPT_BARRIER_REQUEST (xid=0x491662db): OFPT_BARRIER_REPLY (xid=0x491662db): OFPT_PORT_STATUS (xid=0x0): MOD: 7(tap76127847-b1): addr:02:d8:47:48:35:26 config: 0 state: 0 current:10MB-FD COPPER OFPT_ECHO_REQUEST (xid=0x0): 0 bytes of payload OFPT_ECHO_REPLY (xid=0x0): 0 bytes of payload OFPT_PACKET_IN (xid=0x0): total_len=90 in_port=7 data_len=90 buffer=0x0167 tunnel0:in_port0007:tci(0) macfa:16:3e:5e:02:17-33:33:00:00:00:16 type86dd proto58 tos0 ipv6::-ff02::16 port143-0 fa:16:3e:5e:02:17 33:33:00:00:00:16, ethertype IPv6 (0x86dd), length 90: :: ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28 OFPT_PACKET_OUT (xid=0x491662dc): in_port=7 actions_len=0 actions=drop buffer= 0x0167 OFPT_PACKET_IN (xid=0x0): total_len=322 in_port=7 data_len=128 buffer= 0x0168 tunnel0:in_port0007:tci(0) macfa:16:3e:5e:02:17-ff:ff:ff:ff:ff:ff type0800 proto17 tos0 ip0.0.0.0-255.255.255.255 port68-67 fa:16:3e:5e:02:17 ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 128: truncated-ip - 194 bytes missing! 0.0.0.0.68 255.255.255.255.67: BOOTP/DHCP, Request from fa:16:3e:5e:02:17, length 280 OFPT_PACKET_OUT (xid=0x491662dd): in_port=7 actions_len=0 actions=drop buffer= 0x0168 OFPT_PACKET_IN (xid=0x0): total_len=78 in_port=7 data_len=78 buffer=0x0169 fa:16:3e:5e:02:17 ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 128: truncated-ip - 194 bytes missing! 0.0.0.0.68 255.255.255.255.67: BOOTP/DHCP, Request from fa:16:3e:5e:02:17, length 280 OFPT_PACKET_OUT (xid=0x491662e3): in_port=7 actions_len=0 actions=drop buffer= 0x016e OFPT_PACKET_IN (xid=0x0): total_len=70 in_port=7 data_len=70 buffer=0x016f tunnel0:in_port0007:tci(0) macfa:16:3e:5e:02:17-33:33:00:00:00:02 type86dd proto58 tos0 ipv6fe80::f816:3eff:fe5e:217-ff02::2 port133-0 fa:16:3e:5e:02:17 33:33:00:00:00:02, ethertype IPv6 (0x86dd), length 70: fe80::f816:3eff:fe5e:217 ff02::2: ICMP6, router
[Openstack] nova state machine simplification and clarification
Hi, There are vm_states, task_states, and power_states for each VM. The use of them is complicated. Some states are confusing, and sometimes ambiguous. There also lacks a guideline to extend/add new state. This proposal aims to simplify things, explain and define precisely what they mean, and why we need them. A new user-friendly behavior of deleting a VM is also discussed. A TL;DR summary: * power_state is the hypervisor state, loaded “bottom-up” from compute worker; * vm_state reflects the stable state based on API calls, matching user expectation, revised “top-down” within API implementation. * task_state reflects the transition state introduced by in-progress API calls. * “hard” delete of a VM should always succeed no matter what. * power_state and vm_state may conflict with each other, which needs to be resolved case-by-case. It's not a definite guide yet and is up for discussion. I'd like to thank vishy and comstud for the early input. comstud: the task_state is different from when you looked at it. It's a lot closer to what's in the current code. The full text is here and is editable by anyone like etherpad. https://docs.google.com/document/d/1nlKmYld3xxpTv6Xx0Iky6L46smbEqg7-SWPu_o6VJws/edit?pli=1 Thanks, Yun ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Nova] nova floating-ip-list hangs, even when nova-network is running
I've no idea what's happening, but downgrade rabbitmq-server from 2.8.2-2 to 2.8.1-1 fixed the problem. I'm on Debian sid, BTW. Ding Deng ding.d...@gmail.com writes: Hi, I've a new 1-node 2012.1 setup in FlatDHCP mode. When I try to open the Access Security page in Horizon, it hangs. I've also tried the CLI way (nova floating-ip-list), which hangs too. I found some similar reports [0][1] which indicated that there may be something wrong with the nova-network service. But as far as I know, nova-network is fine: # nova-manage service list Binary Host Zone Status State Updated_At nova-console host nova enabled :-) 2012-05-15 22:44:59 nova-consoleauth host nova enabled :-) 2012-05-15 22:44:56 nova-scheduler host nova enabled :-) 2012-05-15 22:44:59 nova-compute host nova enabled :-) 2012-05-15 22:44:58 nova-network host nova enabled :-) 2012-05-15 22:44:59 What should I check next? Thanks. Ding Deng [0] https://bugs.launchpad.net/horizon/+bug/961761 [1] https://bugzilla.redhat.com/show_bug.cgi?id=812661 * nova-api.log 2012-05-16 06:49:42 INFO nova.api.openstack.wsgi [req-3cc1da1e-cfe0-40e4-bbf1-516a5196eca6 1ae03a42d2364fb3bc9fa2162632fdc7 3fbde8c6c6ae431c9798c49d796cc066] GET http://localhost:8774/v1.1/3fbde8c6c6ae431c9798c49d796cc066/os-floating-ips 2012-05-16 06:49:42 DEBUG nova.api.openstack.wsgi [req-3cc1da1e-cfe0-40e4-bbf1-516a5196eca6 1ae03a42d2364fb3bc9fa2162632fdc7 3fbde8c6c6ae431c9798c49d796cc066] Unrecognized Content-Type provided in request from (pid=4372) get_body /usr/lib/python2.7/dist-packages/nova/api/openstack/wsgi.py:697 2012-05-16 06:49:42 DEBUG nova.rpc.amqp [req-3cc1da1e-cfe0-40e4-bbf1-516a5196eca6 1ae03a42d2364fb3bc9fa2162632fdc7 3fbde8c6c6ae431c9798c49d796cc066] Making asynchronous call on network ... from (pid=4372) multicall /usr/lib/python2.7/dist-packages/nova/rpc/amqp.py:321 2012-05-16 06:49:42 DEBUG nova.rpc.amqp [req-3cc1da1e-cfe0-40e4-bbf1-516a5196eca6 1ae03a42d2364fb3bc9fa2162632fdc7 3fbde8c6c6ae431c9798c49d796cc066] MSG_ID is e1d0950c2e014a2a9948f20152a92089 from (pid=4372) multicall /usr/lib/python2.7/dist-packages/nova/rpc/amqp.py:324 2012-05-16 06:49:42 DEBUG nova.rpc.amqp [req-3cc1da1e-cfe0-40e4-bbf1-516a5196eca6 1ae03a42d2364fb3bc9fa2162632fdc7 3fbde8c6c6ae431c9798c49d796cc066] Pool creating new connection from (pid=4372) create /usr/lib/python2.7/dist-packages/nova/rpc/amqp.py:59 2012-05-16 06:49:42 INFO nova.rpc.common [req-3cc1da1e-cfe0-40e4-bbf1-516a5196eca6 1ae03a42d2364fb3bc9fa2162632fdc7 3fbde8c6c6ae431c9798c49d796cc066] Connected to AMQP server on localhost:5672 * nova-network.log Nothing except some periodic tasks. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Infra] Mailing-list split
On Thu, May 10, 2012 at 3:28 PM, James E. Blair cor...@inaugust.com wrote: Duncan McGreggor dun...@dreamhost.com writes: I want to wait on creating openstack-dev until we've got Exim setup properly. Someone else will need to do that. I'm not sure if the mailman Ubuntu package updates Exim properly, and I wouldn't know where to look to check :-/ Take a look at this: https://review.openstack.org/#/c/7319/ It's merged now! Thanks, guys :-) Once it's merged, you (or anyone else) can make changes to the mailman config by proposing patches to that repo. Nice. I'm asking you about this on IRC right now :-) The Exim config will automatically handle new lists (no aliases or any config changes need to happen after running the newlist command). That change enables VERP, but has Exim generate the VERP addresses for efficiency. We need to talk about migrating data: * from the old host to the new one * from LP archives (don't know if that's possible) Do you have access to the old host? I believe Stef knows who to ask to get archives from LP. We need to figure out DNS, and see what we can do about testing the lists/Exim with just the IP address/temp CNAME/etc ... Let me know if you want a temporary alternate A/CNAME record. You'll notice the exim/mailman config has that as a parameter, so it'll be easy for us to change it back. Yeah, let's to a temporary CNAME (actually, maybe A is better? lists.openstack.org points elsewhere...). How about stagelists.openstack.org? We will be able to set the reverse dns for the IP correctly. And when it comes time for the move, we can set the ttl to 300 and make the change for the A record. Nice! Thanks, Jim! d -Jim ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Dashboard] Can't access images/snapshots
Now i made sure nova-volume is installed and running. I still keep running into the same problem. It also happens from the command line tool. This is the output produced http://paste.openstack.org/show/17929/ On Thu, May 17, 2012 at 11:17 AM, Leander Bessa Beernaert leande...@gmail.com wrote: I have no trouble from the command line. One thing i find peculiar is that i haven't installed swift and nova-volume yet and they show up as enabled services in the dashboard. Is that normal? On Wed, May 16, 2012 at 11:39 PM, Sébastien Han han.sebast...@gmail.comwrote: Hi, Do you also have an error when retrieving from the command line? ~Cheers! On Wed, May 16, 2012 at 5:38 PM, Leander Bessa Beernaert leande...@gmail.com wrote: Hello, I keep running into this error when i try to list the images/snapshot in dashboard: http://paste.openstack.org/show/17820/ This is my local_settings.py file: http://paste.openstack.org/show/17822/ , am i missing something? Regards, Leander ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [Infra] Mailing-list split
Oh, one more thing: On Thu, May 10, 2012 at 3:28 PM, James E. Blair cor...@inaugust.com wrote: Duncan McGreggor dun...@dreamhost.com writes: [snip] We need to talk about migrating data: * from the old host to the new one * from LP archives (don't know if that's possible) Do you have access to the old host? I believe Stef knows who to ask to get archives from LP. Yeah, Stef and Ant are working on that. I'm thinking we shouldn't copy the archives until we've actually made the switch, so that we don't miss any messages that might have made it to the old lists in the interim... d ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] RFC: Plugin framework draft
I would appreciate comments on the nascent Nova plugin framework that I'm working on. My Nova code is in a fairly modern forked branch here: https://github.com/andrewbogott/nova/tree/plugin I've also written two example plugins, which live here: https://github.com/andrewbogott/novawikiplugins The two plugins in that repo implement actual features that we need here at Wikimedia Labs -- One of them is an implementation of shared volumes similar to the one I presented at the design summit. Please let me know right away if I've messed up the permissions on either of those repos. And, feel free to add your hopes and dreams under the 'use cases' section of the blueprint at http://wiki.openstack.org/novaplugin. == Long, rambling notes == Goals: 1) Provide rudimentary support code in Nova to help with the development, packing, and installation of custom features 2) Provide a clear interface for third-party code to interact with Nova 3) Establish some basic design patterns and examples for developing, packing, and installing custom features in Nova and/or Openstack. I mention goal 2 in order to defend the 'Plugin' class in my code. My hope is that we can expand on that class and use it as way to enforce that Nova provides a versioned, testable interface for third party code. Alas, not all of the features that my plugin uses (in particular, the additional shell commands in the sharedfs plugin) pass through the plugin class currently. So the scope of the plugin 'interface' is still evolving, and I welcome suggestions about where to draw the lines. Existing features: - Plugin loading via via setup.py and entrypoints - Plugin loading via nova.conf switches - Command-line extension (free, thanks to python-openstackclient) - Extension of the nova REST API - Installation additional notification drivers at runtime - Notification callbacks inherit authorization from the associated request Concerns: - Two different loading pathways -- is that useful or just confusing? - Should the plugin base class interpose itself between the plugin and python-openstackclient in order to enforce interface versioning? Is that even possible? Remaining tasks: - Extending rootwrap (or, specifically, getting gluster into sudo somehow) - Versioning - Describe best practices for modifying core Nova code when necessary (additional notifications and/or synchronous callbacks) - Add your desired features here! ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] [metering] example of discrete counter
I have added a row to the list of counters for discrete events such as uploading an image to glance [1]. Please let me know if you think I need more exposition to explain discrete counters. Doug [1] http://wiki.openstack.org/EfficientMetering?action=diffrev2=89rev1=87 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] RFC - dynamically loading virt drivers
Rationale: nova loads drivers for various subsystems in very different ways, and not all of them are truly dynamic (i.e. a new driver could be fully self contained and not have to change a core source code file or monkey patch to load itself). I'd like to get all the driver plug points fully dynamic, and eventually a common pattern and loading mechanism is used on all of them, from a consistency perspective. I've got a first attempt at refactoring the nova.virt.connection module to stop having a pre-defined list of virt drivers as strings, and instead load modules dynamically using the the nova.openstack.commons.importutils. This is in a branch on github - https://github.com/sdague/nova The changed files are: git diff master | diffstat -w 20 tests/test_virt_driver_loader.py | 54 ++ utils.py |3 virt/connection.py | 51 ++--- virt/fake.py |4 virt/libvirt/__init__.py |1 5 files changed, 75 insertions(+), 38 deletions(-) This passes the unit test battery on fake and libvirt drivers (* on fake) Because the strings passed to connection_type do map to module names, this shouldn't cause any issues with existing configurations. The xenapi and vmwareapi modules probably just need a similar __init__.py addition to make get_connection available on module load. Baremetal will be slightly more work (but not much) because it had some additional setup in nova/virt/connection.py. What I'm mostly looking for is comments on approach. Is importutils the prefered way to go about this (which is the nova.volume approach) now, or should this be using utils.LazyPluggable as is in nova.db.api, or some other approach entirely? Comments, redirections, appreciated. * one test fails for Fake in test_virt_drivers, but only when it's run as the full unit test, not when run on it's own. It looks like it has to do with FakeConnection.instance() caching, which actually confuses me a bit, as I would have assumed one unit test file couldn't affect another (i.e. they started a clean env each time). -Sean -- Sean Dague IBM Linux Technology Center email: sda...@linux.vnet.ibm.com alt-email: slda...@us.ibm.com ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] not able to attach a volume to a running instance
Hello,
I am not able to attach a volume to a running instance.
I am able to create volume but attaching it to the running instance is failing.
Using Essex release.
I am getting the following error:
File /etc/iscsi/initiatorname.iscsi could not be found.
Detailed nova-compute log:
2012-05-17 13:50:28 ERROR nova.rpc.amqp
[req-301e50a2-3238-4924-b7f0-477be7e0ffa8 75899f2562cc44d9aa0f120ff1d246be
6672d2141fe4454e87fad2ba19223327] Exception during message handling
2012-05-17 13:50:28 TRACE nova.rpc.amqp Traceback (most recent call last):
2012-05-17 13:50:28 TRACE nova.rpc.amqp File
/usr/local/lib/python2.7/dist-packages/nova-2012.1-py2.7.egg/nova/rpc/amqp.py,
line 252, in _process_data
2012-05-17 13:50:28 TRACE nova.rpc.amqp rval = node_func(context=ctxt,
**node_args)
2012-05-17 13:50:28 TRACE nova.rpc.amqp File
/usr/local/lib/python2.7/dist-packages/nova-2012.1-py2.7.egg/nova/exception.py,
line 114, in wrapped
2012-05-17 13:50:28 TRACE nova.rpc.amqp return f(*args, **kw)
2012-05-17 13:50:28 TRACE nova.rpc.amqp File
/usr/local/lib/python2.7/dist-packages/nova-2012.1-py2.7.egg/nova/compute/manager.py,
line 153, in decorated_function
2012-05-17 13:50:28 TRACE nova.rpc.amqp function(self, context,
instance_uuid, *args, **kwargs)
2012-05-17 13:50:28 TRACE nova.rpc.amqp File
/usr/local/lib/python2.7/dist-packages/nova-2012.1-py2.7.egg/nova/compute/manager.py,
line 177, in decorated_function
2012-05-17 13:50:28 TRACE nova.rpc.amqp sys.exc_info())
2012-05-17 13:50:28 TRACE nova.rpc.amqp File
/usr/lib/python2.7/contextlib.py, line 24, in __exit__
2012-05-17 13:50:28 TRACE nova.rpc.amqp self.gen.next()
2012-05-17 13:50:28 TRACE nova.rpc.amqp File
/usr/local/lib/python2.7/dist-packages/nova-2012.1-py2.7.egg/nova/compute/manager.py,
line 171, in decorated_function
2012-05-17 13:50:28 TRACE nova.rpc.amqp return function(self, context,
instance_uuid, *args, **kwargs)
2012-05-17 13:50:28 TRACE nova.rpc.amqp File
/usr/local/lib/python2.7/dist-packages/nova-2012.1-py2.7.egg/nova/compute/manager.py,
line 1717, in attach_volume
2012-05-17 13:50:28 TRACE nova.rpc.amqp
self.volume_api.unreserve_volume(context, volume)
2012-05-17 13:50:28 TRACE nova.rpc.amqp File
/usr/lib/python2.7/contextlib.py, line 24, in __exit__
2012-05-17 13:50:28 TRACE nova.rpc.amqp self.gen.next()
2012-05-17 13:50:28 TRACE nova.rpc.amqp File
/usr/local/lib/python2.7/dist-packages/nova-2012.1-py2.7.egg/nova/compute/manager.py,
line 1708, in attach_volume
2012-05-17 13:50:28 TRACE nova.rpc.amqp connector =
self.driver.get_volume_connector(instance_ref)
2012-05-17 13:50:28 TRACE nova.rpc.amqp File
/usr/local/lib/python2.7/dist-packages/nova-2012.1-py2.7.egg/nova/virt/libvirt/connection.py,
line 479, in get_volume_connector
2012-05-17 13:50:28 TRACE nova.rpc.amqp self._initiator =
libvirt_utils.get_iscsi_initiator()
2012-05-17 13:50:28 TRACE nova.rpc.amqp File
/usr/local/lib/python2.7/dist-packages/nova-2012.1-py2.7.egg/nova/virt/libvirt/utils.py,
line 42, in get_iscsi_initiator
2012-05-17 13:50:28 TRACE nova.rpc.amqp contents =
utils.read_file_as_root('/etc/iscsi/initiatorname.iscsi')
2012-05-17 13:50:28 TRACE nova.rpc.amqp File
/usr/local/lib/python2.7/dist-packages/nova-2012.1-py2.7.egg/nova/utils.py,
line 1635, in read_file_as_root
2012-05-17 13:50:28 TRACE nova.rpc.amqp raise
exception.FileNotFound(file_path=file_path)
2012-05-17 13:50:28 TRACE nova.rpc.amqp FileNotFound: File
/etc/iscsi/initiatorname.iscsi could not be found.
2012-05-17 13:50:28 TRACE nova.rpc.amqp
I appreciate any help.
Thanks,
-vj
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Third Party APIs
On May 17, 2012, at 11:57 AM, Andy Edmonds wrote: Hey Vish, In the case of option 2, can such a isolated component remain under the 'nova' module (e.g. the ec2 module under nova/api/) on the nova repository or must it be on a separate repository and yet be, via some means, made easily integrated to the master branch code? Remaining under the nova module would be option 3 (doing it in a feature branch). Option 2 is putting it in a separate repository. Vish Cheers, Andy andy.edmonds.be On Thu, May 17, 2012 at 8:18 PM, Vishvananda Ishaya vishvana...@gmail.com wrote: Hello Everyone, In the ppb meeting last week[1] we discussed third party apis and decided that the policy is not to include them in core. Specifically the motion that passed is: An OpenStack project will support an official API in it's core implementation (the OpenStack API). other APIs will be implemented external to core. the core project will expose stable, complete, performant interfaces so that 3rd party APIs can be implemented in a complete and performant manner. So now that we have settled on a long term goal for third party apis, we need to deal with the short term. We do have a stable interface in Nova in the form of the OpenStack API but it remains to be seen whether it is complete and performant enough to allow other apis to be layered on top of it. Ultimately, I would like to see a stable internal python api that the other apis could speak through (including the OpenStack api layer), but it will probably take a while to get there. In the short term I see three possibilities for third party apis. 1 Proxy Layer This is the approach being taken by AWSOME, and it is definitely the easiest to maintain. It has some big advantages, like allowing new apis deployed in a completely decoupled manner. The main potential drawbacks are performance and an incomplete mapping of concepts from one api to another. This will most likely require adding OpenStack api extensions to support some of the extra features in other apis 2 Separate Project that talks to internal apis It is possible to write a separate component that imports the compute.api in nova and uses it directly. This will deal with the performance issues of the above approach, but it runs the risk of being broken if the compute.api changes over the course of the release. The advantage of this approach is it will drive requirements for having a stable/versioned internal api. In this model, automated testing would be necessary to alert any breakages. 3 Feature Branch in Core We are doing some work to support Feature and Subsystem branches in our CI system. 3rd party apis could live in a feature branch so that they can be tested using our CI infrastructure. This is very similar to the above solution, and gives us a temporary place to do development until the internal apis are more stable. Changes to internal apis and 3rd party apis could be done concurrently in the branch and tested. Once the branch has stabilized, the updates could be pushed into the internal apis in nova, and the 3rd party api could grow up into its own project like option 2 It may be that there are other options that I haven't thought of, but regardless of the approach taken by the various 3rd party apis, I think it is valuable for us all to work together on stabilizing the internal apis. I'd like the ec2 api to be able to live separately as well. Vish [1] http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-05-08-20.00.log.txt ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] nova-manage network create does not create the bridges/vlans immediately
Hi Eric, Actually i am following your guide/pdf based on page 17 and after the vlans were created as example you type the ip addr and brctl show to make sure the bridges and vlans have been created, i guess it just applies to the admin tenant, is it right? because i noticed that if i add in --project_id the id of the Admin Tenant the bridge and vlan is created immediately but if I add another project id it is not created. Thanks in advance, Omar L. On 05/17/2012 07:07 AM, Eric Dodemont wrote: Omar, After you have configured all your networks/vlans with nova-manage network create, no vlan interfaces and no bridges will be created on the nova-network node and the nova-compute nodes. The first vlan interface and bridge will only be created the first time you boot an instance for a given tenant. If you boot for the first time an instance for a given tenant: - a free network/vlan will be attributed to that tenant and this for ever; - a vlan interface with a bridge and a dhcp connected on it will be created on the nova-network node; - a vlan interface with a bridge connected on it will be created on the nova-compute node which has been chosen to run the instance. Eric On 05/17/2012 06:06 AM, Omar Lara wrote: Thanks Nathanael, so the bridges and vlans are created until the instance is created?, because my understanding was that the interfaces were created once the network create is applied, and the interface appears in nova-network node and nova-compute node, is it right? Omar L. On 05/16/2012 10:13 PM, Nathanael Burton wrote: On May 16, 2012 9:47 PM, Omar Lara o...@scasoftware.net mailto:o...@scasoftware.net wrote: Hi, i am trying to deploy a VlanManager networking model in Essex, i am not using Quantum, and my problem is when i try to do: nova-manage network create --label vlan1 --fixed_range_v4 10.0.1.0/24 http://10.0.1.0/24 --num_networks 1 --network_size 256 --vlan 1 --project_id 2e744c1a2032ccb1a0cdf7c5f825d046 The bridge and the vlan are not created immediately, do you have any idea if there is another daemon that needs to run or something so or some additional advice, my nova-network is a server different from the nova-compute. Also i noticed that the ensure_bridge method from linux_net.py never is called, in this script there is the brctl addbr call to posix. root@devlabnova:~# nova-manage network list id IPv4 IPv6 start address DNS1 DNS2 VlanID project uuid 20 10.0.1.0/24 http://10.0.1.0/24 None 10.0.1.3 None None 1 2e744c1a2032ccb1a0cdf7c5f825d046 a667af77-8ffe-42f8-a094-c2ce71d59171 root@devlabnova:~# brctl show bridge namebridge idSTP enabledinterfaces My nova.conf is as follows in terms of nova-network # nova-network # network_manager=nova.network.manager.VlanManager public_interface=eth0 vlan_interface=eth1 network_host=devlabnova fixed_range=10.0.0.0/8 http://10.0.0.0/8 network_size=1024 dhcpbridge_flagfile=/etc/nova/nova.conf dhcpbridge=/usr/bin/nova-dhcpbridge force_dhcp_release=True fixed_ip_disassociate_timeout=30 my_ip=172.16.16.10 Thanks in advance! -- - Omar Lara CEO ScaSoftware t: +52(55) 84.21.84.43 Twitter: @elchito http://www.scasoftware.net - ___ Mailing list: https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack https://launchpad.net/%7Eopenstack More help : https://help.launchpad.net/ListHelp Omar, The vlan tagged interfaces and bridges are created on the fly as needed as users within the relevant projects start instances that are scheduled to the relevant compute nodes. Nate -- - Omar Lara CEO ScaSoftware t: +52(55) 84.21.84.43 Twitter: @elchito http://www.scasoftware.net - ___ Mailing list:https://launchpad.net/~openstack Post to :openstack@lists.launchpad.net Unsubscribe :https://launchpad.net/~openstack More help :https://help.launchpad.net/ListHelp -- - Omar Lara CEO ScaSoftware t: +52(55) 84.21.84.43 Twitter: @elchito http://www.scasoftware.net - ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] RFC - dynamically loading virt drivers
On May 17, 2012, at 1:52 PM, Sean Dague wrote: What I'm mostly looking for is comments on approach. Is importutils the prefered way to go about this (which is the nova.volume approach) now, or should this be using utils.LazyPluggable as is in nova.db.api, or some other approach entirely? Comments, redirections, appreciated. -1 to LazyPluggable So we already have plugabillity by just specifying a different compute_driver config option. I don't like that we defer another level in compute and call get_connection. IMO the best cleanup would be to remove the get_connection altogether and just construct the driver directly based on compute_driver. The main issue with changing this is breaking existing installs. So I guess this would be my strategy: a) remove get_connection from the drivers (and just have it construct the 'connection' class directly) b) modify the global get_connection to construct the drivers for backwards compatibilty c) modify the documentation to suggest changing drivers by specifying the full path to the driver instead of connection_type d) rename the connection classes to something reasonable representing drivers (libvirt.driver:LibvirtDriver() vs libvirt.connection.LibvirtConnection) e) bonus points if it could be done with a short path for ease of use (compute_driver=libvirt.LibvirtDriver vs compute_driver=nova.virt.libvirt.driver.LibvirtDriver) * one test fails for Fake in test_virt_drivers, but only when it's run as the full unit test, not when run on it's own. It looks like it has to do with FakeConnection.instance() caching, which actually confuses me a bit, as I would have assumed one unit test file couldn't affect another (i.e. they started a clean env each time). Generally breakage like this is due to some global state that is not cleaned up, so if FakeConnection is caching globally, then this could happen. Vish ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Swift on Webob-1.2 anyone?
On Wed, 09 May 2012 18:18:52 +0200 Ionuț Arțăriși iartar...@suse.cz wrote: It would be great to have it on 1.2b3, though. I think I had a pretty good start, here: https://review.openstack.org/7569 Not sure if I am doing the right thing, however. I split it like this: - Proxy server does a lot of processing and checking of the keys, so it needs to operate on byte strings, not the unicode (it may be fixed up, but I found it too hard). So, I just force unicode strings that are actually UTF-8 with each UTF-8 byte taking 1 unicode symbol. This is totally wrong, but it works. If someone can cook up an alternative patch, I'm all for it. Note that this permits Proxy to work on keys that are binary garbage, in case of e.g. LFS. - Object, Container, and Account are fixed up to work on Unicode in Pythonic way. One side effect of this is that they ONLY accept UTF-8 encoded keys now. It appears that they verify such, so I am not breaking any compatibility, I think. Would love to see any fixes, objections, additions, etc. -- Pete ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Keystone issue?
Hi,
Working on stable/essex:
When I delete a user-tenant-role keystone continues returning null for the
deleted roles
In the example I have deleted KeystoneAdmin and KeystoneServiceAdmin roles
from a
devstack installation and then added them again as part of my tests
This is the result,
{roles: [{id: 5172006c48c942c499beb79740a8021a, name: admin}, *null,
null*, {id: 5adca868452746388f5d526db1bfcf9c, name: KeystoneAdmin},
{id: fea9871c0e2d492da75c2d4a73c7269b, name: KeystoneServiceAdmin}]}
which causes every nova api call become unusable :
error on auth_token.py [line 398]
TypeError: 'NoneType' object has no attribute '__getitem__'
I think this issue is related to metadata table where roles are not updated
when a role is deleted
--
---
Luis Alberto Gervaso Martin
Woorea Solutions, S.L
CEO CTO
mobile: (+34) 627983344
luis@ luis.gerv...@gmail.comwoorea.es
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Keystone issue?
To reproduce:
First delete a role that is assigned to a tenant-user pair
If you delete tenant-user-role first, and then delete the role all works
fine
Regards
On Fri, May 18, 2012 at 4:33 AM, Luis Gervaso l...@woorea.es wrote:
Hi,
Working on stable/essex:
When I delete a user-tenant-role keystone continues returning null for the
deleted roles
In the example I have deleted KeystoneAdmin and KeystoneServiceAdmin roles
from a
devstack installation and then added them again as part of my tests
This is the result,
{roles: [{id: 5172006c48c942c499beb79740a8021a, name: admin}, *null,
null*, {id: 5adca868452746388f5d526db1bfcf9c, name:
KeystoneAdmin}, {id: fea9871c0e2d492da75c2d4a73c7269b, name:
KeystoneServiceAdmin}]}
which causes every nova api call become unusable :
error on auth_token.py [line 398]
TypeError: 'NoneType' object has no attribute '__getitem__'
I think this issue is related to metadata table where roles are not
updated
when a role is deleted
--
---
Luis Alberto Gervaso Martin
Woorea Solutions, S.L
CEO CTO
mobile: (+34) 627983344
luis@ luis.gerv...@gmail.comwoorea.es
--
---
Luis Alberto Gervaso Martin
Woorea Solutions, S.L
CEO CTO
mobile: (+34) 627983344
luis@ luis.gerv...@gmail.comwoorea.es
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
[Openstack] About openstack common client
Hi,I just want to ask about the relationship among openstackclient https://launchpad.net/python-openstackclient and other clients.Will openstackclient replace other clients ( such as quantum client, keystone client, nova client, xx) or just a supplement?by now, the openstackclient is calling codes from other clients, so it seems it is just another client wrapper. In this case, we will have to implement two set of front codes to call specific client. One will be in openstackclient, and one will be in separate client itself.ThanksYong Sheng Gong ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
