atom feed51 messages in org.openstack.lists.openstack-dev[openstack-dev] [nova] Call for Help ...
FromSent OnAttachments
Vishvananda IshayaAug 9, 2012 3:25 pm 
George ReeseAug 9, 2012 3:32 pm 
Vishvananda IshayaAug 9, 2012 3:52 pm 
George ReeseAug 9, 2012 4:02 pm 
Paul McMillanAug 9, 2012 4:15 pm 
George ReeseAug 9, 2012 4:20 pm 
Christopher B FerrisAug 9, 2012 5:10 pm 
Doug DavisAug 9, 2012 6:14 pm 
Daryl WalleckAug 9, 2012 6:28 pm 
George ReeseAug 9, 2012 7:58 pm 
Vishvananda IshayaAug 9, 2012 8:05 pm 
Mark McLoughlinAug 9, 2012 10:28 pm 
George ReeseAug 10, 2012 5:07 am 
George ReeseAug 10, 2012 5:21 am 
Anne GentleAug 10, 2012 5:39 am 
Daniel P. BerrangeAug 10, 2012 5:47 am 
David KranzAug 10, 2012 5:57 am 
Christopher B FerrisAug 10, 2012 6:01 am 
Sandy WalshAug 10, 2012 6:09 am 
Gabe WestmaasAug 10, 2012 6:14 am 
Gabe WestmaasAug 10, 2012 6:17 am 
Paul McMillanAug 10, 2012 6:19 am 
Paul McMillanAug 10, 2012 6:28 am 
Thierry CarrezAug 10, 2012 6:43 am 
George ReeseAug 10, 2012 6:53 am 
Gabe WestmaasAug 10, 2012 7:33 am 
25 later messages
Subject:[openstack-dev] [nova] Call for Help -- OpenStack API XML Support
From:Vishvananda Ishaya (
Date:Aug 9, 2012 3:25:01 pm

Hello Everyone,

We are in the unfortunate position of not knowing how good our OpenStack API XML
support is. All of our integration tests use json. Many of the compute
extensions don't even have XML deserializers. We also assume that there bugs we
don't even know about due to underuse. We need to do something about XML by
Folsom, because releasing a buggy api isn't good for anyone.

We don't want to alienate the communtity by dropping XML support, but we also
can't recommend it in its current state. If there are people out there who use
XML (or want to use XML) we need your help. We need help identifying what works
and what doesn't, we need bug reports, and we need merge proposals for the extra
serializers and fixes that are important. Nova-core has too much going on right
now to tackle XML.

I see a few potential results from this effort.

1) We get a lot of community support and we manage to get XML into usable shape
by Folsom.

2) We get enough community support to get the core api working and the most
important extensions in place. We release clear documentation on what is
expected to work.

3) We get no support, in which case we mark XML support deprecated and encourage
people to use JSON only.

Note that other openstack projects only support json, and there are already java
bindings that use json so option 3) isn't terrible, but we don't want to go that
route without discussing it with the community first. If anyone has alternative
solutions or suggestions, feel free to let me know.

Thanks, Vish