Re: [Openstack] Openstack

2014-11-15 Thread Tzach Shefi
Hi, 

If all your application needs is a connection between the instances, just 
connect all three instances on same virtual network. 
Then check nova security group rules (think of it like you would of a firewall) 
add rules for needed ports and that's it. 
Instances should be able to access one another over the ports you enabled. 

Check these links:
http://docs.openstack.org/openstack-ops/content/network_design.html
docs.openstack.org/openstack-ops/content/security_groups.html 

REST interface, if I'm guessing what you are referring to, is the method used 
to manage Openstack deployments. 
https://wiki.openstack.org/wiki/OpenStackRESTAPI
https://blueprints.launchpad.net/nova/+spec/open-stack-api

Hope this help a bit.
Tshefi


- Original Message -
From: "Sandhya S" 
To: openstack@lists.openstack.org
Sent: Friday, November 14, 2014 7:53:51 PM
Subject: [Openstack] Openstack

Hi all, 

My application requires three servers which are in 3 different VM's to 
communicate with each other. 
So how can it be approached? Should REST interface be deployed? 



Thanks 

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


Re: [Openstack] weird behavior of keystone+apache+mod_wsgi

2014-11-15 Thread Boris Bobrov
On Saturday 15 November 2014 14:42:56 Li Ma wrote:
> On 2014/11/15 17:40, Boris Bobrov wrote:
> > On Saturday 15 November 2014 12:25:23 Li Ma wrote:
> >> Hi all, I just set up keystone with apache(2.2.15) and mod_wsgi. It runs
> >> perfectly.
> >> But when I tested my own application, it threw an exception of 404 Not
> >> Found, because it accessed the url: http://192.168.242.10:/35357/v2.0
> >> 
> >> And I curl to get keystone versions, the result is weird.
> >> 
> >> Here's what keystone+apache shows:
> >> [...]
> >> Here's what keystone shows:
> >> [...]
> > 
> > Very interesting. We have this bug in MOS for simillar (if not the same)
> > issue and I thought it is fixed in "master" branch --
> > https://bugs.launchpad.net/mos/6.0.x/+bug/1382570
> > 
> > Where did you get your keystone from?
> 
> I'm using Icehouse 2014.1. Thanks for your information.
> 

OK, I've found this bug on vanilla keystone -- 
https://bugs.launchpad.net/keystone/+bug/1343579 . It was fixed and was fixed 
in 
2014.2.

Hope that helps!

-- 
С наилучшими пожеланиями,
Boris

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


Re: [Openstack] weird behavior of keystone+apache+mod_wsgi

2014-11-15 Thread Li Ma


On 2014/11/15 17:40, Boris Bobrov wrote:

On Saturday 15 November 2014 12:25:23 Li Ma wrote:

Hi all, I just set up keystone with apache(2.2.15) and mod_wsgi. It runs
perfectly.
But when I tested my own application, it threw an exception of 404 Not
Found, because it accessed the url: http://192.168.242.10:/35357/v2.0

And I curl to get keystone versions, the result is weird.

Here's what keystone+apache shows:
[...]
Here's what keystone shows:
[...]

Very interesting. We have this bug in MOS for simillar (if not the same) issue
and I thought it is fixed in "master" branch --
https://bugs.launchpad.net/mos/6.0.x/+bug/1382570

Where did you get your keystone from?


I'm using Icehouse 2014.1. Thanks for your information.

Li Ma

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


Re: [Openstack] OpenStack ecosystem

2014-11-15 Thread Muhammed Salehi
HelloOo Nicolas

Its very nice, congrats!
I'm not a front-end developer, but I think if we are able "Pin" some of
components and make them static, we can use it in our conferences. I
suggest "double click" or "Ctrl + Left Click" to force a circle to be
static and not moving. You can also add the online presentation editors (
which is found in HTML5 and JavaScript ) in order to any one be able to
create him/his own presentation. The result is very helpful. :)

Be lucky buddy :)

On Thu, Nov 13, 2014 at 7:19 PM, Nicolas Borboën 
wrote:

> Hello all,
> I attended the Paris conference as a newcomer to the world of
> OpenStack and I really loved the excitement around the project.
>
> As I'm in the beginning of my crusade OpenStack, I had difficulty
> representing my various projects operating in this environment, so I
> decided to try to represent the OpenStack ecosystem in a web page.
> I did it quickly, it's of course incomplete and there are probably some
> mistakes but in the end I think it would have helped me to have access to a
> similar visualization during my first contact with OpenStack.
>
> So I share with you my "OpenStack ecosystem": http://ponsfrilus.github.io/
> openstack_ecosystem/
>
> I hope this will help other newcomers and some of you will find an
> interest in proposing improvements on github.
>
> Feedbacks appreciated.
>
> Cheers,
> Nicolas
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
>



-- 
-BEGIN PGP PUBLIC KEY BLOCK-
Version: GnuPG v1

mQENBFRX8IoBCADCn76BbNN5m/GwP1rWaOvZMYfdm4Tv9oJehK7zAAzrHPZOaV/i
kdxG6LGadCGh/uTWoos441A8MKN/GufruEz1jvR+rgamD0oiTdRHTXz3Wkzcd62y
+U9pNLmYZyLUM1ebXXoxgmdNMGHvYLbdTIFgmxfIthKzRx9vd5WQGnsg/gFLTcdY
cWd5/THfkImJUHmjLAOepcewQcODijTp27xMwK354SG0BwbWroGAj5AVRqXqD6Qg
vO5zIgfMUsoOTMVF5WhAAf1xAjjGjEDi9EqeV1EVyO83s54gfAH/pWYV0K0RZvRw
h96wxZVVmCq9Ys8aU8D+hOjEvkjHZPAd3uNXABEBAAG0NFNleXllZCBNdWhhbW1l
ZCBTYWRlZ2ggU2FsZWhpIDxzYWxlaGkxOTk0QGdtYWlsLmNvbT6JAT4EEwECACgF
AlRX8IoCGwMFCQHhM4AGCwkIBwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEKs5CKNB
Z6zv/JQIALd5MnRhvAatGl/HcTYrm/S2Vsp3LgvC6R/w2uNiTm9tfSf596+2flF7
xgWUdROZ5O7s188oWiZRNb88XjdMMJtl0KpNpxLbYRyNPZL0klAps46Wlmy3fr8m
7RdovLSy2QtmFtEAsXfYyXmLGB4PeexqYyfcXYhfP1W4kyTScBRUZ4SuFWDhBvvZ
8vHHhWjiPVFvgi1cX3rwqtzp4eYFTHeH8QhKDeDk3760XVMk+jl+kvzqUzwh5V6+
SJs63YoiTSXyk37844NOGvYDHsupDO0R4O+YBwcZLxah/nqfTodfAnsmOA6W6oOy
lnVOH4IwrfcoVyjjqIlLWGws7BkPN6+5AQ0EVFfwigEIALLGTAxtT7lLuywmNTaq
hqpUtYsOWx7Cxjj1tVfG3bN/PbW+nKFvfyJkURYVyjn4z7GHLVCrYIr9ixhBRFcz
zmHuMkxMEr5u/m+H8CSsZ02V81v6+1uM2NvPxCYCUqDxEbcPrs8XrmPZGINY2Fya
XLpljTh06s1vdBAk32Wxy2Vz6Ii6pQD5WDgrdgDOgpTTlPdIxg9eq6yZi+GMJj/4
28Rt6HJhGaqGXN0bCPQ78tQygcY4EDQwpkToWxLCizsj1+9XFwwjnOQON/FNsAT7
g+XsVQJKfGmRe2QuRJ9oqSK6pi16O7VXg6bAw1dLsEmNoSto1ofy7DVTqqSlEG2o
N0MAEQEAAYkBJQQYAQIADwUCVFfwigIbDAUJAeEzgAAKCRCrOQijQWes7xemB/92
1PRHt24/hfCKR86aCnZk8bzNP+HDeewHXmFLEk9Hk7k2kuo6zVLjPnMA4M9rgOwh
W5EYhyVpNWKnzzhMwyCGz0J7doK2HYRXJKez1RErLW4GPLzM+4sfY5pWBAjDY62e
1Tz1ay+fS3CLh4zCCZYqraHKa6PJYYp9Bz3NRj3xkFtkcLspNq4DkiEBPJVLIPko
OkVOpBuNpj1YDSZZXwM8HzDMvJc1qgAVxWk56BjePrx8SHfDah1UQqZst4dWeepJ
0E2xj4H+WMrIW/3btSTVdlr4zPFwGQ9qE2CcbDJJhH68U9eve3njEPDFiu1TS/f5
Tt1scwgVintCWdVX9BS2
=cxjk
-END PGP PUBLIC KEY BLOCK-
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


Re: [Openstack] weird behavior of keystone+apache+mod_wsgi

2014-11-15 Thread Steve Martinelli
Li Ma  wrote on 11/15/2014 04:25:23 AM:

> From: Li Ma 
> To: "openstack@lists.openstack.org" 
> Date: 11/15/2014 04:32 AM
> Subject: [Openstack] weird behavior of keystone+apache+mod_wsgi
> 
> Hi all, I just set up keystone with apache(2.2.15) and mod_wsgi. It runs 

> perfectly.
> But when I tested my own application, it threw an exception of 404 Not 
> Found, because it accessed the url: http://192.168.242.10:/35357/v2.0

Might be nothing, but you have an extra slash in the url you posted. 
It should be http://192.168.242.10:35357/v2.0 not 
http://192.168.242.10:/35357/v2.0

Can you show the curl output when you hit http://192.168.242.10:35357/v2.0 
?

Did you change the keystone-paste.ini file around?

Though the bug Boris mentions looks like a match (
https://bugs.launchpad.net/mos/6.0.x/+bug/1382570).

> 
> And I curl to get keystone versions, the result is weird.
> 
> Here's what keystone+apache shows:
> # curl -i -X GET http://192.168.242.10:35357/ -H 
> "Content-Type:application/json"
> HTTP/1.1 300 Multiple Choices
> Date: Sat, 15 Nov 2014 09:18:14 GMT
> Server: Apache/2.2.15 (Red Hat)
> Vary: X-Auth-Token
> Content-Length: 346
> Connection: close
> Content-Type: application/json
> 
> {"versions": {"values": [{"status": "stable", "updated": 
> "2013-03-06T00:00:00Z", "media-types": [{"base": "application/json", 
> "type": "application/vnd.openstack.identity-v3+json"}, {"base": 
> "application/xml", "type": 
> "application/vnd.openstack.identity-v3+xml"}], "id": "v3.0", "links": 
> [{"href": "http://localhost:35357/v3/";, "rel": "self"}]}]}}
> 
> Here's what keystone shows:
> # curl -i -X GET http://192.242.10:35357/ -H 
"Content-Type:application/json"
> HTTP/1.1 300 Multiple Choices
> Vary: X-Auth-Token
> Content-Type: application/json
> Content-Length: 948
> Date: Sat, 15 Nov 2014 09:21:18 GMT
> 
> {"versions": {"values": [{"status": "stable", "updated": 
> "2013-03-06T00:00:00Z", "media-types": [{"base": "application/json", 
> "type": "application/vnd.openstack.identity-v3+json"}, {"base": 
> "application/xml", "type": 
> "application/vnd.openstack.identity-v3+xml"}], "id": "v3.0", "links": 
> [{"href": "http://localhost:35357/v3/";, "rel": "self"}]}, {"status": 
> "stable", "updated": "2014-04-17T00:00:00Z", "media-types": [{"base": 
> "application/json", "type": 
> "application/vnd.openstack.identity-v2.0+json"}, {"base": 
> "application/xml", "type": 
> "application/vnd.openstack.identity-v2.0+xml"}], "id": "v2.0", "links": 
> [{"href": "http://localhost:35357/v2.0/";, "rel": "self"}, {"href": 
> "http://docs.openstack.org/api/openstack-identity-service/2.0/content/";, 

> "type": "text/html", "rel": "describedby"}, {"href": 
> "http://docs.openstack.org/api/openstack-identity-service/2.0/
> identity-dev-guide-2.0.pdf", 
> "type": "application/pdf", "rel": "describedby"}]}]}}
> 
> ___
> Mailing list: 
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : 
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> 
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


Re: [Openstack] weird behavior of keystone+apache+mod_wsgi

2014-11-15 Thread Boris Bobrov
On Saturday 15 November 2014 12:25:23 Li Ma wrote:
> Hi all, I just set up keystone with apache(2.2.15) and mod_wsgi. It runs
> perfectly.
> But when I tested my own application, it threw an exception of 404 Not
> Found, because it accessed the url: http://192.168.242.10:/35357/v2.0
> 
> And I curl to get keystone versions, the result is weird.
> 
> Here's what keystone+apache shows:
> [...]
> Here's what keystone shows:
> [...]

Very interesting. We have this bug in MOS for simillar (if not the same) issue 
and I thought it is fixed in "master" branch -- 
https://bugs.launchpad.net/mos/6.0.x/+bug/1382570

Where did you get your keystone from?

-- 
С наилучшими пожеланиями,
Boris

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


[Openstack] weird behavior of keystone+apache+mod_wsgi

2014-11-15 Thread Li Ma
Hi all, I just set up keystone with apache(2.2.15) and mod_wsgi. It runs 
perfectly.
But when I tested my own application, it threw an exception of 404 Not 
Found, because it accessed the url: http://192.168.242.10:/35357/v2.0


And I curl to get keystone versions, the result is weird.

Here's what keystone+apache shows:
# curl -i -X GET http://192.168.242.10:35357/ -H 
"Content-Type:application/json"

HTTP/1.1 300 Multiple Choices
Date: Sat, 15 Nov 2014 09:18:14 GMT
Server: Apache/2.2.15 (Red Hat)
Vary: X-Auth-Token
Content-Length: 346
Connection: close
Content-Type: application/json

{"versions": {"values": [{"status": "stable", "updated": 
"2013-03-06T00:00:00Z", "media-types": [{"base": "application/json", 
"type": "application/vnd.openstack.identity-v3+json"}, {"base": 
"application/xml", "type": 
"application/vnd.openstack.identity-v3+xml"}], "id": "v3.0", "links": 
[{"href": "http://localhost:35357/v3/";, "rel": "self"}]}]}}


Here's what keystone shows:
# curl -i -X GET http://192.242.10:35357/ -H "Content-Type:application/json"
HTTP/1.1 300 Multiple Choices
Vary: X-Auth-Token
Content-Type: application/json
Content-Length: 948
Date: Sat, 15 Nov 2014 09:21:18 GMT

{"versions": {"values": [{"status": "stable", "updated": 
"2013-03-06T00:00:00Z", "media-types": [{"base": "application/json", 
"type": "application/vnd.openstack.identity-v3+json"}, {"base": 
"application/xml", "type": 
"application/vnd.openstack.identity-v3+xml"}], "id": "v3.0", "links": 
[{"href": "http://localhost:35357/v3/";, "rel": "self"}]}, {"status": 
"stable", "updated": "2014-04-17T00:00:00Z", "media-types": [{"base": 
"application/json", "type": 
"application/vnd.openstack.identity-v2.0+json"}, {"base": 
"application/xml", "type": 
"application/vnd.openstack.identity-v2.0+xml"}], "id": "v2.0", "links": 
[{"href": "http://localhost:35357/v2.0/";, "rel": "self"}, {"href": 
"http://docs.openstack.org/api/openstack-identity-service/2.0/content/";, 
"type": "text/html", "rel": "describedby"}, {"href": 
"http://docs.openstack.org/api/openstack-identity-service/2.0/identity-dev-guide-2.0.pdf";, 
"type": "application/pdf", "rel": "describedby"}]}]}}


___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


Re: [Openstack] cinder and EMC VNX storage

2014-11-15 Thread mad Engineer
Thanks Xin,i will try for a separate license for snapshot and see how it
goes.

Can you help me understand this better.

in my existing cinder volume which is a single server that act as iscsi
target , i use LVM in qcow2 disk format and it has thin provisioning and
snapshot capability.

With VNX as backend what format does it use.Can it create disks as qcow2
format and uses its capability rather than using VNX 's native thin
provisioning and snapshot feature.

Long back if i remember correctly with vmware vmdk on hp 3par array  there
was performance degradation with two layers of thing provisioning ie vmdk
thin provisioning over 3par thin provisioning.

Thanks for your help

On Sat, Nov 15, 2014 at 3:12 AM, yang, xing  wrote:

>  Yes, VNX snapshot should work with thick LUN.
>
>
>
> Thanks,
>
> Xing
>
>
>
>
>
> *From:* mad Engineer [mailto:themadengin...@gmail.com]
> *Sent:* Friday, November 14, 2014 4:31 PM
> *To:* yang, xing
> *Cc:* openstack@lists.openstack.org
> *Subject:* Re: [Openstack] cinder and EMC VNX storage
>
>
>
> Thank you Xing ,
>
> can snapshot work with thick LUN? can i just buy snapshot license and make
> it work
>
>
>
> Thanks
>
>
>
> On Sat, Nov 15, 2014 at 1:58 AM, yang, xing  wrote:
>
> Hi,
>
>
>
> The document you referenced is for the VNX Direct Driver.  If you use the
> VNX Direct driver, you need the “thin provisioning license” to create thin
> LUNs.  If you are only creating thick LUNs, you can skip this license.  You
> need the VNX Snapshot license to create a snapshot in Cinder.
>
>
>
> I’m not sure why the licenses are not required when you are using VMWare
> cluster.  Maybe they are thick LUNs only and snapshots are snapview
> snapshots instead of VNX snapshots.
>
>
>
> You need to have cinder-volume running, either on a separate node or on
> the controller node in order to use a cinder driver.
>
>
>
> Thanks,
>
> Xing
>
>
>
>
>
>
>
> *From:* mad Engineer [mailto:themadengin...@gmail.com]
> *Sent:* Friday, November 14, 2014 12:44 PM
> *To:* openstack@lists.openstack.org
> *Subject:* [Openstack] cinder and EMC VNX storage
>
>
>
> Hi all,
>
> Currently i am using icehouse release with KVM compute nodes and a
> server with *cinder-volume* installed as my storage server,(it uses iscsi
> to export lvm disks to compute nodes.)
>
> Now i got a chance to TEST EMC storage ie EMC VNX for couple of days which
> is currently used by our vmware cluster .
>
>
>
> but as per icehouse documentation
>
>
>
> *You must activate VNX Snapshot and Thin Provisioning license for the
> array.*
>
>
>
> But i don't have separate license for this and i am sure vmware was using
> this array without any issue (not managed by openstack)
>
>
>
> 1.Do i really need this license to make it work with cinder (if i don't
> care about thin provisioning).
>
> 2.Isn't it possible to use qcow2 image format with EMC VNX and use its
> native snapshot feature?
>
> 3.Do i still need to keep a separate node with cinder-volume installed or
> can my controller node with cinder-api running can directly communicate?
>
>
>
>
>
> i am not aware whether there is any separate mailing list for cinder
>
>
>
>
>
> Thanks
>
>
>
>
>
>
>
>
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack