[Openstack] Retrieve Endpoints

2012-10-24 Thread Tummala Pradeep 

Hi,

I want to configure "openstack.endpoint" and 
"openstack.identity.endpoint". However, I am a bit confused between the 
two. How can I configure them through terminal ?


Thanks

Pradeep

___
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] Retrieve Endpoints

2012-10-25 Thread heckj 
Hi Pradeep,

I'm not sure what the context is for these values, so it's a little hard to 
assert a clear answer.

For most openstack projects, (all but keystone), there's generally a single API 
endpoints, and the keystone service catalog is configured on deployment to 
point to those. The service catalog supports exposing internal and public 
endpoints.

Keystone (quirky thing that it is) has two endpoints - one for general public 
authorization with a very limited API - in the docs and on the CLI, this is 
referred to as the "auth_url". In a devstack setup, this auth_url is 
"http://localhost:5000/v2.0"; - your deployment I'd expect to be different.

There's also an administrative endpoint for Keystone where a Keystone admin (or 
associated scripts) can configure services, endpoints, users, etc depending on 
the keystone deployment configuration. The CLI refers to this as the 
"management_url", and in a devstack setup, it would be 
"http://localhost:35357/v2.0";

This help?

-joe

On Oct 24, 2012, at 10:53 PM, Tummala Pradeep  
wrote:
> Hi,
> 
> I want to configure "openstack.endpoint" and "openstack.identity.endpoint". 
> However, I am a bit confused between the two. How can I configure them 
> through terminal ?
> 
> Thanks
> 
> Pradeep
> 
> ___
> 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] Retrieve Endpoints

2012-10-28 Thread Tummala Pradeep 

Hi Joe,

I am actually trying to integrate cloudify with Openstack. To accomplish 
this, I have to configure openstack.groovy file in cloudify.


There are two fields here - openstack.endpoint & 
openstack.identity.endpoint. I have an example for cloudify integration 
with HP Openstack cloud. Hope, it will help you to understand what 
exactly these two fields (Last 4 lines) require.


cloud {

// Mandatory. The name of the cloud, as it will appear in the Cloudify UI.
name = "Openstack"
configuration {
// Mandatory - openstack Diablo cloud driver.
className 
"org.cloudifysource.esc.driver.provisioning.openstack.OpenstackCloudDriver"
// Optional. The template name for the management machines. Defaults to 
the first template in the templates section below.

managementMachineTemplate "SMALL_LINUX"
// Optional. Indicates whether internal cluster communications should 
use the machine private IP. Defaults to true.

connectToPrivateIp true
remoteUsername "REPLACE_WITH_THE_SSH_USER_NAME"
remotePassword "REPLACE_WITH_THE_SS_USER_PASSWORD"
}
provider {
// optional
provider "openstack"
localDirectory "tools/cli/plugins/esc/hp/upload"
remoteDirectory "/root/gs-files"
cloudifyUrl 
"http://s3.amazonaws.com/gigaspaces-cloudify/cloudify/hp/gigaspaces-hp.zip";

machineNamePrefix "agent"
dedicatedManagementMachines true
managementOnlyFiles ([])
managementGroup "management"
numberOfManagementMachines 1
zones (["agent"])
reservedMemoryCapacityPerMachineInMB 1024
}
user {
user "ENTER_USER"
apiKey "ENTER_KEY"
keyFile "ENTER_KEY_FILE"
}
templates ([
SMALL_LINUX : template{
imageId "221"
machineMemoryMB 1600
hardwareId "102"
//locationId "us-east-1"
options ([
"openstack.securityGroup" : "test",
"openstack.keyPair" : "hp-cloud-demo",
// indicates if a floating IP should be assigned to this machine. 
Defaults to true.

"openstack.allocate-floating-ip" : "true"
])
}
])
custom ([
*"openstack.endpoint" : 
"https://az-2.region-a.geo-1.compute.hpcloudsvc.com/",*
*"openstack.identity.endpoint": 
"https://region-a.geo-1.identity.hpcloudsvc.com:35357/",*

"openstack.tenant" : "ENTER_TENANT",
"openstack.wireLog": "false"
])
}

Now, I am trying the integration with OpenStack deployed on my server. 
Do let me know if you get any idea from the above example.


Thanks

Pradeep


On 10/26/2012 01:36 AM, heckj wrote:

Hi Pradeep,

I'm not sure what the context is for these values, so it's a little hard to 
assert a clear answer.

For most openstack projects, (all but keystone), there's generally a single API 
endpoints, and the keystone service catalog is configured on deployment to 
point to those. The service catalog supports exposing internal and public 
endpoints.

Keystone (quirky thing that it is) has two endpoints - one for general public authorization with a 
very limited API - in the docs and on the CLI, this is referred to as the "auth_url". In 
a devstack setup, this auth_url is "http://localhost:5000/v2.0"; - your deployment I'd 
expect to be different.

There's also an administrative endpoint for Keystone where a Keystone admin (or associated scripts) 
can configure services, endpoints, users, etc depending on the keystone deployment configuration. 
The CLI refers to this as the "management_url", and in a devstack setup, it would be 
"http://localhost:35357/v2.0";

This help?

-joe

On Oct 24, 2012, at 10:53 PM, Tummala Pradeep  
wrote:

Hi,

I want to configure "openstack.endpoint" and "openstack.identity.endpoint". 
However, I am a bit confused between the two. How can I configure them through terminal ?

Thanks

Pradeep

___
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] Retrieve Endpoints

2012-10-29 Thread Dolph Mathews 
It's hard to say without docs, as the openstack.identity.endpoint shown
there is just throwing errors for me, and the openstack.endpoint is raising
401.

However, the port used for the identity endpoint is typically used for the
administrative/management identity endpoint (keystone), and the
openstack.endpoint refers to specifically to "compute" in the hostname
(nova).

-Dolph


On Sun, Oct 28, 2012 at 11:21 PM, Tummala Pradeep <
pradeep.tumm...@ericsson.com> wrote:

>  Hi Joe,
>
> I am actually trying to integrate cloudify with Openstack. To accomplish
> this, I have to configure openstack.groovy file in cloudify.
>
> There are two fields here - openstack.endpoint &
> openstack.identity.endpoint. I have an example for cloudify integration
> with HP Openstack cloud. Hope, it will help you to understand what exactly
> these two fields (Last 4 lines) require.
>
>   
>   cloud {
>
>   // Mandatory. The name of the cloud, as it will appear in the Cloudify 
> UI.
>   name = "Openstack"
>   configuration {
>   // Mandatory - openstack Diablo cloud driver.
>   className 
> "org.cloudifysource.esc.driver.provisioning.openstack.OpenstackCloudDriver"
>   // Optional. The template name for the management machines. 
> Defaults to the first template in the templates section below.
>   managementMachineTemplate "SMALL_LINUX"
>   **// Optional. Indicates whether internal cluster 
> communications should use the machine private IP. Defaults to true.
>   connectToPrivateIp true
>remoteUsername "REPLACE_WITH_THE_SSH_USER_NAME"
>remotePassword "REPLACE_WITH_THE_SS_USER_PASSWORD"
>   }
>   provider {
>   // optional
>   provider "openstack"
>   localDirectory "tools/cli/plugins/esc/hp/upload"
>   remoteDirectory "/root/gs-files"
>   cloudifyUrl 
> "http://s3.amazonaws.com/gigaspaces-cloudify/cloudify/hp/gigaspaces-hp.zip"; 
> 
>   machineNamePrefix "agent"
>   dedicatedManagementMachines true
>   managementOnlyFiles ([])
>   managementGroup "management"
>   numberOfManagementMachines 1
>   zones (["agent"])
>   reservedMemoryCapacityPerMachineInMB 1024
>   }
>   user {
>   user "ENTER_USER"
>   apiKey "ENTER_KEY"
>   keyFile "ENTER_KEY_FILE"
>   }
>   templates ([
>   SMALL_LINUX : template{
>   imageId "221"
>   machineMemoryMB 1600
>   
>   hardwareId "102"
>   //locationId "us-east-1"
>   options ([
>   "openstack.securityGroup" : 
> "test",
>   "openstack.keyPair" : 
> "hp-cloud-demo",
>   // indicates if a floating IP 
> should be assigned to this machine. Defaults to true.
>   
> "openstack.allocate-floating-ip" : "true"
>   ])
>   }
>   ])
>   custom ([
>   *"openstack.endpoint" : 
> "https://az-2.region-a.geo-1.compute.hpcloudsvc.com/"; 
> ,*
> * "openstack.identity.endpoint": 
> "https://region-a.geo-1.identity.hpcloudsvc.com:35357/"; 
> ,*
>   "openstack.tenant" : "ENTER_TENANT",
>   "openstack.wireLog": "false"
>   ])
> }
>
> Now, I am trying the integration with OpenStack deployed on my server. Do
> let me know if you get any idea from the above example.
>
> Thanks
>
> Pradeep
>
>
> On 10/26/2012 01:36 AM, heckj wrote:
>
> Hi Pradeep,
>
> I'm not sure what the context is for these values, so it's a little hard to 
> assert a clear answer.
>
> For most openstack projects, (all but keystone), there's generally a single 
> API endpoints, and the keystone service catalog is configured on deployment 
> to point to those. The service catalog supports exposing internal and public 
> endpoints.
>
> Keystone (quirky thing that it is) has two endpoints - one for general public 
> authorization with a very limited API - in the docs and on the CLI, this is 
> referred to as the "auth_url". In a devstack setup, this auth_url is 
> "http://localhost:5000/v2.0";  - your deployment 
> I'd expect to be different.
>
> There's also an administrative endpoint for Keystone where a Keystone admin 
> (or associated scripts) can configure services, endpoints, users, etc 
> depending on the keystone