Re: [Openstack] [HyperV][Quantum] Quantum dhcp agent not working for Hyper-V
is the MAC addr coming from the hyper-v on the dhcp request the same one the dhcp-agent is expecting? s On 06/05/2013 03:23 PM, Bruno Oliveira wrote: Hello all, Guys, there's something regarding quantum that we've been hitting our heads against a wall for a few weeks, but can't figure out. Can you please take a look? Here's the scenario: We currently have a single-node devstack build, running nova (compute), glance, quantum (with OpenVSwitch), swift and cinder -- besides keystone and ceilometer. On that very same machine, our kvm hypervisor is running. Everything works like a charm with it: dhcp, magic_ip (169.254.169.254), reaching in/outside networks, etc. Now for the issue: there's another host running hyper-v 2008 r2, and on top of that, we got Cloudbase's (cloudbase.it) Compute Driver for Hyper-V. That way, we're successfully being able to create VMs for it (Hyper-V), BUT... Even though there's a virtual switch in there (hyper-v), the network for the instances are not working - the instances are not being assigned with an IP from quantum-dhcp UNLESS I use the FLAT NETWORK model to assign a public ip for each of them. So... 1. Is there a must to have ANOTHER quantum-server just for hyper-v nodes taking that I do not want to use Flat Network ? (by another, I mean one besides the working one I have for KVM) 2. In our case, we're intending to have NAT IPs for each of the instance we have running on hyper-v, not public_ips directly assigned to them, is it possible? After all the testing and research we did, we concluded that we CAN see the DHCP broadcast coming from hyper-v (via tcpdump'ing on any interface that is on the same subnet) but the DHCP response/reply is not working. Note: $quantum agent-list DOES list the quantum-agent from kvm but not from hyper-v Does anyone have any guesses or suggestions of what we could possibly try ? Thank you a lot -- Bruno Oliveira Developer, Software Engineer ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Steve Heistand NASA Ames Research Center SciCon Group Mail Stop 258-6 steve.heist...@nasa.gov (650) 604-4369 Moffett Field, CA 94035-1000 Any opinions expressed are those of our alien overlords, not my own. # For Remedy# #Action: Resolve# #Resolution: Resolved # #Reason: No Further Action Required # #Tier1: User Code # #Tier2: Other # #Tier3: Assistance # #Notification: None # 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] cinder malformed url error
2013-05-08 02:13:17 WARNING [cinder.scheduler.host_manager] service is down or disabled. 2013-05-08 02:13:17ERROR [cinder.scheduler.manager] Failed to schedule_create_volume: No valid host was found. I'm running the api and scheduler services on the controller node and the volume service on a compute node. Any ideas why cinder doesn't find a valid host? Ive found that even small time differences between nodes can cause issues like this. s -- Steve Heistand NASA Ames Research Center SciCon Group Mail Stop 258-6 steve.heist...@nasa.gov (650) 604-4369 Moffett Field, CA 94035-1000 Any opinions expressed are those of our alien overlords, not my own. # For Remedy# #Action: Resolve# #Resolution: Resolved # #Reason: No Further Action Required # #Tier1: User Code # #Tier2: Other # #Tier3: Assistance # #Notification: None # 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
[Openstack] quantum error and warning message
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
so during instance startup Im getting error and warning messages coming out
in the quantum server log file of the form:
2013-05-06 08:53:20ERROR [quantum.openstack.common.rpc.common] Failed to
publish
message to topic 'e899b2b51aaa4e8091f700e133b9cf46': [Errno 104] Connection
reset by peer
2013-05-06 08:53:21 WARNING [quantum.db.agentschedulers_db] Fail scheduling
network
{'status': u'ACTIVE', 'subnets': [u'b20988bf-fd0c-4789-b80f-77495b71cd5f'],
'name':
u'Net_of_Steve', 'provider:physical_network': None, 'admin_state_up': True,
'tenant_id':
u'ea9aa5e9f0f14715bb2d7ce26f5109a7', 'provider:network_type': u'gre',
'router:external':
False, 'shared': False, 'id': u'54c3b452-5199-4248-97f0-ff3914a6f8cc',
'provider:segmentation_id': 1L}
in general errors are bad yes but how bad in this case and the warning means
what?
the instance seems to boot up fine and gets networking ok. these message done
repeat, just
1 offs for each instance.
thanks
steve
- --
Steve Heistand NASA Ames Research Center
email: steve.heist...@nasa.gov Steve Heistand/Mail Stop 258-6
ph: (650) 604-4369 Bldg. 258, Rm. 232-5
Scientific HPC ApplicationP.O. Box 1
Development/OptimizationMoffett Field, CA 94035-0001
Any opinions expressed are those of our alien overlords, not my own.
# For Remedy#
#Action: Resolve#
#Resolution: Resolved #
#Reason: No Further Action Required #
#Tier1: User Code #
#Tier2: Other #
#Tier3: Assistance #
#Notification: None #
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (GNU/Linux)
iEYEARECAAYFAlGH034ACgkQoBCTJSAkVrHh+ACfQU25Lve1mhoZeMeVoPyeWscX
IuUAn1IM0H62xBmq+N4lNynoyAQA/375
=Valq
-END PGP 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
[Openstack] slow terminate jobs..
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 so in addition to my problem of really long startup times, the process of trying to terminate a number of instances is taking ages as well. currently into an 18 instance terminate and its been 45 minutes. As there probably isnt much data movement involved with terminating a job Im wondering if there is a keystone/nova/mysql/apache/something deadlock going on. normal CLI commands are taking a fairly long time to complete. 10 seconds for a nova service-list (only 16 compute nodes) 8 seconds for a userland nova list (20 instances running) 7 seconds for a keystone tenant-list not really sure there is a question in all this aside from something like has anyone else seen such slowness? s - -- Steve Heistand NASA Ames Research Center email: steve.heist...@nasa.gov Steve Heistand/Mail Stop 258-6 ph: (650) 604-4369 Bldg. 258, Rm. 232-5 Scientific HPC ApplicationP.O. Box 1 Development/OptimizationMoffett Field, CA 94035-0001 Any opinions expressed are those of our alien overlords, not my own. # For Remedy# #Action: Resolve# #Resolution: Resolved # #Reason: No Further Action Required # #Tier1: User Code # #Tier2: Other # #Tier3: Assistance # #Notification: None # -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAlGD/noACgkQoBCTJSAkVrEvOACg1/mjC45NrTey36xvNrhmOlM1 mhAAn0Q3I2vu20ydFmlZzcL6tmhjmldG =dRui -END PGP 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] slow terminate jobs..
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 well there are a lot (68) beam.smp processes running, well in existence only a few at a time are consuming cpu time. Aside from that Im not sure how to answer the question. or does this perhaps indicate a problem: root@cloudfe:/var/log/rabbitmq# tail /var/log/rabbitmq/rab...@cloudfe.log =INFO REPORT 3-May-2013::11:14:36 === starting TCP connection 0.14589.260 from 10.0.1.16:40015 =INFO REPORT 3-May-2013::11:19:13 === accepted TCP connection on [::]:5672 from 10.0.1.16:40233 5 minutes from starting connection to accepted connection. thanks s On 05/03/2013 11:22 AM, eric_e_sm...@dell.com wrote: How does RabbitMQ look? Are the messages being consumed in a timely fashion? -Original Message- From: Openstack [mailto:openstack-bounces+eric_e_smith=dell@lists.launchpad.net] On Behalf Of Steve Heistand Sent: Friday, May 03, 2013 1:14 PM To: openstack@lists.launchpad.net Subject: [Openstack] slow terminate jobs.. so in addition to my problem of really long startup times, the process of trying to terminate a number of instances is taking ages as well. currently into an 18 instance terminate and its been 45 minutes. As there probably isnt much data movement involved with terminating a job Im wondering if there is a keystone/nova/mysql/apache/something deadlock going on. normal CLI commands are taking a fairly long time to complete. 10 seconds for a nova service-list (only 16 compute nodes) 8 seconds for a userland nova list (20 instances running) 7 seconds for a keystone tenant-list not really sure there is a question in all this aside from something like has anyone else seen such slowness? s ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp - -- Steve Heistand NASA Ames Research Center email: steve.heist...@nasa.gov Steve Heistand/Mail Stop 258-6 ph: (650) 604-4369 Bldg. 258, Rm. 232-5 Scientific HPC ApplicationP.O. Box 1 Development/OptimizationMoffett Field, CA 94035-0001 Any opinions expressed are those of our alien overlords, not my own. # For Remedy# #Action: Resolve# #Resolution: Resolved # #Reason: No Further Action Required # #Tier1: User Code # #Tier2: Other # #Tier3: Assistance # #Notification: None # -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAlGEAcYACgkQoBCTJSAkVrHmDwCgzC1XvbqxfE62BuKhb3iU95AL miUAoKFFQ6xXZ0Zs6ImFFzG02v8/Q/uz =R+69 -END PGP 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] slow terminate jobs..
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I hadnt seen the management plugin. I am updating from the rabbitmq's repo as the default (and canonical's) repos dont have a version new enough. it also seems there are new openstack versions in canonical's that I will upgrade to as well. once everything reboots I will see what the plugin says. thanks s On 05/03/2013 11:43 AM, eric_e_sm...@dell.com wrote: Have you by chance looked at the management plugin for RabbitMQ? http://www.rabbitmq.com/management.html You can get great information from the management CLI / Web UI and quickly determine if RabbitMQ is having a problem. -Original Message- From: Steve Heistand [mailto:steve.heist...@nasa.gov] Sent: Friday, May 03, 2013 1:28 PM To: Smith, Eric E Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] slow terminate jobs.. well there are a lot (68) beam.smp processes running, well in existence only a few at a time are consuming cpu time. Aside from that Im not sure how to answer the question. or does this perhaps indicate a problem: root@cloudfe:/var/log/rabbitmq# tail /var/log/rabbitmq/rab...@cloudfe.log =INFO REPORT 3-May-2013::11:14:36 === starting TCP connection 0.14589.260 from 10.0.1.16:40015 =INFO REPORT 3-May-2013::11:19:13 === accepted TCP connection on [::]:5672 from 10.0.1.16:40233 5 minutes from starting connection to accepted connection. thanks s On 05/03/2013 11:22 AM, eric_e_sm...@dell.com wrote: How does RabbitMQ look? Are the messages being consumed in a timely fashion? -Original Message- From: Openstack [mailto:openstack-bounces+eric_e_smith=dell@lists.launchpad.net] On Behalf Of Steve Heistand Sent: Friday, May 03, 2013 1:14 PM To: openstack@lists.launchpad.net Subject: [Openstack] slow terminate jobs.. so in addition to my problem of really long startup times, the process of trying to terminate a number of instances is taking ages as well. currently into an 18 instance terminate and its been 45 minutes. As there probably isnt much data movement involved with terminating a job Im wondering if there is a keystone/nova/mysql/apache/something deadlock going on. normal CLI commands are taking a fairly long time to complete. 10 seconds for a nova service-list (only 16 compute nodes) 8 seconds for a userland nova list (20 instances running) 7 seconds for a keystone tenant-list not really sure there is a question in all this aside from something like has anyone else seen such slowness? s ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp - -- Steve Heistand NASA Ames Research Center email: steve.heist...@nasa.gov Steve Heistand/Mail Stop 258-6 ph: (650) 604-4369 Bldg. 258, Rm. 232-5 Scientific HPC ApplicationP.O. Box 1 Development/OptimizationMoffett Field, CA 94035-0001 Any opinions expressed are those of our alien overlords, not my own. # For Remedy# #Action: Resolve# #Resolution: Resolved # #Reason: No Further Action Required # #Tier1: User Code # #Tier2: Other # #Tier3: Assistance # #Notification: None # -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAlGECrsACgkQoBCTJSAkVrGi9ACcDWuFH3C5vrstu7egwACM6Kn6 qYkAoJs/TUwJqEJCKdL2FJLO/R+YKelU =9Mr+ -END PGP 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
[Openstack] time from patch to canonical repo?
is there any way to judge how long it takes a patch to go from committed into the source tree until it shows up in the canonical repo? or alternatively I guess are there a guide to building from source? thanks -- Steve Heistand NASA Ames Research Center SciCon Group Mail Stop 258-6 steve.heist...@nasa.gov (650) 604-4369 Moffett Field, CA 94035-1000 Any opinions expressed are those of our alien overlords, not my own. # For Remedy# #Action: Resolve# #Resolution: Resolved # #Reason: No Further Action Required # #Tier1: User Code # #Tier2: Other # #Tier3: Assistance # #Notification: None # 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] Cinder - attach / detach / reattach fails
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have noticed in grizzly that sometimes the actual iscsi device is still logged in on the compute node where the VM is. This has caused the issue you described, running an iscsiadm --logout on the device makes it go back to normal. s On 05/02/2013 07:28 AM, eric_e_sm...@dell.com wrote: Has anyone seen this issue in Folsom? -Original Message- From: B, Vivekanandan (HP Software (BLR)) [mailto:vivekanandan.bangarus...@hp.com] Sent: Thursday, May 02, 2013 8:59 AM To: Smith, Eric E; openstack@lists.launchpad.net Subject: RE: Cinder - attach / detach / reattach fails Hi, I tried the same on my Grizzly setup and I was able to add the same volume back with the same device file name. ~Vivek -Original Message- From: Openstack [mailto:openstack-bounces+bvivek=hp@lists.launchpad.net] On Behalf Of eric_e_sm...@dell.com Sent: Thursday, May 02, 2013 6:29 PM To: openstack@lists.launchpad.net Subject: Re: [Openstack] Cinder - attach / detach / reattach fails A little more information, I've discovered that this only happens if I reuse the previous device (/dev/vdc in this instance). If I use the next device (/dev/vdd) the attachment works fine. -Original Message- From: Openstack [mailto:openstack-bounces+eric_e_smith=dell@lists.launchpad.net] On Behalf Of Smith, Eric E Sent: Thursday, May 02, 2013 7:42 AM To: openstack@lists.launchpad.net Subject: [Openstack] Cinder - attach / detach / reattach fails Is this a bug perhaps? I have a volume and a VM, I can attach the volume to the VM and see the disk with fdisk -l, I can detach the volume and see it is missing. When I try to reattach the volume I get the following error: May 2 12:18:01 compute-4 ERROR nova.compute.manager [instance: 4fcd874f-f8e5-4a08-9745-838b0636bd83] Failed to attach volume 2e307a3d-3635-432d-99ed-6e8f5792 at /dev/vdc 0122013-05-02 12:18:01,209 30214 TRACE nova.compute.manager [instance: 4fcd874f-f8e5-4a08-9745-838b0636bd83] Traceback (most recent call last): 0122013-05-02 12:18:01,209 30214 TRACE nova.compute.manager [instance: 4fcd874f-f8e5-4a08-9745-838b0636bd83] File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 2039, in _attach_volume 0122013-05-02 12:18:01,209 30214 TRACE nova.compute.manager [instance: 4fcd874f-f8e5-4a08-9745-838b0636bd83] mountpoint) 0122013-05-02 12:18:01,209 30214 TRACE nova.compute.manager [instance: 4fcd874f-f8e5-4a08-9745-838b0636bd83] File /usr/lib/python2.7/dist-packages/nova/exception.py, line 104, in wrapped 0122013-05-02 12:18:01,209 30214 TRACE nova.compute.manager [instance: 4fcd874f-f8e5-4a08-9745-838b0636bd83] temp_level, payload) 0122013-05-02 12:18:01,209 30214 TRACE nova.compute.manager [instance: 4fcd874f-f8e5-4a08-9745-838b0636bd83] File /usr/lib/python2.7/contextlib.py, line 24, in __exit__ 0122013-05-02 12:18:01,209 30214 TRACE nova.compute.manager [instance: 4fcd874f-f8e5-4a08-9745-838b0636bd83] self.gen.next() 0122013-05-02 12:18:01,209 30214 TRACE nova.compute.manager [instance: 4fcd874f-f8e5-4a08-9745-838b0636bd83] File /usr/lib/python2.7/dist-packages/nova/exception.py, line 79, in wrapped 0122013-05-02 12:18:01,209 30214 TRACE nova.compute.manager [instance: 4fcd874f-f8e5-4a08-9745-838b0636bd83] return f(*args, **kw) 0122013-05-02 12:18:01,209 30214 TRACE nova.compute.manager [instance: 4fcd874f-f8e5-4a08-9745-838b0636bd83] File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py, line 673, in attach_volume 0122013-05-02 12:18:01,209 30214 TRACE nova.compute.manager [instance: 4fcd874f-f8e5-4a08-9745-838b0636bd83] mount_device) Does anyone else have this issue? ___ 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 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp - -- Steve Heistand NASA Ames Research Center email: steve.heist...@nasa.gov Steve Heistand/Mail Stop 258-6 ph: (650) 604-4369 Bldg. 258, Rm. 232-5 Scientific HPC ApplicationP.O. Box 1 Development/OptimizationMoffett Field, CA 94035-0001
Re: [Openstack] launching multiple VMs takes very long time
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 ok a followup to this. its not any sort of disk access issue. I created a new disk to hold the glance directory and running atop while launching shows all the activity on the original root drive nothing using glance. Normally at idle the root drive does get heavily used by something, mostly keystone and rabbit so atop show that partition as busy. When launching a VM it doesnt seem to get more busy though. (maybe an LVM / is a bad idea) Ive also tried launching tiny (ie cirros) images and they too take ages to boot into tiny flavors. The really really weird part is that I ran an experiment of only launching 1 vm at a time. the time this takes grows each time I launch one. 1st vm 2 minutes 2nd 2.5m 3rd 4m 4th 8m 5th 10m 6th 12m ... there may be some network issues going on here, trying to shove some amount of data bigger then a few Gig seems to start slowing things down. s On 04/30/2013 11:42 AM, Steve Heistand wrote: if I launch one vm at a time its doesnt very long to start up the instance. maybe a minute. if I launch 4 instances (of the same snapshot as before) it takes 30 minutes. they are all launching to different compute nodes, the controllers are all multicore, I dont see any processes on the compute nodes taking much cpu power, the controller has a keystone process mostly sucking up 1 core, loads and loads of beam.smp from rabbitmq but none are really taking any cpu time. the glance image storage is on the controller node, the snapshots are 2-3G in size. where should I start looking to find out why things are so slow? thanks s - -- Steve Heistand NASA Ames Research Center email: steve.heist...@nasa.gov Steve Heistand/Mail Stop 258-6 ph: (650) 604-4369 Bldg. 258, Rm. 232-5 Scientific HPC ApplicationP.O. Box 1 Development/OptimizationMoffett Field, CA 94035-0001 Any opinions expressed are those of our alien overlords, not my own. # For Remedy# #Action: Resolve# #Resolution: Resolved # #Reason: No Further Action Required # #Tier1: User Code # #Tier2: Other # #Tier3: Assistance # #Notification: None # -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAlGBVD4ACgkQoBCTJSAkVrErjACfetTt4wDzuh9Pq8AuI+iGjXFB toMAmgKR96PJ89edpdHnRyjFyqN25g6k =/+lx -END PGP 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] launching multiple VMs takes very long time
so I dont think there is a network or disk bottle neck now. in watching instances launch I see that the disk image itself gets copied out to the compute node in 1 minute, the xml file for libvirt gets created. then a pause of ~ 20 minutes then the kvm process starts up and off the VM goes just fine. aside from messages like: 2013-05-01 19:43:40.363+: 2377: warning : virAuditSend:135 : Failed to send audit message virt=kvm vm=instance-014c uuid=d72afa21-844a-4ea0-8b96-0a4e5e4da5eb vm-ctx=? img-ctx=? model=stack: Operation not permitted and these dont start until the kvm process starts, I see nothing in the logs. but then I dont have debug on which I will do next. what is causing the pause in between is the question. hopefully debug on will help. s On 05/01/2013 11:43 AM, Rick Jones wrote: On 05/01/2013 10:43 AM, Steve Heistand wrote: there may be some network issues going on here, trying to shove some amount of data bigger then a few Gig seems to start slowing things down. If you think there is an actual network problem, you could I suppose try exploring that with netperf or iperf. It seems unlikely that the network could retain a memory of a previous transfer to cause a subsequent, non-overlapping transfer to run more slowly. The logs on the compute node(s) will show how long it took to actually retrieve the image yes? rick jones -- Steve Heistand NASA Ames Research Center SciCon Group Mail Stop 258-6 steve.heist...@nasa.gov (650) 604-4369 Moffett Field, CA 94035-1000 Any opinions expressed are those of our alien overlords, not my own. # For Remedy# #Action: Resolve# #Resolution: Resolved # #Reason: No Further Action Required # #Tier1: User Code # #Tier2: Other # #Tier3: Assistance # #Notification: None # 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
[Openstack] detach volume from horizon?
Im not seeing a way to detach a volume from within horizon? is this CLI only? s -- Steve Heistand NASA Ames Research Center SciCon Group Mail Stop 258-6 steve.heist...@nasa.gov (650) 604-4369 Moffett Field, CA 94035-1000 Any opinions expressed are those of our alien overlords, not my own. # For Remedy# #Action: Resolve# #Resolution: Resolved # #Reason: No Further Action Required # #Tier1: User Code # #Tier2: Other # #Tier3: Assistance # #Notification: None # 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] detach volume from horizon?
heh :) to my old eyes that looked like delete not detach. will have to crank up font size me thinks. s On 04/30/2013 09:15 AM, eric_e_sm...@dell.com wrote: I guess it depends on the version of horizon you're using, in horizon while logged in as a member of the project who owns the volume, do you see Volumes--Edit Attachments--Detach Volume? -Original Message- From: Openstack [mailto:openstack-bounces+eric_e_smith=dell@lists.launchpad.net] On Behalf Of Steve Heistand Sent: Tuesday, April 30, 2013 10:45 AM To: openstack@lists.launchpad.net Subject: [Openstack] detach volume from horizon? Im not seeing a way to detach a volume from within horizon? is this CLI only? s -- Steve Heistand NASA Ames Research Center SciCon Group Mail Stop 258-6 steve.heist...@nasa.gov (650) 604-4369 Moffett Field, CA 94035-1000 Any opinions expressed are those of our alien overlords, not my own. # For Remedy# #Action: Resolve# #Resolution: Resolved # #Reason: No Further Action Required # #Tier1: User Code # #Tier2: Other # #Tier3: Assistance # #Notification: None # 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
[Openstack] launching multiple VMs takes very long time
if I launch one vm at a time its doesnt very long to start up the instance. maybe a minute. if I launch 4 instances (of the same snapshot as before) it takes 30 minutes. they are all launching to different compute nodes, the controllers are all multicore, I dont see any processes on the compute nodes taking much cpu power, the controller has a keystone process mostly sucking up 1 core, loads and loads of beam.smp from rabbitmq but none are really taking any cpu time. the glance image storage is on the controller node, the snapshots are 2-3G in size. where should I start looking to find out why things are so slow? thanks s -- Steve Heistand NASA Ames Research Center SciCon Group Mail Stop 258-6 steve.heist...@nasa.gov (650) 604-4369 Moffett Field, CA 94035-1000 Any opinions expressed are those of our alien overlords, not my own. # For Remedy# #Action: Resolve# #Resolution: Resolved # #Reason: No Further Action Required # #Tier1: User Code # #Tier2: Other # #Tier3: Assistance # #Notification: None # 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] launching multiple VMs takes very long time
They are all booting the same image. there still may be a random read issues if they arent mostly synced in copying the file to the compute node. But there isnt much of a load on the disk while the instances are being launched. Its just a sata drive at this point so the performance isnt great but better then this. The network isnt being used much either during launch. At least as near as I can tell from netstat and trying to move data around independently of openstack. scp'ing a file for example from controller to compute (being launched on) shows basically no different in speed vs no launch on at the same time. I did have to drop the mtu9000 on the network devices. Not sure if it was the switch or what but after so much data performance just tanked and stayed bad. on normal mtu1500 it stayed good. On 04/30/2013 11:56 AM, Rick Jones wrote: On 04/30/2013 11:42 AM, Steve Heistand wrote: if I launch one vm at a time its doesnt very long to start up the instance. maybe a minute. if I launch 4 instances (of the same snapshot as before) it takes 30 minutes. they are all launching to different compute nodes, the controllers are all multicore, I dont see any processes on the compute nodes taking much cpu power, the controller has a keystone process mostly sucking up 1 core, loads and loads of beam.smp from rabbitmq but none are really taking any cpu time. the glance image storage is on the controller node, the snapshots are 2-3G in size. where should I start looking to find out why things are so slow? I am something of a networking guy so that will color my response :) Is each instance using the same image or a different one? If a different one, the workload to the glance storage will become (I suspect) a random read workload accessing the four different images even though each individual stream may be sequential. How much storage oomph do you have on/serving the glance/controller node? After that, what do the network statistics look like? Starting I suppose with the glance/controller node. Take some snapshots over an interval in each case and run them through something like beforeafter: netstat -s before ...wait a defined/consistent moment... netstat -s after beforeafter before after delta and go from there. rick jones -- Steve Heistand NASA Ames Research Center SciCon Group Mail Stop 258-6 steve.heist...@nasa.gov (650) 604-4369 Moffett Field, CA 94035-1000 Any opinions expressed are those of our alien overlords, not my own. # For Remedy# #Action: Resolve# #Resolution: Resolved # #Reason: No Further Action Required # #Tier1: User Code # #Tier2: Other # #Tier3: Assistance # #Notification: None # 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] launching multiple VMs takes very long time
this certainly looks promising.. thanks s On 04/30/2013 01:36 PM, Melanie Witt wrote: This presentation from the summit might be of interest to you: http://www.openstack.org/summit/portland-2013/session-videos/presentation/scaling-the-boot-barrier-identifying-and-eliminating-contention-in-openstack I couldn't find just the slide deck anywhere so far. Your issue is different being that you're seeing 30 minute launch time, that's extreme, but this info might help you get a high level picture of the flow. Melanie On 4/30/13 11:42 AM, Steve Heistand wrote: if I launch one vm at a time its doesnt very long to start up the instance. maybe a minute. if I launch 4 instances (of the same snapshot as before) it takes 30 minutes. they are all launching to different compute nodes, the controllers are all multicore, I dont see any processes on the compute nodes taking much cpu power, the controller has a keystone process mostly sucking up 1 core, loads and loads of beam.smp from rabbitmq but none are really taking any cpu time. the glance image storage is on the controller node, the snapshots are 2-3G in size. where should I start looking to find out why things are so slow? thanks s ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Steve Heistand NASA Ames Research Center SciCon Group Mail Stop 258-6 steve.heist...@nasa.gov (650) 604-4369 Moffett Field, CA 94035-1000 Any opinions expressed are those of our alien overlords, not my own. # For Remedy# #Action: Resolve# #Resolution: Resolved # #Reason: No Further Action Required # #Tier1: User Code # #Tier2: Other # #Tier3: Assistance # #Notification: None # 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
[Openstack] weird nova attach of a volume
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 ok so I have a volume that Im trying to attach to an instance from within horizon. It always fails with the message of could not attach volume. I try it via a nova CLI version and get messages about /dev/vdb is already in use. I had tried to attach it to /dev/vdb. I move up to vdc and same issue. I go up to vdd and all is well. however it actually shows up in the instance as /dev/vdb. so a) why is it thinking something is already using the devices when they really arent in use. b) related but not part of this problem: why is it ignoring the device I give it to mount to and just pick then next available vd device? thanks (grizzly/ubunt 12.04 controllers/centos 6.4 VMs.) steve - -- Steve Heistand NASA Ames Research Center email: steve.heist...@nasa.gov Steve Heistand/Mail Stop 258-6 ph: (650) 604-4369 Bldg. 258, Rm. 232-5 Scientific HPC ApplicationP.O. Box 1 Development/OptimizationMoffett Field, CA 94035-0001 Any opinions expressed are those of our alien overlords, not my own. # For Remedy# #Action: Resolve# #Resolution: Resolved # #Reason: No Further Action Required # #Tier1: User Code # #Tier2: Other # #Tier3: Assistance # #Notification: None # -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAlF+op0ACgkQoBCTJSAkVrG/nQCcCFr00+an/i8revlFbxT+KBNH zfEAn3b5C3t7tou1yo9Ykh1t8pFfxBL9 =LpWd -END PGP 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
[Openstack] openstack and PBS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 has anyone heard or seen (or got working) an interface to openstack from PBS's batch system? thanks s - -- Steve Heistand NASA Ames Research Center email: steve.heist...@nasa.gov Steve Heistand/Mail Stop 258-6 ph: (650) 604-4369 Bldg. 258, Rm. 232-5 Scientific HPC ApplicationP.O. Box 1 Development/OptimizationMoffett Field, CA 94035-0001 Any opinions expressed are those of our alien overlords, not my own. # For Remedy# #Action: Resolve# #Resolution: Resolved # #Reason: No Further Action Required # #Tier1: User Code # #Tier2: Other # #Tier3: Assistance # #Notification: None # -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAlF+r4EACgkQoBCTJSAkVrH4hgCg8S9lb4lcJsHFJFcmt4csltB8 UeIAn0mG+Hi3Z+iqi0jfbvMSoDwb8LEY =LO+J -END PGP 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] weird nova attach of a volume
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 followup on this, what I think is going on: I have an image that I am tweaking and snapshot'ing. the snapshot process remembers that a volume is attached to it but doesnt attach the volume to it when you launch a new copy of the snapshot. ideally snapshot shouldnt save what volumes are currently attached to it. filing bug. s On 04/29/2013 09:41 AM, Steve Heistand wrote: ok so I have a volume that Im trying to attach to an instance from within horizon. It always fails with the message of could not attach volume. I try it via a nova CLI version and get messages about /dev/vdb is already in use. I had tried to attach it to /dev/vdb. I move up to vdc and same issue. I go up to vdd and all is well. however it actually shows up in the instance as /dev/vdb. so a) why is it thinking something is already using the devices when they really arent in use. b) related but not part of this problem: why is it ignoring the device I give it to mount to and just pick then next available vd device? thanks (grizzly/ubunt 12.04 controllers/centos 6.4 VMs.) steve ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp - -- Steve Heistand NASA Ames Research Center email: steve.heist...@nasa.gov Steve Heistand/Mail Stop 258-6 ph: (650) 604-4369 Bldg. 258, Rm. 232-5 Scientific HPC ApplicationP.O. Box 1 Development/OptimizationMoffett Field, CA 94035-0001 Any opinions expressed are those of our alien overlords, not my own. # For Remedy# #Action: Resolve# #Resolution: Resolved # #Reason: No Further Action Required # #Tier1: User Code # #Tier2: Other # #Tier3: Assistance # #Notification: None # -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAlF+v60ACgkQoBCTJSAkVrGZKACgu58xJW3peSX3Ima78uMYG7CL nJ4AoOjZuJhmmTM2yjRTWogLKwvUhhXD =DpfG -END PGP 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
[Openstack] multiple snapshots at once?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 when I try to snapshot multiple instances at the same time weird things happen. should I be able to do this or do I really need to do only 1 at a time? thanks s - -- Steve Heistand NASA Ames Research Center email: steve.heist...@nasa.gov Steve Heistand/Mail Stop 258-6 ph: (650) 604-4369 Bldg. 258, Rm. 232-5 Scientific HPC ApplicationP.O. Box 1 Development/OptimizationMoffett Field, CA 94035-0001 Any opinions expressed are those of our alien overlords, not my own. # For Remedy# #Action: Resolve# #Resolution: Resolved # #Reason: No Further Action Required # #Tier1: User Code # #Tier2: Other # #Tier3: Assistance # #Notification: None # -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAlF5XEEACgkQoBCTJSAkVrFeWQCff8pbD+2kVi9L6BxKEGVO+bIR I4cAoJ8YfGFil4jPrpWoGYPyPFzVxy/q =n5mr -END PGP 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
[Openstack] [openstack][quantum] stuck subnet
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 so I had a tenant that was assigned a floating IP. I deleted the project before I freed up the floating IP. Now I cant clean up a subnet as it still thinks there is an IP attached to it. any ideas how to get rid of a subnet when it thinks there is a float assigned to it that is owned by a tenant that doesnt exist? thanks s - -- Steve Heistand NASA Ames Research Center email: steve.heist...@nasa.gov Steve Heistand/Mail Stop 258-6 ph: (650) 604-4369 Bldg. 258, Rm. 232-5 Scientific HPC ApplicationP.O. Box 1 Development/OptimizationMoffett Field, CA 94035-0001 Any opinions expressed are those of our alien overlords, not my own. # For Remedy# #Action: Resolve# #Resolution: Resolved # #Reason: No Further Action Required # #Tier1: User Code # #Tier2: Other # #Tier3: Assistance # #Notification: None # -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAlF5gEQACgkQoBCTJSAkVrHFOgCg6rIHRsD2BAoi5xrq5eM553qD accAoOcRHeSXdmJ8HlDAYGgHRpKYuEXm =zq/V -END PGP 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] [OpenStack] What is the best place to run quantum-ovs-cleanup
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I put it in the file:/etc/init/quantum-server.conf post-start script /usr/bin/quantum-ovs-cleanup exit 1 end script On 04/24/2013 02:45 AM, Balamurugan V G wrote: Hi, It seems due to an OVS quantum bug, we need to run the utility quantum-ovs-cleanup before any of the quantum services start, upon a server reboot. Where is the best place to put this utility to run automatically when a server reboots so that the OVS issue is automatically addressed? A script in /etc/init.d or just plugging in a call for quantum-ovs-cleanup in an existing script? Thanks, Balu ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp - -- Steve Heistand NASA Ames Research Center email: steve.heist...@nasa.gov Steve Heistand/Mail Stop 258-6 ph: (650) 604-4369 Bldg. 258, Rm. 232-5 Scientific HPC ApplicationP.O. Box 1 Development/OptimizationMoffett Field, CA 94035-0001 Any opinions expressed are those of our alien overlords, not my own. # For Remedy# #Action: Resolve# #Resolution: Resolved # #Reason: No Further Action Required # #Tier1: User Code # #Tier2: Other # #Tier3: Assistance # #Notification: None # -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAlF36C8ACgkQoBCTJSAkVrGqMACg3Jm7tTBwx08oOSaiTVux7sRl cNMAn0OMrAElV2CZgqZFaayoeOitQMUn =TGy3 -END PGP 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
[Openstack] [Quantum] traffic routes question
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Im having trouble getting the floating IPs on the external network accessible from the outside world. From the network node they work fine but somehow I doubt that means anything. so my network node (also controller node) has 4 ethernets, 1 for management, 1 for VM traffic, 1 that is an extra external connection in case I screw things up and an external connection that is bridged for the normal br-ex interface. the two internal are 10.X, 172.X types, the two external are on the same subnet, .100 for extra, .101 for the 1 qrouter set up at the moment. The external subnet was created with a gateway pointing at the next hop upstream from the network node. setting a VM with an external IP (.102) works ok, from the network node I can ssh into it and all, from other other VMs I can get to the external floating IP. But I doubt any of that means its really set up correctly. My question is this, the upstream routers all think the next hop for the floating IPs are the .101 qrouter IP address. The router that gets set up will route packets in from this side of things will it not? Ive tried turning off iptables in case something was blocking traffic but that didnt help anything. Ive tried tcpdump on the gateway router device (qg-9dd1a800-c5/.101) and see stuff going to the .102 IP when its coming from the VMs. But nothing when I try to connect to it from the outside world. Dont see any traffic for .102 on the other external network either. I dont have any access to the next hop upstream to see what packets are going where. But this should all work correct? thanks s - -- Steve Heistand NASA Ames Research Center email: steve.heist...@nasa.gov Steve Heistand/Mail Stop 258-6 ph: (650) 604-4369 Bldg. 258, Rm. 232-5 Scientific HPC ApplicationP.O. Box 1 Development/OptimizationMoffett Field, CA 94035-0001 Any opinions expressed are those of our alien overlords, not my own. # For Remedy# #Action: Resolve# #Resolution: Resolved # #Reason: No Further Action Required # #Tier1: User Code # #Tier2: Other # #Tier3: Assistance # #Notification: None # -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAlF38CcACgkQoBCTJSAkVrF16QCfXGes9kYSqi0jS3x5Es5Asrs+ fUUAnAkvRJXLY2eMN5N6+RuxZaWmzZe5 =/qEk -END PGP 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] [OpenStack] What is the best place to run quantum-ovs-cleanup
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 it was mentioned to me (by Mr Mihaiescu) that this only works if controller and network node are on the same machine. For the compute nodes I had forgotten its in a different place. On them I am doing it in a pre-start script in quantum-plugin-openvswitch-agent.conf. if the controller/network are on different machines certainly in the quantum-server.conf work on which ever one of them is actually using it, if it doesnt the command will have to be in a different startup script. It was also mentioned that putting things in /etc/rc.local and then restarting all the quantum related services might work too. steve On 04/24/2013 08:15 AM, Balamurugan V G wrote: Thanks Steve. I came across another way at https://bugs.launchpad.net/quantum/+bug/1084355/comments/15. It seems to work as well. But your solution is simpler :) Regards, Balu On Wed, Apr 24, 2013 at 7:41 PM, Steve Heistand steve.heist...@nasa.gov wrote: I put it in the file:/etc/init/quantum-server.conf post-start script /usr/bin/quantum-ovs-cleanup exit 1 end script On 04/24/2013 02:45 AM, Balamurugan V G wrote: Hi, It seems due to an OVS quantum bug, we need to run the utility quantum-ovs-cleanup before any of the quantum services start, upon a server reboot. Where is the best place to put this utility to run automatically when a server reboots so that the OVS issue is automatically addressed? A script in /etc/init.d or just plugging in a call for quantum-ovs-cleanup in an existing script? Thanks, Balu ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp - -- Steve Heistand NASA Ames Research Center email: steve.heist...@nasa.gov Steve Heistand/Mail Stop 258-6 ph: (650) 604-4369 Bldg. 258, Rm. 232-5 Scientific HPC ApplicationP.O. Box 1 Development/OptimizationMoffett Field, CA 94035-0001 Any opinions expressed are those of our alien overlords, not my own. # For Remedy# #Action: Resolve# #Resolution: Resolved # #Reason: No Further Action Required # #Tier1: User Code # #Tier2: Other # #Tier3: Assistance # #Notification: None # -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAlF3+K8ACgkQoBCTJSAkVrFfRACgjiiRXjyRGfc2fGPJWTmJTjnK 89cAnRnstn0e/GiYz0Go13R2B+lBUWWw =HmUJ -END PGP 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] [OpenStack] What is the best place to run quantum-ovs-cleanup
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The network node probably wont be running quantum server just one of the agents, so you put the command in one of those configs not quantum-server. That is what Im doing currently and it is working for me. at some point if you have running VMs with active network connections and need to restart quantum for some reason this 'may' interrupt their connections. something to keep in mind. steve On 04/24/2013 08:32 AM, Balamurugan V G wrote: Right now, I have a single node setup on which I am qualifying my use cases but eventually I will have a controller node, network node and several compute nodes. In that case, do you mean it should something like this? Controller : post-start of quantum-server.cong Network : post-start of quantum-server.cong Compute: pre-start of quantum-plugin-openvswitch-agent.conf Thanks, Balu On Wed, Apr 24, 2013 at 8:52 PM, Steve Heistand steve.heist...@nasa.gov wrote: it was mentioned to me (by Mr Mihaiescu) that this only works if controller and network node are on the same machine. For the compute nodes I had forgotten its in a different place. On them I am doing it in a pre-start script in quantum-plugin-openvswitch-agent.conf. if the controller/network are on different machines certainly in the quantum-server.conf work on which ever one of them is actually using it, if it doesnt the command will have to be in a different startup script. It was also mentioned that putting things in /etc/rc.local and then restarting all the quantum related services might work too. steve On 04/24/2013 08:15 AM, Balamurugan V G wrote: Thanks Steve. I came across another way at https://bugs.launchpad.net/quantum/+bug/1084355/comments/15. It seems to work as well. But your solution is simpler :) Regards, Balu On Wed, Apr 24, 2013 at 7:41 PM, Steve Heistand steve.heist...@nasa.gov wrote: I put it in the file:/etc/init/quantum-server.conf post-start script /usr/bin/quantum-ovs-cleanup exit 1 end script On 04/24/2013 02:45 AM, Balamurugan V G wrote: Hi, It seems due to an OVS quantum bug, we need to run the utility quantum-ovs-cleanup before any of the quantum services start, upon a server reboot. Where is the best place to put this utility to run automatically when a server reboots so that the OVS issue is automatically addressed? A script in /etc/init.d or just plugging in a call for quantum-ovs-cleanup in an existing script? Thanks, Balu ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp - -- Steve Heistand NASA Ames Research Center email: steve.heist...@nasa.gov Steve Heistand/Mail Stop 258-6 ph: (650) 604-4369 Bldg. 258, Rm. 232-5 Scientific HPC ApplicationP.O. Box 1 Development/OptimizationMoffett Field, CA 94035-0001 Any opinions expressed are those of our alien overlords, not my own. # For Remedy# #Action: Resolve# #Resolution: Resolved # #Reason: No Further Action Required # #Tier1: User Code # #Tier2: Other # #Tier3: Assistance # #Notification: None # -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAlF3/W0ACgkQoBCTJSAkVrHdnwCgrnCfjN1NKCml+jFPtHk0s4iA Nx0An3g6abwQons0jMXkJLu4oBhiZ4ot =zh9U -END PGP 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
[Openstack] CLI to get IP address in use
is there a cli command to get the list of IP addresses in use by a given user or tenant? thanks -- Steve Heistand NASA Ames Research Center SciCon Group Mail Stop 258-6 steve.heist...@nasa.gov (650) 604-4369 Moffett Field, CA 94035-1000 Any opinions expressed are those of our alien overlords, not my own. # For Remedy# #Action: Resolve# #Resolution: Resolved # #Reason: No Further Action Required # #Tier1: User Code # #Tier2: Other # #Tier3: Assistance # #Notification: None # 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
[Openstack] is this normal / is there a workaround
so I have a grizzly/quantum/ovs/gre setup that currently only has the 1 extra external IP for a single tenant network. Its assigned to the quantum router so the VMs dont have external floating IPs. Once Im given them by networking they will. But in the mean time the only way I can get to the VMs is either a vnc window or via a command like: ip netns exec qrouter_id ssh VM_IP which of course works but a non-root user cant execute the above 'ip...' command. is this all normal? is there a way that an actual normal user can ssh into the normal VMs? thanks s -- Steve Heistand NASA Ames Research Center SciCon Group Mail Stop 258-6 steve.heist...@nasa.gov (650) 604-4369 Moffett Field, CA 94035-1000 Any opinions expressed are those of our alien overlords, not my own. # For Remedy# #Action: Resolve# #Resolution: Resolved # #Reason: No Further Action Required # #Tier1: User Code # #Tier2: Other # #Tier3: Assistance # #Notification: None # 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] [Cinder] Multi backend config issue
what OS Are you running in the VM? I had similar issues with ubuntu 12.04 but things worked great with centos 6.4 On 04/17/2013 01:15 AM, Heiko Krämer wrote: Hi Guys, I'm running in a strange config issue with cinder-volume service. I try to use the multi backend feature in grizzly and the scheduler works fine but the volume service are not running correctly. I can create/delete volumes but not attach. My cinder.conf (abstract): / // Backend Configuration// //scheduler_driver=cinder.scheduler.filter_scheduler.FilterScheduler// //scheduler_host_manager=cinder.scheduler.host_manager.HostManager// // //enabled_backends=storage1,storage2// //[storage1]// //volume_group=nova-volumes// //volume_driver=cinder.volume.drivers.lvm.LVMISCSIDriver// //volume_backend_name=LVM_ISCSI// //iscsi_helper=tgtadm// // // //[storage2]// //volume_group=nova-volumes// //volume_driver=cinder.volume.drivers.lvm.LVMISCSIDriver// //volume_backend_name=LVM_ISCSI// //iscsi_helper=tgtadm/ this section is on each host the same. If i try to attach an existing volume to an instance i'll get the following error on cinder-volume: /2013-04-16 17:18:13AUDIT [cinder.service] Starting cinder-volume node (version 2013.1)// //2013-04-16 17:18:13 INFO [cinder.volume.manager] Updating volume status// //2013-04-16 17:18:13 INFO [cinder.volume.iscsi] Creating iscsi_target for: volume-b83ff42b-9a58-4bf9-8d95-945829d3ee9d// //2013-04-16 17:18:13 INFO [cinder.openstack.common.rpc.common] Connected to AMQP server on 10.0.0.104:5672// //2013-04-16 17:18:13 INFO [cinder.openstack.common.rpc.common] Connected to AMQP server on 10.0.0.104:5672// //2013-04-16 17:18:14 INFO [cinder.volume.manager] Updating volume status// //2013-04-16 17:18:14 INFO [cinder.openstack.common.rpc.common] Connected to AMQP server on 10.0.0.104:5672// //2013-04-16 17:18:14 INFO [cinder.openstack.common.rpc.common] Connected to AMQP server on 10.0.0.104:5672// //2013-04-16 17:18:26ERROR [cinder.openstack.common.rpc.amqp] Exception during message handling// //Traceback (most recent call last):// // File /usr/lib/python2.7/dist-packages/cinder/openstack/common/rpc/amqp.py, line 430, in _process_data// //rval = self.proxy.dispatch(ctxt, version, method, **args)// // File /usr/lib/python2.7/dist-packages/cinder/openstack/common/rpc/dispatcher.py, line 133, in dispatch// //return getattr(proxyobj, method)(ctxt, **kwargs)// // File /usr/lib/python2.7/dist-packages/cinder/volume/manager.py, line 665, in initialize_connection// //return self.driver.initialize_connection(volume_ref, connector)// // File /usr/lib/python2.7/dist-packages/cinder/volume/driver.py, line 336, in initialize_connection// //if self.configuration.iscsi_helper == 'lioadm':// // File /usr/lib/python2.7/dist-packages/cinder/volume/configuration.py, line 83, in __getattr__// //return getattr(self.local_conf, value)// // File /usr/lib/python2.7/dist-packages/oslo/config/cfg.py, line 1708, in __getattr__// //return self._conf._get(name, self._group)// // File /usr/lib/python2.7/dist-packages/oslo/config/cfg.py, line 1513, in _get// //value = self._substitute(self._do_get(name, group))// // File /usr/lib/python2.7/dist-packages/oslo/config/cfg.py, line 1529, in _do_get// //info = self._get_opt_info(name, group)// // File /usr/lib/python2.7/dist-packages/oslo/config/cfg.py, line 1629, in _get_opt_info// //raise NoSuchOptError(opt_name, group)// //NoSuchOptError: no such option in group storage1: iscsi_helper/ It's very strange the '/volume_driver=cinder.volume.drivers.lvm.LVMISCSIDriver//'/ option should set the iscsi_helper=tgtadm per default. Anyone have an idea or the same issue, otherwise i'll create a bug report. Greetings from Berlin Heiko -- Steve Heistand NASA Ames Research Center SciCon Group Mail Stop 258-6 steve.heist...@nasa.gov (650) 604-4369 Moffett Field, CA 94035-1000 Any opinions expressed are those of our alien overlords, not my own. # For Remedy# #Action: Resolve# #Resolution: Resolved # #Reason: No Further Action Required # #Tier1: User Code # #Tier2: Other # #Tier3: Assistance # #Notification: None # 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] [Cinder] Multi backend config issue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 in my case (as near as I can tell) its something to do with the inability for ubuntu 12.04 (as a vm) to do hot plug pci stuff. the node itself in as 12.04 just the vm part that doesnt work as ubuntu. havent tried 12.10 or rarring as a vm. steve On 04/17/2013 05:42 AM, Heiko Krämer wrote: Hi Steve, yeah it's running ubuntu 12.04 on the nodes and on the vm. But configuration parsing error should have normally nothing todo with a distribution ?! Maybe the oslo version or something like that. But thanks for your hint. Greetings Heiko On 17.04.2013 14:36, Steve Heistand wrote: what OS Are you running in the VM? I had similar issues with ubuntu 12.04 but things worked great with centos 6.4 On 04/17/2013 01:15 AM, Heiko Krämer wrote: Hi Guys, I'm running in a strange config issue with cinder-volume service. I try to use the multi backend feature in grizzly and the scheduler works fine but the volume service are not running correctly. I can create/delete volumes but not attach. My cinder.conf (abstract): / // Backend Configuration// //scheduler_driver=cinder.scheduler.filter_scheduler.FilterScheduler// //scheduler_host_manager=cinder.scheduler.host_manager.HostManager// // //enabled_backends=storage1,storage2// //[storage1]// //volume_group=nova-volumes// //volume_driver=cinder.volume.drivers.lvm.LVMISCSIDriver// //volume_backend_name=LVM_ISCSI// //iscsi_helper=tgtadm// // // //[storage2]// //volume_group=nova-volumes// //volume_driver=cinder.volume.drivers.lvm.LVMISCSIDriver// //volume_backend_name=LVM_ISCSI// //iscsi_helper=tgtadm/ this section is on each host the same. If i try to attach an existing volume to an instance i'll get the following error on cinder-volume: /2013-04-16 17:18:13AUDIT [cinder.service] Starting cinder-volume node (version 2013.1)// //2013-04-16 17:18:13 INFO [cinder.volume.manager] Updating volume status// //2013-04-16 17:18:13 INFO [cinder.volume.iscsi] Creating iscsi_target for: volume-b83ff42b-9a58-4bf9-8d95-945829d3ee9d// //2013-04-16 17:18:13 INFO [cinder.openstack.common.rpc.common] Connected to AMQP server on 10.0.0.104:5672// //2013-04-16 17:18:13 INFO [cinder.openstack.common.rpc.common] Connected to AMQP server on 10.0.0.104:5672// //2013-04-16 17:18:14 INFO [cinder.volume.manager] Updating volume status// //2013-04-16 17:18:14 INFO [cinder.openstack.common.rpc.common] Connected to AMQP server on 10.0.0.104:5672// //2013-04-16 17:18:14 INFO [cinder.openstack.common.rpc.common] Connected to AMQP server on 10.0.0.104:5672// //2013-04-16 17:18:26ERROR [cinder.openstack.common.rpc.amqp] Exception during message handling// //Traceback (most recent call last):// // File /usr/lib/python2.7/dist-packages/cinder/openstack/common/rpc/amqp.py, line 430, in _process_data// //rval = self.proxy.dispatch(ctxt, version, method, **args)// // File /usr/lib/python2.7/dist-packages/cinder/openstack/common/rpc/dispatcher.py, line 133, in dispatch// //return getattr(proxyobj, method)(ctxt, **kwargs)// // File /usr/lib/python2.7/dist-packages/cinder/volume/manager.py, line 665, in initialize_connection// //return self.driver.initialize_connection(volume_ref, connector)// // File /usr/lib/python2.7/dist-packages/cinder/volume/driver.py, line 336, in initialize_connection// //if self.configuration.iscsi_helper == 'lioadm':// // File /usr/lib/python2.7/dist-packages/cinder/volume/configuration.py, line 83, in __getattr__// //return getattr(self.local_conf, value)// // File /usr/lib/python2.7/dist-packages/oslo/config/cfg.py, line 1708, in __getattr__// //return self._conf._get(name, self._group)// // File /usr/lib/python2.7/dist-packages/oslo/config/cfg.py, line 1513, in _get// // value = self._substitute(self._do_get(name, group))// // File /usr/lib/python2.7/dist-packages/oslo/config/cfg.py, line 1529, in _do_get// // info = self._get_opt_info(name, group)// // File /usr/lib/python2.7/dist-packages/oslo/config/cfg.py, line 1629, in _get_opt_info// //raise NoSuchOptError(opt_name, group)// //NoSuchOptError: no such option in group storage1: iscsi_helper/ It's very strange the '/volume_driver=cinder.volume.drivers.lvm.LVMISCSIDriver//'/ option should set the iscsi_helper=tgtadm per default. Anyone have an idea or the same issue, otherwise i'll create a bug report. Greetings from Berlin Heiko - -- Steve Heistand NASA Ames Research Center email: steve.heist...@nasa.gov Steve Heistand/Mail Stop 258-6 ph: (650) 604-4369 Bldg. 258, Rm. 232-5 Scientific HPC ApplicationP.O. Box 1 Development/OptimizationMoffett Field, CA 94035-0001
Re: [Openstack] OpenStack Multi Node Problems with OVS
hi folks, so an update to the networking issues various people have been seeing. I updated the openvswitch package from source instead of apt-get and things are much better now. The errors/warnings in the various log files are now gone. the ovs-dpctl works now without complaint. Im still not able to get the VMs to talk to the outside world but Im beginning to think its a fault with my understanding. I have a node that is both controller and network that is the gateway for the rest of the compute nodes. I suspect that since I only have 1 routable IP address from our network folks Ive configured things wrong. s -- Steve Heistand NASA Ames Research Center SciCon Group Mail Stop 258-6 steve.heist...@nasa.gov (650) 604-4369 Moffett Field, CA 94035-1000 Any opinions expressed are those of our alien overlords, not my own. # For Remedy# #Action: Resolve# #Resolution: Resolved # #Reason: No Further Action Required # #Tier1: User Code # #Tier2: Other # #Tier3: Assistance # #Notification: None # 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] OpenStack Multi Node Problems with OVS
Welcome to the club :)
Been fighting the same problem for a week now. Nothing is working...
Found lots of other people complaining on the web even with grizzly like I'm
using.
S
Atif Wasi aw...@yahoo.com wrote:
Hi Folks,
I am working on bringing up a multi node OpenStack environment with
OVS. I have a Controller, Compute and a Gateway/Network node. This is
running Folsom. Most of the services are up, except that I cannot ping
the floating ip of the VM.
Below are the error messages I am seeing the Gateway/Network node:
root@gateway:/var/log/quantum# ovs-vsctl show
9f3f021a-cb8e-4ef4-87a5-f5bab9f3
Bridge br-ex
Port eth2
Interface eth2
Port qg-0aff855e-9c
Interface qg-0aff855e-9c
type: internal
Port br-ex
Interface br-ex
type: internal
Bridge br-eth1
Port eth1
Interface eth1
Port phy-br-eth1
Interface phy-br-eth1
Port br-eth1
Interface br-eth1
type: internal
Bridge br-int
Port br-int
Interface br-int
type: internal
Port int-br-eth1
Interface int-br-eth1
Port tap47ac110a-fe
tag: 1
Interface tap47ac110a-fe
type: internal
Port qr-12091c58-8a
tag: 1
Interface qr-12091c58-8a
type: internal
ovs_version: 1.4.3
=
L3 Agent.log:
2013-04-16 22:06:08DEBUG [quantum.agent.linux.utils] Running
command: ip -o link show br-ex
2013-04-16 22:06:08DEBUG [quantum.agent.linux.utils]
Command: ['ip', '-o', 'link', 'show', 'br-ex']
Exit code: 0
Stdout: '20: br-ex: BROADCAST,MULTICAST mtu 1500 qdisc noop state
DOWN mode DEFAULT \\link/ether 00:04:23:c9:64:ac brd
ff:ff:ff:ff:ff:ff\n'
Stderr: ''
2013-04-16 22:06:08DEBUG [quantumclient.client] REQ: curl -i
http://192.168.0.2:9696//v2.0/networks.json?router%3Aexternal=True -X
GET -H User-Agent: python-quantumclient -H Content-Type:
application/json -H Accept: application/json -H X-Auth-Token:
3c2cc4afb68f4042bf4bddd9908186d0
2013-04-16 22:06:08DEBUG [quantumclient.client] RESP:{'date': 'Wed,
17 Apr 2013 02:06:08 GMT', 'status': '200', 'content-length': '376',
'content-type': 'application/json', 'content-location':
u'http://192.168.0.2:9696//v2.0/networks.json?router%3Aexternal=True'}
2013-04-16 22:06:08DEBUG [quantumclient.client] RESP
BODY:{networks: [{status: ACTIVE, subnets:
[487ccc01-81ea-4abc-bbb4-061cde722801], name: ext_net,
provider:physical_network: physnet1, admin_state_up: true,
tenant_id: 6bd416e48a394f06bfbf4d0856740262,
provider:network_type: vlan, router:external: true, shared:
false, id: 2f2aa2c9-47be-4b3e-9f05-a547a8d3aaa9,
provider:segmentation_id: 500}]}
2013-04-16 22:06:08DEBUG [quantumclient.client] REQ: curl -i
http://192.168.0.2:9696//v2.0/routers.json -X GET -H User-Agent:
python-quantumclient -H Content-Type: application/json -H Accept:
application/json -H X-Auth-Token: 3c2cc4afb68f4042bf4bddd9908186d0
2013-04-16 22:06:08DEBUG [quantumclient.client] RESP:{'date': 'Wed,
17 Apr 2013 02:06:08 GMT', 'status': '200', 'content-length': '262',
'content-type': 'application/json', 'content-location':
u'http://192.168.0.2:9696//v2.0/routers.json'}
2013-04-16 22:06:08DEBUG [quantumclient.client] RESP
BODY:{routers: [{status: ACTIVE, external_gateway_info:
{network_id: 2f2aa2c9-47be-4b3e-9f05-a547a8d3aaa9}, name:
router_proj_one, admin_state_up: true, tenant_id:
b443045cd0d54377b637cc0ba998bf89, id:
49a92bbc-5f58-400a-a8cb-aebcf54db446}]}
2013-04-16 22:06:08DEBUG [quantumclient.client] REQ: curl -i
http://192.168.0.2:9696//v2.0/ports.json?device_owner=network%3Arouter_gatewaydevice_id=49a92bbc-5f58-400a-a8cb-aebcf54db446
-X GET -H User-Agent: python-quantumclient -H Content-Type:
application/json -H Accept: application/json -H X-Auth-Token:
3c2cc4afb68f4042bf4bddd9908186d0
2013-04-16 22:06:08DEBUG [quantumclient.client] RESP:{'date': 'Wed,
17 Apr 2013 02:06:08 GMT', 'status': '200', 'content-length': '417',
'content-type': 'application/json', 'content-location':
u'http://192.168.0.2:9696//v2.0/ports.json?device_owner=network%3Arouter_gatewaydevice_id=49a92bbc-5f58-400a-a8cb-aebcf54db446'}
2013-04-16 22:06:08DEBUG [quantumclient.client] RESP BODY:{ports:
[{status: ACTIVE, name: , admin_state_up: true, network_id:
2f2aa2c9-47be-4b3e-9f05-a547a8d3aaa9, tenant_id: ,
device_owner: network:router_gateway, mac_address:
fa:16:3e:3a:fe:6a, fixed_ips: [{subnet_id:
487ccc01-81ea-4abc-bbb4-061cde722801, ip_address: 192.168.1.10}],
id: 0aff855e-9cab-4dad-a490-7019e104603a, device_id:
49a92bbc-5f58-400a-a8cb-aebcf54db446}]}
2013-04-16 22:06:08DEBUG [quantumclient.client] REQ: curl -i
[Openstack] quantum router related question
| Ext_Net | | provider:network_type | local| | provider:physical_network | | | provider:segmentation_id | | | router:external | True | | shared| False| | status| ACTIVE | | subnets | eb16b821-c213-4c35-ae4b-2ecaad3e32ef | | tenant_id | 0a333d3291704870859bd3f4bf159dfe | +---+--+ - -- Steve Heistand NASA Ames Research Center email: steve.heist...@nasa.gov Steve Heistand/Mail Stop 258-6 ph: (650) 604-4369 Bldg. 258, Rm. 232-5 Scientific HPC ApplicationP.O. Box 1 Development/OptimizationMoffett Field, CA 94035-0001 Any opinions expressed are those of our alien overlords, not my own. # For Remedy# #Action: Resolve# #Resolution: Resolved # #Reason: No Further Action Required # #Tier1: User Code # #Tier2: Other # #Tier3: Assistance # #Notification: None # -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAlFsH3YACgkQoBCTJSAkVrETqACfdiPN6DYOWvH8WClzqlE6RtHR oKQAoIEs1rZyiOQkTy9M2R2zSKX8XC26 =JXPA -END PGP 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
[Openstack] controller and network node, same machine?
so Im beginning to think my attempts at getting a controller node and a network node to be on the same physical machines/OS are doomed. is it even possible to have all the controller and network node features on the same box? Aside from one of them being in a VM that is. thanks s -- Steve Heistand NASA Ames Research Center SciCon Group Mail Stop 258-6 steve.heist...@nasa.gov (650) 604-4369 Moffett Field, CA 94035-1000 Any opinions expressed are those of our alien overlords, not my own. # For Remedy# #Action: Resolve# #Resolution: Resolved # #Reason: No Further Action Required # #Tier1: User Code # #Tier2: Other # #Tier3: Assistance # #Notification: None # 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] controller and network node, same machine?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 mostly Im concerned about the quantum/OVS/qre settings. there are distinct difference in the values in the ovs_quantum_plugin.ini file depending on what type of node the agent is running on. I wasnt sure if it going to work. The problems Ive been having are all network related all centered around getting VMs on compute nodes to be able to see something besides another VM in their tenant. ie the outside world. But my network/ovs-fu is limited so its entirely possible its my fault. just wanted to see if it was even possible in the first place. s On 04/12/2013 06:05 AM, Mohammed Amine SAYA wrote: Hi Steve, Why do you say that? I am curious to learn about the difficulties you have had. I also tried to have controller node and network node running on the same machine but I have never managed to ping a running VM in this configuration with FOLSOM release. Everything was working fine but impossible to ping a VM. Amine. On Fri, Apr 12, 2013 at 2:40 PM, Steve Heistand steve.heist...@nasa.gov mailto:steve.heist...@nasa.gov wrote: so Im beginning to think my attempts at getting a controller node and a network node to be on the same physical machines/OS are doomed. is it even possible to have all the controller and network node features on the same box? Aside from one of them being in a VM that is. thanks s -- Steve Heistand NASA Ames Research Center SciCon Group Mail Stop 258-6 steve.heist...@nasa.gov mailto:steve.heist...@nasa.gov (650) 604-4369 tel:%28650%29%20604-4369 Moffett Field, CA 94035-1000 Any opinions expressed are those of our alien overlords, not my own. # For Remedy# #Action: Resolve# #Resolution: Resolved # #Reason: No Further Action Required # #Tier1: User Code # #Tier2: Other # #Tier3: Assistance # #Notification: None # ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp - -- Steve Heistand NASA Ames Research Center email: steve.heist...@nasa.gov Steve Heistand/Mail Stop 258-6 ph: (650) 604-4369 Bldg. 258, Rm. 232-5 Scientific HPC ApplicationP.O. Box 1 Development/OptimizationMoffett Field, CA 94035-0001 Any opinions expressed are those of our alien overlords, not my own. # For Remedy# #Action: Resolve# #Resolution: Resolved # #Reason: No Further Action Required # #Tier1: User Code # #Tier2: Other # #Tier3: Assistance # #Notification: None # -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAlFoDYAACgkQoBCTJSAkVrEXDACeMBENxoBLL4OdayOsSHHDfjgg juUAoMzQCTR2DVk1+usy3SV3yENkrtmP =3vok -END PGP 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] controller and network node, same machine?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 well its me playing around with openstack so I wouldnt say production environment. but certainly on a dedicated rack full of nodes that just do openstack. running ubuntu 12.04lts on everything. the controller+network is on its own box with a boatload of ethernet connections around to various places including the dual ethernet dual switch compute nodes. vm to vm is good, vm to anywhere else not so much. s On 04/12/2013 10:32 AM, Pranav wrote: oops clicked send too soon ... Do you mean production environment by same physical box? Because I have tried it and it worked for me but it was on a ubuntu desktop which is kind of like a hybrid of server + desktop now. Regards, Pranav On Fri, Apr 12, 2013 at 11:01 PM, Pranav pps.pra...@gmail.com mailto:pps.pra...@gmail.com wrote: Do you mean production environment by same physical box? Because I have tried it and it worked for me. Regards, Pranav On Fri, Apr 12, 2013 at 10:35 PM, Guilherme Russi luisguilherme...@gmail.com mailto:luisguilherme...@gmail.com wrote: Hello Steve, I had a lot of troubles deploying my openstack and putting my controller node at the same physical machine with my network node, I have 2 NICs in my controller + network node, if you need help, I can help you. Regards. Guilherme. 2013/4/12 Steve Heistand steve.heist...@nasa.gov mailto:steve.heist...@nasa.gov mostly Im concerned about the quantum/OVS/qre settings. there are distinct difference in the values in the ovs_quantum_plugin.ini file depending on what type of node the agent is running on. I wasnt sure if it going to work. The problems Ive been having are all network related all centered around getting VMs on compute nodes to be able to see something besides another VM in their tenant. ie the outside world. But my network/ovs-fu is limited so its entirely possible its my fault. just wanted to see if it was even possible in the first place. s On 04/12/2013 06:05 AM, Mohammed Amine SAYA wrote: Hi Steve, Why do you say that? I am curious to learn about the difficulties you have had. I also tried to have controller node and network node running on the same machine but I have never managed to ping a running VM in this configuration with FOLSOM release. Everything was working fine but impossible to ping a VM. Amine. On Fri, Apr 12, 2013 at 2:40 PM, Steve Heistand steve.heist...@nasa.gov mailto:steve.heist...@nasa.gov mailto:steve.heist...@nasa.gov mailto:steve.heist...@nasa.gov wrote: so Im beginning to think my attempts at getting a controller node and a network node to be on the same physical machines/OS are doomed. is it even possible to have all the controller and network node features on the same box? Aside from one of them being in a VM that is. thanks s -- Steve Heistand NASA Ames Research Center SciCon Group Mail Stop 258-6steve.heist...@nasa.gov mailto:steve.heist...@nasa.gov mailto:steve.heist...@nasa.gov mailto:steve.heist...@nasa.gov (650) 604-4369 tel:%28650%29%20604-4369 Moffett Field, CA 94035-1000 Any opinions expressed are those of our alien overlords, not my own. # For Remedy# #Action: Resolve# #Resolution: Resolved # #Reason: No Further Action Required # #Tier1: User Code # #Tier2: Other # #Tier3: Assistance # #Notification: None # ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net mailto: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 mailto: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 mailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp - -- Steve Heistand NASA Ames Research Center email: steve.heist...@nasa.gov Steve Heistand/Mail Stop 258-6 ph: (650) 604-4369 Bldg. 258, Rm. 232-5 Scientific HPC ApplicationP.O. Box 1
Re: [Openstack] Grizzly official packages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Adding (well trying to add) the grizzly to ubuntu 12.04 and on apt-get update I get: W: GPG error: http://ubuntu-cloud.archive.canonical.com precise-updates/grizzly Release: The following signatures were invalid: BADSIG 5EDB1B62EC4926EA Canonical Cloud Archive Signing Key ftpmas...@canonical.com trying to add the key shows its already there: root@cloudfe:~# apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 5EDB1B62EC4926EA Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /tmp/tmp.B01OViae6E --trustdb-name /etc/apt/trustdb.gpg --keyring /etc/apt/trusted.gpg - --primary-keyring /etc/apt/trusted.gpg --recv-keys --keyserver keyserver.ubuntu.com 5EDB1B62EC4926EA gpg: requesting key EC4926EA from hkp server keyserver.ubuntu.com gpg: key EC4926EA: Canonical Cloud Archive Signing Key ftpmas...@canonical.com not changed gpg: Total number processed: 1 gpg: unchanged: 1 root@cloudfe:~# have deleted the key and tried re-adding it but to no avail. thoughts/suggestions? thanks s On 04/07/2013 04:12 PM, Martinx - ジェームズ wrote: deb http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/grizzly main # deb-src http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/grizzly main # Public -proposed archive mimicking the SRU process for extended testing. # Packages should bake here for at least 7 days. # deb http://ubuntu-cloud.archive.canonical.com/ubuntu precise-proposed/grizzly main # deb-src http://ubuntu-cloud.archive.canonical.com/ubuntu precise-proposed/grizzly main - -- Steve Heistand NASA Ames Research Center email: steve.heist...@nasa.gov Steve Heistand/Mail Stop 258-6 ph: (650) 604-4369 Bldg. 258, Rm. 232-5 Scientific HPC ApplicationP.O. Box 1 Development/OptimizationMoffett Field, CA 94035-0001 Any opinions expressed are those of our alien overlords, not my own. # For Remedy# #Action: Resolve# #Resolution: Resolved # #Reason: No Further Action Required # #Tier1: User Code # #Tier2: Other # #Tier3: Assistance # #Notification: None # -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAlFi6sgACgkQoBCTJSAkVrEEjwCfbNvk4Ftik49ei/CnHuJ1lv1B 9ykAn0mK6KOw+ApCccNGApdr7VhCi2fp =ZAej -END PGP 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] Grizzly official packages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Same error message doing this as well. aptitude update Hit http://ubuntu-cloud.archive.canonical.com precise-updates/grizzly/main amd64 Packages Hit http://ubuntu-cloud.archive.canonical.com precise-updates/grizzly/main i386 Packages Ign http://ubuntu-cloud.archive.canonical.com precise-updates/grizzly/main Translation-en_US Ign http://ubuntu-cloud.archive.canonical.com precise-updates/grizzly/main Translation-en Fetched 543 B in 2s (222 B/s) W: GPG error: http://ubuntu-cloud.archive.canonical.com precise-updates/grizzly Release: The following signatures were invalid: BADSIG 5EDB1B62EC4926EA Canonical Cloud Archive Signing Key ftpmas...@canonical.com steve On 04/08/2013 09:13 AM, Martinx - ジェームズ wrote: aptitude install ubuntu-cloud-keyring aptitude update On 8 April 2013 13:05, Steve Heistand steve.heist...@nasa.gov mailto:steve.heist...@nasa.gov wrote: Adding (well trying to add) the grizzly to ubuntu 12.04 and on apt-get update I get: W: GPG error: http://ubuntu-cloud.archive.canonical.com precise-updates/grizzly Release: The following signatures were invalid: BADSIG 5EDB1B62EC4926EA Canonical Cloud Archive Signing Key ftpmas...@canonical.com mailto:ftpmas...@canonical.com trying to add the key shows its already there: root@cloudfe:~# apt-key adv --recv-keys --keyserver keyserver.ubuntu.com http://keyserver.ubuntu.com 5EDB1B62EC4926EA Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /tmp/tmp.B01OViae6E --trustdb-name /etc/apt/trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --recv-keys --keyserver keyserver.ubuntu.com http://keyserver.ubuntu.com 5EDB1B62EC4926EA gpg: requesting key EC4926EA from hkp server keyserver.ubuntu.com http://keyserver.ubuntu.com gpg: key EC4926EA: Canonical Cloud Archive Signing Key ftpmas...@canonical.com mailto:ftpmas...@canonical.com not changed gpg: Total number processed: 1 gpg: unchanged: 1 root@cloudfe:~# have deleted the key and tried re-adding it but to no avail. thoughts/suggestions? thanks s On 04/07/2013 04:12 PM, Martinx - ジェームズ wrote: debhttp://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/grizzly main # deb-srchttp://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/grizzly main # Public -proposed archive mimicking the SRU process for extended testing. # Packages should bake here for at least 7 days. # deb http://ubuntu-cloud.archive.canonical.com/ubuntu precise-proposed/grizzly main # deb-srchttp://ubuntu-cloud.archive.canonical.com/ubuntu precise-proposed/grizzly main ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net mailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp - -- Steve Heistand NASA Ames Research Center email: steve.heist...@nasa.gov Steve Heistand/Mail Stop 258-6 ph: (650) 604-4369 Bldg. 258, Rm. 232-5 Scientific HPC ApplicationP.O. Box 1 Development/OptimizationMoffett Field, CA 94035-0001 Any opinions expressed are those of our alien overlords, not my own. # For Remedy# #Action: Resolve# #Resolution: Resolved # #Reason: No Further Action Required # #Tier1: User Code # #Tier2: Other # #Tier3: Assistance # #Notification: None # -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAlFi7foACgkQoBCTJSAkVrHDLQCfQCVveQqrk4pN7CcyDgAtWzRk Bt8AoJjyGY906CxVra1vZj/6ldDXVQjF =ras5 -END PGP 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] Grizzly official packages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 thanks, this did point me in a direction that did help. needed to clean up the apt cache and redo the keyring install. but yeah Im just playing around with grizzly at this point so Im ok with changes.. s On 04/08/2013 10:30 AM, Daviey Walker wrote: On 8 April 2013 17:19, Steve Heistand steve.heist...@nasa.gov wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Same error message doing this as well. aptitude update SNIP Hi, Please make sure that 'ubuntu-cloud-keyring' package is installed. dave@frap:~$ apt-cache policy ubuntu-cloud-keyring | grep Installed Installed: 2012.08.14 Also, please note that Grizzly packages are currently in the staging archive and will be promoted to proposed and then to staging; as it passes the levels of QA. It should also be clear that the Ubuntu team do not consider the packages 'released' until the backing release (in this case) Raring is released, on April 25th. However, the packages should be of a usable state before then. HTH, and feedback is most appreciated. - -- Steve Heistand NASA Ames Research Center email: steve.heist...@nasa.gov Steve Heistand/Mail Stop 258-6 ph: (650) 604-4369 Bldg. 258, Rm. 232-5 Scientific HPC ApplicationP.O. Box 1 Development/OptimizationMoffett Field, CA 94035-0001 Any opinions expressed are those of our alien overlords, not my own. # For Remedy# #Action: Resolve# #Resolution: Resolved # #Reason: No Further Action Required # #Tier1: User Code # #Tier2: Other # #Tier3: Assistance # #Notification: None # -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAlFjBSMACgkQoBCTJSAkVrEPOQCgq/cWAB0j0l/mE81e2bZQH8NZ aWwAoL7Z+svF3+HugjBz0ux5100ADeRZ =b5dE -END PGP 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
