[openstack-dev] [Neutron][API Doc] Easy way to generate JSON output for doc?

2013-08-01 Thread Morgan Fainberg
Paul,

Depending on what version of keystone you are utilizing there are a couple
options to use the UUID token format (instead of PKI).

Very recent (current master) of keystone uses a pluggable provider system.
To set the provider to uuid, in the [token] section set the option:
provider=keystone.token.providers.uuid.Provider

In older versions I believe the option (still in the [token] section) is:

token_format=UUID

I hope this info helps you out some.

Cheers,
Morgan Fainberg

Sent from my iPhone (please excuse the brevity)

 31/07/2013, Paul Michali :

 Yeah I was playing with that, however I'm having an issue with
 authentication…

 If I do a request to keystone to get the auth ID, I get a huge key, which
 I have to try to paste into a subsequent request to neutron.

 Is there a way to force this to use the old style (small) auth ID, no
 auth, or username/password for auth on the requests?

 I've been playing with using the CLI and --verbose, and then trying to
 extract the RESP:… output and run through JSON. A bit jacky, but it sorta
 works.


  PCM (Paul Michali)

 Contact info for Cisco users http://twiki.cisco.com/Main/pcm


 On Jul 31, 2013, at 7:00 PM, Mellquist, Peter peter.mellqu...@hp.com
 wrote:

  Paul,
 There are a few ways of doing this but I have used curl then pipe the
 results through a python JSON pretty print tool. This formats the JSON for
 easily dropping into API docs.

 curl ( some Openstack request with JSON output )| python –mjson.tool**
 **

 Hope this helps,
 Peter.



 *From:* Paul Michali [mailto:p...@cisco.com]
 *Sent:* Wednesday, July 31, 2013 3:41 PM
 *To:* OpenStack Development Mailing List
 *Subject:* [openstack-dev] [Neutron][API Doc] Easy way to generate JSON
 output for doc?
 ** **
 Hi!
 ** **
 I'm writing API doc pages for VPNaaS and was wondering if there are any
 tools/scripts to make it easy to generate the needed JSON result output for
 various operations?
 ** **
 It looks like I can do the neutron command with --verbose to get
 unformatted JSON output. Should I do that and then reformat the output (or
 is there way to do that easier)?
 ** **
 I did try to use json.loads() on the RESP: output, but it threw an
 ValueError Expecting property name: line 1 column 1 (char 1)
 ** **
 Ideas?
 ** **
 PCM (Paul Mi
 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




-- 
Sent from my iPhone (please excuse the brevity and any typos)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Neutron][API Doc] Easy way to generate JSON output for doc?

2013-08-01 Thread Paul Michali
Yes that will! Copying and pasting the public key is difficult.

Will try this out.

Regards.

PCM (Paul Michali)

MAIL p...@cisco.com
IRC   pcm_  (irc.freenode.net)
TW   @pmichali

On Aug 1, 2013, at 2:43 AM, Morgan Fainberg m...@metacloud.com wrote:

 Paul,
 
 Depending on what version of keystone you are utilizing there are a couple 
 options to use the UUID token format (instead of PKI). 
 
 Very recent (current master) of keystone uses a pluggable provider system. To 
 set the provider to uuid, in the [token] section set the option:
 provider=keystone.token.providers.uuid.Provider
 
 In older versions I believe the option (still in the [token] section) is:
 
 token_format=UUID
 
 I hope this info helps you out some.
 
 Cheers,
 Morgan Fainberg
 
 Sent from my iPhone (please excuse the brevity) 
 
  31/07/2013, Paul Michali :
 Yeah I was playing with that, however I'm having an issue with authentication…
 
 If I do a request to keystone to get the auth ID, I get a huge key, which I 
 have to try to paste into a subsequent request to neutron.
 
 Is there a way to force this to use the old style (small) auth ID, no auth, 
 or username/password for auth on the requests?
 
 I've been playing with using the CLI and --verbose, and then trying to 
 extract the RESP:… output and run through JSON. A bit jacky, but it sorta 
 works.
 
 
 PCM (Paul Michali)
 
 Contact info for Cisco users http://twiki.cisco.com/Main/pcm
 
 
 On Jul 31, 2013, at 7:00 PM, Mellquist, Peter peter.mellqu...@hp.com 
 wrote:
 
 Paul,
 There are a few ways of doing this but I have used curl then pipe the 
 results through a python JSON pretty print tool. This formats the JSON for 
 easily dropping into API docs.
  
 curl ( some Openstack request with JSON output )| python –mjson.tool
  
 Hope this helps,
 Peter.
  
  
  
 From: Paul Michali [mailto:p...@cisco.com] 
 Sent: Wednesday, July 31, 2013 3:41 PM
 To: OpenStack Development Mailing List
 Subject: [openstack-dev] [Neutron][API Doc] Easy way to generate JSON output 
 for doc?
  
 Hi!
  
 I'm writing API doc pages for VPNaaS and was wondering if there are any 
 tools/scripts to make it easy to generate the needed JSON result output for 
 various operations?
  
 It looks like I can do the neutron command with --verbose to get unformatted 
 JSON output. Should I do that and then reformat the output (or is there way 
 to do that easier)?
  
 I did try to use json.loads() on the RESP: output, but it threw an 
 ValueError Expecting property name: line 1 column 1 (char 1)
  
 Ideas?
  
 PCM (Paul Mi
 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 
 
 
 -- 
 Sent from my iPhone (please excuse the brevity and any typos)
 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [Neutron][API Doc] Easy way to generate JSON output for doc?

2013-07-31 Thread Paul Michali
Hi!

I'm writing API doc pages for VPNaaS and was wondering if there are any 
tools/scripts to make it easy to generate the needed JSON result output for 
various operations?

It looks like I can do the neutron command with --verbose to get unformatted 
JSON output. Should I do that and then reformat the output (or is there way to 
do that easier)?

I did try to use json.loads() on the RESP: output, but it threw an ValueError 
Expecting property name: line 1 column 1 (char 1)

Ideas?

PCM (Paul Michali)

MAIL p...@cisco.com
IRC   pcm_  (irc.freenode.net)
TW   @pmichali

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Neutron][API Doc] Easy way to generate JSON output for doc?

2013-07-31 Thread Mellquist, Peter
Paul,
There are a few ways of doing this but I have used curl then pipe the results 
through a python JSON pretty print tool. This formats the JSON for easily 
dropping into API docs.

curl ( some Openstack request with JSON output )| python -mjson.tool

Hope this helps,
Peter.



From: Paul Michali [mailto:p...@cisco.com]
Sent: Wednesday, July 31, 2013 3:41 PM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [Neutron][API Doc] Easy way to generate JSON output 
for doc?

Hi!

I'm writing API doc pages for VPNaaS and was wondering if there are any 
tools/scripts to make it easy to generate the needed JSON result output for 
various operations?

It looks like I can do the neutron command with --verbose to get unformatted 
JSON output. Should I do that and then reformat the output (or is there way to 
do that easier)?

I did try to use json.loads() on the RESP: output, but it threw an ValueError 
Expecting property name: line 1 column 1 (char 1)

Ideas?

PCM (Paul Michali)

MAIL p...@cisco.commailto:p...@cisco.com
IRC   pcm_  (irc.freenode.nethttp://irc.freenode.net)
TW   @pmichali

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Neutron][API Doc] Easy way to generate JSON output for doc?

2013-07-31 Thread Paul Michali
Yeah I was playing with that, however I'm having an issue with authentication…

If I do a request to keystone to get the auth ID, I get a huge key, which I 
have to try to paste into a subsequent request to neutron.

Is there a way to force this to use the old style (small) auth ID, no auth, or 
username/password for auth on the requests?

I've been playing with using the CLI and --verbose, and then trying to extract 
the RESP:… output and run through JSON. A bit jacky, but it sorta works.


PCM (Paul Michali)

Contact info for Cisco users http://twiki.cisco.com/Main/pcm


On Jul 31, 2013, at 7:00 PM, Mellquist, Peter peter.mellqu...@hp.com wrote:

 Paul,
 There are a few ways of doing this but I have used curl then pipe the results 
 through a python JSON pretty print tool. This formats the JSON for easily 
 dropping into API docs.
  
 curl ( some Openstack request with JSON output )| python –mjson.tool
  
 Hope this helps,
 Peter.
  
  
  
 From: Paul Michali [mailto:p...@cisco.com] 
 Sent: Wednesday, July 31, 2013 3:41 PM
 To: OpenStack Development Mailing List
 Subject: [openstack-dev] [Neutron][API Doc] Easy way to generate JSON output 
 for doc?
  
 Hi!
  
 I'm writing API doc pages for VPNaaS and was wondering if there are any 
 tools/scripts to make it easy to generate the needed JSON result output for 
 various operations?
  
 It looks like I can do the neutron command with --verbose to get unformatted 
 JSON output. Should I do that and then reformat the output (or is there way 
 to do that easier)?
  
 I did try to use json.loads() on the RESP: output, but it threw an ValueError 
 Expecting property name: line 1 column 1 (char 1)
  
 Ideas?
  
 PCM (Paul Michali)
  
 MAIL p...@cisco.com
 IRC   pcm_  (irc.freenode.net)
 TW   @pmichali
  
 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev