Re: [Openstack] How to work with Flat DHCP Grizzly
Hi! Sorry to not answer your private e-mail in time. I'm quite sure that you'll need at least, two networks but, both private (according to my guide), one for openstack components, other for Instances. It doesn't work like OpenNebula as you thought... You don't need nothing related to nova network, since we aren't using it. Ubuntu instance from Canonical depends on a working metadata, because there is no password preconfigured within the image, you'll need the ssh keys from metadata, which I was unable to configure it (metadata) within my environment... Sorry, anyway, you can login into any CirrOS instances via Dashboard - VNC Console. Or, you can create your own Ubuntu image using the command vm-builder and upload it to Glance... Listen, at first, try to follow the my guide line by line, using a new gateway VM as I told you, to test... Later, after a working installation, you can start playing with Quantum networks easily... Best! Thiago On 25 July 2013 08:16, comiqadze co...@yandex.ru wrote: Hi, folks! Does somebody know any guide for installation of the Flat DHCP step by step? I followed this guide for building the system: https://gist.github.com/tmartinx/d36536b7b62a48f859c2 my system is: 2 machines with ubuntu 12.04. one compute, one controller. I neatly followed this guide, except for one thing: my IPs for controller and compute nodes and for instances are of the same network. Controller, Compute - x.x.15.70, 71. Instances pool: x.x.15.230-240 Do I need to specify Network Manager in nova.conf? Like: network_manager=nova.network.manager.FlatManager flat_network_bridge=br-eth0 flat_interface=eth0 Currently I can create an instance, I can see it's IP in Dashboard, but I cannot ping it. And inside there is no network. Even when I manually changed Interfaces file, I still cannot ping it. When I load Ubuntu instance, it requests login and password? Does somebody know where I can find it? Thank you. Any help will be very appreciated. regards, comiq ___ 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] How to Install OpenStack ???????????
Hi! I have a very-easy-to-follow guide to install OpenStack, take a look! Ultimate OpenStack Grizzly Guide: https://gist.github.com/tmartinx/d36536b7b62a48f859c2 Cheers! Thiago On 12 July 2013 03:58, Jake G. dj_dark_jungl...@yahoo.com wrote: Hi All, I have been struggling with installing Openstack for the past 2 weeks and I am about to rip my own hair out. rant Does anyone have installation instructions that a human being can actually understand and follow? I am usually pretty good at installing new tech but OpenStack is the most convoluted environment (even worse documentation) I have ever come in contact with (Worse than IBM software). The advanced install and config of CloudStack 4.1 is a breeze compare to Openstack. Was this made to purposely line the pockets of Openstack deployment consulting companies? Openstack might be great but no one will know because its impossible to deploy. /rant I`m sure I am not the only one who feels this way. I would appreciate any help anyone can give. Someones blog, other installation methods, anything Thank you very much ___ 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] Install from ISO in OpenStack
That is pretty cool! I was thinking on this about a week now... Because I'm facing some problems with a pre-installed Windows 7 VM with Grizzly + Ubuntu 12.04... *** Windows froze on the first boot of the Instance, at its recovery mode checks (or something like that)... So, boot an Instance with an ISO sounds great! To try to do the Windows installation there, directly on Instance first boot, prompting Windows end user license to the clients and etc... Anyway, I'll try now that Golden Image approach... Some info: https://wiki.openstack.org/wiki/BootFromISO Regards, Thiago On 17 May 2013 21:00, Ray Sun xiaoq...@gmail.com wrote: I am trying to create an instance using an ISO which is already in glance. I can successfully use a pre-made qcow2 to launch an instance, from the document, I know the glance support ISO file, so I tried to do this test, but it seems not work on KVM under OpenStack platform. Best Regards -- Ray On Fri, May 17, 2013 at 4:48 PM, Sam Stoelinga sammiest...@gmail.comwrote: Are you trying to create an Openstack instance based on Ubuntu 12.04 or are you trying to install openstack on ubuntu? If you're trying to just launch an ubuntu image, you can use the pre-made qcow2 images by ubuntu, didn't have any issues with those. See: http://docs.openstack.org/trunk/openstack-compute/admin/content/starting-images.html What iso are you using? On Fri, May 17, 2013 at 4:16 PM, Ray Sun xiaoq...@gmail.com wrote: I try to install ubuntu 12.04 on OpenStack, here's my steps: 1. Upload ubuntu iso into OpenStack 2. Launch a new VM and install 3. Network can't detect 4. Can't find any disk Any one met this problem before? Thanks. Best Regards -- Ray ___ 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
Re: [Openstack] Windows 7 not working with Grizzly
So, no one here have Windows 7 on Grizzly? Tks! Thiago On 1 May 2013 21:10, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Hi! With Folsom, I used to create a Windows 7 image, with KVM+libvirt and then, upload it to Glance with the following command: glance image-create --name Windows 7 - ULTIMATE - 32 Bits - Pre-Installed Image --is-public true --container-format bare --disk-format qcow2 /home/openstack/windows7-template.img But now, when I repeat this process in Grizzly, the Windows Instance doesn't complete its boot, a Windows Message appear on VNC console: System Recovery Options I choose: Start up repair, doesn't work... I'm trying everything but, doesn't work. Also, I created this `Windows 7 Template' using exactly the same options of OpenStack instance itself, by dumping the instance-x.xml into a file and using to create the template in first place. So, the virtual CPU is the same, video board is the same, etc... What am I missing? Thanks! Thiago ___ 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] How to configure quantum on two computers each with one NIC?
Hi! My OpenStack guide: https://gist.github.com/tmartinx/d36536b7b62a48f859c2 is based on two computers, each with only one NIC. ;-) Cheers! Thiago On 4 May 2013 16:34, Jing vitoj...@gmail.com wrote: Hi, I'm trying to set up Openstack on two computers, and each of them has only one NIC. I want to set up one computer as control and compute node, and another as compute node. I want to use vlan mode, so quantum is needed. I'm install Openstack according https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_MultiNode/OpenStack_Grizzly_Install_Guide.rst After install quantum server in first computer( used as control and compute node ), I tried to install the Network Node functions. The NIC is configured as follows: # The loopback network interface auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 192.168.1.104 netmask 255.255.255.0 gateway 192.168.1.1 dns-nameservers 8.8.8.8 In the 3.4. OpenVSwitch (Part2) section of the guide, eth2 is cnfigured as # VM internet Access auto eth2 iface eth2 inet manual up ifconfig $IFACE 0.0.0.0 up up ip link set $IFACE promisc on down ip link set $IFACE promisc off down ifconfig $IFACE down I don't have another NIC. How should I write the interface configuration file? And another question , is it possible to use wireless NIC in quantum? thanks ___ 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] Floating IP is wasting IP resources
Use IPv6... No need for Floating IPs, no NAT tables... Billions * billions * billions of public IPs for you... [?] On 2 May 2013 11:31, Joe Topjian joe.topj...@cybera.ca wrote: I agree with you. I'd be interested to know if anyone else has run into this issue and their solution. Here's what I'll be trying to implement to get around this: I have an incoming trunk connection that carries two vlans: a public IP subnet and private subnet. I have them configured as two bridges in OVS: br-nat (the private subnet) and br-floating (the public subnet). Right now I have one L3 service working with br-nat. Users can create routers, set a default gateway, and get outgoing nat'd access to the internet. Since the subnet is private, I can easily configure this L3 service with a large allocation pool. Yet to be implemented: the br-floating L3 service. This will be a smaller pool that will be restricted via quotas. Users will have to be more conservative with access to this service (maybe by creating an instance which will act as a port-forwarding firewall to an internal subnet). This places more work on the user compared to the nova-network vlanmanager workflow. However, I feel the ability to create multiple internal per-project subnets is a decent tradeoff. If this doesn't work out or if this ends up being to complicated for users, I'll probably go with the Provider Router with Private Networks use case ( http://docs.openstack.org/grizzly/openstack-network/admin/content/use_cases_single_router.html ). On Thu, May 2, 2013 at 4:06 AM, 陈雷 raid.c...@gmail.com wrote: Recently I'm test floating IP on version Grizzly, I found the mechanism of floating IP is a little of wasting public IP addresses. In some circumstance, like public cloud environment. there is only one user in one project (tenant). If the user want to using floating IP, he has to create an router and set a gateway for it, this process will occupy one additional public IP address. So the whole process of floating IP will use 2 public address at least. So my question is, are there any ways to avoid this? Thanks Ray ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Joe Topjian Systems Administrator Cybera Inc. www.cybera.ca Cybera is a not-for-profit organization that works to spur and support innovation, for the economic benefit of Alberta, through the use of cyberinfrastructure. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp 347.gif___ 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] Windows 7 not working with Grizzly
Hi! With Folsom, I used to create a Windows 7 image, with KVM+libvirt and then, upload it to Glance with the following command: glance image-create --name Windows 7 - ULTIMATE - 32 Bits - Pre-Installed Image --is-public true --container-format bare --disk-format qcow2 /home/openstack/windows7-template.img But now, when I repeat this process in Grizzly, the Windows Instance doesn't complete its boot, a Windows Message appear on VNC console: System Recovery Options I choose: Start up repair, doesn't work... I'm trying everything but, doesn't work. Also, I created this `Windows 7 Template' using exactly the same options of OpenStack instance itself, by dumping the instance-x.xml into a file and using to create the template in first place. So, the virtual CPU is the same, video board is the same, etc... What am I missing? Thanks! Thiago ___ 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] ANNOUNCE: Ultimate OpenStack Grizzly Guide, with super easy Quantum!
Hi! The `Ultimate OpenStack Grizzly Guide' is a bit more updated! There are two new scripts: keystone_basic.sh and keystone_endpoints_basic.sh which preliminary support for Swift and Ceilometer. Check it out! https://gist.github.com/tmartinx/d36536b7b62a48f859c2 Best! Thiago On 20 March 2013 19:51, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Hi! I'm working with Grizzly G3+RC1 on top of Ubuntu 12.04.2 and here is the guide I wrote: Ultimate OpenStack Grizzly Guidehttps://gist.github.com/tmartinx/d36536b7b62a48f859c2 It covers: * Ubuntu 12.04.2 * Basic Ubuntu setup * KVM * OpenvSwitch * Name Resolution for OpenStack components; * LVM for Instances * Keystone * Glance * Quantum - Single Flat, Super Green!! * Nova * Cinder / tgt * Dashboard It is still a draft but, every time I deploy Ubuntu and Grizzly, I follow this little guide... I would like some help to improve this guide... If I'm doing something wrong, tell me! Please! Probably I'm doing something wrong, I don't know yet, but I'm seeing some errors on the logs, already reported here on this list. Like for example: nova-novncproxy conflicts with novnc (no VNC console for now), dhcp-agent.log / auth.log points to some problems with `sudo' or the `rootwarp' subsystem when dealing with metadata (so it isn't working)... But in general, it works great!! Best! Thiago ___ 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] Grizzly: Does metadata service work when overlapping IPs is enabled
Hi Balu! Listen, is your metadata service up and running?! If yes, which guide you used? I'm trying everything I can to enable metadata without L3 with a Quantum Single Flat topology for my own guide: https://gist.github.com/tmartinx/d36536b7b62a48f859c2 I really appreciate any feedback! Tks! Thiago On 24 April 2013 03:34, Balamurugan V G balamuruga...@gmail.com wrote: Thanks Aaron. I am perhaps not configuring it right then. I am using Ubuntu 12.04 host and even my guest(VM) is Ubuntu 12.04 but metadata not working. I see that the VM's routing table has an entry for 169.254.0.0/16 but I cant ping 169.254.169.254 from the VM. I am using a single node setup with two NICs.10.5.12.20 is the public IP, 10.5.3.230 is the management IP These are my metadata related configurations. */etc/nova/nova.conf * metadata_host = 10.5.12.20 metadata_listen = 127.0.0.1 metadata_listen_port = 8775 metadata_manager=nova.api.manager.MetadataManager service_quantum_metadata_proxy = true quantum_metadata_proxy_shared_secret = metasecret123 */etc/quantum/quantum.conf* allow_overlapping_ips = True */etc/quantum/l3_agent.ini* use_namespaces = True auth_url = http://10.5.3.230:35357/v2.0 auth_region = RegionOne admin_tenant_name = service admin_user = quantum admin_password = service_pass metadata_ip = 10.5.12.20 */etc/quantum/metadata_agent.ini* auth_url = http://10.5.3.230:35357/v2.0 auth_region = RegionOne admin_tenant_name = service admin_user = quantum admin_password = service_pass nova_metadata_ip = 127.0.0.1 nova_metadata_port = 8775 metadata_proxy_shared_secret = metasecret123 I see that /usr/bin/quantum-ns-metadata-proxy process is running. When I ping 169.254.169.254 from VM, in the host's router namespace, I see the ARP request but no response. root@openstack-dev:~# ip netns exec qrouter-d9e87e85-8410-4398-9ddd-2dbc36f4b593 route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 10.5.12.1 0.0.0.0 UG0 00 qg-193bb8ee-f5 10.5.12.0 0.0.0.0 255.255.255.0 U 0 00 qg-193bb8ee-f5 192.168.2.0 0.0.0.0 255.255.255.0 U 0 00 qr-59e69986-6e root@openstack-dev:~# ip netns exec qrouter-d9e87e85-8410-4398-9ddd-2dbc36f4b593 tcpdump -i qr-59e69986-6e tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on qr-59e69986-6e, link-type EN10MB (Ethernet), capture size 65535 bytes ^C23:32:09.638289 ARP, Request who-has 192.168.2.3 tell 192.168.2.1, length 28 23:32:09.650043 ARP, Reply 192.168.2.3 is-at fa:16:3e:4f:ad:df (oui Unknown), length 28 23:32:15.768942 ARP, Request who-has 169.254.169.254 tell 192.168.2.3, length 28 23:32:16.766896 ARP, Request who-has 169.254.169.254 tell 192.168.2.3, length 28 23:32:17.766712 ARP, Request who-has 169.254.169.254 tell 192.168.2.3, length 28 23:32:18.784195 ARP, Request who-has 169.254.169.254 tell 192.168.2.3, length 28 6 packets captured 6 packets received by filter 0 packets dropped by kernel root@openstack-dev:~# Any help will be greatly appreciated. Thanks, Balu On Wed, Apr 24, 2013 at 11:48 AM, Aaron Rosen aro...@nicira.com wrote: Yup, If your host supports namespaces this can be done via the quantum-metadata-agent. The following setting is also required in your nova.conf: service_quantum_metadata_proxy=True On Tue, Apr 23, 2013 at 10:44 PM, Balamurugan V G balamuruga...@gmail.com wrote: Hi, In Grizzly, when using quantum and overlapping IPs, does metadata service work? This wasnt working in Folsom. 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 ___ 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] ANNOUNCE: Ultimate OpenStack Grizzly Guide, with super easy Quantum!
Thank you Orlando! I just remove `quantum-l3-agent' for the sake of simplicity (I don't want it for now) and have enabled `enable_isolated_metadata = True' in dhcp_agent.ini but, same result. Metadata doesn't work. The CirrOS doesn't reach the metadata server. Also, within CirrOS, there is no route to 169.254.0.0/16 network. Probably because its dhcp client isn't ready with option 121 ??? Also, the `Ubuntu Cloud Image' doesn't reach the metadata too, I'm seeing: 20130423 15:13:05,687 util.py[WARNING]: ' http://169.254.169.254/20090404/metadata/instanceid' failed [49/120s]: url error [timed out] And, I have a `Pre-Installed' Ubuntu template that I can boot and login, it have the option 121 configured but, no route to 169.254.0.0/24 network in my routing tables. To try one more option, I just enable the `enable_metadata_network = True' but, doesn't work either. Anyway, this isn't off-topic, because of enabling metadata without L3 on a Single Flat, is on my TODO list to improve my document, the Ultimate OpenStack Grizzly Guide, so, it is right on topic. And I really appreciate your help! Now I have a much better direction to follow. But, I still can't figure out how to put metadata to work. Too complicated... One more question, at the dhcp_agent, there is a message: The metadata service will only be activated when the subnet gateway_ip is None. What this means? It means that I can't use `--gateway 10.33.14.1' when running the `quantum subnet-create' ? Tks! Thiago On 23 April 2013 04:48, Salvatore Orlando sorla...@nicira.com wrote: Quantum's metadata solution for Grizzly can run either with or without the l3 agent. When running within the l3 agent, packets directed to 169.254.169.254 are sent to the default gateway; the l3 agent will spawn a metadata proxy for each router; the metadata proxy forwards them to the metadata agent using a datagram socket, and finally the agent reaches the Nova metadata server. Without the l3 agent, the 'isolated' mode can be enabled for the metadata access service. This is achieved by setting the flag enable_isolated_metadata_proxy to True in the dhcp_agent configuration file. When the isolated proxy is enabled, the dhcp agent will send an additional static route to each VM. This static route will have the dhcp agent as next hop and 169.254.0.0/16 as destination CIDR; the dhcp agent will spawn a metadata proxy for each network. Once the packet reaches the proxy, the procedure works as above. This should also explain why the metadata agent does not depend on the l3 agent. If you are deploying the l3 agent, but do not want to deploy the metadata agent on the same host, the 'metadata access network' can be considered. This option is enabled by setting enable_metadata_network on the dhcp agent configuration file. When enabled, quantum networks whose cidr is included in 169.254.0.0/16 will be regarded as 'metadata networks', and will spawn a metadata proxy. The user can then connect such network to any logical router through the quantum API; thus granting metadata access to all the networks connected to such router. I think the documentation for quantum metadata has not yet been merged in the admin guide. I hope this clarifies the matter a little... although this thread has gone a little bit off-topic. Can you consider submitting one or more questions to ask.openstack.org? Regards, Salvatore On 23 April 2013 00:50, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: That is precisely what I'm trying to figure out! How to setup metadata without L3 using Quantum Single Flat. I can't find any document about this. Plus, to make things worse, the package quantum-metadata-agent *DOES NOT DEPENDS* on quantum-l3-agent. BTW, I'm sure that with my guide, I'll be able to run Quantum on its simplest scenario! Give it a shot!! https://gist.github.com/tmartinx/d36536b7b62a48f859c2 My guide is perfect, have no bugs. Tested it +50 times. Cheers! Thiago On 22 April 2013 19:18, Paras pradhan pradhanpa...@gmail.com wrote: So this is what I understand. Even if you do flat (nova-network style) , no floating ip you still need l3 for metadata(?). I am really confused. I could never ever make quantum work. never had any issues with nova-network. Paras. On Fri, Apr 19, 2013 at 8:35 PM, Daniels Cai danx...@gmail.com wrote: paras In my experience the answer is yes . In grizzly , metadata proxy works in the qrouter's name space ,no router means no metadata . I am not sure whether any other approaches . Daniels Cai http://dnscai.com 在 2013-4-20,9:28,Martinx - ジェームズ thiagocmarti...@gmail.com 写道: Daniels, There is no `Quantum L3' on this setup (at least not on my own environment / guide). So, this leads me to one question: Metadata depends on L3? I do not want Quantum L3 package and I want Metadata... Is that possible? Tks, Thiago On 19 April 2013 21:44, Daniels Cai danx...@gmail.com wrote: Hi
Re: [Openstack] ANNOUNCE: Ultimate OpenStack Grizzly Guide, with super easy Quantum!
Hi! I just delete my subnet, to create it again without specifying `--gateway 10.33.14.1', my pre-installed images still works but, cloud based images, that requires metadata, doesn't. I'm running out of options again... I tried with and without those options: --- enable_isolated_metadata = True enable_metadata_network = True `--gateway 10.33.14.1' on quantum subnet-create... --- ...multiple times, doesn't work. Tks, Thiago On 23 April 2013 13:19, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Thank you Orlando! I just remove `quantum-l3-agent' for the sake of simplicity (I don't want it for now) and have enabled `enable_isolated_metadata = True' in dhcp_agent.ini but, same result. Metadata doesn't work. The CirrOS doesn't reach the metadata server. Also, within CirrOS, there is no route to 169.254.0.0/16 network. Probably because its dhcp client isn't ready with option 121 ??? Also, the `Ubuntu Cloud Image' doesn't reach the metadata too, I'm seeing: 20130423 15:13:05,687 util.py[WARNING]: ' http://169.254.169.254/20090404/metadata/instanceid' failed [49/120s]: url error [timed out] And, I have a `Pre-Installed' Ubuntu template that I can boot and login, it have the option 121 configured but, no route to 169.254.0.0/24 network in my routing tables. To try one more option, I just enable the `enable_metadata_network = True' but, doesn't work either. Anyway, this isn't off-topic, because of enabling metadata without L3 on a Single Flat, is on my TODO list to improve my document, the Ultimate OpenStack Grizzly Guide, so, it is right on topic. And I really appreciate your help! Now I have a much better direction to follow. But, I still can't figure out how to put metadata to work. Too complicated... One more question, at the dhcp_agent, there is a message: The metadata service will only be activated when the subnet gateway_ip is None. What this means? It means that I can't use `--gateway 10.33.14.1' when running the `quantum subnet-create' ? Tks! Thiago On 23 April 2013 04:48, Salvatore Orlando sorla...@nicira.com wrote: Quantum's metadata solution for Grizzly can run either with or without the l3 agent. When running within the l3 agent, packets directed to 169.254.169.254 are sent to the default gateway; the l3 agent will spawn a metadata proxy for each router; the metadata proxy forwards them to the metadata agent using a datagram socket, and finally the agent reaches the Nova metadata server. Without the l3 agent, the 'isolated' mode can be enabled for the metadata access service. This is achieved by setting the flag enable_isolated_metadata_proxy to True in the dhcp_agent configuration file. When the isolated proxy is enabled, the dhcp agent will send an additional static route to each VM. This static route will have the dhcp agent as next hop and 169.254.0.0/16 as destination CIDR; the dhcp agent will spawn a metadata proxy for each network. Once the packet reaches the proxy, the procedure works as above. This should also explain why the metadata agent does not depend on the l3 agent. If you are deploying the l3 agent, but do not want to deploy the metadata agent on the same host, the 'metadata access network' can be considered. This option is enabled by setting enable_metadata_network on the dhcp agent configuration file. When enabled, quantum networks whose cidr is included in 169.254.0.0/16 will be regarded as 'metadata networks', and will spawn a metadata proxy. The user can then connect such network to any logical router through the quantum API; thus granting metadata access to all the networks connected to such router. I think the documentation for quantum metadata has not yet been merged in the admin guide. I hope this clarifies the matter a little... although this thread has gone a little bit off-topic. Can you consider submitting one or more questions to ask.openstack.org? Regards, Salvatore On 23 April 2013 00:50, Martinx - ジェームズ thiagocmarti...@gmail.comwrote: That is precisely what I'm trying to figure out! How to setup metadata without L3 using Quantum Single Flat. I can't find any document about this. Plus, to make things worse, the package quantum-metadata-agent *DOES NOT DEPENDS* on quantum-l3-agent. BTW, I'm sure that with my guide, I'll be able to run Quantum on its simplest scenario! Give it a shot!! https://gist.github.com/tmartinx/d36536b7b62a48f859c2 My guide is perfect, have no bugs. Tested it +50 times. Cheers! Thiago On 22 April 2013 19:18, Paras pradhan pradhanpa...@gmail.com wrote: So this is what I understand. Even if you do flat (nova-network style) , no floating ip you still need l3 for metadata(?). I am really confused. I could never ever make quantum work. never had any issues with nova-network. Paras. On Fri, Apr 19, 2013 at 8:35 PM, Daniels Cai danx...@gmail.com wrote: paras In my experience the answer is yes . In grizzly
Re: [Openstack] ANNOUNCE: Ultimate OpenStack Grizzly Guide, with super easy Quantum!
The Ubuntu requires metadata, since there is no password there... The CirrOS have a pre-configured password cubswin:), so, it can be used without metadata... Best, Thiago On 23 April 2013 15:32, Paras pradhan pradhanpa...@gmail.com wrote: Does these require metadata? http://uec-images.ubuntu.com/releases/12.04/release/ubuntu-12.04-server-cloudimg-amd64-disk1.img http://download.cirros-cloud.net/0.3.1/cirros-0.3.1-x86_64-disk.img Thanks, Paras. On Tue, Apr 23, 2013 at 12:53 PM, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Hi! I just delete my subnet, to create it again without specifying `--gateway 10.33.14.1', my pre-installed images still works but, cloud based images, that requires metadata, doesn't. I'm running out of options again... I tried with and without those options: --- enable_isolated_metadata = True enable_metadata_network = True `--gateway 10.33.14.1' on quantum subnet-create... --- ...multiple times, doesn't work. Tks, Thiago On 23 April 2013 13:19, Martinx - ジェームズ thiagocmarti...@gmail.comwrote: Thank you Orlando! I just remove `quantum-l3-agent' for the sake of simplicity (I don't want it for now) and have enabled `enable_isolated_metadata = True' in dhcp_agent.ini but, same result. Metadata doesn't work. The CirrOS doesn't reach the metadata server. Also, within CirrOS, there is no route to 169.254.0.0/16 network. Probably because its dhcp client isn't ready with option 121 ??? Also, the `Ubuntu Cloud Image' doesn't reach the metadata too, I'm seeing: 20130423 15:13:05,687 util.py[WARNING]: ' http://169.254.169.254/20090404/metadata/instanceid' failed [49/120s]: url error [timed out] And, I have a `Pre-Installed' Ubuntu template that I can boot and login, it have the option 121 configured but, no route to 169.254.0.0/24network in my routing tables. To try one more option, I just enable the `enable_metadata_network = True' but, doesn't work either. Anyway, this isn't off-topic, because of enabling metadata without L3 on a Single Flat, is on my TODO list to improve my document, the Ultimate OpenStack Grizzly Guide, so, it is right on topic. And I really appreciate your help! Now I have a much better direction to follow. But, I still can't figure out how to put metadata to work. Too complicated... One more question, at the dhcp_agent, there is a message: The metadata service will only be activated when the subnet gateway_ip is None. What this means? It means that I can't use `--gateway 10.33.14.1' when running the `quantum subnet-create' ? Tks! Thiago On 23 April 2013 04:48, Salvatore Orlando sorla...@nicira.com wrote: Quantum's metadata solution for Grizzly can run either with or without the l3 agent. When running within the l3 agent, packets directed to 169.254.169.254 are sent to the default gateway; the l3 agent will spawn a metadata proxy for each router; the metadata proxy forwards them to the metadata agent using a datagram socket, and finally the agent reaches the Nova metadata server. Without the l3 agent, the 'isolated' mode can be enabled for the metadata access service. This is achieved by setting the flag enable_isolated_metadata_proxy to True in the dhcp_agent configuration file. When the isolated proxy is enabled, the dhcp agent will send an additional static route to each VM. This static route will have the dhcp agent as next hop and 169.254.0.0/16 as destination CIDR; the dhcp agent will spawn a metadata proxy for each network. Once the packet reaches the proxy, the procedure works as above. This should also explain why the metadata agent does not depend on the l3 agent. If you are deploying the l3 agent, but do not want to deploy the metadata agent on the same host, the 'metadata access network' can be considered. This option is enabled by setting enable_metadata_network on the dhcp agent configuration file. When enabled, quantum networks whose cidr is included in 169.254.0.0/16 will be regarded as 'metadata networks', and will spawn a metadata proxy. The user can then connect such network to any logical router through the quantum API; thus granting metadata access to all the networks connected to such router. I think the documentation for quantum metadata has not yet been merged in the admin guide. I hope this clarifies the matter a little... although this thread has gone a little bit off-topic. Can you consider submitting one or more questions to ask.openstack.org? Regards, Salvatore On 23 April 2013 00:50, Martinx - ジェームズ thiagocmarti...@gmail.comwrote: That is precisely what I'm trying to figure out! How to setup metadata without L3 using Quantum Single Flat. I can't find any document about this. Plus, to make things worse, the package quantum-metadata-agent *DOES NOT DEPENDS* on quantum-l3-agent. BTW, I'm sure that with my guide, I'll be able to run Quantum on its simplest scenario! Give it a shot!! https
[Openstack] Grizzly: Metadata with Quantum Single Flat
Guys, I'm trying to enable the metadata but, I doesn't work... At first, the quantum-l3-agent wasn't installed, because I'm running Quantum Single Flat, like this: keystone tenant-list # To note the admin tenant id. quantum net-create --tenant-id $ADMIN_TENTANT_ID sharednet1 --shared --provider:network_type flat --provider:physical_network physnet1 quantum subnet-create --ip-version 4 --tenant-id $ADMIN_TENANT_ID --gateway 10.33.14.1 sharednet1 10.33.14.0/24 --dns_nameservers list=true 8.8.8.8 8.8.4.4 Now, I've installed quantum-l3-agent, to see it metadata work but, it still doesn't work. Any tips?! Tks! Thiago ___ 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] ANNOUNCE: Ultimate OpenStack Grizzly Guide, with super easy Quantum!
That is precisely what I'm trying to figure out! How to setup metadata without L3 using Quantum Single Flat. I can't find any document about this. Plus, to make things worse, the package quantum-metadata-agent *DOES NOT DEPENDS* on quantum-l3-agent. BTW, I'm sure that with my guide, I'll be able to run Quantum on its simplest scenario! Give it a shot!! https://gist.github.com/tmartinx/d36536b7b62a48f859c2 My guide is perfect, have no bugs. Tested it +50 times. Cheers! Thiago On 22 April 2013 19:18, Paras pradhan pradhanpa...@gmail.com wrote: So this is what I understand. Even if you do flat (nova-network style) , no floating ip you still need l3 for metadata(?). I am really confused. I could never ever make quantum work. never had any issues with nova-network. Paras. On Fri, Apr 19, 2013 at 8:35 PM, Daniels Cai danx...@gmail.com wrote: paras In my experience the answer is yes . In grizzly , metadata proxy works in the qrouter's name space ,no router means no metadata . I am not sure whether any other approaches . Daniels Cai http://dnscai.com 在 2013-4-20,9:28,Martinx - ジェームズ thiagocmarti...@gmail.com 写道: Daniels, There is no `Quantum L3' on this setup (at least not on my own environment / guide). So, this leads me to one question: Metadata depends on L3? I do not want Quantum L3 package and I want Metadata... Is that possible? Tks, Thiago On 19 April 2013 21:44, Daniels Cai danx...@gmail.com wrote: Hi Paras The log says your dhcp works fine while metadata is not Check the following steps 1.Make sure nova API enables metadata service 2. A virtual router should be created for your subnet and this router is binding with a l3 agent 3.in the l3 agent metadata proxy service should be works fine Metadata service config file should contains nova API host and keystone auth info 4. Ovs bridge br-ex is needed in your l3 agent server even you don't need floating ip Daniels Cai http://dnscai.com 在 2013-4-19,23:42,Paras pradhan pradhanpa...@gmail.com 写道: Any idea why I could not hit http://169.254.169.254/20090404/instanceid? Here is what I am seeing in cirros . -- Sending discover... Sending select for 192.168.122.98... Lease of 192.168.122.98 obtained, lease time 120 deleting routers route: SIOCDELRT: No such process route: SIOCADDRT: No such process adding dns 192.168.122.1 adding dns 8.8.8.8 cirrosds 'net' up at 4.62 checking http://169.254.169.254/20090404/instanceid failed 1/20: up 4.79. request failed failed 2/20: up 6.97. request failed failed 3/20: up 9.03. request failed failed 4/20: up 11.08. request fa .. -- Thanks Paras. On Thu, Apr 11, 2013 at 7:22 AM, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Guys! I just update the *Ultimate OpenStack Grizzly Guide*https://gist.github.com/tmartinx/d36536b7b62a48f859c2 ! You guys will note that this environment works with *echo 0 /proc/sys/net/ipv4/ip_forward*, on *both* controller *AND* compute nodes! Take a look! I didn't touch the /etc/sysctl.conf file and it is working! I'll ask for the help of this community to finish my guide. On my `TODO list' I have: enable Metadata, Spice and Ceilometer. Volunteers?! Best! Thiago On 20 March 2013 19:51, Martinx - ジェームズ thiagocmarti...@gmail.comwrote: Hi! I'm working with Grizzly G3+RC1 on top of Ubuntu 12.04.2 and here is the guide I wrote: Ultimate OpenStack Grizzly Guidehttps://gist.github.com/tmartinx/d36536b7b62a48f859c2 It covers: * Ubuntu 12.04.2 * Basic Ubuntu setup * KVM * OpenvSwitch * Name Resolution for OpenStack components; * LVM for Instances * Keystone * Glance * Quantum - Single Flat, Super Green!! * Nova * Cinder / tgt * Dashboard It is still a draft but, every time I deploy Ubuntu and Grizzly, I follow this little guide... I would like some help to improve this guide... If I'm doing something wrong, tell me! Please! Probably I'm doing something wrong, I don't know yet, but I'm seeing some errors on the logs, already reported here on this list. Like for example: nova-novncproxy conflicts with novnc (no VNC console for now), dhcp-agent.log / auth.log points to some problems with `sudo' or the `rootwarp' subsystem when dealing with metadata (so it isn't working)... But in general, it works great!! Best! Thiago ___ 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
Re: [Openstack] controller and network node, same machine?
Hi Steve! Yes, it is possible. Instructions: Ultimate OpenStack Grizzly Guide: https://gist.github.com/tmartinx/d36536b7b62a48f859c2 Best! Thiago On 12 April 2013 09:40, Steve Heistand 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 (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 # ___ 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] Grizzly release packages available in the Ubuntu Cloud Archive
Hi! I figure it out! The nova-api *depends* on iptables but, the Ubuntu package is currently *missing that*. When I first install Grizzly on top of a Ubuntu minimum virtual machine today, iptables wasn't installed... I started it from scratch again, installing iptables before nova-api, the Dashboard works (in parts). --- Now, after login into my Grizzly Dashboard, I'm seeing the following two error messages there: Dashboard error: Error: Unauthorized: Unable to retrieve usage information. Error: Unauthorized: Unable to retrieve quota information. The Apache error: - [Thu Apr 11 05:08:54 2013] [notice] Apache/2.2.22 (Ubuntu) mod_wsgi/3.3 Python/2.7.3 configured -- resuming normal operations [Thu Apr 11 08:09:11 2013] [error] \x1b[31;1mUnauthorized: Unauthorized (HTTP 401)\x1b[0m [Thu Apr 11 08:09:11 2013] [error] Traceback (most recent call last): [Thu Apr 11 08:09:11 2013] [error] File /usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/usage/base.py, line 95, in summarize [Thu Apr 11 08:09:11 2013] [error] self.usage_list = self.get_usage_list(start, end) [Thu Apr 11 08:09:11 2013] [error] File /usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/usage/base.py, line 130, in get_usage_list [Thu Apr 11 08:09:11 2013] [error] return api.nova.usage_list(self.request, start, end) [Thu Apr 11 08:09:11 2013] [error] File /usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/api/nova.py, line 474, in usage_list [Thu Apr 11 08:09:11 2013] [error] novaclient(request).usage.list(start, end, True)] [Thu Apr 11 08:09:11 2013] [error] File /usr/lib/python2.7/dist-packages/novaclient/v1_1/usage.py, line 35, in list [Thu Apr 11 08:09:11 2013] [error] tenant_usages) [Thu Apr 11 08:09:11 2013] [error] File /usr/lib/python2.7/dist-packages/novaclient/base.py, line 62, in _list [Thu Apr 11 08:09:11 2013] [error] _resp, body = self.api.client.get(url) [Thu Apr 11 08:09:11 2013] [error] File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 230, in get [Thu Apr 11 08:09:11 2013] [error] return self._cs_request(url, 'GET', **kwargs) [Thu Apr 11 08:09:11 2013] [error] File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 227, in _cs_request [Thu Apr 11 08:09:11 2013] [error] raise e [Thu Apr 11 08:09:11 2013] [error] Unauthorized: Unauthorized (HTTP 401) [Thu Apr 11 08:09:11 2013] [error] \x1b[31;1mUnauthorized: Unauthorized (HTTP 401)\x1b[0m [Thu Apr 11 08:09:11 2013] [error] Traceback (most recent call last): [Thu Apr 11 08:09:11 2013] [error] File /usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/usage/base.py, line 112, in get_quotas [Thu Apr 11 08:09:11 2013] [error] self.quotas = quotas.tenant_quota_usages(self.request) [Thu Apr 11 08:09:11 2013] [error] File /usr/lib/python2.7/dist-packages/horizon/utils/memoized.py, line 33, in __call__ [Thu Apr 11 08:09:11 2013] [error] value = self.func(*args) [Thu Apr 11 08:09:11 2013] [error] File /usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/usage/quotas.py, line 116, in tenant_quota_usages [Thu Apr 11 08:09:11 2013] [error] disabled_quotas=disabled_quotas): [Thu Apr 11 08:09:11 2013] [error] File /usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/usage/quotas.py, line 99, in get_tenant_quota_data [Thu Apr 11 08:09:11 2013] [error] tenant_id=tenant_id) [Thu Apr 11 08:09:11 2013] [error] File /usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/usage/quotas.py, line 76, in _get_quota_data [Thu Apr 11 08:09:11 2013] [error] quotasets.append(getattr(nova, method_name)(request, tenant_id)) [Thu Apr 11 08:09:11 2013] [error] File /usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/api/nova.py, line 457, in tenant_quota_get [Thu Apr 11 08:09:11 2013] [error] return QuotaSet(novaclient(request).quotas.get(tenant_id)) [Thu Apr 11 08:09:11 2013] [error] File /usr/lib/python2.7/dist-packages/novaclient/v1_1/quotas.py, line 37, in get [Thu Apr 11 08:09:11 2013] [error] return self._get(/os-quota-sets/%s % (tenant_id), quota_set) [Thu Apr 11 08:09:11 2013] [error] File /usr/lib/python2.7/dist-packages/novaclient/base.py, line 140, in _get [Thu Apr 11 08:09:11 2013] [error] _resp, body = self.api.client.get(url) [Thu Apr 11 08:09:11 2013] [error] File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 230, in get [Thu Apr 11 08:09:11 2013] [error] return self._cs_request(url, 'GET', **kwargs) [Thu Apr 11 08:09:11 2013] [error] File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 227, in _cs_request [Thu Apr 11 08:09:11 2013] [error] raise e [Thu Apr 11 08:09:11 2013] [error] Unauthorized: Unauthorized (HTTP 401) - The nova-api.log: -- 2013-04-11 05:12:26.906 1468 INFO
Re: [Openstack] Grizzly release packages available in the Ubuntu Cloud Archive
Just for the record, under Dashboard - System Info, the Default Quotas is empty. On 11 April 2013 05:15, Martinx - ジェ�`ムズ thiagocmarti...@gmail.com wrote: Hi! I figure it out! The nova-api *depends* on iptables but, the Ubuntu package is currently *missing that*. When I first install Grizzly on top of a Ubuntu minimum virtual machine today, iptables wasn't installed... I started it from scratch again, installing iptables before nova-api, the Dashboard works (in parts). --- Now, after login into my Grizzly Dashboard, I'm seeing the following two error messages there: Dashboard error: Error: Unauthorized: Unable to retrieve usage information. Error: Unauthorized: Unable to retrieve quota information. The Apache error: - [Thu Apr 11 05:08:54 2013] [notice] Apache/2.2.22 (Ubuntu) mod_wsgi/3.3 Python/2.7.3 configured -- resuming normal operations [Thu Apr 11 08:09:11 2013] [error] \x1b[31;1mUnauthorized: Unauthorized (HTTP 401)\x1b[0m [Thu Apr 11 08:09:11 2013] [error] Traceback (most recent call last): [Thu Apr 11 08:09:11 2013] [error] File /usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/usage/base.py, line 95, in summarize [Thu Apr 11 08:09:11 2013] [error] self.usage_list = self.get_usage_list(start, end) [Thu Apr 11 08:09:11 2013] [error] File /usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/usage/base.py, line 130, in get_usage_list [Thu Apr 11 08:09:11 2013] [error] return api.nova.usage_list(self.request, start, end) [Thu Apr 11 08:09:11 2013] [error] File /usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/api/nova.py, line 474, in usage_list [Thu Apr 11 08:09:11 2013] [error] novaclient(request).usage.list(start, end, True)] [Thu Apr 11 08:09:11 2013] [error] File /usr/lib/python2.7/dist-packages/novaclient/v1_1/usage.py, line 35, in list [Thu Apr 11 08:09:11 2013] [error] tenant_usages) [Thu Apr 11 08:09:11 2013] [error] File /usr/lib/python2.7/dist-packages/novaclient/base.py, line 62, in _list [Thu Apr 11 08:09:11 2013] [error] _resp, body = self.api.client.get(url) [Thu Apr 11 08:09:11 2013] [error] File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 230, in get [Thu Apr 11 08:09:11 2013] [error] return self._cs_request(url, 'GET', **kwargs) [Thu Apr 11 08:09:11 2013] [error] File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 227, in _cs_request [Thu Apr 11 08:09:11 2013] [error] raise e [Thu Apr 11 08:09:11 2013] [error] Unauthorized: Unauthorized (HTTP 401) [Thu Apr 11 08:09:11 2013] [error] \x1b[31;1mUnauthorized: Unauthorized (HTTP 401)\x1b[0m [Thu Apr 11 08:09:11 2013] [error] Traceback (most recent call last): [Thu Apr 11 08:09:11 2013] [error] File /usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/usage/base.py, line 112, in get_quotas [Thu Apr 11 08:09:11 2013] [error] self.quotas = quotas.tenant_quota_usages(self.request) [Thu Apr 11 08:09:11 2013] [error] File /usr/lib/python2.7/dist-packages/horizon/utils/memoized.py, line 33, in __call__ [Thu Apr 11 08:09:11 2013] [error] value = self.func(*args) [Thu Apr 11 08:09:11 2013] [error] File /usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/usage/quotas.py, line 116, in tenant_quota_usages [Thu Apr 11 08:09:11 2013] [error] disabled_quotas=disabled_quotas): [Thu Apr 11 08:09:11 2013] [error] File /usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/usage/quotas.py, line 99, in get_tenant_quota_data [Thu Apr 11 08:09:11 2013] [error] tenant_id=tenant_id) [Thu Apr 11 08:09:11 2013] [error] File /usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/usage/quotas.py, line 76, in _get_quota_data [Thu Apr 11 08:09:11 2013] [error] quotasets.append(getattr(nova, method_name)(request, tenant_id)) [Thu Apr 11 08:09:11 2013] [error] File /usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/api/nova.py, line 457, in tenant_quota_get [Thu Apr 11 08:09:11 2013] [error] return QuotaSet(novaclient(request).quotas.get(tenant_id)) [Thu Apr 11 08:09:11 2013] [error] File /usr/lib/python2.7/dist-packages/novaclient/v1_1/quotas.py, line 37, in get [Thu Apr 11 08:09:11 2013] [error] return self._get(/os-quota-sets/%s % (tenant_id), quota_set) [Thu Apr 11 08:09:11 2013] [error] File /usr/lib/python2.7/dist-packages/novaclient/base.py, line 140, in _get [Thu Apr 11 08:09:11 2013] [error] _resp, body = self.api.client.get(url) [Thu Apr 11 08:09:11 2013] [error] File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 230, in get [Thu Apr 11 08:09:11 2013] [error] return self._cs_request(url, 'GET', **kwargs) [Thu Apr 11 08:09:11 2013] [error] File
Re: [Openstack] Grizzly release packages available in the Ubuntu Cloud Archive
Another error: Dashboard - Flavors: Error: Unauthorized: Unable to retrieve flavor list. `nova flavor-list' returns: ERROR: Unauthorized (HTTP 401) I am missing something but, where? Tks! Thiago On 11 April 2013 05:20, Martinx - ジェ�`ムズ thiagocmarti...@gmail.com wrote: Just for the record, under Dashboard - System Info, the Default Quotas is empty. On 11 April 2013 05:15, Martinx - ジェ�`ムズ thiagocmarti...@gmail.com wrote: Hi! I figure it out! The nova-api *depends* on iptables but, the Ubuntu package is currently *missing that*. When I first install Grizzly on top of a Ubuntu minimum virtual machine today, iptables wasn't installed... I started it from scratch again, installing iptables before nova-api, the Dashboard works (in parts). --- Now, after login into my Grizzly Dashboard, I'm seeing the following two error messages there: Dashboard error: Error: Unauthorized: Unable to retrieve usage information. Error: Unauthorized: Unable to retrieve quota information. The Apache error: - [Thu Apr 11 05:08:54 2013] [notice] Apache/2.2.22 (Ubuntu) mod_wsgi/3.3 Python/2.7.3 configured -- resuming normal operations [Thu Apr 11 08:09:11 2013] [error] \x1b[31;1mUnauthorized: Unauthorized (HTTP 401)\x1b[0m [Thu Apr 11 08:09:11 2013] [error] Traceback (most recent call last): [Thu Apr 11 08:09:11 2013] [error] File /usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/usage/base.py, line 95, in summarize [Thu Apr 11 08:09:11 2013] [error] self.usage_list = self.get_usage_list(start, end) [Thu Apr 11 08:09:11 2013] [error] File /usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/usage/base.py, line 130, in get_usage_list [Thu Apr 11 08:09:11 2013] [error] return api.nova.usage_list(self.request, start, end) [Thu Apr 11 08:09:11 2013] [error] File /usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/api/nova.py, line 474, in usage_list [Thu Apr 11 08:09:11 2013] [error] novaclient(request).usage.list(start, end, True)] [Thu Apr 11 08:09:11 2013] [error] File /usr/lib/python2.7/dist-packages/novaclient/v1_1/usage.py, line 35, in list [Thu Apr 11 08:09:11 2013] [error] tenant_usages) [Thu Apr 11 08:09:11 2013] [error] File /usr/lib/python2.7/dist-packages/novaclient/base.py, line 62, in _list [Thu Apr 11 08:09:11 2013] [error] _resp, body = self.api.client.get(url) [Thu Apr 11 08:09:11 2013] [error] File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 230, in get [Thu Apr 11 08:09:11 2013] [error] return self._cs_request(url, 'GET', **kwargs) [Thu Apr 11 08:09:11 2013] [error] File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 227, in _cs_request [Thu Apr 11 08:09:11 2013] [error] raise e [Thu Apr 11 08:09:11 2013] [error] Unauthorized: Unauthorized (HTTP 401) [Thu Apr 11 08:09:11 2013] [error] \x1b[31;1mUnauthorized: Unauthorized (HTTP 401)\x1b[0m [Thu Apr 11 08:09:11 2013] [error] Traceback (most recent call last): [Thu Apr 11 08:09:11 2013] [error] File /usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/usage/base.py, line 112, in get_quotas [Thu Apr 11 08:09:11 2013] [error] self.quotas = quotas.tenant_quota_usages(self.request) [Thu Apr 11 08:09:11 2013] [error] File /usr/lib/python2.7/dist-packages/horizon/utils/memoized.py, line 33, in __call__ [Thu Apr 11 08:09:11 2013] [error] value = self.func(*args) [Thu Apr 11 08:09:11 2013] [error] File /usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/usage/quotas.py, line 116, in tenant_quota_usages [Thu Apr 11 08:09:11 2013] [error] disabled_quotas=disabled_quotas): [Thu Apr 11 08:09:11 2013] [error] File /usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/usage/quotas.py, line 99, in get_tenant_quota_data [Thu Apr 11 08:09:11 2013] [error] tenant_id=tenant_id) [Thu Apr 11 08:09:11 2013] [error] File /usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/usage/quotas.py, line 76, in _get_quota_data [Thu Apr 11 08:09:11 2013] [error] quotasets.append(getattr(nova, method_name)(request, tenant_id)) [Thu Apr 11 08:09:11 2013] [error] File /usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/api/nova.py, line 457, in tenant_quota_get [Thu Apr 11 08:09:11 2013] [error] return QuotaSet(novaclient(request).quotas.get(tenant_id)) [Thu Apr 11 08:09:11 2013] [error] File /usr/lib/python2.7/dist-packages/novaclient/v1_1/quotas.py, line 37, in get [Thu Apr 11 08:09:11 2013] [error] return self._get(/os-quota-sets/%s % (tenant_id), quota_set) [Thu Apr 11 08:09:11 2013] [error] File /usr/lib/python2.7/dist-packages/novaclient/base.py, line 140, in _get [Thu Apr 11 08:09:11 2013] [error] _resp, body = self.api.client.get(url) [Thu
Re: [Openstack] Grizzly release packages available in the Ubuntu Cloud Archive
Mmmm... That's true... My mistake, I forgot to setup /etc/nova/api-paste.ini. Sorry about the buzz... Tks! Thiago On 11 April 2013 05:24, James Page james.p...@canonical.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 11/04/13 09:22, Martinx - ジェームズ wrote: Dashboard - Flavors: Error: Unauthorized: Unable to retrieve flavor list. `nova flavor-list' returns: ERROR: Unauthorized (HTTP 401) I am missing something but, where? All of the missing data (and the error above) is due to the fact that the user you are using to access the dashboard does not appear to have the right permissions - I would suspect some sort of misconfiguration in keystone. - -- James Page Technical Lead Ubuntu Server Team james.p...@canonical.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQIcBAEBCAAGBQJRZnNPAAoJEL/srsug59jDVQ0P/2CxVmwT6DOvB08GKE87oIe7 VQUvCkc59+Gq0t6kpr33c2wBD5IPERtU0g0/v+1Q+6f6ay+AnvbFWWHBZuwpujAc IcDqh+NMCU7FwEROEAD5bU9clTqMcepB+ONnjij/jpkhUvwGByhtGyan6Ek5K2Rc ofQusmlk4cZX/k+u4+GCKIrvLIv+mRjnsZYtV8WahOzMDAA3RRWIsOGmjOOT4D73 B3RTUM7W9IqfWo2Tau3JjLzrq09zHG+4tasaWuoNSUPBJaXAy8dKJp4zAoUEbAqd BXf63APMRrz+FQVMTPOsgH+atsuBpUS4UbCzJmfLn6y/XXKyDxDh4QdATIc2ylJl nUCmSa2ucDWFL0vFU8FVS2yQ5VO/VJILYQpiOLg7FFfFvhD/IYXRqLnEHMWGZ1RB dNWYZgGpLjpH23nrPrbd15AmEuacwMLKpbqPXno6Uf6WWHBv8MCxRs4fymfcw4xm rHh4bNWS8bPY7WpfG+WfH9tv1DsAU9m5UJRGPNyIZ7HCr/Q+Jh1qohLrHViD+mYl UFZ3OWrYWEZ7Su14udgBwUH6xzgzr00KR+o1P05Yrs737zAZxWS8o8pRqkhx0H9G DpTk1WrygcIgjp4dNc1u97fiwffXqgjmXZcCXk8QYFKREAEgpn8+zTQDHMbmQST8 cMX7TpyNGIKphX/eVSeW =UeaH -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 release packages available in the Ubuntu Cloud Archive
Only 1 more thing (for now)...=) After I purged the package `openstack-dashboard-ubuntu-theme', the default OpenStack Dashboard opened without any style (I think CSS is missing), don't know... Tips?! On 11 April 2013 05:38, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Mmmm... That's true... My mistake, I forgot to setup /etc/nova/api-paste.ini. Sorry about the buzz... Tks! Thiago On 11 April 2013 05:24, James Page james.p...@canonical.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 11/04/13 09:22, Martinx - ジェームズ wrote: Dashboard - Flavors: Error: Unauthorized: Unable to retrieve flavor list. `nova flavor-list' returns: ERROR: Unauthorized (HTTP 401) I am missing something but, where? All of the missing data (and the error above) is due to the fact that the user you are using to access the dashboard does not appear to have the right permissions - I would suspect some sort of misconfiguration in keystone. - -- James Page Technical Lead Ubuntu Server Team james.p...@canonical.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQIcBAEBCAAGBQJRZnNPAAoJEL/srsug59jDVQ0P/2CxVmwT6DOvB08GKE87oIe7 VQUvCkc59+Gq0t6kpr33c2wBD5IPERtU0g0/v+1Q+6f6ay+AnvbFWWHBZuwpujAc IcDqh+NMCU7FwEROEAD5bU9clTqMcepB+ONnjij/jpkhUvwGByhtGyan6Ek5K2Rc ofQusmlk4cZX/k+u4+GCKIrvLIv+mRjnsZYtV8WahOzMDAA3RRWIsOGmjOOT4D73 B3RTUM7W9IqfWo2Tau3JjLzrq09zHG+4tasaWuoNSUPBJaXAy8dKJp4zAoUEbAqd BXf63APMRrz+FQVMTPOsgH+atsuBpUS4UbCzJmfLn6y/XXKyDxDh4QdATIc2ylJl nUCmSa2ucDWFL0vFU8FVS2yQ5VO/VJILYQpiOLg7FFfFvhD/IYXRqLnEHMWGZ1RB dNWYZgGpLjpH23nrPrbd15AmEuacwMLKpbqPXno6Uf6WWHBv8MCxRs4fymfcw4xm rHh4bNWS8bPY7WpfG+WfH9tv1DsAU9m5UJRGPNyIZ7HCr/Q+Jh1qohLrHViD+mYl UFZ3OWrYWEZ7Su14udgBwUH6xzgzr00KR+o1P05Yrs737zAZxWS8o8pRqkhx0H9G DpTk1WrygcIgjp4dNc1u97fiwffXqgjmXZcCXk8QYFKREAEgpn8+zTQDHMbmQST8 cMX7TpyNGIKphX/eVSeW =UeaH -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 release packages available in the Ubuntu Cloud Archive
Hi! I'm still facing a small issue (already reported here during test phase) with Quantum (Grizzly + Ubuntu 12.04). If I do not do this: visudo --- quantum ALL=NOPASSWD: ALL --- Quantum doesn't work... Too much erros on auth.log. ...And if I try this within `visudo': --- includedir /etc/sudoers.d --- ...The `visudo' section doesn't close, a warning about a fatal error appear. NOTE: I'm following this guide: *Ultimate OpenStack Grizzly Guide* https://gist.github.com/tmartinx/d36536b7b62a48f859c2 Tks, Thiago On 9 April 2013 10:20, James Page james.p...@canonical.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi All OpenStack Grizzly release packages are now available in the Ubuntu Cloud Archive for Ubuntu 12.04 - see https://wiki.ubuntu.com/ServerTeam/CloudArchive for details on how to enable and use these packages on Ubuntu 12.04. Please note that further Ubuntu related updates may land into the Cloud Archive for Grizzly between now and the final release of Ubuntu 13.04 in a couple of weeks time; 13.04 is now feature frozen so these should be bug fixes only. Enjoy James - -- James Page Technical Lead Ubuntu Server Team james.p...@canonical.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQIcBAEBCAAGBQJRZBWSAAoJEL/srsug59jDasAQALXgHF2OfrAySBGdati0GImP gKJ7gHs5uNgOHi99m4XX/LUsRWMYrYhmswKTGpFvnIhgy4nxsvvQPc5+9k9Om/lz ArGDivKmf7idInGfRTdp7hGm/llgNa7WLaU+GwVACuj0utBkF5RcTTE0kES1kFX2 CAvHMQMDqLfVBpDWunsarVyE9VBMJdVHJQZWpdzDhiTForhawcZXxB9fh2qHpKhS nX6AqP77JZ6XARw4fTLI30n6gQritwPsbK1J93QwXFtNqu5W5TUc+GAukQSVcoAy frkYSkJX+4MawkhI7PJ919O0y9q9O3UAn6sH+q4xk8Mpak/xJ0KUxHZX81MUw0Q5 5BmdRsJwCkRPYiz1Qc0sqqT5ROlr/WnDiHUIEwjs8IYAf2/hjTUD+KjOz7ycPWqg V/asjzqtgTuLDCESWv5yG4vF/CWHTf00e6nqTgfoORHHVBnTnImFsq7CryLzUxes nSRvTAALoa/71+1qMpUoUS61bCcKhY2fBsCn2uqMM1nHiot2MUH1wVEajKiX332N X2IWSyHvNzr7/UP3BS5A5LKj3ck5NTdr46ft0HfLeknu5jcjOb7cltDH2wkFSunU 9t7p2Z3yBPw5tK5c8Fmt5gAscw9YfYhjE4Dufd12nOCD3Go2Xw8gbzjCkSQYtiY7 RoxivOeqbSwAJu0Q6Zm4 =kvSY -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 ___ 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] ANNOUNCE: Ultimate OpenStack Grizzly Guide, with super easy Quantum!
Awesome!!! :-D Guide updated! Cheers! Thiago On 21 March 2013 12:10, Razique Mahroua razique.mahr...@gmail.com wrote: great guide, thanks a lot ! *Razique Mahroua** - **Nuage Co* razique.mahr...@gmail.com Tel : +33 9 72 37 94 15 Le 21 mars 2013 à 15:26, Jean-Baptiste RANSY jean-baptiste.ra...@alyseo.com a écrit : Hello Thiago, I think it's better to use rootwrap in sudoers : nova ALL = (root) NOPASSWD: /usr/bin/nova-rootwrap /etc/nova/rootwrap.conf * cinder ALL = (root) NOPASSWD: /usr/bin/cinder-rootwrap /etc/cinder/rootwrap.conf * quantum ALL = (root) NOPASSWD: /usr/bin/quantum-rootwrap /etc/quantum/rootwrap.conf * NOTE : with quantum (l3, dhcp, etc ..) you can encounter issue with rootwrap, especially with namespaces (i don't know if this is still the case) To fix that, just add 'root_helper = sudo /usr/bin/quantum-rootwrap /etc/quantum/rootwrap.conf' in the .ini file of each quantum service. I don't know why root_helper isn't in each quantum service sample files if it must be configured ... is it normal or not ? If this addition (to add root_helper in each ini file) should not be necessary, I think i identified the root problem. In the dhcp_agent for example, just need to replace each occurrences of 'self.conf.root_helper' by 'self.root_helper' If someone has the answer, let me know if I should open a bug or not. Regards, jbr_ On 03/21/2013 01:19 AM, Martinx - ジェームズ wrote: 1 problem fixed with: visudo --- quantum ALL=NOPASSWD: ALL cinder ALL=NOPASSWD: ALL nova ALL=NOPASSWD: ALL --- Guide updated... On 20 March 2013 19:51, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Hi! I'm working with Grizzly G3+RC1 on top of Ubuntu 12.04.2 and here is the guide I wrote: Ultimate OpenStack Grizzly Guidehttps://gist.github.com/tmartinx/d36536b7b62a48f859c2 It covers: * Ubuntu 12.04.2 * Basic Ubuntu setup * KVM * OpenvSwitch * Name Resolution for OpenStack components; * LVM for Instances * Keystone * Glance * Quantum - Single Flat, Super Green!! * Nova * Cinder / tgt * Dashboard It is still a draft but, every time I deploy Ubuntu and Grizzly, I follow this little guide... I would like some help to improve this guide... If I'm doing something wrong, tell me! Please! Probably I'm doing something wrong, I don't know yet, but I'm seeing some errors on the logs, already reported here on this list. Like for example: nova-novncproxy conflicts with novnc (no VNC console for now), dhcp-agent.log / auth.log points to some problems with `sudo' or the `rootwarp' subsystem when dealing with metadata (so it isn't working)... But in general, it works great!! Best! Thiago ___ 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 NUAGECO-LOGO-Fblan_petit.jpg___ 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] ANNOUNCE: Ultimate OpenStack Grizzly Guide, with super easy Quantum!
Guys! I just update the *Ultimate OpenStack Grizzly Guide*https://gist.github.com/tmartinx/d36536b7b62a48f859c2 ! You guys will note that this environment works with *echo 0 /proc/sys/net/ipv4/ip_forward*, on *both* controller *AND* compute nodes! Take a look! I didn't touch the /etc/sysctl.conf file and it is working! I'll ask for the help of this community to finish my guide. On my `TODO list' I have: enable Metadata, Spice and Ceilometer. Volunteers?! Best! Thiago On 20 March 2013 19:51, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Hi! I'm working with Grizzly G3+RC1 on top of Ubuntu 12.04.2 and here is the guide I wrote: Ultimate OpenStack Grizzly Guidehttps://gist.github.com/tmartinx/d36536b7b62a48f859c2 It covers: * Ubuntu 12.04.2 * Basic Ubuntu setup * KVM * OpenvSwitch * Name Resolution for OpenStack components; * LVM for Instances * Keystone * Glance * Quantum - Single Flat, Super Green!! * Nova * Cinder / tgt * Dashboard It is still a draft but, every time I deploy Ubuntu and Grizzly, I follow this little guide... I would like some help to improve this guide... If I'm doing something wrong, tell me! Please! Probably I'm doing something wrong, I don't know yet, but I'm seeing some errors on the logs, already reported here on this list. Like for example: nova-novncproxy conflicts with novnc (no VNC console for now), dhcp-agent.log / auth.log points to some problems with `sudo' or the `rootwarp' subsystem when dealing with metadata (so it isn't working)... But in general, it works great!! Best! Thiago ___ 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] Grizzly Dashboad problem...
Guys, I just install Grizzly from UCA. When I try to access the Dashboard, I'm getting: Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, webmaster@localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log. -- On the apache error.log: UncompressableFileError: 'horizon/js/horizon.js' isn't accessible via COMPRESS_URL ('/static/') and can't be compressed, referer: http://10.32.14.232/horizon The file /etc/openstack-dashboard/local_settings.py contains: COMPRESS_OFFLINE = False What am I doing wrong? I'm weeks now without Dashboard, I tough that this problem was solved with the stable release but, it isn't stable yet... I appreciate any help. Thanks! Thiago ___ 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 Dashboad problem...
Here is the full apache error log after login into the Dashboard: http://paste.openstack.org/show/35722/ What can I do? Tks, Thiago On 10 April 2013 12:04, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Guys, I just install Grizzly from UCA. When I try to access the Dashboard, I'm getting: Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, webmaster@localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log. -- On the apache error.log: UncompressableFileError: 'horizon/js/horizon.js' isn't accessible via COMPRESS_URL ('/static/') and can't be compressed, referer: http://10.32.14.232/horizon The file /etc/openstack-dashboard/local_settings.py contains: COMPRESS_OFFLINE = False What am I doing wrong? I'm weeks now without Dashboard, I tough that this problem was solved with the stable release but, it isn't stable yet... I appreciate any help. Thanks! Thiago ___ 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 release packages available in the Ubuntu Cloud Archive
Guys, This isn't ready. Just install Ubuntu 12.04 + Grizzly via UCA, after login into Dashboard, getting Internal Server Error message. Dashboard is broken. Tks, Thiago On 9 April 2013 10:20, James Page james.p...@canonical.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi All OpenStack Grizzly release packages are now available in the Ubuntu Cloud Archive for Ubuntu 12.04 - see https://wiki.ubuntu.com/ServerTeam/CloudArchive for details on how to enable and use these packages on Ubuntu 12.04. Please note that further Ubuntu related updates may land into the Cloud Archive for Grizzly between now and the final release of Ubuntu 13.04 in a couple of weeks time; 13.04 is now feature frozen so these should be bug fixes only. Enjoy James - -- James Page Technical Lead Ubuntu Server Team james.p...@canonical.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQIcBAEBCAAGBQJRZBWSAAoJEL/srsug59jDasAQALXgHF2OfrAySBGdati0GImP gKJ7gHs5uNgOHi99m4XX/LUsRWMYrYhmswKTGpFvnIhgy4nxsvvQPc5+9k9Om/lz ArGDivKmf7idInGfRTdp7hGm/llgNa7WLaU+GwVACuj0utBkF5RcTTE0kES1kFX2 CAvHMQMDqLfVBpDWunsarVyE9VBMJdVHJQZWpdzDhiTForhawcZXxB9fh2qHpKhS nX6AqP77JZ6XARw4fTLI30n6gQritwPsbK1J93QwXFtNqu5W5TUc+GAukQSVcoAy frkYSkJX+4MawkhI7PJ919O0y9q9O3UAn6sH+q4xk8Mpak/xJ0KUxHZX81MUw0Q5 5BmdRsJwCkRPYiz1Qc0sqqT5ROlr/WnDiHUIEwjs8IYAf2/hjTUD+KjOz7ycPWqg V/asjzqtgTuLDCESWv5yG4vF/CWHTf00e6nqTgfoORHHVBnTnImFsq7CryLzUxes nSRvTAALoa/71+1qMpUoUS61bCcKhY2fBsCn2uqMM1nHiot2MUH1wVEajKiX332N X2IWSyHvNzr7/UP3BS5A5LKj3ck5NTdr46ft0HfLeknu5jcjOb7cltDH2wkFSunU 9t7p2Z3yBPw5tK5c8Fmt5gAscw9YfYhjE4Dufd12nOCD3Go2Xw8gbzjCkSQYtiY7 RoxivOeqbSwAJu0Q6Zm4 =kvSY -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 ___ 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 Dashboad problem...
Okay, I'll double check it... Tks! On 10 April 2013 13:59, Ritesh Nanda riteshnand...@gmail.com wrote: Most probably your nova-* services are having some problem. Check whether nova is working properly. On Wed, Apr 10, 2013 at 8:47 PM, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Here is the full apache error log after login into the Dashboard: http://paste.openstack.org/show/35722/ What can I do? Tks, Thiago On 10 April 2013 12:04, Martinx - ジェームズ thiagocmarti...@gmail.comwrote: Guys, I just install Grizzly from UCA. When I try to access the Dashboard, I'm getting: Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, webmaster@localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log. -- On the apache error.log: UncompressableFileError: 'horizon/js/horizon.js' isn't accessible via COMPRESS_URL ('/static/') and can't be compressed, referer: http://10.32.14.232/horizon The file /etc/openstack-dashboard/local_settings.py contains: COMPRESS_OFFLINE = False What am I doing wrong? I'm weeks now without Dashboard, I tough that this problem was solved with the stable release but, it isn't stable yet... I appreciate any help. Thanks! Thiago ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- * With Regards * * Ritesh Nanda * *** * http://www.ericsson.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
Re: [Openstack] Grizzly release packages available in the Ubuntu Cloud Archive
YAY!!! Thank you guys!!! On 9 April 2013 10:20, James Page james.p...@canonical.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi All OpenStack Grizzly release packages are now available in the Ubuntu Cloud Archive for Ubuntu 12.04 - see https://wiki.ubuntu.com/ServerTeam/CloudArchive for details on how to enable and use these packages on Ubuntu 12.04. Please note that further Ubuntu related updates may land into the Cloud Archive for Grizzly between now and the final release of Ubuntu 13.04 in a couple of weeks time; 13.04 is now feature frozen so these should be bug fixes only. Enjoy James - -- James Page Technical Lead Ubuntu Server Team james.p...@canonical.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQIcBAEBCAAGBQJRZBWSAAoJEL/srsug59jDasAQALXgHF2OfrAySBGdati0GImP gKJ7gHs5uNgOHi99m4XX/LUsRWMYrYhmswKTGpFvnIhgy4nxsvvQPc5+9k9Om/lz ArGDivKmf7idInGfRTdp7hGm/llgNa7WLaU+GwVACuj0utBkF5RcTTE0kES1kFX2 CAvHMQMDqLfVBpDWunsarVyE9VBMJdVHJQZWpdzDhiTForhawcZXxB9fh2qHpKhS nX6AqP77JZ6XARw4fTLI30n6gQritwPsbK1J93QwXFtNqu5W5TUc+GAukQSVcoAy frkYSkJX+4MawkhI7PJ919O0y9q9O3UAn6sH+q4xk8Mpak/xJ0KUxHZX81MUw0Q5 5BmdRsJwCkRPYiz1Qc0sqqT5ROlr/WnDiHUIEwjs8IYAf2/hjTUD+KjOz7ycPWqg V/asjzqtgTuLDCESWv5yG4vF/CWHTf00e6nqTgfoORHHVBnTnImFsq7CryLzUxes nSRvTAALoa/71+1qMpUoUS61bCcKhY2fBsCn2uqMM1nHiot2MUH1wVEajKiX332N X2IWSyHvNzr7/UP3BS5A5LKj3ck5NTdr46ft0HfLeknu5jcjOb7cltDH2wkFSunU 9t7p2Z3yBPw5tK5c8Fmt5gAscw9YfYhjE4Dufd12nOCD3Go2Xw8gbzjCkSQYtiY7 RoxivOeqbSwAJu0Q6Zm4 =kvSY -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 ___ 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
`Ultimate OpenStack Grizzly Guide' (updating it today to make use of new Ubuntu Cloud Archive for Grizzly): https://gist.github.com/tmartinx/d36536b7b62a48f859c2 ;-) On 9 April 2013 10:42, Filipe Manco filipe.ma...@gmail.com wrote: Is it safe to downgrade to a previous Ubuntu version? Can someone point a good tutorial on how to do it properly? Thanks Filipe Manco http://about.me/fmanco 2013/4/9 Brad Knowles bknow...@momentumsi.com On Apr 9, 2013, at 1:43 AM, skible.openst...@gmail.coma skible.openst...@gmail.com wrote: Thanks for your reply. In that case, i will upgrade my ubuntu server to 13.04 and download the grizzly packages from there. Is this the best you to get grizzly ? Quoting Mac Innes, Kiall ki...@hp.com: 12.04 will get packages for OpenStack Grizzly, Havana and I, 13.04 on the other hand will get Grizzly and that's it. If you want Havana, you'll need to upgrade to 13.10, or downgrade to 12.04 when the time comes. So, it all depends on what you want to do with those systems. Do you want to keep upgrading the OS on them to each new release, maybe because there are other things being released that you want to play with which won't be made available for 12.04? In that case, going with 13.04 should be fine. -- Brad Knowles bknow...@momentumsi.com Senior Consultant ___ 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
Re: [Openstack] Grizzly official packages
aptitude install ubuntu-cloud-keyring aptitude update On 8 April 2013 13:05, Steve Heistand steve.heist...@nasa.gov wrote: -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.comprecise-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.com5EDB1B62EC4926EA 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/ubuntuprecise-updates/grizzly main # deb-src http://ubuntu-cloud.archive.canonical.com/ubuntuprecise-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/ubuntuprecise-proposed/grizzly main # deb-src http://ubuntu-cloud.archive.canonical.com/ubuntuprecise-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 ___ 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
BTW, I used to add Ubuntu Cloud Archives (Folsom sub dir) to my regular hypervisors (only with KVM - no Nova, no OpenStack), to get new versions of libvirt and use it with virt-manager. But, now, with UCA for Grizzly, there a libvirt version 1.0.2 and, when I tried to create a LVM LV trough virt-manager (details - storage - lvm - new volume), I'm getting this: --- Logical volume --- LV Name/dev/vg01/raring-disk0 VG Namevg01 LV UUID LV Write Accessread/write *LV snapshot status active destination for /dev/vg01/raring-disk0_vorigin ???* LV Status available # open 0 LV SizeX.XX GiB Current LE 2500 COW-table size 4.00 MiB COW-table LE 1 Allocated to snapshot 0.20% Snapshot chunk size4.00 KiB Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 252:8 Instead of this (previous libvirt): --- Logical volume --- LV Name/dev/vg01/raring1-disk0 VG Namevg01 LV UUIDX LV Write Accessread/write LV Status available # open 0 LV SizeX.XX GiB Current LE 1250 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 252:7 The main problem is, after a system reboot and lots of failures, I'm getting this: --- Logical volume --- LV Name/dev/vg01/raring-disk0 VG Namevg01 LV UUIDXX LV Write Accessread/write *LV snapshot status INACTIVE destination for /dev/vg01/bank2-disk0_vorigin ??* LV Status NOT available LV Size5.86 GiB Current LE 1500 COW-table size 4.00 MiB COW-table LE 1 Snapshot chunk size4.00 KiB Segments 1 Allocation inherit Read ahead sectors auto LOGICAL VOLUME GONE!! VM CONTENTS LOST AFTER REBOOT! Maybe this is a problem only when using new libvirt 1.0.2 with virt-manager 0.9.3 from Ubuntu LTS, and it does not affect Grizzly... Don't know yet... Anyway, I'm just reporting it here to spread this info. Someone here knows how to fix this? I mean, probably the new libvirt is creating the LV as a broken snapshots instead of regular LV? If so, maybe I should ask on libvirt-users instead... I'm downgrading all my regular hypervisors to UCA Folsom (previous libvirt). Sorry about the buzz (or a bit off-topic)... Best, Thiago On 7 April 2013 05:06, Sam Stoelinga sammiest...@gmail.com wrote: Checked this monning and there is no official 2013.1 out yet. Latest version is a built of 2013.1RC1. See http://ubuntu-cloud.archive.canonical.com/ubuntu/pool/main/n/nova/ Taken from packages file: Package: glance Version: 1:2013.1~rc1-0ubuntu2~cloud0 On Sun, Apr 7, 2013 at 12:34 PM, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: I just figured this out too... I think that Ubuntu Cloud Archive for Grizzly isn't ready for production yet... On 6 April 2013 23:28, Jason Ford ja...@chatinara.com wrote: Dave, Can you point to where the cloud archive has updated 2013.1 Grizzly packages for 12.04? I don't see it when I look at the packages listed here: http://ubuntu-cloud.archive.canonical.com Is there somewhere else we should be pointing to get the 2013.1 release instead of seeing the RC packages? If they are indeed not out yet, when will they be? Thanks! jason - Original Message - From: Daviey Walker dave.wal...@canonical.com To: Filipe Manco filipe.ma...@gmail.com Cc: openstack@lists.launchpad.net Sent: Saturday, April 6, 2013 4:16:42 PM Subject: Re: [Openstack] Grizzly official packages On 6 April 2013 19:56, Filipe Manco filipe.ma...@gmail.com wrote: Is there any way to use OpenStack Grizzly in Ubuntu 12.10? Can we use the cloud archive repos? Filipe Manco http://about.me/fmanco Hi Filipe, We have made Grizzly available in both the current Ubuntu development series, which is 13.04 (Raring Ringtail), and also made it available to the most recent LTS (Long Term Support) version which is 12.04 (Precise Pangolin), via the Ubuntu Cloud Archive. At this current time, there are not packages available for 12.10. Our focus is currently on the current development version, and the most recent LTS. May I ask what makes 12.10 interesting to you, for Grizzly? Thanks. -- Kind Regards, Dave Walker dave.wal...@canonical.com Engineering Manager, Ubuntu Server ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe
Re: [Openstack] Grizzly official packages
Oops... I was using from another example with same problem: %s/bank2-disk0_vorigin/raring-disk0_vorigin/ :-) On 7 April 2013 05:21, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: BTW, I used to add Ubuntu Cloud Archives (Folsom sub dir) to my regular hypervisors (only with KVM - no Nova, no OpenStack), to get new versions of libvirt and use it with virt-manager. But, now, with UCA for Grizzly, there a libvirt version 1.0.2 and, when I tried to create a LVM LV trough virt-manager (details - storage - lvm - new volume), I'm getting this: --- Logical volume --- LV Name/dev/vg01/raring-disk0 VG Namevg01 LV UUID LV Write Accessread/write *LV snapshot status active destination for /dev/vg01/raring-disk0_vorigin ???* LV Status available # open 0 LV SizeX.XX GiB Current LE 2500 COW-table size 4.00 MiB COW-table LE 1 Allocated to snapshot 0.20% Snapshot chunk size4.00 KiB Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 252:8 Instead of this (previous libvirt): --- Logical volume --- LV Name/dev/vg01/raring1-disk0 VG Namevg01 LV UUIDX LV Write Accessread/write LV Status available # open 0 LV SizeX.XX GiB Current LE 1250 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 252:7 The main problem is, after a system reboot and lots of failures, I'm getting this: --- Logical volume --- LV Name/dev/vg01/raring-disk0 VG Namevg01 LV UUIDXX LV Write Accessread/write *LV snapshot status INACTIVE destination for /dev/vg01/bank2-disk0_vorigin ??* LV Status NOT available LV Size5.86 GiB Current LE 1500 COW-table size 4.00 MiB COW-table LE 1 Snapshot chunk size4.00 KiB Segments 1 Allocation inherit Read ahead sectors auto LOGICAL VOLUME GONE!! VM CONTENTS LOST AFTER REBOOT! Maybe this is a problem only when using new libvirt 1.0.2 with virt-manager 0.9.3 from Ubuntu LTS, and it does not affect Grizzly... Don't know yet... Anyway, I'm just reporting it here to spread this info. Someone here knows how to fix this? I mean, probably the new libvirt is creating the LV as a broken snapshots instead of regular LV? If so, maybe I should ask on libvirt-users instead... I'm downgrading all my regular hypervisors to UCA Folsom (previous libvirt). Sorry about the buzz (or a bit off-topic)... Best, Thiago On 7 April 2013 05:06, Sam Stoelinga sammiest...@gmail.com wrote: Checked this monning and there is no official 2013.1 out yet. Latest version is a built of 2013.1RC1. See http://ubuntu-cloud.archive.canonical.com/ubuntu/pool/main/n/nova/ Taken from packages file: Package: glance Version: 1:2013.1~rc1-0ubuntu2~cloud0 On Sun, Apr 7, 2013 at 12:34 PM, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: I just figured this out too... I think that Ubuntu Cloud Archive for Grizzly isn't ready for production yet... On 6 April 2013 23:28, Jason Ford ja...@chatinara.com wrote: Dave, Can you point to where the cloud archive has updated 2013.1 Grizzly packages for 12.04? I don't see it when I look at the packages listed here: http://ubuntu-cloud.archive.canonical.com Is there somewhere else we should be pointing to get the 2013.1 release instead of seeing the RC packages? If they are indeed not out yet, when will they be? Thanks! jason - Original Message - From: Daviey Walker dave.wal...@canonical.com To: Filipe Manco filipe.ma...@gmail.com Cc: openstack@lists.launchpad.net Sent: Saturday, April 6, 2013 4:16:42 PM Subject: Re: [Openstack] Grizzly official packages On 6 April 2013 19:56, Filipe Manco filipe.ma...@gmail.com wrote: Is there any way to use OpenStack Grizzly in Ubuntu 12.10? Can we use the cloud archive repos? Filipe Manco http://about.me/fmanco Hi Filipe, We have made Grizzly available in both the current Ubuntu development series, which is 13.04 (Raring Ringtail), and also made it available to the most recent LTS (Long Term Support) version which is 12.04 (Precise Pangolin), via the Ubuntu Cloud Archive. At this current time, there are not packages available for 12.10. Our focus is currently on the current development version, and the most recent LTS. May I ask what makes 12.10 interesting to you, for Grizzly
Re: [Openstack] Grizzly official packages
Or Ubuntu 12.04 with Ubuntu Cloud Archive for Grizzly... But, not ready yet, I think... I'm installing it right now but, I'm still seeing some *rc* releases there... My /etc/apt/sources.list.d/uca-grizzly.list: --- # The primary updates archive that users should be using deb http://ubuntu-cloud.archive.canonical.com/ubuntuprecise-updates/grizzly main # deb-src http://ubuntu-cloud.archive.canonical.com/ubuntuprecise-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/ubuntuprecise-proposed/grizzly main # deb-src http://ubuntu-cloud.archive.canonical.com/ubuntuprecise-proposed/grizzly main --- On 7 April 2013 19:39, Filipe Manco filipe.ma...@gmail.com wrote: No big deal. Asked only because some of my test/development machines are running Ubuntu 12.10. Should have installed Ubuntu LTS. The way to go is upgrade to Ubuntu 13.04, right? Regards Filipe Manco http://about.me/fmanco 2013/4/6 Daviey Walker dave.wal...@canonical.com On 6 April 2013 19:56, Filipe Manco filipe.ma...@gmail.com wrote: Is there any way to use OpenStack Grizzly in Ubuntu 12.10? Can we use the cloud archive repos? Filipe Manco http://about.me/fmanco Hi Filipe, We have made Grizzly available in both the current Ubuntu development series, which is 13.04 (Raring Ringtail), and also made it available to the most recent LTS (Long Term Support) version which is 12.04 (Precise Pangolin), via the Ubuntu Cloud Archive. At this current time, there are not packages available for 12.10. Our focus is currently on the current development version, and the most recent LTS. May I ask what makes 12.10 interesting to you, for Grizzly? Thanks. -- Kind Regards, Dave Walker dave.wal...@canonical.com Engineering Manager, Ubuntu Server ___ 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] Grizzly official packages
I just figured this out too... I think that Ubuntu Cloud Archive for Grizzly isn't ready for production yet... On 6 April 2013 23:28, Jason Ford ja...@chatinara.com wrote: Dave, Can you point to where the cloud archive has updated 2013.1 Grizzly packages for 12.04? I don't see it when I look at the packages listed here: http://ubuntu-cloud.archive.canonical.com Is there somewhere else we should be pointing to get the 2013.1 release instead of seeing the RC packages? If they are indeed not out yet, when will they be? Thanks! jason - Original Message - From: Daviey Walker dave.wal...@canonical.com To: Filipe Manco filipe.ma...@gmail.com Cc: openstack@lists.launchpad.net Sent: Saturday, April 6, 2013 4:16:42 PM Subject: Re: [Openstack] Grizzly official packages On 6 April 2013 19:56, Filipe Manco filipe.ma...@gmail.com wrote: Is there any way to use OpenStack Grizzly in Ubuntu 12.10? Can we use the cloud archive repos? Filipe Manco http://about.me/fmanco Hi Filipe, We have made Grizzly available in both the current Ubuntu development series, which is 13.04 (Raring Ringtail), and also made it available to the most recent LTS (Long Term Support) version which is 12.04 (Precise Pangolin), via the Ubuntu Cloud Archive. At this current time, there are not packages available for 12.10. Our focus is currently on the current development version, and the most recent LTS. May I ask what makes 12.10 interesting to you, for Grizzly? Thanks. -- Kind Regards, Dave Walker dave.wal...@canonical.com Engineering Manager, Ubuntu Server ___ 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
Re: [Openstack] Dashboard gone - Internal Server Error
Ah! Okay! Tks!!! On 21 March 2013 02:43, Sandeep Raman sandeep.ra...@gmail.com wrote: Please remember the bug link i provided in another email. It seems to be a packaging bug. The Ubuntu theme with COMPRESS section disabled [per the bug response] works. I'm currently installing RC1 bits on Raring. I'll post back the experience with dashboard. On Thu, Mar 21, 2013 at 10:51 AM, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Oops! I just did: aptitude purge openstack-dashboard-ubuntu-theme #2013.1+git201303201651~precise-0ubuntu1 ..and the Internal Server Error message disapear... But, Dashboard still doesn't work... A new error page appear now: --- Something went wrong! An unexpected error has occurred. Try refreshing the page. If that doesn't help, contact your local administrator. Home http://10.32.14.232/ Help http://docs.openstack.org --- Apache2 error.log doesn't show anything more. Tks, Thiago On 20 March 2013 21:28, Martinx - ジェームズ thiagocmarti...@gmail.comwrote: Guys, Of of nothing, my Dashboard (1:2013.1+git201303201651~precise-0ubuntu1) gives Internal Server Error. Apache error.log contains: http://paste.openstack.org/show/34196/ I'm running: cd /usr/share/openstack-dashboard python manage.py compress service apache2 restart ...but the problem just sat here and don't go away. I'm using Ubuntu 12.04.2 with Grizzly G3+RC1 from PPA. Help! Tks, Thiago ___ 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] Dashboard gone - Internal Server Error
Tks Sandeep! But my Dashboard isn't working with `COMPRESS_OFFLINE = False'... With or without the Ubuntu theme... Anyway, I'll wait for new packages. Best, Thiago On 21 March 2013 06:46, Sandeep Raman sandeep.ra...@gmail.com wrote: With Ubuntu theme and COMPRESS_OFFLINE = False it works. With default theme and COMPRESS_OFFLINE = False it works, however the UI format is shabby because the tags {% compress js %} and {% endcompress %} is removed from _scripts.html. On Thu, Mar 21, 2013 at 11:28 AM, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Ah! Okay! Tks!!! On 21 March 2013 02:43, Sandeep Raman sandeep.ra...@gmail.com wrote: Please remember the bug link i provided in another email. It seems to be a packaging bug. The Ubuntu theme with COMPRESS section disabled [per the bug response] works. I'm currently installing RC1 bits on Raring. I'll post back the experience with dashboard. On Thu, Mar 21, 2013 at 10:51 AM, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Oops! I just did: aptitude purge openstack-dashboard-ubuntu-theme #2013.1+git201303201651~precise-0ubuntu1 ..and the Internal Server Error message disapear... But, Dashboard still doesn't work... A new error page appear now: --- Something went wrong! An unexpected error has occurred. Try refreshing the page. If that doesn't help, contact your local administrator. Home http://10.32.14.232/ Help http://docs.openstack.org --- Apache2 error.log doesn't show anything more. Tks, Thiago On 20 March 2013 21:28, Martinx - ジェームズ thiagocmarti...@gmail.comwrote: Guys, Of of nothing, my Dashboard (1:2013.1+git201303201651~precise-0ubuntu1) gives Internal Server Error. Apache error.log contains: http://paste.openstack.org/show/34196/ I'm running: cd /usr/share/openstack-dashboard python manage.py compress service apache2 restart ...but the problem just sat here and don't go away. I'm using Ubuntu 12.04.2 with Grizzly G3+RC1 from PPA. Help! Tks, Thiago ___ 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] Grizzly G3+RC1 - Quantum DHCP problem...
Guys, This problem still persist... I tried everything... Here is more error message from dhcp-agent.log: http://paste.openstack.org/show/34167/ I really need help to fix this... It is a fresh installation of Grizzly G3+RC1 from PPA, Ubuntu 12.04.2 64 bits... Tks! Thiago On 19 March 2013 20:09, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Guys, My /var/log/quantum/dhcp-agent.log file shows: 2013-03-19 20:04:48DEBUG [quantum.agent.linux.utils] Running command: ['sudo', 'ip', 'netns', 'exec', 'qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91', 'quantum-ns-metadata-proxy', '--pid_file=/var/lib/quantum/external/pids/21a39c11-03fd-4e2e-b7a0-94eee95f5f91.pid', '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91', '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug', '--verbose', '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log', '--log-dir=/var/log/quantum'] 2013-03-19 20:04:48DEBUG [quantum.agent.linux.utils] Command: ['sudo', 'ip', 'netns', 'exec', 'qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91', 'quantum-ns-metadata-proxy', '--pid_file=/var/lib/quantum/external/pids/21a39c11-03fd-4e2e-b7a0-94eee95f5f91.pid', '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91', '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug', '--verbose', '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log', '--log-dir=/var/log/quantum'] Exit code: 1 Stdout: '' Stderr: 'sudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: 3 incorrect password attempts\n' 2013-03-19 20:04:48ERROR [quantum.agent.dhcp_agent] Unable to sync network state. Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 154, in sync_state self.refresh_dhcp_helper(network_id) File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 208, in refresh_dhcp_helper return self.enable_dhcp_helper(network_id) File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 187, in enable_dhcp_helper self.enable_isolated_metadata_proxy(network) File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 321, in enable_isolated_metadata_proxy pm.enable(callback) File /usr/lib/python2.7/dist-packages/quantum/agent/linux/external_process.py, line 55, in enable ip_wrapper.netns.execute(cmd) File /usr/lib/python2.7/dist-packages/quantum/agent/linux/ip_lib.py, line 407, in execute check_exit_code=check_exit_code) File /usr/lib/python2.7/dist-packages/quantum/agent/linux/utils.py, line 61, in execute raise RuntimeError(m) RuntimeError: Command: ['sudo', 'ip', 'netns', 'exec', 'qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91', 'quantum-ns-metadata-proxy', '--pid_file=/var/lib/quantum/external/pids/21a39c11-03fd-4e2e-b7a0-94eee95f5f91.pid', '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91', '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug', '--verbose', '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log', '--log-dir=/var/log/quantum'] Exit code: 1 Stdout: '' Stderr: 'sudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: 3 incorrect password attempts\n' Tips? It is a fresh installation to test Grizzly... I'm not using GRE or L3, only Quantum Single FLAT... With Folsom and previous Grizzly my Quantum was fine... quantum-dhcp-agent 1:2013.1+git201303190501~precise-0ubuntu1 Tks, Thiago ___ 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 G3+RC1 - Quantum DHCP problem...
Leandro! My /etc/sudoers: --- # # This file MUST be edited with the 'visudo' command as root. # # Please consider adding local content in /etc/sudoers.d/ instead of # directly modifying this file. # # See the man page for details on how to write a sudoers file. # Defaults env_reset Defaults secure_path=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin # Host alias specification # User alias specification # Cmnd alias specification # User privilege specification root ALL=(ALL:ALL) ALL # Members of the admin group may gain root privileges %admin ALL=(ALL) ALL # Allow members of group sudo to execute any command %sudo ALL=(ALL:ALL) ALL # See sudoers(5) for more information on #include directives: #includedir /etc/sudoers.d --- My /etc/sudoers.d/cinder_sudoers --- Defaults:cinder !requiretty cinder ALL = (root) NOPASSWD: /usr/bin/cinder-rootwrap --- My /etc/sudoers.d/nova_sudoers --- Defaults:nova !requiretty nova ALL = (root) NOPASSWD: /usr/bin/nova-rootwrap --- My /etc/sudoers.d/quantum_sudoers --- Defaults:quantum !requiretty quantum ALL = (root) NOPASSWD: /usr/bin/quantum-rootwrap --- Tks, Thiago On 20 March 2013 15:41, Leandro Reox leandro.r...@mercadolibre.com wrote: Please paste all your sudoers files ** * * *Leandro Reox * *#melicloud CloudBuilders* *Arias 3751, Piso 7 (C1430CRG) * *Ciudad de Buenos Aires - Argentina* *Cel: +549(11) 15-3770-1938* *Tel : +54(11) 4640-8726* On Wed, Mar 20, 2013 at 3:35 PM, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Guys, This problem still persist... I tried everything... Here is more error message from dhcp-agent.log: http://paste.openstack.org/show/34167/ I really need help to fix this... It is a fresh installation of Grizzly G3+RC1 from PPA, Ubuntu 12.04.2 64 bits... Tks! Thiago On 19 March 2013 20:09, Martinx - ジェームズ thiagocmarti...@gmail.comwrote: Guys, My /var/log/quantum/dhcp-agent.log file shows: 2013-03-19 20:04:48DEBUG [quantum.agent.linux.utils] Running command: ['sudo', 'ip', 'netns', 'exec', 'qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91', 'quantum-ns-metadata-proxy', '--pid_file=/var/lib/quantum/external/pids/21a39c11-03fd-4e2e-b7a0-94eee95f5f91.pid', '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91', '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug', '--verbose', '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log', '--log-dir=/var/log/quantum'] 2013-03-19 20:04:48DEBUG [quantum.agent.linux.utils] Command: ['sudo', 'ip', 'netns', 'exec', 'qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91', 'quantum-ns-metadata-proxy', '--pid_file=/var/lib/quantum/external/pids/21a39c11-03fd-4e2e-b7a0-94eee95f5f91.pid', '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91', '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug', '--verbose', '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log', '--log-dir=/var/log/quantum'] Exit code: 1 Stdout: '' Stderr: 'sudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: 3 incorrect password attempts\n' 2013-03-19 20:04:48ERROR [quantum.agent.dhcp_agent] Unable to sync network state. Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 154, in sync_state self.refresh_dhcp_helper(network_id) File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 208, in refresh_dhcp_helper return self.enable_dhcp_helper(network_id) File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 187, in enable_dhcp_helper self.enable_isolated_metadata_proxy(network) File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 321, in enable_isolated_metadata_proxy pm.enable(callback) File /usr/lib/python2.7/dist-packages/quantum/agent/linux/external_process.py, line 55, in enable ip_wrapper.netns.execute(cmd) File /usr/lib/python2.7/dist-packages/quantum/agent/linux/ip_lib.py, line 407, in execute check_exit_code=check_exit_code) File /usr/lib/python2.7/dist-packages/quantum/agent/linux/utils.py, line 61, in execute raise RuntimeError(m) RuntimeError: Command: ['sudo', 'ip', 'netns', 'exec', 'qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91', 'quantum-ns-metadata-proxy', '--pid_file=/var/lib/quantum/external/pids/21a39c11-03fd-4e2e-b7a0-94eee95f5f91.pid', '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91', '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug', '--verbose', '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log', '--log-dir=/var/log/quantum'] Exit code: 1 Stdout: '' Stderr: 'sudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass
Re: [Openstack] On Grizzly PPA testing, the package nova-novncproxy conflicts with novnc
Guys, The nova-novncproxy `1:2013.1+git201303201334~precise-0ubuntu1' still conflicts with `novnc_2012.1~e3+dfsg+1-2_amd64.deb'. I'm trying Grizzly from PPA on top of Ubuntu 12.04.2. Look (trying to install novnc): --- Unpacking novnc (from .../novnc_2012.1~e3+dfsg+1-2_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/novnc_2012.1~e3+dfsg+1-2_amd64.deb (--unpack): trying to overwrite '/usr/bin/nova-novncproxy', which is also in package nova-novncproxy 1:2013.1+git201303201334~precise-0ubuntu1 No apport report written because MaxReports is reached already Processing triggers for ureadahead ... Errors were encountered while processing: /var/cache/apt/archives/novnc_2012.1~e3+dfsg+1-2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) --- VNC consoles are down. Tips?! Tks, Thiago On 19 March 2013 19:50, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Guys, Witn Folsom and previos Grizzly, I was using the following command to install Nova: aptitude install nova-api nova-cert novnc nova-consoleauth nova-scheduler nova-novncproxy But today, on my fresh Grizzly G3+RC1 install, I'm getting: root@controller:~# aptitude install nova-novncproxy The following NEW packages will be installed: nova-novncproxy 0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/2,401 kB of archives. After unpacking 2,456 kB will be used. Selecting previously unselected package nova-novncproxy. (Reading database ... 77462 files and directories currently installed.) Unpacking nova-novncproxy (from .../nova-novncproxy_1%3a2013.1+git201303191310~precise-0ubuntu1_all.deb) ... dpkg: error processing /var/cache/apt/archives/nova-novncproxy_1%3a2013.1+git201303191310~precise-0ubuntu1_all.deb (--unpack): trying to overwrite '/usr/bin/nova-novncproxy', which is also in package novnc 2012.1~e3+dfsg+1-2 No apport report written because MaxReports is reached already Processing triggers for ureadahead ... Errors were encountered while processing: /var/cache/apt/archives/nova-novncproxy_1%3a2013.1+git201303191310~precise-0ubuntu1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: [ 0%] Reading package lists The VNC isn't working via Dashboard... Nothing listening on port controller:6080... Tips?! Thanks! Thiago ___ 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] ANNOUNCE: Ultimate OpenStack Grizzly Guide, with super easy Quantum!
Hi! I'm working with Grizzly G3+RC1 on top of Ubuntu 12.04.2 and here is the guide I wrote: Ultimate OpenStack Grizzly Guidehttps://gist.github.com/tmartinx/d36536b7b62a48f859c2 It covers: * Ubuntu 12.04.2 * Basic Ubuntu setup * KVM * OpenvSwitch * Name Resolution for OpenStack components; * LVM for Instances * Keystone * Glance * Quantum - Single Flat, Super Green!! * Nova * Cinder / tgt * Dashboard It is still a draft but, every time I deploy Ubuntu and Grizzly, I follow this little guide... I would like some help to improve this guide... If I'm doing something wrong, tell me! Please! Probably I'm doing something wrong, I don't know yet, but I'm seeing some errors on the logs, already reported here on this list. Like for example: nova-novncproxy conflicts with novnc (no VNC console for now), dhcp-agent.log / auth.log points to some problems with `sudo' or the `rootwarp' subsystem when dealing with metadata (so it isn't working)... But in general, it works great!! Best! Thiago ___ 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] ANNOUNCE: Ultimate OpenStack Grizzly Guide, with super easy Quantum!
1 problem fixed with: visudo --- quantum ALL=NOPASSWD: ALL cinder ALL=NOPASSWD: ALL nova ALL=NOPASSWD: ALL --- Guide updated... On 20 March 2013 19:51, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Hi! I'm working with Grizzly G3+RC1 on top of Ubuntu 12.04.2 and here is the guide I wrote: Ultimate OpenStack Grizzly Guidehttps://gist.github.com/tmartinx/d36536b7b62a48f859c2 It covers: * Ubuntu 12.04.2 * Basic Ubuntu setup * KVM * OpenvSwitch * Name Resolution for OpenStack components; * LVM for Instances * Keystone * Glance * Quantum - Single Flat, Super Green!! * Nova * Cinder / tgt * Dashboard It is still a draft but, every time I deploy Ubuntu and Grizzly, I follow this little guide... I would like some help to improve this guide... If I'm doing something wrong, tell me! Please! Probably I'm doing something wrong, I don't know yet, but I'm seeing some errors on the logs, already reported here on this list. Like for example: nova-novncproxy conflicts with novnc (no VNC console for now), dhcp-agent.log / auth.log points to some problems with `sudo' or the `rootwarp' subsystem when dealing with metadata (so it isn't working)... But in general, it works great!! Best! Thiago ___ 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] Dashboard gone - Internal Server Error
Guys, Of of nothing, my Dashboard (1:2013.1+git201303201651~precise-0ubuntu1) gives Internal Server Error. Apache error.log contains: http://paste.openstack.org/show/34196/ I'm running: cd /usr/share/openstack-dashboard python manage.py compress service apache2 restart ...but the problem just sat here and don't go away. I'm using Ubuntu 12.04.2 with Grizzly G3+RC1 from PPA. Help! Tks, Thiago ___ 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 gone - Internal Server Error
Oops! I just did: aptitude purge openstack-dashboard-ubuntu-theme #2013.1+git201303201651~precise-0ubuntu1 ..and the Internal Server Error message disapear... But, Dashboard still doesn't work... A new error page appear now: --- Something went wrong! An unexpected error has occurred. Try refreshing the page. If that doesn't help, contact your local administrator. Home http://10.32.14.232/ Help http://docs.openstack.org --- Apache2 error.log doesn't show anything more. Tks, Thiago On 20 March 2013 21:28, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Guys, Of of nothing, my Dashboard (1:2013.1+git201303201651~precise-0ubuntu1) gives Internal Server Error. Apache error.log contains: http://paste.openstack.org/show/34196/ I'm running: cd /usr/share/openstack-dashboard python manage.py compress service apache2 restart ...but the problem just sat here and don't go away. I'm using Ubuntu 12.04.2 with Grizzly G3+RC1 from PPA. Help! Tks, Thiago ___ 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 openstack-dashboard installation / upgrade problem
Awesome Sandeep! Thank you! BTW, just to make sure, Dashboard now depends on the `node-less / nodejs' Ubuntu packages? - Thiago On 19 March 2013 04:34, Sandeep Raman sandeep.ra...@gmail.com wrote: Check my last comment - https://bugs.launchpad.net/horizon/+bug/1143897 On Tue, Mar 19, 2013 at 11:06 AM, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: BTW, I'm using openstack-dashboard 1:2013.1+git201303182101~precise-0ubuntu1... =P On 19 March 2013 02:27, Martinx - ジェームズ thiagocmarti...@gmail.comwrote: Hi! Everytime I install or upgrade the Ubuntu packages `openstack-dashboard / openstack-dashboard-ubuntu-theme', I must run the following commands before being able to use the Dashboard: cd /usr/share/openstack-dashboard/ python manage.py compress Otherwise, I get Internal Server Error after login and some erros on Apache error.log file, like this: [Tue Mar 19 04:08:28 2013] [error] [client 192.168.15.136] File /usr/lib/python2.7/dist-packages/compressor/templatetags/compress.py, line 72, in render_offline, referer: http://cloud.quilombas.com/horizon [Tue Mar 19 04:08:28 2013] [error] [client 192.168.15.136] 'You may need to run python manage.py compress.' % key), referer: http://10.32.14.232/horizon [Tue Mar 19 04:08:28 2013] [error] [client 192.168.15.136] OfflineGenerationError: You have offline compression enabled but key 5c40b85be56c93c77e8d169e635c9beb is missing from offline manifest. You may need to run python manage.py compress., referer: http://10.32.14.232/horizon I believe that the Ubuntu/Debian post-install script can handle this, right? Best, Thiago ___ 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
[Openstack] On Grizzly PPA testing, the package nova-novncproxy conflicts with novnc
Guys, Witn Folsom and previos Grizzly, I was using the following command to install Nova: aptitude install nova-api nova-cert novnc nova-consoleauth nova-scheduler nova-novncproxy But today, on my fresh Grizzly G3+RC1 install, I'm getting: root@controller:~# aptitude install nova-novncproxy The following NEW packages will be installed: nova-novncproxy 0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/2,401 kB of archives. After unpacking 2,456 kB will be used. Selecting previously unselected package nova-novncproxy. (Reading database ... 77462 files and directories currently installed.) Unpacking nova-novncproxy (from .../nova-novncproxy_1%3a2013.1+git201303191310~precise-0ubuntu1_all.deb) ... dpkg: error processing /var/cache/apt/archives/nova-novncproxy_1%3a2013.1+git201303191310~precise-0ubuntu1_all.deb (--unpack): trying to overwrite '/usr/bin/nova-novncproxy', which is also in package novnc 2012.1~e3+dfsg+1-2 No apport report written because MaxReports is reached already Processing triggers for ureadahead ... Errors were encountered while processing: /var/cache/apt/archives/nova-novncproxy_1%3a2013.1+git201303191310~precise-0ubuntu1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: [ 0%] Reading package lists The VNC isn't working via Dashboard... Nothing listening on port controller:6080... Tips?! Thanks! Thiago ___ 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] Grizzly G3+RC1 - Quantum DHCP problem...
Guys, My /var/log/quantum/dhcp-agent.log file shows: 2013-03-19 20:04:48DEBUG [quantum.agent.linux.utils] Running command: ['sudo', 'ip', 'netns', 'exec', 'qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91', 'quantum-ns-metadata-proxy', '--pid_file=/var/lib/quantum/external/pids/21a39c11-03fd-4e2e-b7a0-94eee95f5f91.pid', '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91', '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug', '--verbose', '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log', '--log-dir=/var/log/quantum'] 2013-03-19 20:04:48DEBUG [quantum.agent.linux.utils] Command: ['sudo', 'ip', 'netns', 'exec', 'qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91', 'quantum-ns-metadata-proxy', '--pid_file=/var/lib/quantum/external/pids/21a39c11-03fd-4e2e-b7a0-94eee95f5f91.pid', '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91', '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug', '--verbose', '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log', '--log-dir=/var/log/quantum'] Exit code: 1 Stdout: '' Stderr: 'sudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: 3 incorrect password attempts\n' 2013-03-19 20:04:48ERROR [quantum.agent.dhcp_agent] Unable to sync network state. Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 154, in sync_state self.refresh_dhcp_helper(network_id) File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 208, in refresh_dhcp_helper return self.enable_dhcp_helper(network_id) File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 187, in enable_dhcp_helper self.enable_isolated_metadata_proxy(network) File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 321, in enable_isolated_metadata_proxy pm.enable(callback) File /usr/lib/python2.7/dist-packages/quantum/agent/linux/external_process.py, line 55, in enable ip_wrapper.netns.execute(cmd) File /usr/lib/python2.7/dist-packages/quantum/agent/linux/ip_lib.py, line 407, in execute check_exit_code=check_exit_code) File /usr/lib/python2.7/dist-packages/quantum/agent/linux/utils.py, line 61, in execute raise RuntimeError(m) RuntimeError: Command: ['sudo', 'ip', 'netns', 'exec', 'qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91', 'quantum-ns-metadata-proxy', '--pid_file=/var/lib/quantum/external/pids/21a39c11-03fd-4e2e-b7a0-94eee95f5f91.pid', '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91', '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug', '--verbose', '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log', '--log-dir=/var/log/quantum'] Exit code: 1 Stdout: '' Stderr: 'sudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: 3 incorrect password attempts\n' Tips? It is a fresh installation to test Grizzly... I'm not using GRE or L3, only Quantum Single FLAT... With Folsom and previous Grizzly my Quantum was fine... quantum-dhcp-agent 1:2013.1+git201303190501~precise-0ubuntu1 Tks, Thiago ___ 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 G3+RC1 - Quantum DHCP problem...
After disabling namespaces, with: `allow_overlapping_ips = False' in quantum.conf and with: `use_namespaces = False' in /etc/quantum/dhcp_agent.ini The previous error message dissapear but, My Instance isn't getting its IP via DHCP now... Weird thing is that it was working couple minutes ago, without disabling namespaces explicitly... If I add the Instance IP by hand, I can reach the Internet / gateway from it. I'm finishing my Grizzly Quantum Single Flat PoC environment, planning to publish a nice guide soon! I appreciate any help! Tks! Thiago On 19 March 2013 20:09, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Guys, My /var/log/quantum/dhcp-agent.log file shows: 2013-03-19 20:04:48DEBUG [quantum.agent.linux.utils] Running command: ['sudo', 'ip', 'netns', 'exec', 'qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91', 'quantum-ns-metadata-proxy', '--pid_file=/var/lib/quantum/external/pids/21a39c11-03fd-4e2e-b7a0-94eee95f5f91.pid', '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91', '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug', '--verbose', '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log', '--log-dir=/var/log/quantum'] 2013-03-19 20:04:48DEBUG [quantum.agent.linux.utils] Command: ['sudo', 'ip', 'netns', 'exec', 'qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91', 'quantum-ns-metadata-proxy', '--pid_file=/var/lib/quantum/external/pids/21a39c11-03fd-4e2e-b7a0-94eee95f5f91.pid', '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91', '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug', '--verbose', '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log', '--log-dir=/var/log/quantum'] Exit code: 1 Stdout: '' Stderr: 'sudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: 3 incorrect password attempts\n' 2013-03-19 20:04:48ERROR [quantum.agent.dhcp_agent] Unable to sync network state. Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 154, in sync_state self.refresh_dhcp_helper(network_id) File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 208, in refresh_dhcp_helper return self.enable_dhcp_helper(network_id) File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 187, in enable_dhcp_helper self.enable_isolated_metadata_proxy(network) File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 321, in enable_isolated_metadata_proxy pm.enable(callback) File /usr/lib/python2.7/dist-packages/quantum/agent/linux/external_process.py, line 55, in enable ip_wrapper.netns.execute(cmd) File /usr/lib/python2.7/dist-packages/quantum/agent/linux/ip_lib.py, line 407, in execute check_exit_code=check_exit_code) File /usr/lib/python2.7/dist-packages/quantum/agent/linux/utils.py, line 61, in execute raise RuntimeError(m) RuntimeError: Command: ['sudo', 'ip', 'netns', 'exec', 'qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91', 'quantum-ns-metadata-proxy', '--pid_file=/var/lib/quantum/external/pids/21a39c11-03fd-4e2e-b7a0-94eee95f5f91.pid', '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91', '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug', '--verbose', '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log', '--log-dir=/var/log/quantum'] Exit code: 1 Stdout: '' Stderr: 'sudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: 3 incorrect password attempts\n' Tips? It is a fresh installation to test Grizzly... I'm not using GRE or L3, only Quantum Single FLAT... With Folsom and previous Grizzly my Quantum was fine... quantum-dhcp-agent 1:2013.1+git201303190501~precise-0ubuntu1 Tks, Thiago ___ 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 G3+RC1 - Quantum DHCP problem...
Also, my compute quantum node shows: /var/log/quantum/openvswitch-agent.log: Exit code: 242 Stdout: '' Stderr: '' 2013-03-19 20:25:31ERROR [quantum.agent.linux.ovs_lib] Unable to execute ['ovs-vsctl', '--timeout=2', 'list-ports', 'br-int']. Exception: Command: ['sudo', 'quantum-rootwrap', '/etc/quantum/rootwrap.conf', 'ovs-vsctl', '--timeout=2', 'list-ports', 'br-int'] Exit code: 242 Stdout: '' Stderr: '' Don't know how to fix it... Tks, Thiago On 19 March 2013 20:35, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: After disabling namespaces, with: `allow_overlapping_ips = False' in quantum.conf and with: `use_namespaces = False' in /etc/quantum/dhcp_agent.ini The previous error message dissapear but, My Instance isn't getting its IP via DHCP now... Weird thing is that it was working couple minutes ago, without disabling namespaces explicitly... If I add the Instance IP by hand, I can reach the Internet / gateway from it. I'm finishing my Grizzly Quantum Single Flat PoC environment, planning to publish a nice guide soon! I appreciate any help! Tks! Thiago On 19 March 2013 20:09, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Guys, My /var/log/quantum/dhcp-agent.log file shows: 2013-03-19 20:04:48DEBUG [quantum.agent.linux.utils] Running command: ['sudo', 'ip', 'netns', 'exec', 'qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91', 'quantum-ns-metadata-proxy', '--pid_file=/var/lib/quantum/external/pids/21a39c11-03fd-4e2e-b7a0-94eee95f5f91.pid', '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91', '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug', '--verbose', '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log', '--log-dir=/var/log/quantum'] 2013-03-19 20:04:48DEBUG [quantum.agent.linux.utils] Command: ['sudo', 'ip', 'netns', 'exec', 'qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91', 'quantum-ns-metadata-proxy', '--pid_file=/var/lib/quantum/external/pids/21a39c11-03fd-4e2e-b7a0-94eee95f5f91.pid', '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91', '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug', '--verbose', '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log', '--log-dir=/var/log/quantum'] Exit code: 1 Stdout: '' Stderr: 'sudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: 3 incorrect password attempts\n' 2013-03-19 20:04:48ERROR [quantum.agent.dhcp_agent] Unable to sync network state. Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 154, in sync_state self.refresh_dhcp_helper(network_id) File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 208, in refresh_dhcp_helper return self.enable_dhcp_helper(network_id) File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 187, in enable_dhcp_helper self.enable_isolated_metadata_proxy(network) File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 321, in enable_isolated_metadata_proxy pm.enable(callback) File /usr/lib/python2.7/dist-packages/quantum/agent/linux/external_process.py, line 55, in enable ip_wrapper.netns.execute(cmd) File /usr/lib/python2.7/dist-packages/quantum/agent/linux/ip_lib.py, line 407, in execute check_exit_code=check_exit_code) File /usr/lib/python2.7/dist-packages/quantum/agent/linux/utils.py, line 61, in execute raise RuntimeError(m) RuntimeError: Command: ['sudo', 'ip', 'netns', 'exec', 'qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91', 'quantum-ns-metadata-proxy', '--pid_file=/var/lib/quantum/external/pids/21a39c11-03fd-4e2e-b7a0-94eee95f5f91.pid', '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91', '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug', '--verbose', '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log', '--log-dir=/var/log/quantum'] Exit code: 1 Stdout: '' Stderr: 'sudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: 3 incorrect password attempts\n' Tips? It is a fresh installation to test Grizzly... I'm not using GRE or L3, only Quantum Single FLAT... With Folsom and previous Grizzly my Quantum was fine... quantum-dhcp-agent 1:2013.1+git201303190501~precise-0ubuntu1 Tks, Thiago ___ 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] Error: Unable to retrieve list of security groups
Hi! I'm trying Grizzly G3+RC1 via PPA with Ubuntu 12.04... I'll use Quantum Single Flat network, since it is working with my Folsom (less metadata). When I click on Launch a Image, Dashboard shows: Error: Unable to retrieve list of security groups The nova-api.log server log shows: http://paste.openstack.org/show/34114/ Sorry to flood you guys, I'm trying Grizzly here alone in my lab... :-P I'll restore the OpenStack Ubuntu package configuration files to start it over... Tks, Thiago ___ 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 G3+RC1 - Quantum DHCP problem...
Hi! I just rollback to the default namespace options, my Instance now get its IP without problem. But, the message from my first e-mail on this thread, still persist... I tried to enable quantum metadata proxy stuff but, nothing changes... The following error keeps rolling at my /var/log/quantum/dhcp-agent.log: --- ... Command: ['sudo', 'ip', 'netns', 'exec', 'qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91', 'quantum-ns-metadata-proxy', '--pid_file=/var/lib/quantum/external/pids/21a39c11-03fd-4e2e-b7a0-94eee95f5f91.pid', '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91', '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug', '--verbose', '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log', '--log-dir=/var/log/quantum'] Exit code: 1 Stdout: '' Stderr: 'sudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: 3 incorrect password attempts\n' --- I tried everything I could... But this message persist... The namespaces are enabled, look: ip netns exec qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91 ip r 10.33.14.0/24 dev tapeb27823a-5e proto kernel scope link src 10.33.14.2 What can I do? Tks, Thiago On 19 March 2013 20:35, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: After disabling namespaces, with: `allow_overlapping_ips = False' in quantum.conf and with: `use_namespaces = False' in /etc/quantum/dhcp_agent.ini The previous error message dissapear but, My Instance isn't getting its IP via DHCP now... Weird thing is that it was working couple minutes ago, without disabling namespaces explicitly... If I add the Instance IP by hand, I can reach the Internet / gateway from it. I'm finishing my Grizzly Quantum Single Flat PoC environment, planning to publish a nice guide soon! I appreciate any help! Tks! Thiago On 19 March 2013 20:09, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Guys, My /var/log/quantum/dhcp-agent.log file shows: 2013-03-19 20:04:48DEBUG [quantum.agent.linux.utils] Running command: ['sudo', 'ip', 'netns', 'exec', 'qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91', 'quantum-ns-metadata-proxy', '--pid_file=/var/lib/quantum/external/pids/21a39c11-03fd-4e2e-b7a0-94eee95f5f91.pid', '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91', '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug', '--verbose', '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log', '--log-dir=/var/log/quantum'] 2013-03-19 20:04:48DEBUG [quantum.agent.linux.utils] Command: ['sudo', 'ip', 'netns', 'exec', 'qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91', 'quantum-ns-metadata-proxy', '--pid_file=/var/lib/quantum/external/pids/21a39c11-03fd-4e2e-b7a0-94eee95f5f91.pid', '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91', '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug', '--verbose', '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log', '--log-dir=/var/log/quantum'] Exit code: 1 Stdout: '' Stderr: 'sudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: 3 incorrect password attempts\n' 2013-03-19 20:04:48ERROR [quantum.agent.dhcp_agent] Unable to sync network state. Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 154, in sync_state self.refresh_dhcp_helper(network_id) File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 208, in refresh_dhcp_helper return self.enable_dhcp_helper(network_id) File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 187, in enable_dhcp_helper self.enable_isolated_metadata_proxy(network) File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 321, in enable_isolated_metadata_proxy pm.enable(callback) File /usr/lib/python2.7/dist-packages/quantum/agent/linux/external_process.py, line 55, in enable ip_wrapper.netns.execute(cmd) File /usr/lib/python2.7/dist-packages/quantum/agent/linux/ip_lib.py, line 407, in execute check_exit_code=check_exit_code) File /usr/lib/python2.7/dist-packages/quantum/agent/linux/utils.py, line 61, in execute raise RuntimeError(m) RuntimeError: Command: ['sudo', 'ip', 'netns', 'exec', 'qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91', 'quantum-ns-metadata-proxy', '--pid_file=/var/lib/quantum/external/pids/21a39c11-03fd-4e2e-b7a0-94eee95f5f91.pid', '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91', '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug', '--verbose', '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log', '--log-dir=/var
Re: [Openstack] Error: Unable to retrieve list of security groups
Never mind... lol I enabled by accident the following option in nova.conf: `security_group_api = quantum' Message gone. Sorry about the buzz... - Thiago On 19 March 2013 22:19, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Hi! I'm trying Grizzly G3+RC1 via PPA with Ubuntu 12.04... I'll use Quantum Single Flat network, since it is working with my Folsom (less metadata). When I click on Launch a Image, Dashboard shows: Error: Unable to retrieve list of security groups The nova-api.log server log shows: http://paste.openstack.org/show/34114/ Sorry to flood you guys, I'm trying Grizzly here alone in my lab... :-P I'll restore the OpenStack Ubuntu package configuration files to start it over... Tks, Thiago ___ 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 G3+RC1 - Quantum DHCP problem...
My /etc/sudoers.d/nova_sudoers contains: -- Defaults:nova !requiretty nova ALL = (root) NOPASSWD: /usr/bin/nova-rootwrap -- Do I need to change it? Tks! Thiago On 19 March 2013 22:46, gong yong sheng gong...@linux.vnet.ibm.com wrote: It seems be about sudo. to create one sudo file under /etc/sudoers.d mine is: nova_sudoers: Defaults:gongysh !requiretty gongysh ALL = (ALL) NOPASSWD: ALL On 03/20/2013 09:37 AM, Martinx - ジェームズ wrote: Hi! I just rollback to the default namespace options, my Instance now get its IP without problem. But, the message from my first e-mail on this thread, still persist... I tried to enable quantum metadata proxy stuff but, nothing changes... The following error keeps rolling at my /var/log/quantum/dhcp-agent.log: --- ... Command: ['sudo', 'ip', 'netns', 'exec', 'qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91', 'quantum-ns-metadata-proxy', '--pid_file=/var/lib/quantum/external/pids/21a39c11-03fd-4e2e-b7a0-94eee95f5f91.pid', '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91', '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug', '--verbose', '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log', '--log-dir=/var/log/quantum'] Exit code: 1 Stdout: '' Stderr: 'sudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: 3 incorrect password attempts\n' --- I tried everything I could... But this message persist... The namespaces are enabled, look: ip netns exec qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91 ip r 10.33.14.0/24 dev tapeb27823a-5e proto kernel scope link src 10.33.14.2 What can I do? Tks, Thiago On 19 March 2013 20:35, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: After disabling namespaces, with: `allow_overlapping_ips = False' in quantum.conf and with: `use_namespaces = False' in /etc/quantum/dhcp_agent.ini The previous error message dissapear but, My Instance isn't getting its IP via DHCP now... Weird thing is that it was working couple minutes ago, without disabling namespaces explicitly... If I add the Instance IP by hand, I can reach the Internet / gateway from it. I'm finishing my Grizzly Quantum Single Flat PoC environment, planning to publish a nice guide soon! I appreciate any help! Tks! Thiago On 19 March 2013 20:09, Martinx - ジェームズ thiagocmarti...@gmail.comwrote: Guys, My /var/log/quantum/dhcp-agent.log file shows: 2013-03-19 20:04:48DEBUG [quantum.agent.linux.utils] Running command: ['sudo', 'ip', 'netns', 'exec', 'qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91', 'quantum-ns-metadata-proxy', '--pid_file=/var/lib/quantum/external/pids/21a39c11-03fd-4e2e-b7a0-94eee95f5f91.pid', '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91', '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug', '--verbose', '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log', '--log-dir=/var/log/quantum'] 2013-03-19 20:04:48DEBUG [quantum.agent.linux.utils] Command: ['sudo', 'ip', 'netns', 'exec', 'qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91', 'quantum-ns-metadata-proxy', '--pid_file=/var/lib/quantum/external/pids/21a39c11-03fd-4e2e-b7a0-94eee95f5f91.pid', '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91', '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug', '--verbose', '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log', '--log-dir=/var/log/quantum'] Exit code: 1 Stdout: '' Stderr: 'sudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: 3 incorrect password attempts\n' 2013-03-19 20:04:48ERROR [quantum.agent.dhcp_agent] Unable to sync network state. Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 154, in sync_state self.refresh_dhcp_helper(network_id) File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 208, in refresh_dhcp_helper return self.enable_dhcp_helper(network_id) File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 187, in enable_dhcp_helper self.enable_isolated_metadata_proxy(network) File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 321, in enable_isolated_metadata_proxy pm.enable(callback) File /usr/lib/python2.7/dist-packages/quantum/agent/linux/external_process.py, line 55, in enable ip_wrapper.netns.execute(cmd) File /usr/lib/python2.7/dist-packages/quantum/agent/linux/ip_lib.py, line 407, in execute check_exit_code=check_exit_code) File /usr/lib/python2.7/dist-packages/quantum/agent/linux
Re: [Openstack] Grizzly G3+RC1 - Quantum DHCP problem...
User quantum running `python /usr/bin/quantum-dhcp-agent'... On 19 March 2013 22:55, gong yong sheng gong...@linux.vnet.ibm.com wrote: that depends what user is running the dhcp agent. On 03/20/2013 09:52 AM, Martinx - ジェームズ wrote: My /etc/sudoers.d/nova_sudoers contains: -- Defaults:nova !requiretty nova ALL = (root) NOPASSWD: /usr/bin/nova-rootwrap -- Do I need to change it? Tks! Thiago On 19 March 2013 22:46, gong yong sheng gong...@linux.vnet.ibm.comwrote: It seems be about sudo. to create one sudo file under /etc/sudoers.d mine is: nova_sudoers: Defaults:gongysh !requiretty gongysh ALL = (ALL) NOPASSWD: ALL On 03/20/2013 09:37 AM, Martinx - ジェームズ wrote: Hi! I just rollback to the default namespace options, my Instance now get its IP without problem. But, the message from my first e-mail on this thread, still persist... I tried to enable quantum metadata proxy stuff but, nothing changes... The following error keeps rolling at my /var/log/quantum/dhcp-agent.log: --- ... Command: ['sudo', 'ip', 'netns', 'exec', 'qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91', 'quantum-ns-metadata-proxy', '--pid_file=/var/lib/quantum/external/pids/21a39c11-03fd-4e2e-b7a0-94eee95f5f91.pid', '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91', '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug', '--verbose', '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log', '--log-dir=/var/log/quantum'] Exit code: 1 Stdout: '' Stderr: 'sudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: 3 incorrect password attempts\n' --- I tried everything I could... But this message persist... The namespaces are enabled, look: ip netns exec qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91 ip r 10.33.14.0/24 dev tapeb27823a-5e proto kernel scope link src 10.33.14.2 What can I do? Tks, Thiago On 19 March 2013 20:35, Martinx - ジェームズ thiagocmarti...@gmail.comwrote: After disabling namespaces, with: `allow_overlapping_ips = False' in quantum.conf and with: `use_namespaces = False' in /etc/quantum/dhcp_agent.ini The previous error message dissapear but, My Instance isn't getting its IP via DHCP now... Weird thing is that it was working couple minutes ago, without disabling namespaces explicitly... If I add the Instance IP by hand, I can reach the Internet / gateway from it. I'm finishing my Grizzly Quantum Single Flat PoC environment, planning to publish a nice guide soon! I appreciate any help! Tks! Thiago On 19 March 2013 20:09, Martinx - ジェームズ thiagocmarti...@gmail.comwrote: Guys, My /var/log/quantum/dhcp-agent.log file shows: 2013-03-19 20:04:48DEBUG [quantum.agent.linux.utils] Running command: ['sudo', 'ip', 'netns', 'exec', 'qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91', 'quantum-ns-metadata-proxy', '--pid_file=/var/lib/quantum/external/pids/21a39c11-03fd-4e2e-b7a0-94eee95f5f91.pid', '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91', '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug', '--verbose', '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log', '--log-dir=/var/log/quantum'] 2013-03-19 20:04:48DEBUG [quantum.agent.linux.utils] Command: ['sudo', 'ip', 'netns', 'exec', 'qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91', 'quantum-ns-metadata-proxy', '--pid_file=/var/lib/quantum/external/pids/21a39c11-03fd-4e2e-b7a0-94eee95f5f91.pid', '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91', '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug', '--verbose', '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log', '--log-dir=/var/log/quantum'] Exit code: 1 Stdout: '' Stderr: 'sudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: 3 incorrect password attempts\n' 2013-03-19 20:04:48ERROR [quantum.agent.dhcp_agent] Unable to sync network state. Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 154, in sync_state self.refresh_dhcp_helper(network_id) File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 208, in refresh_dhcp_helper return self.enable_dhcp_helper(network_id) File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 187, in enable_dhcp_helper self.enable_isolated_metadata_proxy(network) File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 321, in enable_isolated_metadata_proxy pm.enable(callback) File /usr/lib/python2.7/dist-packages/quantum/agent/linux/external_process.py
Re: [Openstack] Grizzly G3+RC1 - Quantum DHCP problem...
Also, my file `/etc/sudoers.d/quantum_sudoers' contains: --- Defaults:quantum !requiretty quantum ALL = (root) NOPASSWD: /usr/bin/quantum-rootwrap --- The error sudo: no tty present and no askpass program specified at `/var/log/quantum/dhcp-agent.log' persist... :-/ I don't think it is something missing with sudo... Tks, Thiago On 19 March 2013 22:52, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: My /etc/sudoers.d/nova_sudoers contains: -- Defaults:nova !requiretty nova ALL = (root) NOPASSWD: /usr/bin/nova-rootwrap -- Do I need to change it? Tks! Thiago On 19 March 2013 22:46, gong yong sheng gong...@linux.vnet.ibm.comwrote: It seems be about sudo. to create one sudo file under /etc/sudoers.d mine is: nova_sudoers: Defaults:gongysh !requiretty gongysh ALL = (ALL) NOPASSWD: ALL On 03/20/2013 09:37 AM, Martinx - ジェームズ wrote: Hi! I just rollback to the default namespace options, my Instance now get its IP without problem. But, the message from my first e-mail on this thread, still persist... I tried to enable quantum metadata proxy stuff but, nothing changes... The following error keeps rolling at my /var/log/quantum/dhcp-agent.log: --- ... Command: ['sudo', 'ip', 'netns', 'exec', 'qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91', 'quantum-ns-metadata-proxy', '--pid_file=/var/lib/quantum/external/pids/21a39c11-03fd-4e2e-b7a0-94eee95f5f91.pid', '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91', '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug', '--verbose', '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log', '--log-dir=/var/log/quantum'] Exit code: 1 Stdout: '' Stderr: 'sudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: 3 incorrect password attempts\n' --- I tried everything I could... But this message persist... The namespaces are enabled, look: ip netns exec qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91 ip r 10.33.14.0/24 dev tapeb27823a-5e proto kernel scope link src 10.33.14.2 What can I do? Tks, Thiago On 19 March 2013 20:35, Martinx - ジェームズ thiagocmarti...@gmail.comwrote: After disabling namespaces, with: `allow_overlapping_ips = False' in quantum.conf and with: `use_namespaces = False' in /etc/quantum/dhcp_agent.ini The previous error message dissapear but, My Instance isn't getting its IP via DHCP now... Weird thing is that it was working couple minutes ago, without disabling namespaces explicitly... If I add the Instance IP by hand, I can reach the Internet / gateway from it. I'm finishing my Grizzly Quantum Single Flat PoC environment, planning to publish a nice guide soon! I appreciate any help! Tks! Thiago On 19 March 2013 20:09, Martinx - ジェームズ thiagocmarti...@gmail.comwrote: Guys, My /var/log/quantum/dhcp-agent.log file shows: 2013-03-19 20:04:48DEBUG [quantum.agent.linux.utils] Running command: ['sudo', 'ip', 'netns', 'exec', 'qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91', 'quantum-ns-metadata-proxy', '--pid_file=/var/lib/quantum/external/pids/21a39c11-03fd-4e2e-b7a0-94eee95f5f91.pid', '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91', '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug', '--verbose', '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log', '--log-dir=/var/log/quantum'] 2013-03-19 20:04:48DEBUG [quantum.agent.linux.utils] Command: ['sudo', 'ip', 'netns', 'exec', 'qdhcp-21a39c11-03fd-4e2e-b7a0-94eee95f5f91', 'quantum-ns-metadata-proxy', '--pid_file=/var/lib/quantum/external/pids/21a39c11-03fd-4e2e-b7a0-94eee95f5f91.pid', '--network_id=21a39c11-03fd-4e2e-b7a0-94eee95f5f91', '--state_path=/var/lib/quantum', '--metadata_port=80', '--debug', '--verbose', '--log-file=quantum-ns-metadata-proxy21a39c11-03fd-4e2e-b7a0-94eee95f5f91.log', '--log-dir=/var/log/quantum'] Exit code: 1 Stdout: '' Stderr: 'sudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: no tty present and no askpass program specified\nSorry, try again.\nsudo: 3 incorrect password attempts\n' 2013-03-19 20:04:48ERROR [quantum.agent.dhcp_agent] Unable to sync network state. Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 154, in sync_state self.refresh_dhcp_helper(network_id) File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 208, in refresh_dhcp_helper return self.enable_dhcp_helper(network_id) File /usr/lib/python2.7/dist-packages/quantum/agent/dhcp_agent.py, line 187, in enable_dhcp_helper self.enable_isolated_metadata_proxy(network) File /usr/lib/python2.7/dist-packages/quantum/agent
Re: [Openstack] Grizzly Dashboard Quota Problem...
Hello Mauro! I'm reinstalling everything (Grizzly from PPA) from scratch again, if I hit the BUG one more time, I'll let you guys know. Best Regards, Thiago On 18 March 2013 13:11, Mauro Rodrigues maur...@linux.vnet.ibm.com wrote: Hey Thiago! Did you open a bug for this issue? If so let me know (I'm maurosr at the irc channels), it seems we need to deal with this in conductor. If you're going to open the bug now, please don't forget to add the conductor log. Thanks, -- Mauro S M Rodrigues Software Engineer IBM LTC Brazil On 03/15/2013 08:57 PM, Martinx - ジェームズ wrote: Hi! I don't know if it is related to this issue but, when I Terminate an Instance, nova-conductor.log shows: 2013-03-15 20:56:33.739 ERROR nova.quota [req-558f180c-4092-4dad-9be0-04b105e6a51b 773fad6638fe4def95dd996db7af5161 7428cb7265d04ff398202b45f84d96bf] Failed to commit reservations [u'73a2da17-7b5a-4913-87f2-33bf47b7ab02', u'd2e4334a-679d-4664-bdc9-abff1247c89c', u'b284d408-2788-4fad-b191-9fc6f857cdee'] 2013-03-15 20:56:33.739 6218 TRACE nova.quota Traceback (most recent call last): 2013-03-15 20:56:33.739 6218 TRACE nova.quota File /usr/lib/python2.7/dist-packages/nova/quota.py, line 982, in commit 2013-03-15 20:56:33.739 6218 TRACE nova.quota self._driver.commit(context, reservations, project_id=project_id) 2013-03-15 20:56:33.739 6218 TRACE nova.quota File /usr/lib/python2.7/dist-packages/nova/quota.py, line 370, in commit 2013-03-15 20:56:33.739 6218 TRACE nova.quota db.reservation_commit(context, reservations, project_id=project_id) 2013-03-15 20:56:33.739 6218 TRACE nova.quota File /usr/lib/python2.7/dist-packages/nova/db/api.py, line 972, in reservation_commit 2013-03-15 20:56:33.739 6218 TRACE nova.quota project_id=project_id) 2013-03-15 20:56:33.739 6218 TRACE nova.quota File /usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.py, line 112, in wrapper 2013-03-15 20:56:33.739 6218 TRACE nova.quota return f(*args, **kwargs) 2013-03-15 20:56:33.739 6218 TRACE nova.quota File /usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.py, line 2681, in reservation_commit 2013-03-15 20:56:33.739 6218 TRACE nova.quota usage = usages[reservation.resource] 2013-03-15 20:56:33.739 6218 TRACE nova.quota KeyError: u'instances' 2013-03-15 20:56:33.739 6218 TRACE nova.quota Tks, Thiago On 15 March 2013 20:37, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Hi! Finally I have my Grizzly G3 + RC1 working! But, when I tried to setup the Project quotas, an error appear on the Dashboard and at Apache error.log. The error appear even when creating a Project, with default quota settings... Dashboard message: Error: Unable to set project quotas. error.log: [Fri Mar 15 23:35:57 2013] [error] \x1b[31;1mRecoverable error: Bad key(s) gigabytes,volumes in quota_set (HTTP 400) (Request-ID: req-555844dc-3cdc-4a33-a7e8-c1836b8f)\x1b[0m Is this a know BUG? Can I do something about it? Thanks! Thiago ___ 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
[Openstack] Grizzly openstack-dashboard installation / upgrade problem
Hi! Everytime I install or upgrade the Ubuntu packages `openstack-dashboard / openstack-dashboard-ubuntu-theme', I must run the following commands before being able to use the Dashboard: cd /usr/share/openstack-dashboard/ python manage.py compress Otherwise, I get Internal Server Error after login and some erros on Apache error.log file, like this: [Tue Mar 19 04:08:28 2013] [error] [client 192.168.15.136] File /usr/lib/python2.7/dist-packages/compressor/templatetags/compress.py, line 72, in render_offline, referer: http://cloud.quilombas.com/horizon [Tue Mar 19 04:08:28 2013] [error] [client 192.168.15.136] 'You may need to run python manage.py compress.' % key), referer: http://10.32.14.232/horizon [Tue Mar 19 04:08:28 2013] [error] [client 192.168.15.136] OfflineGenerationError: You have offline compression enabled but key 5c40b85be56c93c77e8d169e635c9beb is missing from offline manifest. You may need to run python manage.py compress., referer: http://10.32.14.232/horizon I believe that the Ubuntu/Debian post-install script can handle this, right? Best, Thiago ___ 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 openstack-dashboard installation / upgrade problem
BTW, I'm using openstack-dashboard 1:2013.1+git201303182101~precise-0ubuntu1... =P On 19 March 2013 02:27, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Hi! Everytime I install or upgrade the Ubuntu packages `openstack-dashboard / openstack-dashboard-ubuntu-theme', I must run the following commands before being able to use the Dashboard: cd /usr/share/openstack-dashboard/ python manage.py compress Otherwise, I get Internal Server Error after login and some erros on Apache error.log file, like this: [Tue Mar 19 04:08:28 2013] [error] [client 192.168.15.136] File /usr/lib/python2.7/dist-packages/compressor/templatetags/compress.py, line 72, in render_offline, referer: http://cloud.quilombas.com/horizon [Tue Mar 19 04:08:28 2013] [error] [client 192.168.15.136] 'You may need to run python manage.py compress.' % key), referer: http://10.32.14.232/horizon [Tue Mar 19 04:08:28 2013] [error] [client 192.168.15.136] OfflineGenerationError: You have offline compression enabled but key 5c40b85be56c93c77e8d169e635c9beb is missing from offline manifest. You may need to run python manage.py compress., referer: http://10.32.14.232/horizon I believe that the Ubuntu/Debian post-install script can handle this, right? Best, Thiago ___ 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] Grizzly Dashboard Quota Problem...
Hi! Finally I have my Grizzly G3 + RC1 working! But, when I tried to setup the Project quotas, an error appear on the Dashboard and at Apache error.log. The error appear even when creating a Project, with default quota settings... Dashboard message: Error: Unable to set project quotas. error.log: [Fri Mar 15 23:35:57 2013] [error] \x1b[31;1mRecoverable error: Bad key(s) gigabytes,volumes in quota_set (HTTP 400) (Request-ID: req-555844dc-3cdc-4a33-a7e8-c1836b8f)\x1b[0m Is this a know BUG? Can I do something about it? Thanks! Thiago ___ 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] Testing Grizzly - What repository is the recommended?
Hi! Just for the record, Ubuntu PPA grizzly-trunk-testing repository is working (with Ubuntu 12.04)! Best, Thiago On 14 March 2013 19:35, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Guys, I'm about to test Grizzly but, I'm seeing two alternatives: 1- Install Ubuntu 12.04 and add http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/grizzly main /etc/apt/sources.list.d/grizzly.list ( http://docs.openstack.org/trunk/openstack-compute/install/apt/content/osfolubuntu-prerquisite.html ) 2- Install Ubuntu 12.04 and add https://launchpad.net/~openstack-ubuntu-testing/+archive/grizzly-trunk-testing?field.series_filter=precise ... From what I'm seeing, the PPA grizzly-trunk-testing is more updated... Right? BTW, even if I'm going to try it with Raring, the PPA seems more updated for it too, if I'm not wrong... Is Quantum RC1 at this PPA ? Thanks! Thiago ___ 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 Dashboard Quota Problem...
Hi! I don't know if it is related to this issue but, when I Terminate an Instance, nova-conductor.log shows: 2013-03-15 20:56:33.739 ERROR nova.quota [req-558f180c-4092-4dad-9be0-04b105e6a51b 773fad6638fe4def95dd996db7af5161 7428cb7265d04ff398202b45f84d96bf] Failed to commit reservations [u'73a2da17-7b5a-4913-87f2-33bf47b7ab02', u'd2e4334a-679d-4664-bdc9-abff1247c89c', u'b284d408-2788-4fad-b191-9fc6f857cdee'] 2013-03-15 20:56:33.739 6218 TRACE nova.quota Traceback (most recent call last): 2013-03-15 20:56:33.739 6218 TRACE nova.quota File /usr/lib/python2.7/dist-packages/nova/quota.py, line 982, in commit 2013-03-15 20:56:33.739 6218 TRACE nova.quota self._driver.commit(context, reservations, project_id=project_id) 2013-03-15 20:56:33.739 6218 TRACE nova.quota File /usr/lib/python2.7/dist-packages/nova/quota.py, line 370, in commit 2013-03-15 20:56:33.739 6218 TRACE nova.quota db.reservation_commit(context, reservations, project_id=project_id) 2013-03-15 20:56:33.739 6218 TRACE nova.quota File /usr/lib/python2.7/dist-packages/nova/db/api.py, line 972, in reservation_commit 2013-03-15 20:56:33.739 6218 TRACE nova.quota project_id=project_id) 2013-03-15 20:56:33.739 6218 TRACE nova.quota File /usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.py, line 112, in wrapper 2013-03-15 20:56:33.739 6218 TRACE nova.quota return f(*args, **kwargs) 2013-03-15 20:56:33.739 6218 TRACE nova.quota File /usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.py, line 2681, in reservation_commit 2013-03-15 20:56:33.739 6218 TRACE nova.quota usage = usages[reservation.resource] 2013-03-15 20:56:33.739 6218 TRACE nova.quota KeyError: u'instances' 2013-03-15 20:56:33.739 6218 TRACE nova.quota Tks, Thiago On 15 March 2013 20:37, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Hi! Finally I have my Grizzly G3 + RC1 working! But, when I tried to setup the Project quotas, an error appear on the Dashboard and at Apache error.log. The error appear even when creating a Project, with default quota settings... Dashboard message: Error: Unable to set project quotas. error.log: [Fri Mar 15 23:35:57 2013] [error] \x1b[31;1mRecoverable error: Bad key(s) gigabytes,volumes in quota_set (HTTP 400) (Request-ID: req-555844dc-3cdc-4a33-a7e8-c1836b8f)\x1b[0m Is this a know BUG? Can I do something about it? Thanks! Thiago ___ 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-operators] Help with simplest Quantum setup possible...
Hi! My Quantum Single Flat is almost working! My Instance get an IPv4 without any problem but, the metadata isn't working... What can I do? My compute node have the `nova-api-metadata' package, nova.conf have `metadata_host = 10.32.14.234', the iptables `169.254.169.254' NAT rule is there too... The Instance log shows: Starting network... udhcpc (v1.20.1) started Sending discover... Sending select for 10.33.14.3... Lease of 10.33.14.3 obtained, lease time 120 deleting routers route: SIOCDELRT: No such process adding dns 8.8.4.4 adding dns 8.8.8.8 cirros-ds 'net' up at 1.84 checking http://169.254.169.254/2009-04-04/instance-id failed 1/20: up 1.87. request failed failed 2/20: up 13.98. request failed failed 3/20: up 26.02. request failed failed 4/20: up 38.06. request failed failed 5/20: up 50.09. request failed failed 6/20: up 62.13. request failed failed 7/20: up 74.16. request failed failed 8/20: up 86.20. request failed failed 9/20: up 98.24. request failed failed 10/20: up 110.27. request failed failed 11/20: up 122.31. request failed failed 12/20: up 134.34. request failed failed 13/20: up 146.38. request failed failed 14/20: up 158.41. request failed failed 15/20: up 170.45. request failed failed 16/20: up 182.49. request failed failed 17/20: up 194.52. request failed failed 18/20: up 206.56. request failed failed 19/20: up 218.59. request failed failed 20/20: up 230.63. request failed failed to read iid from metadata. tried 20 no results found for mode=net. up 242.66. searched: nocloud configdrive ec2 failed to get instance-id of datasource Starting dropbear sshd: generating rsa key... generating dsa key... OK Any clue? Thanks! Thiago On 13 March 2013 10:10, Daneyon Hansen (danehans) daneh...@cisco.comwrote: Regards, Daneyon Hansen On Mar 13, 2013, at 1:04 AM, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Guys, Here: http://docs.openstack.org/trunk/openstack-network/admin/content/demo_flat_installions.html ...at the step 1. Install the L2 agent. but, what is the name of the Ubuntu package (I'm using Folsom)? ...apt-get install what? quantum-plugin-openvswitch-agent I thought that the Quantum L2 agent was the package `quantum-plugin-linuxbridge' but, this doc uses OpenvSwitch... So, I'm confused now... As you know Quantum uses plugins to realize the network abstractions. Some plugins (such as OVS) use an agent to collect information from the Quantum db to implement the logical data model on the local vswitch. The following packages quantum-server quantum-plugin-openvswitch quantum-plugin-openvswitch-agent quantum-dhcp-agent will be enough for my `controller+network node'? That should work for flat networking implementations. At the compute-node, I'll install only the quantum-plugin-openvswitch-agent, right? Correct. That package should install the openvswitch and other dependencies. Tks, Thiago On 13 March 2013 00:58, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Daneyon, Thank you for your time! I'll check it! I read that guide from Cisto once... Too complex. I also, tried the following guides too, appears to be like the one from Cisco: https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/stable/GRE/OpenStack_Folsom_Install_Guide_WebVersion.rst and: https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/GRE/2NICs/OpenStack_Folsom_Install_Guide_WebVersion.rst Anyway, at first, I do not want L3 or GRE. Only the most basic setup (Flat / L2). Do you know if my `controller+network node' server eth0 needs to be promisc? Tks! Thiago On 13 March 2013 00:49, Daneyon Hansen (danehans) daneh...@cisco.comwrote: Make sure the quantum-dhcp and l3 agents are running and properly configured. It sounds like either the q-dhcp agent is not functioning or connectivity between the dhcp agent and vm is not functioning. If using GRE tunnels, test connectivity between the tunnel endpoints. You should also see the IP's of your tunnel peers in ovs-vsctl show. If your instance spawns successfully, console into it and manually assign an IP and ping the q-l3-agent and q-dhcp agent. You can follow this guide for deploying Quantum with OpenvSwitch using GRE tunnels: http://docwiki.cisco.com/wiki/Cisco_OpenStack_Edition:_Folsom_Manual_Install Regards, Daneyon Hansen From: Martinx - ジェームズ thiagocmarti...@gmail.com Date: Tuesday, March 12, 2013 8:14 PM To: openstack@lists.launchpad.net openstack@lists.launchpad.net, openstack-operat...@lists.openstack.org openstack-operat...@lists.openstack.org Subject: Re: [Openstack-operators] Help with simplest Quantum setup possible... Well, Just for the record, I'll stick with Quatum + OpenvSwtich... Someone on IRC told me that it is the best way to go with Quantum. I'm still needing help to set it up (Single Flat / multi=false, still the same simplest topology). OpenvSwitch
Re: [Openstack] [Openstack-operators] Help with simplest Quantum setup possible...
Daneyon, Thanks! But, I'm not using L3, or GRE, or namespaces... I read the http://docs.openstack.org/trunk/openstack-network/admin/content/ch_limitations.htmland I don't think my setup (Single Flat, no GRE, no L3) fits that case... From my understandings, I'm not using overlapping IP's, since it is disabled by default... Anyway, after forcing `allow_overlapping_ips to False', nothing happens... From the compute node, I can connect to metadata by running: `telnet 10.32.14.232 8775' and / or `telnet 10.32.14.234 8775', both answer but, doesn't work in the end... I tried with metadata @ 10.32.14.232 (controller) and @ 10.32.14.234 (compute node with `nova-api-metadata') but, same broken result. From within my instance, when I run: `telnet 169.254.169.254 80', I can see the packages passing trough the NAT rule `169.254.169.254 tcp dpt:80 to:10.32.14.232:8775' but, the telnet connection times up. Do I need the package `quantum-plugin-metaplugin' instead `nova-api-metadata'? If yes, where, controller or on each compute node? BTW, if I set `use_namespaces = False' in dhcp_agent.ini, my Instances doesn't boots up anymore. Maybe it is time to go with Grizzly RC1? Anyway, I would like to finish everything I can with Quantum in Folsom, before going to try Grizzly... I really appreciate your help!! Regards, Thiago On 14 March 2013 15:21, Daneyon Hansen (danehans) daneh...@cisco.comwrote: Take a look at the limitations section of the Quantum docs. You will need to set allow overlapping IP's to false and make sure you have bidirectional network connectivity between the metadata ip and the tenant private network(s). The L3 agent.ini also should be configured with the metadata ip. The docs cover these topics in more detail. Regards, Daneyon Hansen On Mar 14, 2013, at 12:11 PM, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Hi! My Quantum Single Flat is almost working! My Instance get an IPv4 without any problem but, the metadata isn't working... What can I do? My compute node have the `nova-api-metadata' package, nova.conf have `metadata_host = 10.32.14.234', the iptables `169.254.169.254' NAT rule is there too... The Instance log shows: Starting network... udhcpc (v1.20.1) started Sending discover... Sending select for 10.33.14.3... Lease of 10.33.14.3 obtained, lease time 120 deleting routers route: SIOCDELRT: No such process adding dns 8.8.4.4 adding dns 8.8.8.8 cirros-ds 'net' up at 1.84 checking http://169.254.169.254/2009-04-04/instance-id failed 1/20: up 1.87. request failed failed 2/20: up 13.98. request failed failed 3/20: up 26.02. request failed failed 4/20: up 38.06. request failed failed 5/20: up 50.09. request failed failed 6/20: up 62.13. request failed failed 7/20: up 74.16. request failed failed 8/20: up 86.20. request failed failed 9/20: up 98.24. request failed failed 10/20: up 110.27. request failed failed 11/20: up 122.31. request failed failed 12/20: up 134.34. request failed failed 13/20: up 146.38. request failed failed 14/20: up 158.41. request failed failed 15/20: up 170.45. request failed failed 16/20: up 182.49. request failed failed 17/20: up 194.52. request failed failed 18/20: up 206.56. request failed failed 19/20: up 218.59. request failed failed 20/20: up 230.63. request failed failed to read iid from metadata. tried 20 no results found for mode=net. up 242.66. searched: nocloud configdrive ec2 failed to get instance-id of datasource Starting dropbear sshd: generating rsa key... generating dsa key... OK Any clue? Thanks! Thiago On 13 March 2013 10:10, Daneyon Hansen (danehans) daneh...@cisco.comwrote: Regards, Daneyon Hansen On Mar 13, 2013, at 1:04 AM, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Guys, Here: http://docs.openstack.org/trunk/openstack-network/admin/content/demo_flat_installions.html ...at the step 1. Install the L2 agent. but, what is the name of the Ubuntu package (I'm using Folsom)? ...apt-get install what? quantum-plugin-openvswitch-agent I thought that the Quantum L2 agent was the package `quantum-plugin-linuxbridge' but, this doc uses OpenvSwitch... So, I'm confused now... As you know Quantum uses plugins to realize the network abstractions. Some plugins (such as OVS) use an agent to collect information from the Quantum db to implement the logical data model on the local vswitch. The following packages quantum-server quantum-plugin-openvswitch quantum-plugin-openvswitch-agent quantum-dhcp-agent will be enough for my `controller+network node'? That should work for flat networking implementations. At the compute-node, I'll install only the quantum-plugin-openvswitch-agent, right? Correct. That package should install the openvswitch and other dependencies. Tks, Thiago On 13 March 2013 00:58, Martinx - ジェームズ thiagocmarti...@gmail.comwrote: Daneyon, Thank you for your
Re: [Openstack] [Quantum] OpenStack Networking Grizzly RC1 available
I really appreciate the work from this community!!! :-D Installing Ubuntu Raring right now to try Grizzly... Thank you guys!!! Best, Thiago On 14 March 2013 06:01, Thierry Carrez thie...@openstack.org wrote: Hello everyone, The first project to publish a release candidate in preparation for the Grizzly release is OpenStack Networking (code named Quantum)! The RC1 is available for download at: https://launchpad.net/quantum/grizzly/grizzly-rc1 Congratulations to the Quantum development team for reaching that milestone so early, and fixing 97 bugs in 3 weeks ! Unless release-critical issues are found that warrant a release candidate respin, this RC1 will be formally released as the 2013.1 final version on April 4. You are therefore strongly encouraged to test and validate this tarball. Alternatively, you can directly test the milestone-proposed branch at: https://github.com/openstack/quantum/tree/milestone-proposed If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/quantum/+filebug and tag it *grizzly-rc-potential* to bring it to the release crew's attention. Note that the master branch of Quantum is now open for Havana development, and feature freeze restrictions no longer apply. Regards, -- Thierry Carrez (ttx) Release Manager, OpenStack ___ 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
[Openstack] Testing Grizzly - What repository is the recommended?
Guys, I'm about to test Grizzly but, I'm seeing two alternatives: 1- Install Ubuntu 12.04 and add http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/grizzly main /etc/apt/sources.list.d/grizzly.list ( http://docs.openstack.org/trunk/openstack-compute/install/apt/content/osfolubuntu-prerquisite.html ) 2- Install Ubuntu 12.04 and add https://launchpad.net/~openstack-ubuntu-testing/+archive/grizzly-trunk-testing?field.series_filter=precise ... From what I'm seeing, the PPA grizzly-trunk-testing is more updated... Right? BTW, even if I'm going to try it with Raring, the PPA seems more updated for it too, if I'm not wrong... Is Quantum RC1 at this PPA ? Thanks! Thiago ___ 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-operators] Help with simplest Quantum setup possible...
Well, I'm giving it up. It is almost impossible to enable metadata with Folsom / Quantum / Single Flat... I tried everything... Even this do not help me: Folsom-Quantum-metadata server issue: https://answers.launchpad.net/quantum/+question/218237 Since I have now a working Quantum (without metadata) PoC, I'll try Grizzly from now... Unless someone help me more! =P Now I'll take a look into this: http://cloudistic.me/blog/hacking-together-metadata-support-when-using-folsom-with-grizzly-quantum/- but, with Grizzly G3 + RC1... Tks, Thiago On 14 March 2013 18:21, Narayan Desai narayan.de...@gmail.com wrote: Make sure that the metadata server has a route back to the VM. Traffic hitting that NAT rule ensures that data is flowing properly in one direction, but you need to make sure bits can flow back to establish a tcp connection. We had this problem running multiple nova-network servers. -nld On Thu, Mar 14, 2013 at 2:28 PM, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Daneyon, Thanks! But, I'm not using L3, or GRE, or namespaces... I read the http://docs.openstack.org/trunk/openstack-network/admin/content/ch_limitations.html and I don't think my setup (Single Flat, no GRE, no L3) fits that case... From my understandings, I'm not using overlapping IP's, since it is disabled by default... Anyway, after forcing `allow_overlapping_ips to False', nothing happens... From the compute node, I can connect to metadata by running: `telnet 10.32.14.232 8775' and / or `telnet 10.32.14.234 8775', both answer but, doesn't work in the end... I tried with metadata @ 10.32.14.232 (controller) and @ 10.32.14.234 (compute node with `nova-api-metadata') but, same broken result. From within my instance, when I run: `telnet 169.254.169.254 80', I can see the packages passing trough the NAT rule `169.254.169.254 tcp dpt:80 to:10.32.14.232:8775' but, the telnet connection times up. Do I need the package `quantum-plugin-metaplugin' instead `nova-api-metadata'? If yes, where, controller or on each compute node? BTW, if I set `use_namespaces = False' in dhcp_agent.ini, my Instances doesn't boots up anymore. Maybe it is time to go with Grizzly RC1? Anyway, I would like to finish everything I can with Quantum in Folsom, before going to try Grizzly... I really appreciate your help!! Regards, Thiago On 14 March 2013 15:21, Daneyon Hansen (danehans) daneh...@cisco.com wrote: Take a look at the limitations section of the Quantum docs. You will need to set allow overlapping IP's to false and make sure you have bidirectional network connectivity between the metadata ip and the tenant private network(s). The L3 agent.ini also should be configured with the metadata ip. The docs cover these topics in more detail. Regards, Daneyon Hansen On Mar 14, 2013, at 12:11 PM, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Hi! My Quantum Single Flat is almost working! My Instance get an IPv4 without any problem but, the metadata isn't working... What can I do? My compute node have the `nova-api-metadata' package, nova.conf have `metadata_host = 10.32.14.234', the iptables `169.254.169.254' NAT rule is there too... The Instance log shows: Starting network... udhcpc (v1.20.1) started Sending discover... Sending select for 10.33.14.3... Lease of 10.33.14.3 obtained, lease time 120 deleting routers route: SIOCDELRT: No such process adding dns 8.8.4.4 adding dns 8.8.8.8 cirros-ds 'net' up at 1.84 checking http://169.254.169.254/2009-04-04/instance-id failed 1/20: up 1.87. request failed failed 2/20: up 13.98. request failed failed 3/20: up 26.02. request failed failed 4/20: up 38.06. request failed failed 5/20: up 50.09. request failed failed 6/20: up 62.13. request failed failed 7/20: up 74.16. request failed failed 8/20: up 86.20. request failed failed 9/20: up 98.24. request failed failed 10/20: up 110.27. request failed failed 11/20: up 122.31. request failed failed 12/20: up 134.34. request failed failed 13/20: up 146.38. request failed failed 14/20: up 158.41. request failed failed 15/20: up 170.45. request failed failed 16/20: up 182.49. request failed failed 17/20: up 194.52. request failed failed 18/20: up 206.56. request failed failed 19/20: up 218.59. request failed failed 20/20: up 230.63. request failed failed to read iid from metadata. tried 20 no results found for mode=net. up 242.66. searched: nocloud configdrive ec2 failed to get instance-id of datasource Starting dropbear sshd: generating rsa key... generating dsa key... OK Any clue? Thanks! Thiago On 13 March 2013 10:10, Daneyon Hansen (danehans) daneh...@cisco.com wrote: Regards, Daneyon Hansen On Mar 13, 2013, at 1:04 AM, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Guys, Here
Re: [Openstack] [Openstack-operators] Help with simplest Quantum setup possible...
Guys, Here: http://docs.openstack.org/trunk/openstack-network/admin/content/demo_flat_installions.html ...at the step 1. Install the L2 agent. but, what is the name of the Ubuntu package (I'm using Folsom)? ...apt-get install what? I thought that the Quantum L2 agent was the package `quantum-plugin-linuxbridge' but, this doc uses OpenvSwitch... So, I'm confused now... The following packages quantum-server quantum-plugin-openvswitch quantum-plugin-openvswitch-agent quantum-dhcp-agent will be enough for my `controller+network node'? At the compute-node, I'll install only the quantum-plugin-openvswitch-agent, right? Tks, Thiago On 13 March 2013 00:58, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Daneyon, Thank you for your time! I'll check it! I read that guide from Cisto once... Too complex. I also, tried the following guides too, appears to be like the one from Cisco: https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/stable/GRE/OpenStack_Folsom_Install_Guide_WebVersion.rst and: https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/GRE/2NICs/OpenStack_Folsom_Install_Guide_WebVersion.rst Anyway, at first, I do not want L3 or GRE. Only the most basic setup (Flat / L2). Do you know if my `controller+network node' server eth0 needs to be promisc? Tks! Thiago On 13 March 2013 00:49, Daneyon Hansen (danehans) daneh...@cisco.comwrote: Make sure the quantum-dhcp and l3 agents are running and properly configured. It sounds like either the q-dhcp agent is not functioning or connectivity between the dhcp agent and vm is not functioning. If using GRE tunnels, test connectivity between the tunnel endpoints. You should also see the IP's of your tunnel peers in ovs-vsctl show. If your instance spawns successfully, console into it and manually assign an IP and ping the q-l3-agent and q-dhcp agent. You can follow this guide for deploying Quantum with OpenvSwitch using GRE tunnels: http://docwiki.cisco.com/wiki/Cisco_OpenStack_Edition:_Folsom_Manual_Install Regards, Daneyon Hansen From: Martinx - ジェームズ thiagocmarti...@gmail.com Date: Tuesday, March 12, 2013 8:14 PM To: openstack@lists.launchpad.net openstack@lists.launchpad.net, openstack-operat...@lists.openstack.org openstack-operat...@lists.openstack.org Subject: Re: [Openstack-operators] Help with simplest Quantum setup possible... Well, Just for the record, I'll stick with Quatum + OpenvSwtich... Someone on IRC told me that it is the best way to go with Quantum. I'm still needing help to set it up (Single Flat / multi=false, still the same simplest topology). OpenvSwitch is already working, bridges `br-int' and `br-eth0' created... My main problem, I think, is that my Instances doesn't get an IP (they supposed to be at 10.33.14.X/24). Everything else seems to be working as expected, no apparent errors on the logs... quantum net-create / subnet-create worked... I appreciate any help, tips or docs! Best! Thiago On 12 March 2013 23:34, Martinx - ジェームズ thiagocmarti...@gmail.comwrote: Hi! Sorry about the double posting... I need help! :-P I'm trying, without any kind of success, to deploy OpenStack with Quantum on its simplest scenario, I think, which is `Single Flat' with `Linux Bridge' plugin. My topology is: 1 firewall with 2 ethX (eth0 public, eth1 10.32.14.1 and 10.33.14.1) 1 controller with 1 eth0 (10.32.14.232/24 gateway 10.32.14.1) 1 node with 1 eth0 (10.32.14.234/24 gateway 10.32.14.1) Instances Network: 10.33.14.0/24 (Instances gateway must be 10.33.14.1, same router of the physical servers above, NOT its own host hypervisor). I'm trying this: http://docs.openstack.org/trunk/openstack-network/admin/content/demo_flat_installions.html- doesn't work... Even enabling OpenvSwith (but I don't want it for now, only Quantum instead of nova-network, with Linux Bridge for the sake of simplicity). The following guide help me a lot (with Nova Network everything is fine): http://openstack-folsom-install-guide.readthedocs.org/en/latest/- I'm trying to follow it, by replacing nota-network instructions, for Quantum instructions but, doesn't work... Any docs or tips? NOTE: I do not want any kind of NAT (like nova-network multi=true) or `Floating IPs' within my Cloud Computing environment. Thanks! Thiago ___ 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-operators] Help with simplest Quantum setup possible...
Thanks!! I'm trying it right now... At my `controller+network node' nova.conf file, I'm changing this: # NETWORK - Nova Network # network_manager = nova.network.manager.FlatDHCPManager # force_dhcp_release = True # dhcpbridge_flagfile = /etc/nova/nova.conf # firewall_driver = nova.virt.libvirt.firewall.IptablesFirewallDriver # # Change my_ip to match each host # my_ip = 10.32.14.232 # public_interface = br100 # vlan_interface = eth0 # flat_network_bridge = br100 # flat_interface = eth0 Into this: # NETWORK - QUANTUM network_api_class=nova.network.quantumv2.api.API quantum_url=http://controller:9696/ quantum_auth_strategy=keystone quantum_admin_tenant_name=service quantum_admin_username=quantum quantum_admin_password=service_pass quantum_admin_auth_url=http://controller:35357/v2.0/ libvirt_vif_driver=nova.virt.libvirt.vif.LibvirtHybridOVSBridgeDriver But, here: http://docs.openstack.org/trunk/openstack-network/admin/content/demo_flat_installions.html- they say to configure this at the nova.conf of the compute node... Do I need to write it on all nova.conf files across my cloud? Also, do I need this (in nova.conf for Quantum): linuxnet_interface_driver=nova.network.linux_net.LinuxOVSInterfaceDriver firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver .. or not??? I'm reading this two options from here: https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/VLAN/2NICs/OpenStack_Folsom_Install_Guide_WebVersion.rst Best, Thiago On 13 March 2013 10:10, Daneyon Hansen (danehans) daneh...@cisco.comwrote: Regards, Daneyon Hansen On Mar 13, 2013, at 1:04 AM, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Guys, Here: http://docs.openstack.org/trunk/openstack-network/admin/content/demo_flat_installions.html ...at the step 1. Install the L2 agent. but, what is the name of the Ubuntu package (I'm using Folsom)? ...apt-get install what? quantum-plugin-openvswitch-agent I thought that the Quantum L2 agent was the package `quantum-plugin-linuxbridge' but, this doc uses OpenvSwitch... So, I'm confused now... As you know Quantum uses plugins to realize the network abstractions. Some plugins (such as OVS) use an agent to collect information from the Quantum db to implement the logical data model on the local vswitch. The following packages quantum-server quantum-plugin-openvswitch quantum-plugin-openvswitch-agent quantum-dhcp-agent will be enough for my `controller+network node'? That should work for flat networking implementations. At the compute-node, I'll install only the quantum-plugin-openvswitch-agent, right? Correct. That package should install the openvswitch and other dependencies. Tks, Thiago On 13 March 2013 00:58, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Daneyon, Thank you for your time! I'll check it! I read that guide from Cisto once... Too complex. I also, tried the following guides too, appears to be like the one from Cisco: https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/stable/GRE/OpenStack_Folsom_Install_Guide_WebVersion.rst and: https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/GRE/2NICs/OpenStack_Folsom_Install_Guide_WebVersion.rst Anyway, at first, I do not want L3 or GRE. Only the most basic setup (Flat / L2). Do you know if my `controller+network node' server eth0 needs to be promisc? Tks! Thiago On 13 March 2013 00:49, Daneyon Hansen (danehans) daneh...@cisco.comwrote: Make sure the quantum-dhcp and l3 agents are running and properly configured. It sounds like either the q-dhcp agent is not functioning or connectivity between the dhcp agent and vm is not functioning. If using GRE tunnels, test connectivity between the tunnel endpoints. You should also see the IP's of your tunnel peers in ovs-vsctl show. If your instance spawns successfully, console into it and manually assign an IP and ping the q-l3-agent and q-dhcp agent. You can follow this guide for deploying Quantum with OpenvSwitch using GRE tunnels: http://docwiki.cisco.com/wiki/Cisco_OpenStack_Edition:_Folsom_Manual_Install Regards, Daneyon Hansen From: Martinx - ジェームズ thiagocmarti...@gmail.com Date: Tuesday, March 12, 2013 8:14 PM To: openstack@lists.launchpad.net openstack@lists.launchpad.net, openstack-operat...@lists.openstack.org openstack-operat...@lists.openstack.org Subject: Re: [Openstack-operators] Help with simplest Quantum setup possible... Well, Just for the record, I'll stick with Quatum + OpenvSwtich... Someone on IRC told me that it is the best way to go with Quantum. I'm still needing help to set it up (Single Flat / multi=false, still the same simplest topology). OpenvSwitch is already working, bridges `br-int' and `br-eth0' created... My main problem, I think, is that my Instances doesn't get an IP (they supposed to be at 10.33.14.X/24). Everything else seems
[Openstack] Help with simplest Quantum setup possible...
Hi! Sorry about the double posting... I need help! :-P I'm trying, without any kind of success, to deploy OpenStack with Quantum on its simplest scenario, I think, which is `Single Flat' with `Linux Bridge' plugin. My topology is: 1 firewall with 2 ethX (eth0 public, eth1 10.32.14.1 and 10.33.14.1) 1 controller with 1 eth0 (10.32.14.232/24 gateway 10.32.14.1) 1 node with 1 eth0 (10.32.14.234/24 gateway 10.32.14.1) Instances Network: 10.33.14.0/24 (Instances gateway must be 10.33.14.1, same router of the physical servers above, NOT its own host hypervisor). I'm trying this: http://docs.openstack.org/trunk/openstack-network/admin/content/demo_flat_installions.html- doesn't work... Even enabling OpenvSwith (but I don't want it for now, only Quantum instead of nova-network, with Linux Bridge for the sake of simplicity). The following guide help me a lot (with Nova Network everything is fine): http://openstack-folsom-install-guide.readthedocs.org/en/latest/ - I'm trying to follow it, by replacing nota-network instructions, for Quantum instructions but, doesn't work... Any docs or tips? NOTE: I do not want any kind of NAT (like nova-network multi=true) or `Floating IPs' within my Cloud Computing environment. Thanks! Thiago ___ 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-operators] Help with simplest Quantum setup possible...
Daneyon, Thank you for your time! I'll check it! I read that guide from Cisto once... Too complex. I also, tried the following guides too, appears to be like the one from Cisco: https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/stable/GRE/OpenStack_Folsom_Install_Guide_WebVersion.rst and: https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/GRE/2NICs/OpenStack_Folsom_Install_Guide_WebVersion.rst Anyway, at first, I do not want L3 or GRE. Only the most basic setup (Flat / L2). Do you know if my `controller+network node' server eth0 needs to be promisc? Tks! Thiago On 13 March 2013 00:49, Daneyon Hansen (danehans) daneh...@cisco.comwrote: Make sure the quantum-dhcp and l3 agents are running and properly configured. It sounds like either the q-dhcp agent is not functioning or connectivity between the dhcp agent and vm is not functioning. If using GRE tunnels, test connectivity between the tunnel endpoints. You should also see the IP's of your tunnel peers in ovs-vsctl show. If your instance spawns successfully, console into it and manually assign an IP and ping the q-l3-agent and q-dhcp agent. You can follow this guide for deploying Quantum with OpenvSwitch using GRE tunnels: http://docwiki.cisco.com/wiki/Cisco_OpenStack_Edition:_Folsom_Manual_Install Regards, Daneyon Hansen From: Martinx - ジェームズ thiagocmarti...@gmail.com Date: Tuesday, March 12, 2013 8:14 PM To: openstack@lists.launchpad.net openstack@lists.launchpad.net, openstack-operat...@lists.openstack.org openstack-operat...@lists.openstack.org Subject: Re: [Openstack-operators] Help with simplest Quantum setup possible... Well, Just for the record, I'll stick with Quatum + OpenvSwtich... Someone on IRC told me that it is the best way to go with Quantum. I'm still needing help to set it up (Single Flat / multi=false, still the same simplest topology). OpenvSwitch is already working, bridges `br-int' and `br-eth0' created... My main problem, I think, is that my Instances doesn't get an IP (they supposed to be at 10.33.14.X/24). Everything else seems to be working as expected, no apparent errors on the logs... quantum net-create / subnet-create worked... I appreciate any help, tips or docs! Best! Thiago On 12 March 2013 23:34, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Hi! Sorry about the double posting... I need help! :-P I'm trying, without any kind of success, to deploy OpenStack with Quantum on its simplest scenario, I think, which is `Single Flat' with `Linux Bridge' plugin. My topology is: 1 firewall with 2 ethX (eth0 public, eth1 10.32.14.1 and 10.33.14.1) 1 controller with 1 eth0 (10.32.14.232/24 gateway 10.32.14.1) 1 node with 1 eth0 (10.32.14.234/24 gateway 10.32.14.1) Instances Network: 10.33.14.0/24 (Instances gateway must be 10.33.14.1, same router of the physical servers above, NOT its own host hypervisor). I'm trying this: http://docs.openstack.org/trunk/openstack-network/admin/content/demo_flat_installions.html- doesn't work... Even enabling OpenvSwith (but I don't want it for now, only Quantum instead of nova-network, with Linux Bridge for the sake of simplicity). The following guide help me a lot (with Nova Network everything is fine): http://openstack-folsom-install-guide.readthedocs.org/en/latest/- I'm trying to follow it, by replacing nota-network instructions, for Quantum instructions but, doesn't work... Any docs or tips? NOTE: I do not want any kind of NAT (like nova-network multi=true) or `Floating IPs' within my Cloud Computing environment. Thanks! Thiago ___ 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] Network node needed?
Is it possible to deploy Quantum (Flat) with two servers (controller + compute) that have only 1 ethernet on each? Plus, the Instances gateway will not be the controller, but my office firewall, external to the cloud, can be? Tks! On 11 March 2013 09:55, Logan McNaughton lo...@bacoosta.com wrote: No it's not needed, you just run quantum-server, the L3 agent, the DHCP agent, and the plugin agent (probably open vSwitch) all on the controller. You'll just need to plan out which NICs you'll use for what purpose and setup accordingly. As a side note, you'll also need to run the plugin agent on all your compute nodes On Mar 9, 2013 4:57 PM, JR botem...@gmail.com wrote: Greetings all, Next week I'll be putting up a new folsom cluster (perhaps using these instructions: https://github.com/mseknibilel/OpenStack-Folsom-Install-guide). Presently, I don't have a box to devote to being a network node. Is it necessary? The clouds I've put up so far have just had controller and compute nodes? Is the network node required by quantum? Thanks much, JR ___ 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
Re: [Openstack] Network node needed?
Well, I've read that but, I'm still unable to run Quantum on its simplest scenario... FlatDHCP single (multi=false, no-GRE, no L3 agents?)...? I mean, I'm trying Quantum without the network-node too (i.e. controller does that job)... So, not off-topic... =) Today, I have Folsom with Nova-Network FlatDHCP (1 ethernet / physical server), Cloud net 10.32.14.0/24, Instances net 10.33.14.0/24, option multi = true = hypervisores are the gateways of its own Instances. I followed this guide: http://openstack-folsom-install-guide.readthedocs.org/en/latest/ - works almost flawlessly. So, how can I setup Quantum that works almost like Nova-Network-FlatDHCP (but with like multi=false, gateway's instances is outside of the Cloud)? I'm reading this: http://docs.openstack.org/trunk/openstack-network/admin/content/demo_flat_installions.html- but, it doesn't help me to fix my Quantum PoC... My Instances doesn't get an IP... OpenvSwitch is working, I'm already using it with my previous Folsom + Nova-Network (brcompat enabled). So, I'm trying OVSQuantumPluginV2... Best, Thiago On 11 March 2013 12:59, JuanFra Rodriguez Cardoso juanfra.rodriguez.card...@gmail.com wrote: Hi: You could find it in this link: http://docs.openstack.org/trunk/openstack-compute/admin/content/existing-ha-networking-options.html Regards, JuanFra 2013/3/11 Martinx - ジェームズ thiagocmarti...@gmail.com Is it possible to deploy Quantum (Flat) with two servers (controller + compute) that have only 1 ethernet on each? Plus, the Instances gateway will not be the controller, but my office firewall, external to the cloud, can be? Tks! On 11 March 2013 09:55, Logan McNaughton lo...@bacoosta.com wrote: No it's not needed, you just run quantum-server, the L3 agent, the DHCP agent, and the plugin agent (probably open vSwitch) all on the controller. You'll just need to plan out which NICs you'll use for what purpose and setup accordingly. As a side note, you'll also need to run the plugin agent on all your compute nodes On Mar 9, 2013 4:57 PM, JR botem...@gmail.com wrote: Greetings all, Next week I'll be putting up a new folsom cluster (perhaps using these instructions: https://github.com/mseknibilel/OpenStack-Folsom-Install-guide). Presently, I don't have a box to devote to being a network node. Is it necessary? The clouds I've put up so far have just had controller and compute nodes? Is the network node required by quantum? Thanks much, JR ___ 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 ___ 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][Swift] Cifrado 0.1 Swift CLI available
Damn, lots of people doing the same thing...:-P On 4 March 2013 05:41, Diego Parrilla Santamaría diego.parrilla.santama...@gmail.com wrote: * Asymmetric/Symmetric transparent encryption/decryption of files when uploading/downloading using GnuPG. KimDotCom must be really scared! Are you going to build an alternative to MEGA.co.nz based on Swift ? ;-) Nice stuff man! Diego -- 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/ * * ___ 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] 2012.2.1 missing several nova dependency packages.
Try this (WITH CARE): rm -f /var/cache/apt/archives/* rm -f /var/cache/apt/archives/partial/* apt-get update apt-get install On 1 March 2013 16:52, Wyllys Ingersoll wyllys.ingers...@evault.com wrote: I did try that. It made no difference. ** ** *From:* Martinx - ジェームズ [mailto:thiagocmarti...@gmail.com] *Sent:* Friday, March 01, 2013 2:48 PM *To:* Wyllys Ingersoll *Cc:* openstack@lists.launchpad.net *Subject:* Re: [Openstack] 2012.2.1 missing several nova dependency packages. ** ** Try: apt-get update before... ** ** On 1 March 2013 16:42, Wyllys Ingersoll wyllys.ingers...@evault.com wrote: Im trying to install the nova packages from the Ubuntu 12.04 LTS folsom archives, but some of the required dependencies are no longer available.** ** My sources.list file has this entry: deb http://ubuntu-cloud.archive.canonical.com/ubuntuprecise-updates/folsom main If I remove that entry, I can get the 2012.1.3 release and it will work, but why is it not in the 2012.2.1 tree? Thanks, Wyllys $ sudo apt-get install python-nova Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: python-cinderclient python-cliff python-cmd2 python-novaclient python-paramiko python-pyparsing python-quantumclient The following NEW packages will be installed: python-cinderclient python-cliff python-cmd2 python-nova python-novaclient python-paramiko python-pyparsing python-quantumclient 0 upgraded, 8 newly installed, 0 to remove and 3 not upgraded. Need to get 3,121 kB/4,679 kB of archives. After this operation, 26.2 MB of additional disk space will be used. Do you want to continue [Y/n]? Err http://ubuntu-cloud.archive.canonical.com/ubuntu/precise-updates/folsom/main python-nova all 2012.2.1+stable-20121212-a99a802e-0ubuntu1.1~cloud0 404 Not Found Failed to fetch http://ubuntu-cloud.archive.canonical.com/ubuntu/pool/main/n/nova/python-nova_2012.2.1+stable-20121212-a99a802e-0ubuntu1.1~cloud0_all.deb 404 Not Found E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? ___ 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] Grizzly-3 development milestone available (Keystone, Glance, Nova, Horizon, Quantum, Cinder)
Cool! Grizzly G3 is on Raring Ringtail! I'm seeing lots of AWESOME new packages here! Like Ajax Console, SPICE proxy, Ceilometer, Nova Cells and Baremetal and go on... But, no Heat package available... Is Heat a requirement to run Grizzly G3? Or can I start testing it now with those packages? Will Grizzly be available for Ubuntu 12.04 with all those features (Ceilometer, Ajax Console, SPICE and etc)? Tks! Thiago On 22 February 2013 10:49, Chuck Short chuck.sh...@canonical.com wrote: Hi. On 13-02-22 06:16 AM, Martinx - ジェームズ wrote: Hi! What is the status of Openstack Grizzly-3 Ubuntu packages? They will be uploaded to today for raring, precise should be uploaded a couple of hours later Can we already set it up using apt-get / aptitude? With packaged Heat, Ceilometer and etc? Yes Which version is recommended to test Grizzly-3, Precise (via testing UCA), Raring? Raring is the most easiest and fastest Is Grizzly planed to be the default Openstack for Raring? Yes Thanks for the AWESOME work on Openstack! Regards, Thiago On 22 February 2013 05:47, Thierry Carrez thie...@openstack.org mailto: thie...@openstack.org** wrote: Hi everyone, The last milestone of the Grizzly development cycle, grizzly-3 is now available for testing. This milestone contains almost all of the features that will be shipped in the final 2013.1 (Grizzly) release on April 4, 2013. This was an extremely busy milestone, with 100 blueprints implemented and more than 450 bugfixes overall. You can find the full list of new features and fixed bugs, as well as tarball downloads, at: https://launchpad.net/**keystone/grizzly/grizzly-3https://launchpad.net/keystone/grizzly/grizzly-3 https://launchpad.net/glance/**grizzly/grizzly-3https://launchpad.net/glance/grizzly/grizzly-3 https://launchpad.net/nova/**grizzly/grizzly-3https://launchpad.net/nova/grizzly/grizzly-3 https://launchpad.net/horizon/**grizzly/grizzly-3https://launchpad.net/horizon/grizzly/grizzly-3 https://launchpad.net/quantum/**grizzly/grizzly-3https://launchpad.net/quantum/grizzly/grizzly-3 https://launchpad.net/cinder/**grizzly/grizzly-3https://launchpad.net/cinder/grizzly/grizzly-3 Those projects are now temporarily feature-frozen (apart from already-granted exceptions) as we switch to testing and bugfixing mode in preparation for our first release candidates. Please test, try the new features, report bugs and help fix them ! Regards, -- Thierry Carrez (ttx) Release Manager, OpenStack __**_ Mailing list: https://launchpad.net/~**openstackhttps://launchpad.net/~openstack https://launchpad.net/%**7Eopenstackhttps://launchpad.net/%7Eopenstack Post to : openstack@lists.launchpad.net mailto:openstack@lists.**launchpad.netopenstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~**openstackhttps://launchpad.net/~openstack https://launchpad.net/%**7Eopenstackhttps://launchpad.net/%7Eopenstack More help : https://help.launchpad.net/**ListHelphttps://help.launchpad.net/ListHelp __**_ 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/~**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
Re: [Openstack] Grizzly-3 development milestone available (Keystone, Glance, Nova, Horizon, Quantum, Cinder)
Hi! What is the status of Openstack Grizzly-3 Ubuntu packages? Can we already set it up using apt-get / aptitude? With packaged Heat, Ceilometer and etc? Which version is recommended to test Grizzly-3, Precise (via testing UCA), Raring? Is Grizzly planed to be the default Openstack for Raring? Thanks for the AWESOME work on Openstack! Regards, Thiago On 22 February 2013 05:47, Thierry Carrez thie...@openstack.org wrote: Hi everyone, The last milestone of the Grizzly development cycle, grizzly-3 is now available for testing. This milestone contains almost all of the features that will be shipped in the final 2013.1 (Grizzly) release on April 4, 2013. This was an extremely busy milestone, with 100 blueprints implemented and more than 450 bugfixes overall. You can find the full list of new features and fixed bugs, as well as tarball downloads, at: https://launchpad.net/keystone/grizzly/grizzly-3 https://launchpad.net/glance/grizzly/grizzly-3 https://launchpad.net/nova/grizzly/grizzly-3 https://launchpad.net/horizon/grizzly/grizzly-3 https://launchpad.net/quantum/grizzly/grizzly-3 https://launchpad.net/cinder/grizzly/grizzly-3 Those projects are now temporarily feature-frozen (apart from already-granted exceptions) as we switch to testing and bugfixing mode in preparation for our first release candidates. Please test, try the new features, report bugs and help fix them ! Regards, -- Thierry Carrez (ttx) Release Manager, OpenStack ___ 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] Getting the 2012.2.3 release in Ubuntu
+10 for 2012.2.3 @ Ubuntu Cloud Archives! On 11 February 2013 18:48, Logan McNaughton lo...@bacoosta.com wrote: Hi, I've added the Ubuntu Cloud Archive to my apt sources, however it looks like the latest release there is 2012.2.1. How can I get the latest 2012.2.3 release in Ubuntu 12.04? ___ 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] [Quantum] Unable to install Quantum DHCP and L3 agents
Before run apt-get update, run apt-get install ubuntu-cloud-keyring On 6 February 2013 05:06, Veera Reddy veerare...@gmail.com wrote: Hi Trinath, Before installing folsom To Below Step Edit */etc/apt/sources.list.d/cloud-archive.list *: deb http://ubuntu-cloud.archive.canonical.com/ubuntuprecise-updates/folsom main Upgrade the system (and reboot if you need) : apt-get update apt-get upgrade Regards, Veera. On Wed, Feb 6, 2013 at 12:30 PM, Trinath Somanchi trinath.soman...@gmail.com wrote: Hi- When I install Quantum DHCP and L3 agents. I get this error root@NewFolsomController:~# apt-get install quantum-plugin-openvswitch-agent quantum-dhcp-agent quantum-l3-agent Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package quantum-dhcp-agent E: Unable to locate package quantum-l3-agent Kindly help me resolve the issue -- Regards, -- Trinath Somanchi, +91 9866 235 130 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Regards, VeeraReddy.B 9959236555. ___ 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] Cinder-volume doesn't start anymore...
John, I reinstalled it from scratch, using TGT now. Everything seems to be running fine now. Do you think that it worth try to identify this problem or just forget it? I can try to reproduce it. Thank you! Thiago On 3 February 2013 03:13, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Hi John! Thank you for your support! My answers are at the bottom. On 2 February 2013 22:51, John Griffith john.griff...@solidfire.comwrote: On Sat, Feb 2, 2013 at 1:34 PM, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: No one can help me with this? My cinder-volume process is completely down. I don't know what I can do to fix this issue... Thanks! Thiago On 1 February 2013 19:49, Martinx - ジェームズ thiagocmarti...@gmail.comwrote: Guys, At first, tgt was running after one controller.teste.com reboot but, I know I'm using ietd, so, I stop tgt and remove the init script of if and started ietd manually... But cinder doesn't start up anymore... :( I really appreciate any kind of help here... Someone on IRC channel told me that Cinder is trying to use _get_target function in the TargetAdmin class but, how can Cinder use tgt if iscsi_helper = ietadm ? Best, Thiago On 1 February 2013 19:20, Martinx - ジェームズ thiagocmarti...@gmail.comwrote: Guys, At my Cinder logs, I'm seeing this when I run /etc/init.d/cinder-volume start: 2013-02-01 18:16:20 1075 AUDIT cinder.service [-] Starting cinder-volume node (version 2012.2.1-LOCALBRANCH:LOCALREVISION) 2013-02-01 18:16:21 DEBUG cinder.utils [req-1ebb9638-2300-456a-995e-382c96f6632d None None] Running cmd (subprocess): sudo cinder-rootwrap /etc/cinder/rootwrap.conf vgs --noheadings -o name execute /usr/lib/python2.7/dist-packages/cinder/utils.py:163 2013-02-01 18:16:22 DEBUG cinder.utils [req-1ebb9638-2300-456a-995e-382c96f6632d None None] backend module 'cinder.db.sqlalchemy.api' from '/usr/lib/python2.7/dist-packages/cinder/db/sqlalchemy/api.pyc' __get_backend /usr/lib/python2.7/dist-packages/cinder/utils.py:477 2013-02-01 18:16:23 DEBUG cinder.volume.manager [req-1ebb9638-2300-456a-995e-382c96f6632d None None] Re-exporting 1 volumes init_host /usr/lib/python2.7/dist-packages/cinder/volume/manager.py:98 2013-02-01 18:16:23 1075 CRITICAL cinder [-] Got unknown keyword args to utils.execute: {'old_name': None} 2013-02-01 18:16:23 1075 TRACE cinder Traceback (most recent call last): 2013-02-01 18:16:23 1075 TRACE cinder File /usr/bin/cinder-volume, line 48, in module 2013-02-01 18:16:23 1075 TRACE cinder service.wait() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/service.py, line 422, in wait 2013-02-01 18:16:23 1075 TRACE cinder _launcher.wait() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/service.py, line 127, in wait 2013-02-01 18:16:23 1075 TRACE cinder service.wait() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/eventlet/greenthread.py, line 166, in wait 2013-02-01 18:16:23 1075 TRACE cinder return self._exit_event.wait() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/eventlet/event.py, line 116, in wait 2013-02-01 18:16:23 1075 TRACE cinder return hubs.get_hub().switch() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/eventlet/hubs/hub.py, line 177, in switch 2013-02-01 18:16:23 1075 TRACE cinder return self.greenlet.switch() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/eventlet/greenthread.py, line 192, in main 2013-02-01 18:16:23 1075 TRACE cinder result = function(*args, **kwargs) 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/service.py, line 88, in run_server 2013-02-01 18:16:23 1075 TRACE cinder server.start() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/service.py, line 159, in start 2013-02-01 18:16:23 1075 TRACE cinder self.manager.init_host() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/volume/manager.py, line 101, in init_host 2013-02-01 18:16:23 1075 TRACE cinder self.driver.ensure_export(ctxt, volume) 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/volume/driver.py, line 352, in ensure_export 2013-02-01 18:16:23 1075 TRACE cinder old_name=old_name) 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/volume/iscsi.py, line 198, in create_iscsi_target 2013-02-01 18:16:23 1075 TRACE cinder self._new_target(name, tid, **kwargs) 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/volume/iscsi.py, line 211, in _new_target 2013-02-01 18:16:23 1075 TRACE cinder **kwargs) 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/volume/iscsi.py
[Openstack] How to completely disable Floating IPs?
Guys, I have no plans to use the so called Floating IPs in my Cloud Computing environment. Mostly because I'll focus only on IPv6. I do not have any plans to support IPv4 anymore. So, how can I completely disable the Floating IPs from Openstack? Is there a (nova.conf) option like: floating_ips = False that removes everything related to it, from Dashboard and etc...? Thanks! Thiago ___ 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-volume doesn't start anymore...
No one can help me with this? My cinder-volume process is completely down. I don't know what I can do to fix this issue... Thanks! Thiago On 1 February 2013 19:49, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Guys, At first, tgt was running after one controller.teste.com reboot but, I know I'm using ietd, so, I stop tgt and remove the init script of if and started ietd manually... But cinder doesn't start up anymore... :( I really appreciate any kind of help here... Someone on IRC channel told me that Cinder is trying to use _get_target function in the TargetAdmin class but, how can Cinder use tgt if iscsi_helper = ietadm ? Best, Thiago On 1 February 2013 19:20, Martinx - ジェームズ thiagocmarti...@gmail.comwrote: Guys, At my Cinder logs, I'm seeing this when I run /etc/init.d/cinder-volume start: 2013-02-01 18:16:20 1075 AUDIT cinder.service [-] Starting cinder-volume node (version 2012.2.1-LOCALBRANCH:LOCALREVISION) 2013-02-01 18:16:21 DEBUG cinder.utils [req-1ebb9638-2300-456a-995e-382c96f6632d None None] Running cmd (subprocess): sudo cinder-rootwrap /etc/cinder/rootwrap.conf vgs --noheadings -o name execute /usr/lib/python2.7/dist-packages/cinder/utils.py:163 2013-02-01 18:16:22 DEBUG cinder.utils [req-1ebb9638-2300-456a-995e-382c96f6632d None None] backend module 'cinder.db.sqlalchemy.api' from '/usr/lib/python2.7/dist-packages/cinder/db/sqlalchemy/api.pyc' __get_backend /usr/lib/python2.7/dist-packages/cinder/utils.py:477 2013-02-01 18:16:23 DEBUG cinder.volume.manager [req-1ebb9638-2300-456a-995e-382c96f6632d None None] Re-exporting 1 volumes init_host /usr/lib/python2.7/dist-packages/cinder/volume/manager.py:98 2013-02-01 18:16:23 1075 CRITICAL cinder [-] Got unknown keyword args to utils.execute: {'old_name': None} 2013-02-01 18:16:23 1075 TRACE cinder Traceback (most recent call last): 2013-02-01 18:16:23 1075 TRACE cinder File /usr/bin/cinder-volume, line 48, in module 2013-02-01 18:16:23 1075 TRACE cinder service.wait() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/service.py, line 422, in wait 2013-02-01 18:16:23 1075 TRACE cinder _launcher.wait() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/service.py, line 127, in wait 2013-02-01 18:16:23 1075 TRACE cinder service.wait() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/eventlet/greenthread.py, line 166, in wait 2013-02-01 18:16:23 1075 TRACE cinder return self._exit_event.wait() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/eventlet/event.py, line 116, in wait 2013-02-01 18:16:23 1075 TRACE cinder return hubs.get_hub().switch() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/eventlet/hubs/hub.py, line 177, in switch 2013-02-01 18:16:23 1075 TRACE cinder return self.greenlet.switch() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/eventlet/greenthread.py, line 192, in main 2013-02-01 18:16:23 1075 TRACE cinder result = function(*args, **kwargs) 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/service.py, line 88, in run_server 2013-02-01 18:16:23 1075 TRACE cinder server.start() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/service.py, line 159, in start 2013-02-01 18:16:23 1075 TRACE cinder self.manager.init_host() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/volume/manager.py, line 101, in init_host 2013-02-01 18:16:23 1075 TRACE cinder self.driver.ensure_export(ctxt, volume) 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/volume/driver.py, line 352, in ensure_export 2013-02-01 18:16:23 1075 TRACE cinder old_name=old_name) 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/volume/iscsi.py, line 198, in create_iscsi_target 2013-02-01 18:16:23 1075 TRACE cinder self._new_target(name, tid, **kwargs) 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/volume/iscsi.py, line 211, in _new_target 2013-02-01 18:16:23 1075 TRACE cinder **kwargs) 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/volume/iscsi.py, line 60, in _run 2013-02-01 18:16:23 1075 TRACE cinder self._execute(self._cmd, *args, run_as_root=True, **kwargs) 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/utils.py, line 142, in execute 2013-02-01 18:16:23 1075 TRACE cinder 'to utils.execute: %r') % kwargs) 2013-02-01 18:16:23 1075 TRACE cinder Error: Got unknown keyword args to utils.execute: {'old_name': None} 2013-02-01 18:16:23 1075 TRACE cinder My cinder.conf contains: [DEFAULT] sql_connection = mysql
[Openstack] Cinder-volume doesn't start anymore...
Guys, At my Cinder logs, I'm seeing this when I run /etc/init.d/cinder-volume start: 2013-02-01 18:16:20 1075 AUDIT cinder.service [-] Starting cinder-volume node (version 2012.2.1-LOCALBRANCH:LOCALREVISION) 2013-02-01 18:16:21 DEBUG cinder.utils [req-1ebb9638-2300-456a-995e-382c96f6632d None None] Running cmd (subprocess): sudo cinder-rootwrap /etc/cinder/rootwrap.conf vgs --noheadings -o name execute /usr/lib/python2.7/dist-packages/cinder/utils.py:163 2013-02-01 18:16:22 DEBUG cinder.utils [req-1ebb9638-2300-456a-995e-382c96f6632d None None] backend module 'cinder.db.sqlalchemy.api' from '/usr/lib/python2.7/dist-packages/cinder/db/sqlalchemy/api.pyc' __get_backend /usr/lib/python2.7/dist-packages/cinder/utils.py:477 2013-02-01 18:16:23 DEBUG cinder.volume.manager [req-1ebb9638-2300-456a-995e-382c96f6632d None None] Re-exporting 1 volumes init_host /usr/lib/python2.7/dist-packages/cinder/volume/manager.py:98 2013-02-01 18:16:23 1075 CRITICAL cinder [-] Got unknown keyword args to utils.execute: {'old_name': None} 2013-02-01 18:16:23 1075 TRACE cinder Traceback (most recent call last): 2013-02-01 18:16:23 1075 TRACE cinder File /usr/bin/cinder-volume, line 48, in module 2013-02-01 18:16:23 1075 TRACE cinder service.wait() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/service.py, line 422, in wait 2013-02-01 18:16:23 1075 TRACE cinder _launcher.wait() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/service.py, line 127, in wait 2013-02-01 18:16:23 1075 TRACE cinder service.wait() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/eventlet/greenthread.py, line 166, in wait 2013-02-01 18:16:23 1075 TRACE cinder return self._exit_event.wait() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/eventlet/event.py, line 116, in wait 2013-02-01 18:16:23 1075 TRACE cinder return hubs.get_hub().switch() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/eventlet/hubs/hub.py, line 177, in switch 2013-02-01 18:16:23 1075 TRACE cinder return self.greenlet.switch() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/eventlet/greenthread.py, line 192, in main 2013-02-01 18:16:23 1075 TRACE cinder result = function(*args, **kwargs) 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/service.py, line 88, in run_server 2013-02-01 18:16:23 1075 TRACE cinder server.start() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/service.py, line 159, in start 2013-02-01 18:16:23 1075 TRACE cinder self.manager.init_host() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/volume/manager.py, line 101, in init_host 2013-02-01 18:16:23 1075 TRACE cinder self.driver.ensure_export(ctxt, volume) 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/volume/driver.py, line 352, in ensure_export 2013-02-01 18:16:23 1075 TRACE cinder old_name=old_name) 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/volume/iscsi.py, line 198, in create_iscsi_target 2013-02-01 18:16:23 1075 TRACE cinder self._new_target(name, tid, **kwargs) 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/volume/iscsi.py, line 211, in _new_target 2013-02-01 18:16:23 1075 TRACE cinder **kwargs) 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/volume/iscsi.py, line 60, in _run 2013-02-01 18:16:23 1075 TRACE cinder self._execute(self._cmd, *args, run_as_root=True, **kwargs) 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/utils.py, line 142, in execute 2013-02-01 18:16:23 1075 TRACE cinder 'to utils.execute: %r') % kwargs) 2013-02-01 18:16:23 1075 TRACE cinder Error: Got unknown keyword args to utils.execute: {'old_name': None} 2013-02-01 18:16:23 1075 TRACE cinder My cinder.conf contains: [DEFAULT] sql_connection = mysql://cinderUser:cinderp...@controller.teste.com/cinder rootwrap_config = /etc/cinder/rootwrap.conf api_paste_confg = /etc/cinder/api-paste.ini iscsi_helper = ietadm volume_name_template = volume-%s volume_group = cinder-volumes verbose = True auth_strategy = keystone #osapi_volume_listen_port=5900 --- My /etc/cinder/api-paste.ini relevant parts: [filter:authtoken] paste.filter_factory = keystone.middleware.auth_token:filter_factory service_protocol = http service_host = controller.teste.com service_port = 5000 auth_host = controller.teste.com auth_port = 35357 auth_protocol = http admin_tenant_name = service admin_user = cinder admin_password = service_pass The controller.teste.com host resolution is okay (IP 10.32.14.232). It was working yesterday, volumes creation, attaching, deleting, etc...=( I'm using
Re: [Openstack] Cinder-volume doesn't start anymore...
BTW, Just for the record, 1 cinder volume that I created yesterday just DISAPPEAR!!! lvdisplay shows nothing, cinder-volumes is empty... Can you guys imagine the cinder deleting my client's persistent storage without any command??? I'm glad that this is just a PoC. Tks, Thiago On 1 February 2013 19:20, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Guys, At my Cinder logs, I'm seeing this when I run /etc/init.d/cinder-volume start: 2013-02-01 18:16:20 1075 AUDIT cinder.service [-] Starting cinder-volume node (version 2012.2.1-LOCALBRANCH:LOCALREVISION) 2013-02-01 18:16:21 DEBUG cinder.utils [req-1ebb9638-2300-456a-995e-382c96f6632d None None] Running cmd (subprocess): sudo cinder-rootwrap /etc/cinder/rootwrap.conf vgs --noheadings -o name execute /usr/lib/python2.7/dist-packages/cinder/utils.py:163 2013-02-01 18:16:22 DEBUG cinder.utils [req-1ebb9638-2300-456a-995e-382c96f6632d None None] backend module 'cinder.db.sqlalchemy.api' from '/usr/lib/python2.7/dist-packages/cinder/db/sqlalchemy/api.pyc' __get_backend /usr/lib/python2.7/dist-packages/cinder/utils.py:477 2013-02-01 18:16:23 DEBUG cinder.volume.manager [req-1ebb9638-2300-456a-995e-382c96f6632d None None] Re-exporting 1 volumes init_host /usr/lib/python2.7/dist-packages/cinder/volume/manager.py:98 2013-02-01 18:16:23 1075 CRITICAL cinder [-] Got unknown keyword args to utils.execute: {'old_name': None} 2013-02-01 18:16:23 1075 TRACE cinder Traceback (most recent call last): 2013-02-01 18:16:23 1075 TRACE cinder File /usr/bin/cinder-volume, line 48, in module 2013-02-01 18:16:23 1075 TRACE cinder service.wait() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/service.py, line 422, in wait 2013-02-01 18:16:23 1075 TRACE cinder _launcher.wait() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/service.py, line 127, in wait 2013-02-01 18:16:23 1075 TRACE cinder service.wait() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/eventlet/greenthread.py, line 166, in wait 2013-02-01 18:16:23 1075 TRACE cinder return self._exit_event.wait() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/eventlet/event.py, line 116, in wait 2013-02-01 18:16:23 1075 TRACE cinder return hubs.get_hub().switch() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/eventlet/hubs/hub.py, line 177, in switch 2013-02-01 18:16:23 1075 TRACE cinder return self.greenlet.switch() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/eventlet/greenthread.py, line 192, in main 2013-02-01 18:16:23 1075 TRACE cinder result = function(*args, **kwargs) 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/service.py, line 88, in run_server 2013-02-01 18:16:23 1075 TRACE cinder server.start() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/service.py, line 159, in start 2013-02-01 18:16:23 1075 TRACE cinder self.manager.init_host() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/volume/manager.py, line 101, in init_host 2013-02-01 18:16:23 1075 TRACE cinder self.driver.ensure_export(ctxt, volume) 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/volume/driver.py, line 352, in ensure_export 2013-02-01 18:16:23 1075 TRACE cinder old_name=old_name) 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/volume/iscsi.py, line 198, in create_iscsi_target 2013-02-01 18:16:23 1075 TRACE cinder self._new_target(name, tid, **kwargs) 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/volume/iscsi.py, line 211, in _new_target 2013-02-01 18:16:23 1075 TRACE cinder **kwargs) 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/volume/iscsi.py, line 60, in _run 2013-02-01 18:16:23 1075 TRACE cinder self._execute(self._cmd, *args, run_as_root=True, **kwargs) 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/utils.py, line 142, in execute 2013-02-01 18:16:23 1075 TRACE cinder 'to utils.execute: %r') % kwargs) 2013-02-01 18:16:23 1075 TRACE cinder Error: Got unknown keyword args to utils.execute: {'old_name': None} 2013-02-01 18:16:23 1075 TRACE cinder My cinder.conf contains: [DEFAULT] sql_connection = mysql://cinderUser:cinderp...@controller.teste.com/cinder rootwrap_config = /etc/cinder/rootwrap.conf api_paste_confg = /etc/cinder/api-paste.ini iscsi_helper = ietadm volume_name_template = volume-%s volume_group = cinder-volumes verbose = True auth_strategy = keystone #osapi_volume_listen_port=5900 --- My /etc/cinder/api-paste.ini relevant parts: [filter:authtoken
Re: [Openstack] Cinder-volume doesn't start anymore...
Guys, forger about my previous message: On 1 February 2013 19:25, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: BTW, Just for the record, 1 cinder volume that I created yesterday just DISAPPEAR!!! lvdisplay shows nothing, cinder-volumes is empty... Can you guys imagine the cinder deleting my client's persistent storage without any command??? I'm glad that this is just a PoC. Tks, Thiago On 1 February 2013 19:20, Martinx - ジェームズ thiagocmarti...@gmail.comwrote: Guys, At my Cinder logs, I'm seeing this when I run /etc/init.d/cinder-volume start: 2013-02-01 18:16:20 1075 AUDIT cinder.service [-] Starting cinder-volume node (version 2012.2.1-LOCALBRANCH:LOCALREVISION) 2013-02-01 18:16:21 DEBUG cinder.utils [req-1ebb9638-2300-456a-995e-382c96f6632d None None] Running cmd (subprocess): sudo cinder-rootwrap /etc/cinder/rootwrap.conf vgs --noheadings -o name execute /usr/lib/python2.7/dist-packages/cinder/utils.py:163 2013-02-01 18:16:22 DEBUG cinder.utils [req-1ebb9638-2300-456a-995e-382c96f6632d None None] backend module 'cinder.db.sqlalchemy.api' from '/usr/lib/python2.7/dist-packages/cinder/db/sqlalchemy/api.pyc' __get_backend /usr/lib/python2.7/dist-packages/cinder/utils.py:477 2013-02-01 18:16:23 DEBUG cinder.volume.manager [req-1ebb9638-2300-456a-995e-382c96f6632d None None] Re-exporting 1 volumes init_host /usr/lib/python2.7/dist-packages/cinder/volume/manager.py:98 2013-02-01 18:16:23 1075 CRITICAL cinder [-] Got unknown keyword args to utils.execute: {'old_name': None} 2013-02-01 18:16:23 1075 TRACE cinder Traceback (most recent call last): 2013-02-01 18:16:23 1075 TRACE cinder File /usr/bin/cinder-volume, line 48, in module 2013-02-01 18:16:23 1075 TRACE cinder service.wait() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/service.py, line 422, in wait 2013-02-01 18:16:23 1075 TRACE cinder _launcher.wait() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/service.py, line 127, in wait 2013-02-01 18:16:23 1075 TRACE cinder service.wait() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/eventlet/greenthread.py, line 166, in wait 2013-02-01 18:16:23 1075 TRACE cinder return self._exit_event.wait() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/eventlet/event.py, line 116, in wait 2013-02-01 18:16:23 1075 TRACE cinder return hubs.get_hub().switch() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/eventlet/hubs/hub.py, line 177, in switch 2013-02-01 18:16:23 1075 TRACE cinder return self.greenlet.switch() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/eventlet/greenthread.py, line 192, in main 2013-02-01 18:16:23 1075 TRACE cinder result = function(*args, **kwargs) 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/service.py, line 88, in run_server 2013-02-01 18:16:23 1075 TRACE cinder server.start() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/service.py, line 159, in start 2013-02-01 18:16:23 1075 TRACE cinder self.manager.init_host() 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/volume/manager.py, line 101, in init_host 2013-02-01 18:16:23 1075 TRACE cinder self.driver.ensure_export(ctxt, volume) 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/volume/driver.py, line 352, in ensure_export 2013-02-01 18:16:23 1075 TRACE cinder old_name=old_name) 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/volume/iscsi.py, line 198, in create_iscsi_target 2013-02-01 18:16:23 1075 TRACE cinder self._new_target(name, tid, **kwargs) 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/volume/iscsi.py, line 211, in _new_target 2013-02-01 18:16:23 1075 TRACE cinder **kwargs) 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/volume/iscsi.py, line 60, in _run 2013-02-01 18:16:23 1075 TRACE cinder self._execute(self._cmd, *args, run_as_root=True, **kwargs) 2013-02-01 18:16:23 1075 TRACE cinder File /usr/lib/python2.7/dist-packages/cinder/utils.py, line 142, in execute 2013-02-01 18:16:23 1075 TRACE cinder 'to utils.execute: %r') % kwargs) 2013-02-01 18:16:23 1075 TRACE cinder Error: Got unknown keyword args to utils.execute: {'old_name': None} 2013-02-01 18:16:23 1075 TRACE cinder My cinder.conf contains: [DEFAULT] sql_connection = mysql:// cinderUser:cinderp...@controller.teste.com/cinder rootwrap_config = /etc/cinder/rootwrap.conf api_paste_confg = /etc/cinder/api-paste.ini iscsi_helper = ietadm volume_name_template = volume-%s volume_group = cinder-volumes verbose = True auth_strategy
Re: [Openstack] Copy glance image to cinder bootable volumes - copy_image_to_volume
What I just did to successfully boot from a volume: 1- Create a KVM Virtual Machine on top of a LVM Logical Volume of 2.5G as its HD (disk type block - /dev/volgrp0/vmname-disk0); 2- Install your favorite OS; 3- shutdown it; 4- make a image of it: dd if=/dev/volgrp0/vmname-disk0 of=myfavorite-os.img; 5- copy it to your Cinder server: scp myfavorite-os.img to the server where your cinder-volumes LVM VG resides; 6- make a volume of ~5G via Openstack Dashboard or CLI; 7- find your cloud cinder volume on the Cinder server: lvdisplay 8- import your 2.5G image (myfavorite-os.img) into your Cinder volume: dd if=/path/of/myfavorite-os.img of=/dev/cinder-volumes/volume-a2fb85b1-512e-402b-9aaf-6ce1914295a4; 9- start a instance using any image as source (cirros) and choose to boot from this volume (a2fb85b1-512e-402b-9aaf-6ce1914295a4). The image source (cirros) will be ignored, I think... That's it! NOTE: If you can run a KVM VM on the same server of your Cinder, you can shrink part of this procedure, by doing it more directly: dd if=/dev/volgrp0/vmname-disk0 of=/dev/cinder-volumes/volume-a2fb85b1-512e-402b-9aaf-6ce1914295a4 on step 4 (your cinder volume must be ready on that point). I prefer to make specific flavors to use with my boot-from-volume Instances. Best! Thiago On 30 January 2013 13:06, Avishay Traeger avis...@il.ibm.com wrote: Lei Zhang zhang.lei@gmail.com wrote on 01/30/2013 04:39:22 PM: I also have a question. What's the requirement for the image? I found nothing int the doc. Hi, The requirements that I can think of off the top of my head are: 1. The image should be bootable 2. The image is converted to raw before being written to the volume, so it should be a format the 'qemu-img' understands (raw, qcow2, vmdk, vdi) 3. There must be sufficient space to write the raw version of the image Thanks, Avishay ___ 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] Copy glance image to cinder bootable volumes - copy_image_to_volume
BTW! On the step 2, if you install a Ubuntu Minimal Virtual Machine, select Guided LVM Partitioning. This way, when you make a 5~10~50G boot-volume, you'll be able to easily grow your Ubuntu file systems (from 2.5G inicial) using its internal LVM (try parted instead of fdisk/cfdisk!)... You'll see extra HD space to make more primary/extended/GPT partitions... Cheers! Thiago On 30 January 2013 16:47, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: What I just did to successfully boot from a volume: 1- Create a KVM Virtual Machine on top of a LVM Logical Volume of 2.5G as its HD (disk type block - /dev/volgrp0/vmname-disk0); 2- Install your favorite OS; 3- shutdown it; 4- make a image of it: dd if=/dev/volgrp0/vmname-disk0 of=myfavorite-os.img; 5- copy it to your Cinder server: scp myfavorite-os.img to the server where your cinder-volumes LVM VG resides; 6- make a volume of ~5G via Openstack Dashboard or CLI; 7- find your cloud cinder volume on the Cinder server: lvdisplay 8- import your 2.5G image (myfavorite-os.img) into your Cinder volume: dd if=/path/of/myfavorite-os.img of=/dev/cinder-volumes/volume-a2fb85b1-512e-402b-9aaf-6ce1914295a4; 9- start a instance using any image as source (cirros) and choose to boot from this volume (a2fb85b1-512e-402b-9aaf-6ce1914295a4). The image source (cirros) will be ignored, I think... That's it! NOTE: If you can run a KVM VM on the same server of your Cinder, you can shrink part of this procedure, by doing it more directly: dd if=/dev/volgrp0/vmname-disk0 of=/dev/cinder-volumes/volume-a2fb85b1-512e-402b-9aaf-6ce1914295a4 on step 4 (your cinder volume must be ready on that point). I prefer to make specific flavors to use with my boot-from-volume Instances. Best! Thiago On 30 January 2013 13:06, Avishay Traeger avis...@il.ibm.com wrote: Lei Zhang zhang.lei@gmail.com wrote on 01/30/2013 04:39:22 PM: I also have a question. What's the requirement for the image? I found nothing int the doc. Hi, The requirements that I can think of off the top of my head are: 1. The image should be bootable 2. The image is converted to raw before being written to the volume, so it should be a format the 'qemu-img' understands (raw, qcow2, vmdk, vdi) 3. There must be sufficient space to write the raw version of the image Thanks, Avishay ___ 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] [heat] Grizzly-2 development milestone available for Heat
Hi! I just install Keystone and Glance on my Raring Ringtail controller node... Should I install Heat now? Or is it better to install it between? BTW, I'm using this guide to help me: https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/stable/GRE/OpenStack_Folsom_Install_Guide_WebVersion.rst- since it works great for Ubuntu 12.10... Thanks for the info! Best, Thiago On 15 January 2013 07:28, Steven Hardy sha...@redhat.com wrote: On Mon, Jan 14, 2013 at 01:20:09PM -0200, Martinx - ジェームズ wrote: Hi! Is Grizzly-2 available on Ubuntu Raring Ringtail (13.04) daily builds? Tks! Thiago Since your question is in response to the Heat Grizzly-2 announcement, I should point out that Heat is not packaged for Ubuntu (yet!), so you will have to download the tarball and install from source to evaluate this release. Tarball: https://launchpad.net/heat/grizzly/grizzly-2 Install procedure should be the similar to: http://wiki.openstack.org/Heat/GettingStartedUsingMasterOnUbuntu Assuming you already have a functional openstack installation, you can start at Install Heat from master and skip the git clone (just untar the tarball instead) This should be an interim solution as packaging for Ubuntu is in-progress: https://bugs.launchpad.net/heat/+bug/1083501 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
Re: [Openstack] [heat] Grizzly-2 development milestone available for Heat
Well, I'll try this in a few weeks... I just hit this: https://bugs.launchpad.net/ubuntu/+source/python-glanceclient/+bug/1098688 Don't know how to workaround it... :-/ Tks anyway! Thiago On 15 January 2013 10:18, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Hi! I just install Keystone and Glance on my Raring Ringtail controller node... Should I install Heat now? Or is it better to install it between? BTW, I'm using this guide to help me: https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/stable/GRE/OpenStack_Folsom_Install_Guide_WebVersion.rst- since it works great for Ubuntu 12.10... Thanks for the info! Best, Thiago On 15 January 2013 07:28, Steven Hardy sha...@redhat.com wrote: On Mon, Jan 14, 2013 at 01:20:09PM -0200, Martinx - ジェームズ wrote: Hi! Is Grizzly-2 available on Ubuntu Raring Ringtail (13.04) daily builds? Tks! Thiago Since your question is in response to the Heat Grizzly-2 announcement, I should point out that Heat is not packaged for Ubuntu (yet!), so you will have to download the tarball and install from source to evaluate this release. Tarball: https://launchpad.net/heat/grizzly/grizzly-2 Install procedure should be the similar to: http://wiki.openstack.org/Heat/GettingStartedUsingMasterOnUbuntu Assuming you already have a functional openstack installation, you can start at Install Heat from master and skip the git clone (just untar the tarball instead) This should be an interim solution as packaging for Ubuntu is in-progress: https://bugs.launchpad.net/heat/+bug/1083501 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
Re: [Openstack] [heat] Grizzly-2 development milestone available for Heat
Hi! Is Grizzly-2 available on Ubuntu Raring Ringtail (13.04) daily builds? Tks! Thiago On 10 January 2013 19:44, Steven Dake sd...@redhat.com wrote: Hi folks, The OpenStack release team has released the second milestone of the Grizzly development cycle (grizzly-2). This is a significant step in Heat's incubation, as it is our first milestone release leading to the final delivery of OpenStack 2013.1 scheduled for April 4, 2013. You can find the full list of new features and fixed bugs, as well as tarball downloads at: https://launchpad.net/heat/**grizzly/grizzly-2https://launchpad.net/heat/grizzly/grizzly-2 Features and bugs may be resolved until the next milestone, grizzly-3, which will be delivered on February 21st. Come join the growing orchestration development community by contributing to Heat and making orchestration in OpenStack world class! Regards -steve __**_ 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
Re: [Openstack] [heat] Grizzly-2 development milestone available for Heat
Yes! https://launchpad.net/ubuntu/raring/+source/nova :-P On 14 January 2013 13:20, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Hi! Is Grizzly-2 available on Ubuntu Raring Ringtail (13.04) daily builds? Tks! Thiago On 10 January 2013 19:44, Steven Dake sd...@redhat.com wrote: Hi folks, The OpenStack release team has released the second milestone of the Grizzly development cycle (grizzly-2). This is a significant step in Heat's incubation, as it is our first milestone release leading to the final delivery of OpenStack 2013.1 scheduled for April 4, 2013. You can find the full list of new features and fixed bugs, as well as tarball downloads at: https://launchpad.net/heat/**grizzly/grizzly-2https://launchpad.net/heat/grizzly/grizzly-2 Features and bugs may be resolved until the next milestone, grizzly-3, which will be delivered on February 21st. Come join the growing orchestration development community by contributing to Heat and making orchestration in OpenStack world class! Regards -steve __**_ 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] Instance doesn't get an IP (Folsom / Quantum)
Hello! I'm following this guide: http://docs.openstack.org/folsom/basic-install/content/basic-install_intro.html And I'm getting this from my Instance Log: -- cloud-init start-local running: Thu, 03 Jan 2013 04:20:52 +. up 8.53 seconds no instance data found in start-local cloud-init-nonet waiting 120 seconds for a network device. cloud-init-nonet gave up waiting for a network device. ci-info: lo : 1 127.0.0.1 255.0.0.0 . ci-info: eth0 : 1 . . fa:16:3e:83:06:4f route_info failed Waiting for network configuration... Waiting up to 60 more seconds for network configuration... Booting system without full network configuration... -- I already tried this guide more than 10 times, always from scratch and everytime I hit this problem. I'm using Ubuntu 12.04 with Ubuntu Cloud Archives enabled. What can I do? Thanks! Thiago ___ 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] Instance doesn't get an IP (Folsom / Quantum)
Hi Gary! Thank you for your fast answer! 1. The plugin described on that guide; 2. quantum-server running on folsom-controller; quantum-plugin-openvswitch / quantum-plugin-openvswitch-agent installed and/or running within the three nodes; quantum-dhcp-agent running on folsom-network; quantum-l3-agent running on folsom-network. 3. Can't find any errors on quantum log files, debug enabled on all nodes. What kind of message can I look for? 4. ovs-vsctl show output (no Instance running right now): --- root@folsom-controller:~# ovs-vsctl show 218d7774-104c-4d2d-ae9e-9a8dd9ca2450 Bridge br-tun Port patch-int Interface patch-int type: patch options: {peer=patch-tun} Port br-tun Interface br-tun type: internal ovs_version: 1.4.0+build0 root@folsom-network:~# ovs-vsctl show b8b94a53-3294-44ba-855e-002af8fa80ba Bridge br-tun Port patch-int Interface patch-int type: patch options: {peer=patch-tun} Port gre-2 Interface gre-2 type: gre options: {in_key=flow, out_key=flow, remote_ip=10.0.0.2} Port br-tun Interface br-tun type: internal Bridge br-ex Port eth2 Interface eth2 Port br-ex Interface br-ex type: internal Port qg-168da5ed-dd Interface qg-168da5ed-dd type: internal Bridge br-int Port tapa0f18fc7-bc tag: 1 Interface tapa0f18fc7-bc type: internal Port br-int Interface br-int type: internal Port qr-a8d8fda3-d7 tag: 1 Interface qr-a8d8fda3-d7 type: internal Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} ovs_version: 1.4.0+build0 root@folsom-compute:~# ovs-vsctl show 86ff13f6-960d-48c5-8e03-e8d688364dd0 Bridge br-tun Port patch-int Interface patch-int type: patch options: {peer=patch-tun} Port gre-1 Interface gre-1 type: gre options: {in_key=flow, out_key=flow, remote_ip=10.10.10.1} Port br-tun Interface br-tun type: internal Bridge br-int Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} Port br-int Interface br-int type: internal ovs_version: 1.4.0+build0 --- I followed that guide word by word. With a few changes (because I found errors and missing informations on that guide) between the tries... Always with the same result. BTW, I made a lots of comments on that guide webpage (I am Thiago Martins)... Thank you! Thiago On 3 January 2013 06:38, Gary Kotton gkot...@redhat.com wrote: Hi, In order to be able to help can you please provide the following information: 1. Which plugin are you using? I assume that it is OpenvSwitch from the link :) 2. Are all of the Quantum services running: - quantum-server - quantum-openvswitch-agent - quantum-dhcp-agent 3. Can you please check if there are any messages in quantum log files? 4. Can you also please provide the ovs-vsctl show results (this shows the tap device attached to the ovs) Thanks Gary On 01/03/2013 10:26 AM, Martinx - ジェームズ wrote: Hello! I'm following this guide: http://docs.openstack.org/folsom/basic-install/content/basic-install_intro.html And I'm getting this from my Instance Log: -- cloud-init start-local running: Thu, 03 Jan 2013 04:20:52 +. up 8.53 seconds no instance data found in start-local cloud-init-nonet waiting 120 seconds for a network device. cloud-init-nonet gave up waiting for a network device. ci-info: lo : 1 127.0.0.1 255.0.0.0 . ci-info: eth0 : 1 . . fa:16:3e:83:06:4f route_info failed Waiting for network configuration... Waiting up to 60 more seconds for network configuration... Booting system without full network configuration... -- I already tried this guide more than 10 times, always from scratch and everytime I hit this problem. I'm using Ubuntu 12.04 with Ubuntu Cloud Archives enabled. What can I do? Thanks! Thiago ___ 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
Re: [Openstack] VMs not able to contact metadata service
Hi! My Instance doesn't get an IP... Don't know if it is related to this problem... I'm following this guide: http://docs.openstack.org/folsom/basic-install/content/basic-install_operate.html That guide uses Folsom / Quantum and, someone on IRC have said that my instance isn't able to reach metadata but, I have no idea about what's going on... Can someone enlighten me? I mean, if my problem is related to this or not? Thanks! Thiago On 3 January 2013 15:54, Mark McClain mark.mccl...@dreamhost.com wrote: Will- The metadata service in Folsom will only work when overlapping IP ranges are disabled (see: http://docs.openstack.org/trunk/openstack-network/admin/content/ch_limitations.html). For Grizzly, we have added metadata service for overlapping networks. This feature is currently available in devstack when you enable the q-meta service. mark On Jan 2, 2013, at 11:10 PM, Willard Dennis wden...@nec-labs.com wrote: Hello all, I am running Folsom with Quantum v2, via Devstack. Am trying to use Ubuntu UEC image to spawn VMs, but when the VM instance boots, it is not able to contact the metadata server in order to (among other things) inject the public key needed in order for me to be able to SSH into the instance. See http://paste.openstack.org/show/28764/ for a log snippet if needed. Following the (incorrect, bug reported) instructions found at http://docs.openstack.org/folsom/openstack-compute/admin/content/configuring-openstack-compute-basics.html#enabling-access-to-vms-on-the-compute-node(search for If you want to use the 10.04 Ubuntu Enterprise Cloud images to get to the instructions, and change the metadata port from the incorrect '8773' to the correct '8775') I added the rule into iptables, with no luck… I still cannot reach the metadata server at 169.254.169.254:80. When I dump the iptables rules for the 'nat' table, I see that my added rule is being hit, but it's still not working: $ sudo iptables -t nat -L -v -n Chain PREROUTING (policy ACCEPT 982 packets, 159K bytes) pkts bytes target prot opt in out source destination 210 27054 nova-compute-PREROUTING all -- * * 0.0.0.0/0 0.0.0.0/0 17 1020 DNAT tcp -- * * 0.0.0.0/0 169.254.169.254 tcp dpt:80 to:xxx.xx.xx.xx:8775(target IP addr redacted) 3078 520K nova-api-PREROUTING all -- * * 0.0.0.0/0 0.0.0.0/0 I searched and found this thread from this list: http://www.mail-archive.com/openstack@lists.launchpad.net/msg16569.html Does this mean that the Nova metadata service cannot be used with Quantum when using multiple tenant networks (L3 arch)? (this is the model that Devstack implements in my setup) If the above is true, can I revert to another supported configuration (and kindly give me a pointer as to how?) Finally, any plans to fix the metadata service so that it will work with Quantum's L3 service, and enable this out of the box with Devstack? (dare to dream :) Thanks and regards, Will ___ 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
Re: [Openstack] Potential filter scheduler enhancement
I have an idea for the scheduler improvement!! Since Linux have a new feature called Kernel SamePage Merging (KSM), which reduces the amount of RAM used by identical KVM Instances, the Openstack scheduler MUST take this into account. It is simple: * Start identical images on the same hypervisor (as possible). This will reduce the amount of RAM of our entire cloud environment. What do you guys think about it? Cheers! Thiago On 3 January 2013 16:48, Joseph Suh j...@isi.edu wrote: Phil, I agree with the suggestion. We wanted to instantiate a set of VMs whose hosts are located close each other. The current scheduler could not handle this use case since it needed to return optimal set of hosts at the same time. The first optimal host returned by the current scheduler may not be a part of the set of optimal hosts. We worked on the scheduler a little (in draft mode), and if you are interested in it, please let me know. Thanks, Joseph - Original Message - From: Vishvananda Ishaya vishvana...@gmail.com To: Phil Day philip@hp.com Cc: openstack@lists.launchpad.net (openstack@lists.launchpad.net) ( openstack@lists.launchpad.net) openstack@lists.launchpad.net Sent: Thursday, January 3, 2013 12:43:02 PM Subject: Re: [Openstack] Potential filter scheduler enhancement I think this seems reasonable, although FYI, openstack-dev seems like a better place for emails like this. Vish On Jan 3, 2013, at 6:40 AM, Day, Phil philip@hp.com wrote: Hi Folks, and Happy New Year. In working with the Filter Scheduler I’m considering an enhancement to make the final host selection stage configurable. Whilst its sometimes fine to just pick the first host from the list of weighted hosts, the more general case is that I’d like to be able to have the scheduler pick one of the first N hosts on the weighted list. The specific use cases that I have in mind are: - On a large system there is very rarely a single ideal / optimal host for a particular instance to be placed on. In practice any of the N most suitable hosts would be fine and allowing the scheduler to randomly pick one of these would add some spread for multiple requests that come in at the same time. (I know we now have the retry mechanism if a particular host can’t in fact handle a specific request – this is a complement to that rather an alternative). Of course anyone who wants to schedule to host in strict weighted order would be able to configure N to be 1 (or we could keep the current host selection method as a separate default) - When creating M instances in one request we could just put each onto one of the first M hosts in the list (since these have all been filtered as being suitable) instead of having to iterate through the filter / weighting functions for each successive instance. Based on this I’m thinking that such a host_selection function would replace the whole of the for loop at the end of the _schedule() method in filter_scheduler.py, and take as input the number of instances. The default function would of course be the current behaviour. Before going any further with this thinking I wanted to get input on: i) Do others recognise these use cases as being useful, and are there other similar use cases to be considered at the same time ? ii) Is it reasonable to make the filter scheduler configurable in this way, rather than creating a separate scheduler ? (My feeling is that because it would only be replacing ~10% of the current filter_scheduler code it would be better to not create a new scheduler) iii) Should the configuration logic for this new function be in the fliter_scheduler itself, or in the host_manager (which is where the filter and weighting functions are configured) ? Cheers, Phil ___ 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 ___ 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] [ovs-discuss] VLAN with OpenVswitch and Quantum
Hi! I'm reading this two guides now (Ubuntu 12.04 / Folsom): https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/stable/GRE/OpenStack_Folsom_Install_Guide_WebVersion.rst http://docwiki.cisco.com/wiki/Cisco_OpenStack_Edition:_Folsom_Manual_Install Both seems to use VLANs with openvswitch+quantum but, didn't test it yet. Maybe that can help you! Do not follow this guide: http://docs.openstack.org/folsom/basic-install/content/basic-install_intro.htmlsince it is a waste of time... Best, Thiago On 19 July 2012 01:53, Trinath Somanchi trinath.soman...@gmail.com wrote: Hi- I'm currently setting up VLAN setup with Quantum and OpenVswitch. I have an idea that, to tenants can configured/act as to different hosts. But being a newbee for this kind of setup, Can any one please guide me on How to bring up the VLAN setup using Quantum and OpenVswitch. Thanking you all Please guide me in this regard, -- Regards, -- Trinath Somanchi, +91 9866 235 130 ___ discuss mailing list disc...@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss ___ 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] [ovs-discuss] VLAN with OpenVswitch and Quantum
Hi Anne! I'll not give it up. I'm trying a very close guide, this one: https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/stable/GRE/OpenStack_Folsom_Install_Guide_WebVersion.rst After that, I'll try it again the basic_install and, if it works, I'll report in details my setup. Sorry if I'm being rude... Thanks! Thiago On 3 January 2013 23:12, Anne Gentle a...@openstack.org wrote: If you would like to help with documentation, it's better if you log doc bugs against existing documents. We are constantly trying to improve the documentation and we only accept documents that have been tested. Even so, we keep updating as we get more input by logging doc bugs. I don't believe you've tracked down the exact problem yet with the Basic Install, but let's not abandon it as it has worked for others. Thanks, Anne On Thu, Jan 3, 2013 at 2:24 PM, Martinx - ジェームズ thiagocmarti...@gmail.com wrote: Hi! I'm reading this two guides now (Ubuntu 12.04 / Folsom): https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/stable/GRE/OpenStack_Folsom_Install_Guide_WebVersion.rst http://docwiki.cisco.com/wiki/Cisco_OpenStack_Edition:_Folsom_Manual_Install Both seems to use VLANs with openvswitch+quantum but, didn't test it yet. Maybe that can help you! Do not follow this guide: http://docs.openstack.org/folsom/basic-install/content/basic-install_intro.htmlsince it is a waste of time... Best, Thiago On 19 July 2012 01:53, Trinath Somanchi trinath.soman...@gmail.comwrote: Hi- I'm currently setting up VLAN setup with Quantum and OpenVswitch. I have an idea that, to tenants can configured/act as to different hosts. But being a newbee for this kind of setup, Can any one please guide me on How to bring up the VLAN setup using Quantum and OpenVswitch. Thanking you all Please guide me in this regard, -- Regards, -- Trinath Somanchi, +91 9866 235 130 ___ discuss mailing list disc...@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss ___ 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