Re: [Openstack] Puppet module for Quantum and vSwitches (Currently OVS)
I've got a noen multi i om the works. Will update during today or the week. Den 9. okt. 2012 06:52 skrev Dmitry Ukov du...@mirantis.com følgende: Thanks a lot On Mon, Oct 8, 2012 at 9:45 PM, Joe Topjian joe.topj...@cybera.ca wrote: Hi Dmitry, Great modules. But you're using function multini to insert values into configuration files. Where can I find sources of this function? https://github.com/jtopjian/puppetlabs-inifile/tree/jtopjian-multini This function is now deprecated as Dan Bode has done a better implementation. Please see the following discussion for more information: https://groups.google.com/a/puppetlabs.com/forum/?fromgroups=#!topic/puppet-openstack/BGaBkYDn2wo Thanks, Joe -- 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. -- Kind regards Dmitry Ukov IT Engineer Mirantis, Inc. ___ 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] Boot from volume (Ceph RBD) and live migration
Hi, I just joined this list and I already have a question: We successfully: - launched instances with lib/nova/instances directory on a Ceph partition, and performed live migration between physical nodes - launched instances from a nova-volume (boot on volume) which was a Ceph Rados Block Device (RBD) My question is: is the live migration feature working with instances that booted from a nova volume (volume is shared between all nodes)? Is someone already tried this type of usage? Thanks for your answer. Best regards. Sam ___ 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] Configuration file and options alignment
Is there any plans to eliminate differences between configuration options? Like Keystone sections in config files and other options? Endre. ___ 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] Help about Quantum Conf
Hi, I have finished installing OpenStack Folsom but i am encountring a small issue about configuring Quantum. I would like to start the simplest scenario Flat Network http://docs.openstack.org/trunk/openstack-network/admin/content/use_cases_single_flat.html but i dont know how to configure my bridges (br-int, br-ex and br-tun) i have two NICs on each node ( primary eth0 and secondary eth1) If someone can show me the way, i will be very grateful since i will be writing a guide about it for future users. 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
Re: [Openstack] Help about Quantum Conf
Hi,I suggest you to read the official documentation [1] which helps to install and configure Quantum + OVS for many use cases.I think you should use 3 NICs for your controller node : eth0 for management network, eth1 for VMs traffic (used by OVS), and eth2 for public network (i.e. Internet). For compute nodes, I suggest using 2 NIC : eth0 for management network and eth1 for VMs traffic.[1] http://docs.openstack.org/trunk/openstack-network/admin/content/demo_installions.htmlRegards--Emilien MacchiOpenStack EngineerEMAIL : emilien.mac...@enovance.com –SKYPE :enovance-emilien.macchiWEB :www.enovance.comDe: "Bilel Msekni" ski...@hotmail.frÀ: openstack@lists.launchpad.net, "emilien openstack" emilien.openst...@gmail.comEnvoyé: Mardi 9 Octobre 2012 09:29:30Objet: [Openstack] Help about Quantum Conf Hi, I have finished installing OpenStack Folsom but i am encountring a small issue about configuring Quantum. I would like to start the simplest scenario Flat Network but i dont know how to configure my bridges (br-int, br-ex and br-tun) i have two NICs on each node ( primary eth0 and secondary eth1) If someone can show me the way, i will be very grateful since i will be writing a guide about it for future users. Thanks. ___Mailing list: https://launchpad.net/~openstackPost to : openstack@lists.launchpad.netUnsubscribe : https://launchpad.net/~openstackMore 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] Help about Quantum Conf
Hi, quantum.conf: core_plugin = quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2 ovs_quantum_plugin.ini: network_vlan_ranges = physnet1 enable_tunneling = False bridge_mappings = physnet1:br-eth0 To create a shared provider network: quantum net-create sharednet1 --shared --provider:network_type flat --provider:physical_network physnet1 Before we can run, create br-eth0: sudo ovs-vsctl add-br br-eth0 sudo ovs-vsctl add-port br-eth0 eth0 we don't need br-ex since we don't use router and floatingip and br-tun since we don't use GRE. Regards, Yong Sheng Gong On 10/09/2012 03:29 PM, Bilel Msekni wrote: Hi, I have finished installing OpenStack Folsom but i am encountring a small issue about configuring Quantum. I would like to start the simplest scenario Flat Network http://docs.openstack.org/trunk/openstack-network/admin/content/use_cases_single_flat.html but i dont know how to configure my bridges (br-int, br-ex and br-tun) i have two NICs on each node ( primary eth0 and secondary eth1) If someone can show me the way, i will be very grateful since i will be writing a guide about it for future users. 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] Help about Quantum Conf
Thanks sheng ! you are a life saver ;) Le 09/10/2012 10:29, gong yong sheng a écrit : Hi, quantum.conf: core_plugin = quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2 ovs_quantum_plugin.ini: network_vlan_ranges = physnet1 enable_tunneling = False bridge_mappings = physnet1:br-eth0 To create a shared provider network: quantum net-create sharednet1 --shared --provider:network_type flat --provider:physical_network physnet1 Before we can run, create br-eth0: sudo ovs-vsctl add-br br-eth0 sudo ovs-vsctl add-port br-eth0 eth0 we don't need br-ex since we don't use router and floatingip and br-tun since we don't use GRE. Regards, Yong Sheng Gong On 10/09/2012 03:29 PM, Bilel Msekni wrote: Hi, I have finished installing OpenStack Folsom but i am encountring a small issue about configuring Quantum. I would like to start the simplest scenario Flat Network http://docs.openstack.org/trunk/openstack-network/admin/content/use_cases_single_flat.html but i dont know how to configure my bridges (br-int, br-ex and br-tun) i have two NICs on each node ( primary eth0 and secondary eth1) If someone can show me the way, i will be very grateful since i will be writing a guide about it for future users. 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] NOVA errors
Hello... I'm sorry, does anybody know what's causing the problem? 2012/10/8 Daniel Oliveira dvalbr...@gmail.com Oh lol what was I thinking. The DEBUG message isn't exactly the same, it's the following: # nova-manage network create private --multi-host=T --fixed_range_v4= 192.168.0.0/24 \ --bridge_interface=br100 --num_networks=1 --network_size=256 2012-10-08 11:09:33 DEBUG nova.utils [req-780639b1-695c-42d8-af9a-1560185af834 None None] backend module 'nova.db.sqlalchemy.api' from '/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.pyc' from (pid=3857) __get_backend /usr/lib/python2.7/dist-packages/nova/utils.py:658 2012/10/8 Daniel Oliveira dvalbr...@gmail.com Hello again, I'm sorry for asking for help so much. Well, after I managed to sucessfully install Glance (thanks to your help), I went to the next steps in the installation tutorial, which means installing nova components. Everything apparently went fine until I was asked to populate the database: # nova-manage db sync 2012-10-08 11:05:35 DEBUG nova.utils [-] backend module 'nova.db.sqlalchemy.migration' from '/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/migration.pyc' from (pid=3574) __get_backend /usr/lib/pýthon2.7/dist-packages/nova/utils.py:658 2012-10-08 11:06:28 WARNING nova.utils [-] /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py:639: SADeprecationWarning: The 'listeners' argument to Pool (and create_engine()) is deprecated. Use event.listen(). Pool.__init__(self, creator, **kw) 2012-10-08 11:06:28 WARNING nova.utils [-] /usr/lib/python2.7/dist-packages/sqlalchemy/pool.py:145: SADeprecationWarning: Pool.add-listener is deprecated. Use event.listen self.add_listener(l) 2012-10-08 11:06:28 AUDIT nova.db.sqlalchemy.fix_dns_domains [-] Applying database fix for Essex dns_domains table. I'm asking for help because supposedly there shouldn't be any output to the db sync command. Also, if I move on on the tutorial, and do the command to create the network for the VMs, I get the same DEBUG message I get on the previous command. Thanks in advance. -- My best regards, Daniel Oliveira. -- My best regards, Daniel Oliveira. -- My best regards, Daniel Oliveira. ___ 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] General questions regarding zones and replicas
Micheal, thanks for your hints and explanations! Regards, Moritz 2012/10/8 Michael Barton mike-launch...@weirdlooking.com On Mon, Oct 8, 2012 at 8:12 AM, Moritz Krinke mkri...@fotocommunity.net wrote: - I cannot change the number of replicas after creating the ring (e.g. changing it from 1 to 2) Not really. Logically it's not a difficult operation, there's just no code to do it. There was a patch a while back, but I guess it wasn't ever approved: https://review.openstack.org/#/c/5484/ - reading about the unique-as-possible feature in folsom im asking myself how would swift know if nodes are in different places, is there a feature like regions i am not aware of? There's no concept of regions (yet). The commit message is pretty descriptive: https://github.com/openstack/swift/commit/bb509dd863dc99c06a232d1d8e0f950a7e73dcc8 - after migration of data and having two replicas spread over those two nodes, how can i make sure that in the event of a node beeing down swift will not start copying files to second drives on the healty nodes? Swift won't over-replicate when a node's down, only when an individual drive is unmounted. There's no way to disable over-replication in that case, though. - Michael ___ 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] Help about Quantum Conf
On Tue, Oct 9, 2012 at 3:11 AM, Bilel Msekni ski...@hotmail.fr wrote: Hi, thanks for replying Emilien, I will surely do my best in there but you know, OpenStack documentation is still really not updated especially for the Folsom release. Hi Bilel - The documentation for Folsom is updated and available as trunk - can you specify the gaps you still see via logging doc bugs at http://bugs.launchpad.net/openstack-manuals? We are 8 doc bugs away from releasing for Folsom, so I'd like to find out more about this perception. Thanks, Anne Le 09/10/2012 09:55, Emilien Macchi a écrit : Hi, I suggest you to read the official documentation [1] which helps to install and configure Quantum + OVS for many use cases. I think you should use 3 NICs for your controller node : eth0 for management network, eth1 for VMs traffic (used by OVS), and eth2 for public network (i.e. Internet). For compute nodes, I suggest using 2 NIC : eth0 for management network and eth1 for VMs traffic. [1] http://docs.openstack.org/trunk/openstack-network/admin/content/demo_installions.html Regards *-- Emilien Macchi** *OpenStack Engineer http://www.enovance.com *EMAIL : *emilien.mac...@enovance.com – *SKYPE : *enovance-emilien.macchi *WEB : *www.enovance.com http://www.enocloud.com -- *De: *Bilel Msekni ski...@hotmail.fr ski...@hotmail.fr *À: *openstack@lists.launchpad.net, emilien openstack emilien.openst...@gmail.com emilien.openst...@gmail.com *Envoyé: *Mardi 9 Octobre 2012 09:29:30 *Objet: *[Openstack] Help about Quantum Conf Hi, I have finished installing OpenStack Folsom but i am encountring a small issue about configuring Quantum. I would like to start the simplest scenario Flat Networkhttp://docs.openstack.org/trunk/openstack-network/admin/content/use_cases_single_flat.htmlbut i dont know how to configure my bridges (br-int, br-ex and br-tun) i have two NICs on each node ( primary eth0 and secondary eth1) If someone can show me the way, i will be very grateful since i will be writing a guide about it for future users. 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 image/pngimage/png___ 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] metadata api with Quantum and provider networks
Hi,
I have managed to create the Quantum router so that all the VMs created on
provider network are going through it. I had to simply use
router-interface-add.
But I have now the problem with accessing metadata service. As L3 agent
adds DNAT rule in router, the packets are rewritten and arrives at metadata
host, but when coming back it doesn't go through the router but directly to
the source host resulting in TCP handshake failure. Could it be because all
the ports in br-int which are somehow related to this provider network are
withing the same VLAN(have the same tag in ovs-vsctl output) thus being in
the same broadcast domain?
So the above could be solved with SNAT rule to router address, but then
metadata service sees routers address instead of VMs and returns HTTP 404
error.
Is it possible to fix this with additional flow in openvswitch somehow? The
vswitch man pages say that it is possible to match against IPs.
What other solution is here to fix this?
Thanks,
--janis
On Mon, Oct 8, 2012 at 11:04 PM, Jānis Ģeņģeris janis.genge...@gmail.comwrote:
Here is the output, with few details.
# quantum router-show router_vlan1501
+---+--+
| Field | Value|
+---+--+
| admin_state_up| True |
| external_gateway_info | |
| id| 3c7383c7-7759-4db6-ba5b-19e754280cb8 |
| name | router_vlan1501 |
| status| ACTIVE |
| tenant_id | 7246a7e9d61f42b8a644bc1551a2a396 |
+---+--+
# quantum net-show vlan1501
+---+--+
| Field | Value|
+---+--+
| admin_state_up| True |
| id| c2161824-a439-40e5-8809-5599f80df2fe |
| name | vlan1501 |
| provider:network_type | vlan |
| provider:physical_network | default |
| provider:segmentation_id | 1501 |
| router:external | False|
| shared| False|
| status| ACTIVE |
| subnets | af6eac1e-dfec-49a0-bfc2-3fbf9a7063b3 |
| tenant_id | 7246a7e9d61f42b8a644bc1551a2a396 |
+---+--+
# quantum router-gateway-set 3c7383c7-7759-4db6-ba5b-19e754280cb8
c2161824-a439-40e5-8809-5599f80df2fe
Bad router request: Network c2161824-a439-40e5-8809-5599f80df2fe is not a
valid external network
I assume this happens because 'router:external' if False, when switching
it to True the above command succeeds. But then if I want to switch back
later (with no ports attached, no routers, even no subnets), I get this:
quantum net-update vlan1501 --router:external False
External network e011d68b-6abd-43a4-b6c3-9dbadf5344ee cannot be updated to
be made non-external, since it has existing gateway ports
Anyway, I have set 'router:external' to True for 'vlan1501' network, set
the gateway for my newly created quantum router(router_vlan1501) with
'router-gateway-set' as a result quantum have created router ns with single
interface from my configured provider network 'vlan1501' with default
gateway set to the one of the 'vlan1501' nets attached subnet.
But now if I boot the VM with '--nic=vlan1501_id' option, I get VM with
default gateway set to networks('vlan1501') gateway(not the freshly created
router gateway, am I missing something in configs?), which is the same as
the created routers gateway. Another thing if I switch to newly created
'router_vlan1501' namespace I can't actually ping the external gateway,
that is there as a default gw for the 'vlan1501' net.
So my thinking is I need to change the default gw in VM to the virtual
router?
On Mon, Oct 8, 2012 at 9:32 PM, Dan Wendlandt d...@nicira.com wrote:
On Mon, Oct 8, 2012 at 12:27 PM, Jānis Ģeņģeris
janis.genge...@gmail.com wrote:
On Mon, Oct 8, 2012 at 6:24 PM, Dan Wendlandt d...@nicira.com wrote:
On Mon, Oct 8, 2012 at 7:52 AM, Jānis Ģeņģeris
janis.genge...@gmail.com
wrote:
Hello,
When using provider networks in Quantum, where should the metadata
service
rule mapping (e.g. 169.254.169.254:80 -
metadata_server:metadata_port)
must
be set?
For example, for floating IPs l3-agent handles this, but for provider
networks router is not used. I tried to
[Openstack] Folsom nova-scheduler race condition?
Hi All, Looking for a sanity test before I file a bug. I very recently upgraded my install to Folsom (on top of Ubuntu 12.04/kvm). My scheduler settings in nova.conf are: scheduler_available_filters=nova.scheduler.filters.standard_filters scheduler_default_filters=AvailabilityZoneFilter,RamFilter,CoreFilter,ComputeFilter least_cost_functions=nova.scheduler.least_cost.compute_fill_first_cost_fn compute_fill_first_cost_fn_weight=1.0 cpu_allocation_ratio=1.0 This had been working to fill systems based on available RAM and to not exceed 1:1 allocation ration of CPU resources with Essex. With Folsom, if I specify a moderately large number of instances to boot or spin up single instances in a tight shell loop they will all get schedule on the same compute node well in excess of the number of available vCPUs . If I start them one at a time (using --poll in a shell loop so each instance is started before the next launches) then I get the expected allocation behaviour. I see https://bugs.launchpad.net/nova/+bug/1011852 which seems to attempt to address this issue but as I read it that fix is based on retrying failures. Since KVM is capable of over committing both CPU and Memory I don't seem to get retryable failure, just really bad performance. Am I missing something this this fix or perhaps there's a reported bug I didn't find in my search, or is this really a bug no one has reported? Thanks, -Jon ___ 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] billing for openstack
hi all my member asks related to billing for openstack, so we can bill anyone use openstack's services are one of this? WHMCS, Clientexec, Blesta, Hostbill or anyone can help? F ___ 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] billing for openstack
On 10/09/2012 05:33 PM, Frans Thamura wrote: hi all my member asks related to billing for openstack, so we can bill anyone use openstack's services are one of this? WHMCS, Clientexec, Blesta, Hostbill or anyone can help? Hello Frans, We are just about to release a first version of Ceilometer[1][2] which provides a central point for a billing implementation to fetch its usage data from. Not sure if that fully answers your question though... [1]http://launchpad.net/ceilometer [2]http://ceilometer.readthedocs.org Best, -- Nick Barcet nick.bar...@canonical.com aka: nijaba, nicolas signature.asc Description: OpenPGP digital signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Discussion / proposal: Ability to reset tenant's quotas to default
HI All,
I would like to open a discussion on a topic user should have a
option to reset the tenant’s quotas( to the default).
Hi Vijaya,
I don't think a new nova command is needed for this use-case,
just add a simple custom script:
nova quota-update `nova quota-defaults $1 | tail -n +4 | tr '_' '-' | awk
'/|/ {printf( --%s %s, $2,$4)}'` $1
then call with the tenant ID as command line arg.
Cheers,
Eoghan
At present nova client has following commands for the quota
operation.
$nova --help | grep quota
quota-defaults List the default quotas for a tenant.
quota-show List the quotas for a tenant.
quota-update Update the quotas for a tenant.
It will be very helpful to have a command to reset quota values to
defaults .
For ex: User who wants to do huge tests on the system and rollback
once the test is done.
So my proposal is to add a new command quota-reset to the nova client
which reverts the quota value supplied for the tenant ,to the
default.
Some thing similar to nova quota-reset( tenant-id key)
Let me know your suggestion/thoughts on the same.
Thanks,
Vijaya
DISCLAIMER == This e-mail may contain privileged and
confidential information which is the property of Persistent Systems
Ltd. It is intended only for the use of the individual or entity to
which it is addressed. If you are not the intended recipient, you
are not authorized to read, retain, copy, print, distribute or use
this message. If you have received this communication in error,
please notify the sender and delete all copies of this message.
Persistent Systems Ltd. does not accept any liability for virus
infected mails.
___
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] billing for openstack
interesting.. still learning how to implement best billing for openstack. in private this is good to make revenue center for IT division F On Tue, Oct 9, 2012 at 11:05 PM, Nick Barcet nick.bar...@canonical.com wrote: On 10/09/2012 05:33 PM, Frans Thamura wrote: hi all my member asks related to billing for openstack, so we can bill anyone use openstack's services are one of this? WHMCS, Clientexec, Blesta, Hostbill or anyone can help? Hello Frans, We are just about to release a first version of Ceilometer[1][2] which provides a central point for a billing implementation to fetch its usage data from. Not sure if that fully answers your question though... [1]http://launchpad.net/ceilometer [2]http://ceilometer.readthedocs.org Best, -- Nick Barcet nick.bar...@canonical.com aka: nijaba, nicolas ___ 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] Discussion / proposal: Ability to reset tenant's quotas to default
Isn't that just changing one custom limit with another ?
A true reset to the defaults would see the user stay in step with any
changes to the default values.
Do you mean configured changes to the defaults?
AFAIK 'nova quota-defaults' returns the current set of defaults,
which seems to be the logical point to reset against.
HI All,
I would like to open a discussion on a topic user should have a
option
to reset the tenant’s quotas( to the default).
Hi Vijaya,
I don't think a new nova command is needed for this use-case, just
add a simple custom script:
nova quota-update `nova quota-defaults $1 | tail -n +4 | tr '_' '-'
| awk '/|/ {printf( --%s %s, $2,$4)}'` $1
then call with the tenant ID as command line arg.
Cheers,
Eoghan
At present nova client has following commands for the quota
operation.
$nova --help | grep quota
quota-defaults List the default quotas for a tenant.
quota-show List the quotas for a tenant.
quota-update Update the quotas for a tenant.
It will be very helpful to have a command to reset quota values to
defaults .
For ex: User who wants to do huge tests on the system and rollback
once the test is done.
So my proposal is to add a new command quota-reset to the nova
client
which reverts the quota value supplied for the tenant ,to the
default.
Some thing similar to nova quota-reset( tenant-id key)
Let me know your suggestion/thoughts on the same.
Thanks,
Vijaya
DISCLAIMER == This e-mail may contain privileged and
confidential information which is the property of Persistent
Systems
Ltd. It is intended only for the use of the individual or entity to
which it is addressed. If you are not the intended recipient, you
are
not authorized to read, retain, copy, print, distribute or use this
message. If you have received this communication in error, please
notify the sender and delete all copies of this message.
Persistent Systems Ltd. does not accept any liability for virus
infected mails.
___
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] Discussion / proposal: Ability to reset tenant's quotas to default
Hi Glynn,
My point was that if a user is currently configured to have a quota of 50 VMs,
and the default is currently configured to be 20 VMs then there is a difference
between configuring the user to have a quota of 20 and configuring a user to
have the default quota.The first is just a subsequent update to give a
user a different but still specific quota value, whereas the second undoes any
quota value that has been specifically assigned. And the intent here is the
second case.
Perhaps quota delete would be a more appropriate description (and the right way
to implement this in the API) ?
Cheers,
Phil
-Original Message-
From: Eoghan Glynn [mailto:egl...@redhat.com]
Sent: 09 October 2012 17:32
To: Day, Phil
Cc: openstack@lists.launchpad.net; Vijaya Erukala
Subject: Re: [Openstack] Discussion / proposal: Ability to reset tenant's
quotas to default
Isn't that just changing one custom limit with another ?
A true reset to the defaults would see the user stay in step with any
changes to the default values.
Do you mean configured changes to the defaults?
AFAIK 'nova quota-defaults' returns the current set of defaults, which seems to
be the logical point to reset against.
HI All,
I would like to open a discussion on a topic user should have a
option to reset the tenant’s quotas( to the default).
Hi Vijaya,
I don't think a new nova command is needed for this use-case, just
add a simple custom script:
nova quota-update `nova quota-defaults $1 | tail -n +4 | tr '_' '-'
| awk '/|/ {printf( --%s %s, $2,$4)}'` $1
then call with the tenant ID as command line arg.
Cheers,
Eoghan
At present nova client has following commands for the quota
operation.
$nova --help | grep quota
quota-defaults List the default quotas for a tenant.
quota-show List the quotas for a tenant.
quota-update Update the quotas for a tenant.
It will be very helpful to have a command to reset quota values to
defaults .
For ex: User who wants to do huge tests on the system and rollback
once the test is done.
So my proposal is to add a new command quota-reset to the nova
client
which reverts the quota value supplied for the tenant ,to the
default.
Some thing similar to nova quota-reset( tenant-id key)
Let me know your suggestion/thoughts on the same.
Thanks,
Vijaya
DISCLAIMER == This e-mail may contain privileged and
confidential information which is the property of Persistent
Systems
Ltd. It is intended only for the use of the individual or entity to
which it is addressed. If you are not the intended recipient, you
are
not authorized to read, retain, copy, print, distribute or use this
message. If you have received this communication in error, please
notify the sender and delete all copies of this message.
Persistent Systems Ltd. does not accept any liability for virus
infected mails.
___
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] Folsom nova-scheduler race condition?
Hi Jon, I believe the retry is meant to occur not just if the spawn fails, but also if a host receives a request which it can't honour because it already has too many VMs running or in progress of being launched. Maybe try reducing your filters down a bit (standard_filters means all filters I think) in case there is some odd interaction between that full set ? Phil -Original Message- From: openstack-bounces+philip.day=hp@lists.launchpad.net [mailto:openstack-bounces+philip.day=hp@lists.launchpad.net] On Behalf Of Jonathan Proulx Sent: 09 October 2012 15:53 To: openstack@lists.launchpad.net Subject: [Openstack] Folsom nova-scheduler race condition? Hi All, Looking for a sanity test before I file a bug. I very recently upgraded my install to Folsom (on top of Ubuntu 12.04/kvm). My scheduler settings in nova.conf are: scheduler_available_filters=nova.scheduler.filters.standard_filters scheduler_default_filters=AvailabilityZoneFilter,RamFilter,CoreFilter,ComputeFilter least_cost_functions=nova.scheduler.least_cost.compute_fill_first_cost_fn compute_fill_first_cost_fn_weight=1.0 cpu_allocation_ratio=1.0 This had been working to fill systems based on available RAM and to not exceed 1:1 allocation ration of CPU resources with Essex. With Folsom, if I specify a moderately large number of instances to boot or spin up single instances in a tight shell loop they will all get schedule on the same compute node well in excess of the number of available vCPUs . If I start them one at a time (using --poll in a shell loop so each instance is started before the next launches) then I get the expected allocation behaviour. I see https://bugs.launchpad.net/nova/+bug/1011852 which seems to attempt to address this issue but as I read it that fix is based on retrying failures. Since KVM is capable of over committing both CPU and Memory I don't seem to get retryable failure, just really bad performance. Am I missing something this this fix or perhaps there's a reported bug I didn't find in my search, or is this really a bug no one has reported? Thanks, -Jon ___ 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] Discussion / proposal: Ability to reset tenant's quotas to default
My point was that if a user is currently configured to have a quota of 50 VMs, and the default is currently configured to be 20 VMs then there is a difference between configuring the user to have a quota of 20 and configuring a user to have the default quota.The first is just a subsequent update to give a user a different but still specific quota value, whereas the second undoes any quota value that has been specifically assigned. And the intent here is the second case. A-ha, got it now. Perhaps quota delete would be a more appropriate description (and the right way to implement this in the API) ? Yep, that would probably be clearer. Cheers, Eoghan ___ 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] Discussion / proposal: Ability to reset tenant's quotas to default
On Tue, 2012-10-09 at 12:17 -0400, Eoghan Glynn wrote:
I don't think a new nova command is needed for this use-case,
just add a simple custom script:
nova quota-update `nova quota-defaults $1 | tail -n +4 | tr '_' '-' | awk
'/|/ {printf( --%s %s, $2,$4)}'` $1
then call with the tenant ID as command line arg.
The problem with this approach is that if you then change the default
quotas, they are not reflected for the tenant. I've noticed the lack of
a DELETE handler in the quotas (and quota_classes) extension(s) and
often thought we needed to add one for just this case…
--
Kevin L. Mitchell kevin.mitch...@rackspace.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] Versioning for notification messages
On 10/09/2012 01:07 PM, Day, Phil wrote: What do people think about adding a version number to the notification systems, so that consumers of notification messages are protected to some extent from changes in the message contents ? For example, would it be enough to add a version number to the messages – or should we have the version number as part of the topic itself (so that the notification system can provide both a 1.0 and 1.1 feed), etc ? Putting a version number in the messages is easy, and should work fine. Of course it only really helps if someone writes clients that can deal with multiple versions, or at least give helpful error messages when they get an unexpected version. I think using separate topics for each version would be inefficient and error-prone. Inefficient because you'd have to send out multiples of each message, some of which would probably never be read. Obviously, if you're sending out N copies of each message then you expect only 1/N the queue performance. Worse, if you're sending out N copies of each message but only 1 of them is being consumed, your queue server is using a lot more memory than it needs to, to hold onto old messages that nobody needs. (If you properly configure a high-water mark or timeout, then the old messages will eventually be thrown away. If you don't, then your queue server will eventually consume way too much memory and start swapping, your cloud will break, and someone will get paged at 2 a.m.) Error-prone because someone would end up reusing the notification queue code for less idempotent/safe uses of queues, like internal API calls. And then client A would pick up the message from topic_v1, and client B would pick up the same message from topic_v2, and they'd both perform the same API operation, resulting in wasted resources in the best case and data corruption in the worst case. -- David Ripton Red Hat drip...@redhat.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] Versioning for notification messages
On Tuesday, October 9, 2012 at 15:58 PM, David Ripton wrote: On 10/09/2012 01:07 PM, Day, Phil wrote: What do people think about adding a version number to the notification systems, so that consumers of notification messages are protected to some extent from changes in the message contents ? Right now, there is no appropriate or acceptable way to consume notifications. Plainly, while notifications exist, they shouldn't be considered stable or even usable until this exists. Message formats and versioning should be a consideration in the effort to create a reusable consumption pattern. Regards, Eric Windisch ___ 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] Call for testing : nova, glance and keystone 2012.1.3 tarballs
On Tue, 2012-10-09 at 22:53 +0100, Mark McLoughlin wrote: Hey, We're hoping to publish Nova, Keystone and Horizon 2012.1.3 releases this Thursday (Oct 11). Doh, I only noticed the incorrect subject line after sending :) Cheers, Mark. ___ 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] Call for testing : nova, glance and keystone 2012.1.2 tarballs
Hey, We're hoping to publish Nova, Keystone and Horizon 2012.1.3 releases this Thursday (Oct 11). The list of issues fixed so far can be seen here: https://launchpad.net/nova/+milestone/2012.1.3 https://launchpad.net/keystone/+milestone/2012.1.3 https://launchpad.net/horizon/+milestone/2012.1.3 That's roughly 30 bugs. There's limited time remaining for testing, but we'd appreciate anyone who could give the candidate 2012.1.3 tarballs a whirl: http://tarballs.openstack.org/nova/nova-stable-essex.tar.gz http://tarballs.openstack.org/keystone/keystone-stable-essex.tar.gz http://tarballs.openstack.org/horizon/horizon-stable-essex.tar.gz Note, this is the final planned official Essex release of these projects. We may yet do one more release of Glance from stable/essex to fix this serious issue with Diablo-Essex migrations: https://bugs.launchpad.net/glance/+bug/1012820 Thanks! Mark. ___ 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] Versioning for notification messages
On Tue, Oct 9, 2012 at 4:12 PM, Eric Windisch e...@cloudscaling.com wrote: On Tuesday, October 9, 2012 at 15:58 PM, David Ripton wrote: On 10/09/2012 01:07 PM, Day, Phil wrote: What do people think about adding a version number to the notification systems, so that consumers of notification messages are protected to some extent from changes in the message contents ? Right now, there is no appropriate or acceptable way to consume notifications. Plainly, while notifications exist, they shouldn't be considered stable or even usable until this exists. Message formats and versioning should be a consideration in the effort to create a reusable consumption pattern. This will be part of what is covered during the Using the message bus for messages session Tuesday afternoon at the summit. http://summit.openstack.org/cfp/details/117 Doug ___ 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] Cinder Improvement for Grizzly
Hi all, I want to join the next design summit but I can't because of the current job. So I wrote my ideas for cinder improvement to etherpad. I hope someone will take up them (or a part of them) at the summit. http://etherpad.openstack.org/CinderImprovementsForGrizzly Table of contents: * New features * Shared volumes for instances * APIs * Validation for all parameters * Validation for state transitions * Keeping previous state for rollback * Drivers * VolumeDriver as the real base class * Unification of create_volume()+create_export() and remove_export()+delete_volume() * Zeroing volumes not at deleting but at creating * Common FileDriver * Post function of nova-side drivers for terminate_connection() * One driver per module file * Checking whether commands work in check_for_setup_error() Any comments will be gratefully appreciated. Thank you, Akira Yoshiyama akirayoshiy...@gmail.com ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] Bottleneck of message queue
Hi guys, I am trying to figure out how the internal interaction processes within different modules of OpenStack. Frankly speaking, while I'm reading the source codes I lost myself and have to jump out again to look at OpenStack from out of the box. I don't know if anybody has the similiar feeling with me. Is there any picture I can follow to see the message flows? OpenStack is based on message queue to ensure the expansion easy. Here come my questions. Does anybody know the capacity of message queue? Would the capacity be a bottleneck of the platform? Thanks, Howard ___ 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] Folsom nova-scheduler race condition?
On Tue, Oct 9, 2012 at 10:52 PM, Jonathan Proulx j...@jonproulx.com wrote: Hi All, Looking for a sanity test before I file a bug. I very recently upgraded my install to Folsom (on top of Ubuntu 12.04/kvm). My scheduler settings in nova.conf are: scheduler_available_filters=nova.scheduler.filters.standard_filters scheduler_default_filters=AvailabilityZoneFilter,RamFilter,CoreFilter,ComputeFilter least_cost_functions=nova.scheduler.least_cost.compute_fill_first_cost_fn compute_fill_first_cost_fn_weight=1.0 cpu_allocation_ratio=1.0 This had been working to fill systems based on available RAM and to not exceed 1:1 allocation ration of CPU resources with Essex. With Folsom, if I specify a moderately large number of instances to boot or spin up single instances in a tight shell loop they will all get schedule on the same compute node well in excess of the number of available vCPUs . If I start them one at a time (using --poll in a shell loop so each instance is started before the next launches) then I get the expected allocation behaviour. Per my understanding, this shouldn't happen no matter how (fast) you create instances since the requests are queued and scheduler updates resource information after it processes each request. The only possibility may cause the problem you met that I can think of is there are more than 1 scheduler doing scheduling. I see https://bugs.launchpad.net/nova/+bug/1011852 which seems to attempt to address this issue but as I read it that fix is based on retrying failures. Since KVM is capable of over committing both CPU and Memory I don't seem to get retryable failure, just really bad performance. Am I missing something this this fix or perhaps there's a reported bug I didn't find in my search, or is this really a bug no one has reported? Thanks, -Jon ___ 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 Huang Zhiteng ___ 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 Improvement for Grizzly
On Tue, Oct 9, 2012 at 8:35 PM, Akira Yoshiyama akirayoshiy...@gmail.comwrote: Hi all, I want to join the next design summit but I can't because of the current job. So I wrote my ideas for cinder improvement to etherpad. I hope someone will take up them (or a part of them) at the summit. http://etherpad.openstack.org/CinderImprovementsForGrizzly Table of contents: * New features * Shared volumes for instances * APIs * Validation for all parameters * Validation for state transitions * Keeping previous state for rollback * Drivers * VolumeDriver as the real base class * Unification of create_volume()+create_export() and remove_export()+delete_volume() * Zeroing volumes not at deleting but at creating * Common FileDriver * Post function of nova-side drivers for terminate_connection() * One driver per module file * Checking whether commands work in check_for_setup_error() Any comments will be gratefully appreciated. Thank you, Akira Yoshiyama akirayoshiy...@gmail.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 Hi Akira, Thanks for putting this list together. A number of things on your list have been mentioned at different weekly meetings etc so you definitely targeted some good ideas. I'm sure that we'll cover a number of these during various sessions at the summit. We'll sync up via session etherpads, but don't hesitate to add some items to the weekly cinder meeting agenda [1], and be sure to drop in and present some of these ideas. There's always the blue-print process as well. Thanks, John [1] http://wiki.openstack.org/NovaVolumeMeetings ___ 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: precise_folsom_swift_trunk #95
Title: precise_folsom_swift_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_swift_trunk/95/Project:precise_folsom_swift_trunkDate of build:Tue, 09 Oct 2012 12:30:34 -0400Build duration:3 min 40 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0Changesinternal client unicode pathsby greglangedeletetest/unit/obj/test_internal_client.pyeditswift/common/internal_client.pyaddtest/unit/common/test_internal_client.pyConsole Output[...truncated 2796 lines...]dch -a [7e0c4eb] Fixed leak on 499sdch -a [57b10cd] Restore old SIGPIPE handler in a proxy server test.dch -a [87c1c5d] Gracefully handle stdin flush failure on BSDdch -a [da99c33] Only set TCP_KEEPIDLE where supporteddch -a [8a7afa5] 1.7.2. changelog and version bump to 1.7.3-devdch -a [c97fb37] Fix bug where serialization_format is ignoreddch -a [568b61a] replace a value set with utils.TRUE_VALUESdch -a [411c7cb] Add README.md to the tarball.dch -a [c4f5761] builder.add_devs gets next id if not provideddch -a [bfc114b] new more helpful READMEdch -a [343968b] added disable_fallocate info to docsdch -a [2ca379d] added errno.EINVAL check to fallocatedch -a [463da7e] Adds Error Handling to swift-drive-audit for missing or unreadable /var/log/kern.logdch -a [d24e280] obj replicator speed updch -a [063789b] container_info returns a dictdch -a [a2ac5ef] swift constraints are now settable via configdch -a [3139760] Fix pep8 issuesdch -a [cde6d59] Fix pep8 issuesdch -a [c0537ac] Breakout search_devs & add get_builder() for reusedch -a [54e28fa] fix some formatdch -a [4d6ae96] fix some format issuredch -a [edaaa47] format some code according to pep8dch -a [46a093f] Obj replicator cleans up files where part dirs should be.dch -a [d56772a] Fix pep8 issues in test_memcached.py.dch -a [314d3b7] Fall back to UDP if /dev/log does not exist.dch -a [ed3b12d] Can run swift-bench across multiple cores/servers.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC swift_1.7.5+git201210091231~precise-0ubuntu1_source.changessbuild -d precise-folsom -n -A swift_1.7.5+git201210091231~precise-0ubuntu1.dscTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'swift_1.7.5+git201210091231~precise-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'swift_1.7.5+git201210091231~precise-0ubuntu1.dsc']' returned non-zero exit status 2Build 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: quantal_folsom_swift_trunk #105
Title: quantal_folsom_swift_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_swift_trunk/105/Project:quantal_folsom_swift_trunkDate of build:Tue, 09 Oct 2012 12:30:34 -0400Build duration:3 min 46 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0Changesinternal client unicode pathsby greglangedeletetest/unit/obj/test_internal_client.pyaddtest/unit/common/test_internal_client.pyeditswift/common/internal_client.pyConsole Output[...truncated 2974 lines...]dch -a [d24e280] obj replicator speed updch -a [063789b] container_info returns a dictdch -a [a2ac5ef] swift constraints are now settable via configdch -a [3139760] Fix pep8 issuesdch -a [cde6d59] Fix pep8 issuesdch -a [c0537ac] Breakout search_devs & add get_builder() for reusedch -a [54e28fa] fix some formatdch -a [4d6ae96] fix some format issuredch -a [edaaa47] format some code according to pep8dch -a [46a093f] Obj replicator cleans up files where part dirs should be.dch -a [d56772a] Fix pep8 issues in test_memcached.py.dch -a [73846c2] fix update_deleted directory creation. bug 1035274dch -a [07b4c21] 1.7.1 version bumpdch -a [341da75] changelog and authors updates for 1.7 releasedch -a [2e16b1f] Update swift.common.db to us swift.cmmn.utils.jsondch -a [314d3b7] Fall back to UDP if /dev/log does not exist.dch -a [0bb5d6d] use simplejson to serialize acct/cont resultsdch -a [54a2907] bumped version to 1.7.0 to reflect current dev effortdch -a [7b664c9] Fix PEP8 issues in ./test/unit/common .dch -a [ed3b12d] Can run swift-bench across multiple cores/servers.dch -a [4a2ae2b] Upating proxy-server StatsD logging.dch -a [c509ac2] Added ability to disable fallocatedch -a [2a38a04] Remove the gettext wrapper of server_type.dch -a [9290471] x-newest cleanup code with test. Fixes bug 1037337dch -a [9bda92d] Misc. swift-bench improvements.dch -a [e1ff51c] Do not use pickle for serialization in memcache, but JSONdebcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC swift_1.7.5+git201210091231~quantal-0ubuntu1_source.changessbuild -d quantal-folsom -n -A swift_1.7.5+git201210091231~quantal-0ubuntu1.dscTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'swift_1.7.5+git201210091231~quantal-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'quantal-folsom', '-n', '-A', 'swift_1.7.5+git201210091231~quantal-0ubuntu1.dsc']' returned non-zero exit status 2Build 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: precise_folsom_swift_trunk #96
Title: precise_folsom_swift_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_swift_trunk/96/Project:precise_folsom_swift_trunkDate of build:Tue, 09 Oct 2012 14:30:33 -0400Build duration:3 min 39 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesFixing alterations to sys.pathby derekheditdoc/source/conf.pyConsole Output[...truncated 2799 lines...]dch -a [7e0c4eb] Fixed leak on 499sdch -a [57b10cd] Restore old SIGPIPE handler in a proxy server test.dch -a [87c1c5d] Gracefully handle stdin flush failure on BSDdch -a [da99c33] Only set TCP_KEEPIDLE where supporteddch -a [8a7afa5] 1.7.2. changelog and version bump to 1.7.3-devdch -a [c97fb37] Fix bug where serialization_format is ignoreddch -a [568b61a] replace a value set with utils.TRUE_VALUESdch -a [411c7cb] Add README.md to the tarball.dch -a [c4f5761] builder.add_devs gets next id if not provideddch -a [bfc114b] new more helpful READMEdch -a [343968b] added disable_fallocate info to docsdch -a [2ca379d] added errno.EINVAL check to fallocatedch -a [463da7e] Adds Error Handling to swift-drive-audit for missing or unreadable /var/log/kern.logdch -a [d24e280] obj replicator speed updch -a [063789b] container_info returns a dictdch -a [a2ac5ef] swift constraints are now settable via configdch -a [3139760] Fix pep8 issuesdch -a [cde6d59] Fix pep8 issuesdch -a [c0537ac] Breakout search_devs & add get_builder() for reusedch -a [54e28fa] fix some formatdch -a [4d6ae96] fix some format issuredch -a [edaaa47] format some code according to pep8dch -a [46a093f] Obj replicator cleans up files where part dirs should be.dch -a [d56772a] Fix pep8 issues in test_memcached.py.dch -a [314d3b7] Fall back to UDP if /dev/log does not exist.dch -a [ed3b12d] Can run swift-bench across multiple cores/servers.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC swift_1.7.5+git201210091431~precise-0ubuntu1_source.changessbuild -d precise-folsom -n -A swift_1.7.5+git201210091431~precise-0ubuntu1.dscTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'swift_1.7.5+git201210091431~precise-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'swift_1.7.5+git201210091431~precise-0ubuntu1.dsc']' returned non-zero exit status 2Build 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: precise_folsom_swift_trunk #98
Title: precise_folsom_swift_trunk General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_swift_trunk/98/Project:precise_folsom_swift_trunkDate of build:Tue, 09 Oct 2012 16:30:33 -0400Build duration:3 min 19 secBuild cause:Started by an SCM changeBuilt on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesFix two edge cases with Range: headerby darrelleditswift/common/swob.pyedittest/functional/tests.pyedittest/unit/common/test_swob.pyConsole Output[...truncated 2805 lines...]dch -a [7e0c4eb] Fixed leak on 499sdch -a [57b10cd] Restore old SIGPIPE handler in a proxy server test.dch -a [87c1c5d] Gracefully handle stdin flush failure on BSDdch -a [da99c33] Only set TCP_KEEPIDLE where supporteddch -a [8a7afa5] 1.7.2. changelog and version bump to 1.7.3-devdch -a [c97fb37] Fix bug where serialization_format is ignoreddch -a [568b61a] replace a value set with utils.TRUE_VALUESdch -a [411c7cb] Add README.md to the tarball.dch -a [c4f5761] builder.add_devs gets next id if not provideddch -a [bfc114b] new more helpful READMEdch -a [343968b] added disable_fallocate info to docsdch -a [2ca379d] added errno.EINVAL check to fallocatedch -a [463da7e] Adds Error Handling to swift-drive-audit for missing or unreadable /var/log/kern.logdch -a [d24e280] obj replicator speed updch -a [063789b] container_info returns a dictdch -a [a2ac5ef] swift constraints are now settable via configdch -a [3139760] Fix pep8 issuesdch -a [cde6d59] Fix pep8 issuesdch -a [c0537ac] Breakout search_devs & add get_builder() for reusedch -a [54e28fa] fix some formatdch -a [4d6ae96] fix some format issuredch -a [edaaa47] format some code according to pep8dch -a [46a093f] Obj replicator cleans up files where part dirs should be.dch -a [d56772a] Fix pep8 issues in test_memcached.py.dch -a [314d3b7] Fall back to UDP if /dev/log does not exist.dch -a [ed3b12d] Can run swift-bench across multiple cores/servers.debcommitbzr builddeb -S -- -sa -us -ucbzr builddeb -S -- -sa -us -ucdebsign -k9935ACDC swift_1.7.5+git201210091631~precise-0ubuntu1_source.changessbuild -d precise-folsom -n -A swift_1.7.5+git201210091631~precise-0ubuntu1.dscTraceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'swift_1.7.5+git201210091631~precise-0ubuntu1.dsc']' returned non-zero exit status 2Error in sys.excepthook:Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 68, in apport_excepthookbinary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))OSError: [Errno 2] No such file or directoryOriginal exception was:Traceback (most recent call last): File "/var/lib/jenkins/tools/openstack-ubuntu-testing/bin/build-package", line 141, in raise esubprocess.CalledProcessError: Command '['sbuild', '-d', 'precise-folsom', '-n', '-A', 'swift_1.7.5+git201210091631~precise-0ubuntu1.dsc']' returned non-zero exit status 2Build 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
