Excellent topic Joe, thanks for bringing this up.
There are two main perspectives on WADLs: WADLs from a service developer point
of view and WADLs from a cloud developer point of view. I consider the later
the most important since we need to ensure that developers who write all the
killer Opens
Hi Ziad,Joe, jOrGe W.
>Ziad
I'm agree with you. Blueprint must contain clear specs!!
Current api document is not covering all accepted blueprints.
As Joe mentioned, current WADL is not perfect. It is the reason of i'm
reverse checking code for now.
> Joe
Ah, it it is just a patch, I need a paper
Hi-
I am looking for the way to get system usage data for a billing purpose
in Diablo release. Is there anyone know as to how to get event messages
such as compute.instance.create, compute.instance.delete, etc? I believe
this information cat be retrieved via log files or AMQP.
P.S: I guess system
The WADL should be complete for Nova. There are a couple of error fixes that
I've completed but haven't pushed up yet. I'll try to get to those tomorrow
and I'll look over Nachi's contributions as well.
What's not done in Nova is documenting all of the extensions. I'm working on
that and wil
Hi Nati - I might be opening a can of worms here, but I thought the API spec
and WADL were complete and we were working on implementing it. It sounds to me
like you are doing the reverse and matching the WADL to the current state of
the code. There's value in that, but i know it will cause probl
The WADL is unfortunately not complete for Nova, Glance, and Quantum - I
believe Keystone has been keeping it quite up to date as the changes to the API
have been being made. Nachi's made a couple of pull requests today for updates
to the WADL related to the OpenStack API, and offered to help c
On Wed, Oct 26, 2011 at 12:37 AM, Scott Moser wrote:
> It was probably me, Dave, and I pinged you and zul also to verify or
> confirm, and said that I wasn't sure.
>
> 10/20/11 17:06:41 smoser, BTW, any idea if openstack keystone in
> oneiric will be fixed relatively s
On 26/10/2011, at 9:34 AM, Caitlin Bestler wrote:
> WADL sounds like a wonderful validation tool.
>
> But shouldn’t our primary goal be finding a consistent way to describe the
> APIs
> for *application developers*.
>
> Syntax tools, whether ancient notations like BNF or the latest XML conco
hi all
can i know, the openstack focus in community program?
sound spector's is not official..
thx
--
Frans Thamura (曽志胜)
Chief of Advisory
Meruvian.
Integrated Hypermedia Java Solution Provider.
Mobile: +628557888699
Blog: http://blogs.mervpolis.com/roller/flatburger (id)
FB: http://www.fac
Agreed. Not having migrations is a bad idea. There should be a common
approach.
Sent from my iPhone
On Oct 25, 2011, at 7:32 PM, Jesse Andrews wrote:
> I don't think the debate is whether to do migrations or not. I think
> the debate should be:
>
> Is there more value in not doing it the
Frans,
I don't think any of us have used swagger, only seen and admired its output.
-joe
On Oct 25, 2011, at 4:41 PM, Frans Thamura wrote:
> we are working to use swagger, but i think the s/w is not working
>
> can help?
>
> F
>
>
> On Wed, Oct 26, 2011 at 3:24 AM, Anne Gentle wrote:
>>
The hard thing about processing a WADL is that WADLs uses links and references.
For example: WADL A may refer to a method defined in WADL B, that's useful
when you're defining extensions. Or WADL A may define two resources that share
GET, PUT, POST operations: You see this with metadata in se
On Tue, 25 Oct 2011, Kiall Mac Innes wrote:
> On Oct 25, 2011 8:04 p.m., "Dave Walker" wrote:
> >
> > Can you point me to this discussion? It sound awfully like there has
> > been some confusion.. Who was it that said this?
>
> It was on one of the OpenStack or Ubuntu IRC channels a week or so
we are working to use swagger, but i think the s/w is not working
can help?
F
On Wed, Oct 26, 2011 at 3:24 AM, Anne Gentle wrote:
> Hi all -
>
> Would also love Swagger. Nati looked into it and he thought it would require
> a Python client generator, based on reading that "Client generators ar
That's exactly what I'm poking at (and what Nati has started doing as well). I
was trying to see if there was a consistent way to describe all the API
endpoints that could be used to document the combined set.
The raw description is clearly insufficient, so how best to create a final
product th
Totally agree. The goal is to create narrative documents that devs can read
etc. The WADL is just there to fill in the nitty gritty details in a
consistent way.
-jOrGe W.
On Oct 25, 2011, at 5:34 PM, Caitlin Bestler wrote:
WADL sounds like a wonderful validation tool.
But shouldn’t our prim
Keystone is using it more than Nova, especially to document their extensions.
It's working with our existing docs tool chain.
You can reference a WADL directly from the DocBook source, you can go in and
reference particular resources and methods it will parse stuff out and put it
in the right
I don't think the debate is whether to do migrations or not. I think
the debate should be:
Is there more value in not doing it the same way another openstack
project does it?
If you can use nova's method, then we get closer to having standard
operating procedures for openstack projects...
On
Hi Joe
2011/10/25 Joseph Heck :
> It sounds like even though most of us hate WADL, it's what we're expending
> effort after to make a consolidated API set. So unless Nati and Ravi want to
> switch to using Swagger (or something else), WADL is the direction we're
> heading.
I'm voting WADL for sur
WADL sounds like a wonderful validation tool.
But shouldn't our primary goal be finding a consistent way to describe the APIs
for *application developers*.
Syntax tools, whether ancient notations like BNF or the latest XML concoction
only tell you the syntax of the operation.
There also has to b
It sounds like even though most of us hate WADL, it's what we're expending
effort after to make a consolidated API set. So unless Nati and Ravi want to
switch to using Swagger (or something else), WADL is the direction we're
heading. I totally agree with Daryl that reading it is a PITA, and am f
Which dev docs and how? I haven't spotted those scripts or systems...
-joe
On Oct 25, 2011, at 2:58 PM, Jorge Williams wrote:
> Some of that dev guide documentation is generated from a WADL :-) The
> purpose of a WADL is that it is machine readable so it opens up a lot of
> possibilities, for
Hi Folks
> Daryl
I know to read and write WADL is awful.. because I'm working on that.
My main point is for clear specs. Current docs are very helpful, but
it is not includes
clear specs (parameter structures and types).
>Jorge
Sounds Great
My review request is
https://review.openstack.org/#chang
Some of that dev guide documentation is generated from a WADL :-) The purpose
of a WADL is that it is machine readable so it opens up a lot of possibilities,
for creating docs, testing, validation, etc.
-jOrGe W.
On Oct 25, 2011, at 4:14 PM, Daryl Walleck wrote:
Hi everyone,
This is just my
Hi Nati,
I've actually fixed some of the issues you're describing but haven't had a
chance to check these in. Let's talk about the issues you're seeing off line
and combine our efforts.
-jOrGe W.
On Oct 25, 2011, at 3:52 PM, Nati Ueno wrote:
> Hi Joe, Anne
>
> I'm working on WADL of Openst
It's probably the best approach that doesn't depend on the Django ORM (like
South). Does anyone use the "experimental" command line migrate to generate
the migrate script? I always did it by hand.
http://packages.python.org/sqlalchemy-migrate/
On the dev side, one of the big headaches in nova
We've done quite a bit of work to get high quality documentation from a WADL,
in fact we are using some of this today. We've taken most of the hard work re:
parsing the WADL, at least for the purpose of generating docs from it and of
writing code that can read it (though that later part can us
Our schema right now is auto generated from the model using sqlalchemy.
Whenever we change the model, the generated schema is different for new
installations but this does not address existing deployments.
Looking for feedback on how to handle this better:
anotherjesses offered:
https://github.
Hi everyone,
This is just my opinion, but I've only found WADLs very useful when use tool
based automation. To me they're a huge headache to read. To me, the current dev
guide style of documentation has been far more helpful in developing automation.
Daryl
On Oct 25, 2011, at 3:24 PM, Anne Gen
On Oct 25, 2011, at 12:54 PM, Jesse Andrews wrote:
> I'm not an expert ... adding some comments
>
> On Tue, Oct 25, 2011 at 12:05 PM, Joseph Heck wrote:
>> I've just dropped in place a bunch of developer documentation (RST) for
>> Keystone - one in, one pending (https://review.openstack.org/#ch
Hi Joe, Anne
I'm working on WADL of Openstack Diablo in order to generate both of
Test List and API docs from WADL.
I wrote simple script which generate a simple api list from WADL. It
is very helpful.
Nova and Keystone has WADL, and Ravi@HP is working for glance.
Nova's WADL is inconsistent wit
I'm not an expert ... adding some comments
On Tue, Oct 25, 2011 at 12:05 PM, Joseph Heck wrote:
> I've just dropped in place a bunch of developer documentation (RST) for
> Keystone - one in, one pending (https://review.openstack.org/#change,1089).
> Making these docs brought up a number of quest
Hi all -
Would also love Swagger. Nati looked into it and he thought it would require
a Python client generator, based on reading that "Client generators are
currently available for Scala, Java, Javascript, Ruby, PHP, and Actionscript
3." So in the meantime the QA list and Nati suggested WADL as a
There is now a network subteam as well.
https://launchpad.net/~nova-network
http://wiki.openstack.org/Teams
-tr3buchet
On Mon, Oct 17, 2011 at 12:56 AM, Vishvananda Ishaya
wrote:
> Hello Everyone,
>
> I've been assimilating the plans from the design summit into blueprints.
> In the process i'v
I expect this is going to open a nasty can of worms... today we don't have a
consistent way of describing the APIs for the various services. I saw Nati's
bug (https://launchpad.net/bugs/881621), which implies that all the services
should have a WADL somewhere describing the API.
I'm not a huge
On Oct 25, 2011 8:04 p.m., "Dave Walker" wrote:
>
> Can you point me to this discussion? It sound awfully like there has
> been some confusion.. Who was it that said this?
It was on one of the OpenStack or Ubuntu IRC channels a week or so ago, I'd
have to go digging through logs (if there are a
Inline also.
On Tue, Oct 25, 2011 at 06:34:28PM +0100, Kiall Mac Innes wrote:
> See inline.
>
> On Oct 25, 2011 10:24 a.m., "Dave Walker" wrote:
> >
> > Hi Kiall,
> >
> > This is great news that you are working on resolving Diablo issues on
> > Oneiric.
> >
> > I'd like to question what gave you
I've just dropped in place a bunch of developer documentation (RST) for
Keystone - one in, one pending (https://review.openstack.org/#change,1089).
Making these docs brought up a number of questions that I wasn't able to
answer. I want to put more context around the commands and concepts for th
See inline.
On Oct 25, 2011 10:24 a.m., "Dave Walker" wrote:
>
> Hi Kiall,
>
> This is great news that you are working on resolving Diablo issues on
> Oneiric.
>
> I'd like to question what gave you the impression Ubuntu were not
> working on post-release fixes for Oneiric?
One of the names invo
I'm at a loss how to assist this poster:
https://answers.launchpad.net/glance/+question/176064
If anyone has experience using Nova with the VMWare drivers, please
try to lend a hand.
Thanks!
-jay
___
Mailing list: https://launchpad.net/~openstack
Post
All,
This is the follow-up for our "Deployment Fixture" blueprint brainstorm at the
conference
(https://blueprints.launchpad.net/openstack-common/+spec/deployer-api ).
As an Essex release object, I'd like to be automatically deploy OpenStack from
a community standard configuration description
Along the same lines, how do you export the shell variables for
euca-tools with keystone since nova-manage to create the zipfile does
not work?
-David
On 10/24/2011 8:29 PM, Vishvananda Ishaya wrote:
Speaking of keystone diablo tag, it is currently missing the following
commit:
https://gi
andi abes wrote:
> I'm a bit confused with the state of affairs for swift diablo.
> I've seen notes and checkins for backports to nova from essex, and
> found https://launchpad.net/~openstack-release/+archive/2011.3 which
> seems to be the repo for the patched packages...
>
> Is that right? Is thi
On Fri, Oct 21, 2011 at 08:58:16PM +0100, Kiall Mac Innes wrote:
> Hiya,
>
> I've gone ahead and updated the OpenStack Ubuntu Oneiric packages to the
> latest diablo/stable branches, Since it seems Ububtu won't be fixing
> keystone any time soon :(
>
> So far, I have nova+glance+keystone+python-n
Hello everyone,
Our general meeting will take place at 21:00 UTC this Tuesday in
#openstack-meeting on IRC. PTLs, if you can't make it, please name a
substitute on [2].
Only two weeks to go before essex-1, it's about time to get the Essex
plans in order and get a picture of where we are trying to
Razique:
I have fixed it
modified three fils:(Actually only nova/virt/libvirt/volume.py need to be
modified)
/usr/local/lib/python2.7/dist-packages/nova/virt/libvirt/volume.py
nova/volume/driver.py
nova/virt/libvirt/volume.py
change lun0->lun1
- host_device = ("/dev/disk/by-path/ip-%s-iscsi-%s-l
Hi livemoon,
the error is here :
ISCSI volume not yet found at: vdc. Will rescan & retry. Try number: 2
From the node which is supposed to get the volume, run :
$ iscsiadm -m discovery -t st -p 10.200.200.4
You should see a list of volumes (aka "targets"):
IP NAME
Then run :
$iscsiadmn -m no
Mark McLoughlin wrote:
> I just noticed a few things when reviewing the Fedora packaging of
> keystone:
>
> - There's no diablo release tarball on https://launchpad.net/keystone
> like other projects
That's because Keystone was not a core project until the Essex cycle.
Doesn't mean it can'
48 matches
Mail list logo
