Re: [Openstack] [Cinder] Cinder snapshots
John Griffith john.griff...@solidfire.com wrote on 08/11/2012 19:58:39: Hi Avishay, So we have plans to improve some of this in the Grizzly release, here's a few thoughts: a. Why is a snapshot a fundamentally different entity than a volume? I've asked this question a number of times myself :) There are a number of different ideas/definitions of what a snapshot is, versus a clone, versus a backup, etc etc I've proposed that we leave snapshots as they are today and introduce a clone option to just directly get a new volume to work with and move on, as well as the ability to restore a volume to a specific snapshot (the originating volume, not a new one). I don't know how popular this idea is though, there were a number of folks at the Summit that seemed to think that was crazy talk. c. Is this what the snapshot-to-volume operation was meant to achieve? Yep d. If a back-end supports nested snapshots, each snapshot will need to be converted to volume before a nested snapshot can be taken? e. And in this case, will the back-end driver simply do nothing for the snapshot-to-volume operation? Not sure I follow here... 2) Why can't you take snapshots of attached volumes? I think most/all back-ends will be fine with it (of course they will be crash-consistent if the OS/application doesn't sync to disk). Worth investigating for those back-ends that support it 3) Most back-ends support various types of snapshots - e.g., read-only, read-write, full copy, etc. How can we better support this notion? Not sure how I feel about trying to match up to every option every vendor might have. The reality also is that there are differences in definitions from vendor A to vendor B on these sorts of things. The direction I was going with snapshots, clones would *kinda* give at least part of what you're talking about here. I started a blueprint for this sort of thing here: https:// blueprints.launchpad.net/cinder/+spec/add-cloning-support-to-cinder, feel free to add suggestions or give me feed-back if you like. It's by no means complete, but I should be working on it week after next. Thanks, John Hi John, Thanks for your reply. I guess I'm still confused about what a snapshot is in OpenStack. Currently you can't really do anything with them via OpenStack. I think every back-end supports reads, so at the very minimum, why not allow attaching a snapshot to a VM in read-only mode? Further, I think all current back-ends support writable snapshots, so we could consider attaching read-write, or making that a capability. The way I'm thinking about it now is that volumes are stand-alone (i.e., full copies with no CoW mappings or any other dependencies), while snapshots may depend on their respective source volumes. I guess clones, then, would be a full copy of the original volume, and would basically be a shortcut for snapshot + create_volume_from_snapshot. Do you agree? And finally, with regard to supporting various types of snapshots - maybe we can do something similar as with volume types? 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
Re: [Openstack] [Tempest] unable to run subset of tests via nosetests
ServerActionsTestBase is not the test class. You have to use
ServerActionsTestJSON (or XML).
Look at the bottom of
https://github.com/openstack/tempest/blob/master/tempest/tests/compute/servers/test_server_actions.py
-David
On 11/9/2012 8:04 PM, Stef T wrote:
Hey Ravi,
Cool, and how do you run (say) only test_reboot_server_hard from
ServerActionsTestBase ?
Whenever I try, I get;
stack@DevStack:~/tempest$ nosetests -sv
tempest.tests.compute.servers.test_server_actions.py:ServerActionsTestBase.test_reboot_server_hard
The server should be power cycled ... ERROR
==
ERROR: The server should be power cycled
--
Traceback (most recent call last):
File /usr/lib/pymodules/python2.7/nose/case.py, line 371, in setUp
try_run(self.inst, ('setup', 'setUp'))
File /usr/lib/pymodules/python2.7/nose/util.py, line 478, in try_run
return func()
File
/opt/stack/tempest/tempest/tests/compute/servers/test_server_actions.py,
line 39, in setUp
resp, server = self.client.create_server(self.name,
AttributeError: 'ServerActionsTestBase' object has no attribute 'client'
begin captured logging
tempest.config: INFO: Using tempest config file
/opt/stack/tempest/etc/tempest.conf
tempest.tests.compute: DEBUG: Entering tempest.tests.compute.setup_package
- end captured logging -
On 11/09/2012 07:16 PM, Venkatesan, Ravikumar wrote:
Test_server_actions.py
~/openstack_projects/tempest$ nosetests -sv
tempest/tests/compute/servers/test_server_actions.py
The server's password should be set to the provided password ...
SKIP: Change password not available.
Negative Test: The server reboot on non existent server should return
... ok
The server should be power cycled ... ok
The server should be signaled to reboot gracefully ... SKIP: Until
bug 1014647 is dealt with.
Negative test: The server rebuild for a non existing server should
not ... ok
The server should be rebuilt using the provided image and data ... ok
The server's RAM and disk space should be modified to that of ...
SKIP: Resize not available.
The server's RAM and disk space should return to its original ...
SKIP: Resize not available.
The server's password should be set to the provided password ...
SKIP: Change password not available.
Negative Test: The server reboot on non existent server should return
... ok
The server should be power cycled ... ok
The server should be signaled to reboot gracefully ... SKIP: Until
bug 1014647 is dealt with.
Negative test: The server rebuild for a non existing server should
not ... ok
The server should be rebuilt using the provided image and data ... ok
The server's RAM and disk space should be modified to that of ...
SKIP: Resize not available.
The server's RAM and disk space should return to its original ...
SKIP: Resize not available.
--
Ran 16 tests in 127.553s
OK (SKIP=8)
Regards,
Ravi
*From:*openstack-bounces+ravikumar.venkatesan=hp@lists.launchpad.net
[mailto:openstack-bounces+ravikumar.venkatesan=hp@lists.launchpad.net]
*On Behalf Of *Venkatesan, Ravikumar
*Sent:* Friday, November 09, 2012 4:13 PM
*To:* Stef T; openstack@lists.launchpad.net
*Subject:* Re: [Openstack] [Tempest] unable to run subset of tests
via nosetests
To run a single test from Tempest:
~/openstack_projects/tempest$ nosetests -sv
tempest/tests/compute/flavors/test_flavors.py
The expected flavor details should be returned ... ok
Ensure 404 returned for non-existant flavor ID ... ok
flavor details are not returned for non existant flavors ... ok
List of all flavors should contain the expected flavor ... ok
The detailed list of flavors should be filtered by disk space ... ok
The detailed list of flavors should be filtered by RAM ... ok
Only the expected number of flavors (detailed) should be returned ... ok
The list of flavors should start from the provided marker ... ok
The list of flavors should be filtered by disk space ... ok
The list of flavors should be filtered by RAM ... ok
Only the expected number of flavors should be returned ... ok
The list of flavors should start from the provided marker ... ok
Detailed list of all flavors should contain the expected flavor ... ok
The expected flavor details should be returned ... ok
Ensure 404 returned for non-existant flavor ID ... ok
flavor details are not returned for non existant flavors ... ok
List of all flavors should contain the expected flavor ... ok
The detailed list of flavors should be filtered by disk space ... ok
The detailed list of flavors should be filtered by RAM ... ok
Only the expected number of flavors (detailed) should be returned ... ok
The list of flavors should start from the provided marker
Re: [Openstack] [Cinder] Cinder snapshots
On Sun, Nov 11, 2012 at 6:30 AM, Avishay Traeger avis...@il.ibm.com wrote: John Griffith john.griff...@solidfire.com wrote on 08/11/2012 19:58:39: Hi Avishay, So we have plans to improve some of this in the Grizzly release, here's a few thoughts: a. Why is a snapshot a fundamentally different entity than a volume? I've asked this question a number of times myself :) There are a number of different ideas/definitions of what a snapshot is, versus a clone, versus a backup, etc etc I've proposed that we leave snapshots as they are today and introduce a clone option to just directly get a new volume to work with and move on, as well as the ability to restore a volume to a specific snapshot (the originating volume, not a new one). I don't know how popular this idea is though, there were a number of folks at the Summit that seemed to think that was crazy talk. c. Is this what the snapshot-to-volume operation was meant to achieve? Yep d. If a back-end supports nested snapshots, each snapshot will need to be converted to volume before a nested snapshot can be taken? e. And in this case, will the back-end driver simply do nothing for the snapshot-to-volume operation? Not sure I follow here... 2) Why can't you take snapshots of attached volumes? I think most/all back-ends will be fine with it (of course they will be crash-consistent if the OS/application doesn't sync to disk). Worth investigating for those back-ends that support it 3) Most back-ends support various types of snapshots - e.g., read-only, read-write, full copy, etc. How can we better support this notion? Not sure how I feel about trying to match up to every option every vendor might have. The reality also is that there are differences in definitions from vendor A to vendor B on these sorts of things. The direction I was going with snapshots, clones would *kinda* give at least part of what you're talking about here. I started a blueprint for this sort of thing here: https:// blueprints.launchpad.net/cinder/+spec/add-cloning-support-to-cinder, feel free to add suggestions or give me feed-back if you like. It's by no means complete, but I should be working on it week after next. Thanks, John Hi John, Thanks for your reply. I guess I'm still confused about what a snapshot is in OpenStack. Currently you can't really do anything with them via OpenStack. I think every back-end supports reads, so at the very minimum, why not allow attaching a snapshot to a VM in read-only mode? Further, I think all current back-ends support writable snapshots, so we could consider attaching read-write, or making that a capability. The way I'm thinking about it now is that volumes are stand-alone (i.e., full copies with no CoW mappings or any other dependencies), while snapshots may depend on their respective source volumes. I guess clones, then, would be a full copy of the original volume, and would basically be a shortcut for snapshot + create_volume_from_snapshot. Do you agree? And finally, with regard to supporting various types of snapshots - maybe we can do something similar as with volume types? Thanks, Avishay Hey Avishay, I guess I'm still confused about what a snapshot is in OpenStack. Currently you can't really do anything with them via OpenStack. Sure you can, you can use them to create a new volume. They make a good backup mechanism IMO. I guess my question to you in your definition then is 'what's the difference between a snapshot and a clone'? Also, it Seems to me if we go with the idea of adding snapshot-restore, and a true clone feature you get everything that you're asking for here and more... so I'm not sure of the problem? Maybe you could help me understand why defining snapshot and clone in the manner described doesn't seem appropriate? FWIW, I think a R/O attach is something that would be good to have as an option regardless. Thanks, John ___ 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 l3_agent when you have Per-tenant Routers !
There is a router_id in l3_agent.ini, You can create a router for a tenant and then start a l3 agent for it. On 11/11/2012 01:34 AM, Skible OpenStack wrote: https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/GRE-Tunneling/OpenStack_Folsom_Install_Guide_WebVersion.rst i have set my namespace in l3 agent and dhcp agent to true. set external network id to my external network id in the l3 agent file do i need to run multiple l3 agents to have the per tenant router usecase ? Le 10/11/2012 18:29, Razique Mahroua a crit: Hey there, which guide did you followed ? Nuage Co - Razique Mahroua razique.mahr...@gmail.com Le 10 nov. 2012 17:57, Skible OpenStack skible.openst...@gmail.com a crit : Hello, I am having trouble configuring my l3 agent when i have a quantum router for each of my tenants. None of my VMs seem to be internet accessible ! However, It seems that i can only use one router and set the router_id in the l3_agent to allow VMs access to internet ! please help ___ 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 :: Folsom] Quantum Network Node setup
On 11/10/2012 10:06 PM, balaji patnala wrote: Hi Yong, I downloaded the Quantum Architecture in Folsom Powerpoint prepared by you and found that in slide-10: lL3-agent lTo implement floating Ipsand other L3 features, such as NAT _lOne per network_ Can you elaborate on the comment 'one per network' for L3-Agent. # If use_namespaces is set as False then the agent can only configure one router. # This is done by setting the specific router_id. # router_id = # Each L3 agent can be associated with at most one external network. This # value should be set to the UUID of that external network. If empty, # the agent will enforce that only a single external networks exists and # use that external network id # gateway_external_network_id = two options: 1. use namespace = False and set router_id to specific one can support multi l3-agent, or 2. create multiples external networks, and use gateway_external_network_id = to run multil3-agent This way, we must set router's gateway port: we can create router with external_gateway_info: such as quantum router-create router1 --external_gateway_info network_id=id or quantum router-create router2 quantum router-gateway-set As i understood that the L3-Agent will be only one for complete setup. If we have more than one Network Node then we must install dhcp-agent and L3-Agent in each of these Network Nodes. So, the comment of 'one per network' is like we can have one router/gateway per tenant network. Can you give us your comments on this. you can reach at this target by creating a router or external network per tenant. bye, balaji On Wed, Oct 31, 2012 at 10:38 AM, balaji patnala patnala...@gmail.com mailto:patnala...@gmail.com wrote: Hi Yong, Thanks for information. I think you mean to say that these Quantum Network Node is not per Tenant basis and it can serve all the Tenants of DC setup. Just want to understand what will be the advantages we are thinking of by doing so. Regards, Balaji On Tue, Oct 30, 2012 at 2:26 PM, gong yong sheng gong...@linux.vnet.ibm.com mailto:gong...@linux.vnet.ibm.com wrote: Hi, In fact, we can split Quantum network Node into two categories: one is for dhcp, which install ovs agent and dhcp agent. We can have one such kind of node one is for l3 agent, we can deal with one external network on one l3 agent. We can have many nodes of this kind. Regards, Yong Sheng Gong On 10/30/2012 02:27 PM, balaji patnala wrote: Hi Salvatore, Just want to understand more on Network Node in the below given app_demo page. As i see in the setup, it looks like there will be one Quantum Network Node for one Data centre setup. Please correct me if my assumptions are wrong. This Quantum Network Node will have all the virtual routers, gateway which can be created with quantum-l3-agent plugin. Also my assumption is that this quantum Network Node will serve all the Tenant virtual gateways and routers created using quantum. Please give us some more information on this to understand the setup. Also do we have any specific reason for having quantum Network Node instead of keeping these plugin on the Controller Node similar to earlier release like Essex. Thanks in advance. Regards, Balaji On Fri, Oct 26, 2012 at 3:31 PM, Salvatore Orlando sorla...@nicira.com mailto:sorla...@nicira.com wrote: Hi Trinath, Even if is perfectly reasonable to run the DHCP/L3 agents in the controller node, the advice we give in the administration guide is slightly different. As suggested in [1], the only Quantum component running on the controller node should be the API server. The DHCP and L3 agents might run in a dedicated network node. Please note you will need also the L2 agent running on that node. Regards, Salvatore [1] http://docs.openstack.org/trunk/openstack-network/admin/content/app_demo.html On 26 October 2012 10:50, Trinath Somanchi trinath.soman...@gmail.com mailto:trinath.soman...@gmail.com wrote: Hi Stackers- I have found many installation and configuration manuals for Openstack Folsom which state the installation and configuration of Quantum-DHCP-Agent in the Controller machine. But I have doubt here, Can't we have the Quantum-DHCP/L3-Agent to be running in the Compute NODE rather than in the controller. How does the Installation and configuration change with this type of Installation? Please guide me on
Re: [Openstack] OpenStack (+ Quantum Deployment) Scenarios
and then... ping back from controller_ip(metata_ip) to your instance. if your instance has a private subnet you should manage the route back to instance. matadata traffic is connected to metadata_ip via DNAT iptables rule. so metadata api server should connect to instance directly. i have follow routing item to back to my instance. 172.16.1.0 10.100.1.130255.255.255.0 UG0 00 eth1 - 172.16.1.0/24: tenant's subnet - 10.100.1.130: tenant's default public ip for connect to internet -- Choe, Cheng-Dae http://blog.woosum.net twitter: kiddtm 2012. 11. 10., 오후 3:53, Veera Reddy veerare...@gmail.com 작성: Hi, In my setup metadata_ip is controller ip. I am able to ping to controller from network node. Regards, Veera. On Fri, Nov 9, 2012 at 7:02 PM, Choe, Cheng-Dae white...@gmail.com wrote: First. Ping to your metadata_ip in network router namespace. 2012년 11월 9일 금요일에 Veera Reddy님이 작성: Hi Skible, I followed the install guide https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst I am able to bring up guest, but unable to get ip to guest vm from network node. Also attached respective configuraion files . Please help in finding the issue. My setup : Controller : (10.232.91.33) nova-api nova-cert nova-consoleauth nova-scheduler quantum-server Network Node:(10.232.90.222) quantum-plugin-openvswitch-agent quantum-dhcp-agent quantum-l3-agent Compute Node: (10.232.90.62) quantum-plugin-openvswitch-agent nova-compute controller-nova.conf attached compute_node-nova.conf attached compute-ovs_quantum_plugin.ini attached network_node_ovs_quantum_plugin.ini attached Thanks in advance Regards, Veera. On Thu, Nov 8, 2012 at 2:57 PM, Skible OpenStack skible.openst...@gmail.com wrote: Hello Stackers ! I am currently trying to create pictures of my OpenStack deployment architecture as a part of my OpenStack Folsom install guide and i would like to ask a favorite. Could you be kind and please take a look at these Pics below and report back if there is a missing or wrong thing. Thank you. ==Quantum on VLAN + 3 NICs on controller node http://i.imgur.com/Ueh5Z.jpg === ==Quantum on VLAN + 2 NICs on controller node http://i.imgur.com/RK6X7.jpg === ==Quantum on GRE-tunneling + 3 NICs on controller node=== http://i.imgur.com/1jCFC.jpg === To make of OpenStack, the IT project of the century Best regards ___ 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. -- Choe, Cheng-Dae Blog: http://www.woosum.net -- 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
Re: [Openstack] [Cinder] Cinder snapshots
John Griffith john.griff...@solidfire.com wrote on 11/11/2012 17:01:37: Hey Avishay, I guess I'm still confused about what a snapshot is in OpenStack. Currently you can't really do anything with them via OpenStack. Sure you can, you can use them to create a new volume. They make a good backup mechanism IMO. Right - you can either make a new volume (=clone) or figure out somehow what name Cinder gave to the snapshot and make a backup on your own. [ Off topic question: How can a user determine the name of a volume/snapshot on the back-end for a given volume/snapshot? ] I guess my question to you in your definition then is 'what's the difference between a snapshot and a clone'? IMHO, a clone is a full, independent copy of the volume. It would copy all data (either in foreground or background) and leave the user with a volume - as if he created a new volume and used dd to copy all the data. A snapshot is something that depends on the original volume and in most implementations would contain only changed blocks. Clone definitely has other meanings - what's your definition? Also, it Seems to me if we go with the idea of adding snapshot- restore, and a true clone feature you get everything that you're asking for here and more... so I'm not sure of the problem? Maybe you could help me understand why defining snapshot and clone in the manner described doesn't seem appropriate? So as I stated above, clone would give me a full copy, which can be wasteful. I should be able to read and write to snapshots within the context of Cinder. FWIW, I think a R/O attach is something that would be good to have as an option regardless. It's a necessity IMO. R/W is less common, but also very important. It's obvious that Cinder can't support features found in some storage controllers, but even LVM2 supports R/W snapshots (released almost 10 years ago). Don't get me wrong - LVM is awesome - but if ubiquitous, freely-available software supports a feature that controllers also generally support, I think Cinder should support it too. Thanks, John Thank you, 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
[Openstack] Turn off ip-spoofing filter on a port
All, Is there a way to turn off ip-spoofing on a port in a private network? Below is my libvirt config libvirt_vif_driver=nova.virt.libvirt.vif.LibvirtHybridOVSBridgeDriver linuxnet_interface_driver=nova.network.linux_net.LinuxOVSInterfaceDriver firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver I don't want to turn off spooing filter for entire network, but only one port. Thanks Yi ___ 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-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_nova_trunk #69
Title: raring_grizzly_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/69/Project:raring_grizzly_nova_trunkDate of build:Sun, 11 Nov 2012 07:01:24 -0500Build duration:15 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0Changesimprove session handling of dnsdomain_listby devananda.vdveditnova/tests/test_db_api.pyeditnova/db/sqlalchemy/api.pyConsole Output[...truncated 32439 lines...]deleting and forgetting pool/main/n/nova/nova-volume_2013.1+git20120232~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-network_2013.1+git20120232~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-plugins_2013.1+git20120232~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xvpvncproxy_2013.1+git20120232~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/python-nova_2013.1+git20120232~raring-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/nova/raring-grizzly']Pushed up to revision 486.INFO:root:Storing current commit for next build: d993d947c7d8310a53c285cc7ea44cd4d8a06162INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/raring-grizzly-proposed /tmp/tmpgmu4le/novamk-build-deps -i -r -t apt-get -y /tmp/tmpgmu4le/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/nova/raring-grizzly --forcedch -b -D raring --newversion 2013.1+git20120702~raring-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2013.1+git20120702~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A nova_2013.1+git20120702~raring-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing nova_2013.1+git20120702~raring-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include raring-grizzly nova_2013.1+git20120702~raring-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/nova/raring-grizzly+ [ ! 0 ]+ jenkins-cli build raring_grizzly_deployNo such job 'raring_grizzly_deploy' perhaps you meant 'raring_grizzly_cinder_trunk'?java -jar jenkins-cli.jar build args...Starts a build, and optionally waits for a completion.Aside from general scripting use, this command can beused to invoke another job from within a build of one job.With the -s option, this command changes the exit code based onthe outcome of the build (exit code 0 indicates a success.)With the -c option, a build will only run if there has beenan SCM change JOB : Name of the job to build -c : Check for SCM changes before starting the build, and if there's no change, exit without doing a build -p : Specify the build parameters in the key=value format. -s : Wait until the completion/abortion of the command --username VAL : User name to authenticate yourself to Jenkins --password VAL : Password for authentication. Note that passing a password in arguments is insecure. --password-file VAL : File that contains the passwordBuild step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
[Openstack-ubuntu-testing-notifications] Build Still Failing: raring_grizzly_nova_trunk #71
Title: raring_grizzly_nova_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/71/Project:raring_grizzly_nova_trunkDate of build:Sun, 11 Nov 2012 23:31:23 -0500Build duration:15 minBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesSwitch from FLAGS to CONF in nova.dbby markmceditnova/db/sqlalchemy/migration.pyeditnova/db/sqlalchemy/migrate_repo/versions/082_essex.pyeditnova/db/base.pyeditnova/db/sqlalchemy/api.pyeditnova/db/sqlalchemy/session.pyeditnova/db/api.pyeditnova/db/sqlalchemy/models.pyConsole Output[...truncated 32443 lines...]deleting and forgetting pool/main/n/nova/nova-volume_2013.1+git20121832~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-network_2013.1+git20121832~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xcp-plugins_2013.1+git20121832~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/nova-xvpvncproxy_2013.1+git20121832~raring-0ubuntu1_all.debdeleting and forgetting pool/main/n/nova/python-nova_2013.1+git20121832~raring-0ubuntu1_all.debINFO:root:Pushing changes back to bzr testing branchDEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/nova/raring-grizzly']Pushed up to revision 486.INFO:root:Storing current commit for next build: d993d947c7d8310a53c285cc7ea44cd4d8a06162INFO:root:Complete command log:INFO:root:Destroying schroot.bzr branch lp:~openstack-ubuntu-testing/nova/raring-grizzly-proposed /tmp/tmpe8gA3i/novamk-build-deps -i -r -t apt-get -y /tmp/tmpe8gA3i/nova/debian/controlpython setup.py sdistgit log -n1 --no-merges --pretty=format:%Hbzr merge lp:~openstack-ubuntu-testing/nova/raring-grizzly --forcedch -b -D raring --newversion 2013.1+git20122332~raring-0ubuntu1 Automated Ubuntu testing build:dch -a No change rebuild.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC nova_2013.1+git20122332~raring-0ubuntu1_source.changessbuild -d raring-grizzly -n -A nova_2013.1+git20122332~raring-0ubuntu1.dscdput ppa:openstack-ubuntu-testing/grizzly-trunk-testing nova_2013.1+git20122332~raring-0ubuntu1_source.changesreprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include raring-grizzly nova_2013.1+git20122332~raring-0ubuntu1_amd64.changesbzr push lp:~openstack-ubuntu-testing/nova/raring-grizzly+ [ ! 0 ]+ jenkins-cli build raring_grizzly_deployNo such job 'raring_grizzly_deploy' perhaps you meant 'raring_grizzly_cinder_trunk'?java -jar jenkins-cli.jar build args...Starts a build, and optionally waits for a completion.Aside from general scripting use, this command can beused to invoke another job from within a build of one job.With the -s option, this command changes the exit code based onthe outcome of the build (exit code 0 indicates a success.)With the -c option, a build will only run if there has beenan SCM change JOB : Name of the job to build -c : Check for SCM changes before starting the build, and if there's no change, exit without doing a build -p : Specify the build parameters in the key=value format. -s : Wait until the completion/abortion of the command --username VAL : User name to authenticate yourself to Jenkins --password VAL : Password for authentication. Note that passing a password in arguments is insecure. --password-file VAL : File that contains the passwordBuild step 'Execute shell' marked build as failureEmail was triggered for: FailureSending email for trigger: Failure-- Mailing list: https://launchpad.net/~openstack-ubuntu-testing-notifications Post to : openstack-ubuntu-testing-notifications@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack-ubuntu-testing-notifications More help : https://help.launchpad.net/ListHelp
