Hi ,
I tried the following yaml:
location:
jclouds:openstack-devtest-compute:
endpoint: https://x.x.x.x:5000/v2.0/
identity: "my-tenant:my-username"
credential: password
# optional
imageId: RegionOne/image-id
hardwareId: RegionOne/2
templateOptions:
networks: [ "network-id" ]
floatingIpPoolNames: [ "name-of-my-floatingIp-pool" ]
loginUser: ubuntu
# optional - user to ssh into the VM the first time (usually
`ubuntu`or `root` is expected)
# overrideLoginUser: ubuntu
# overrideLoginPassword: <login password>
name: VM-new
services:
- type: brooklyn.entity.basic.EmptySoftwareProcess
name: Empty software process
A VM gets created in openstack with a floating IP assigned. But the
application is stuck in starting state ( Provisioning> DST Manager) for a
long time .But application is still in starting state .
Any suggestions?
On Tue, Jun 21, 2016 at 2:30 PM, Andrea Turli <
[email protected]> wrote:
> Hi,
>
> Can you please try with the following YAML
>
> name: VM4
>
> services:
> - type: brooklyn.entity.basic.EmptySoftwareProcess
>
> location:
> jclouds:openstack-devtest-compute:
> endpoint: http://x.x.x.x:5000/v2.0/
> identity: "my-tenant:my-username"
> credential: my-password
> # optional
> #imageId: RegionOne/adec65c4-de61-41ff-a4c7-f1f3163e750c
> #hardwareId: RegionOne/1
>
> # templateOptions:
> # networks: [ "18073710-7e5e-4023-a117-44f963443c4c" ]
> # floatingIpPoolNames: [ "public" ]
> # optional - user to ssh into the VM the first time (usually `ubuntu`
> or `root` is expected)
> # overrideLoginUser: <login username>
> # overrideLoginPassword: <login password>
>
> I think your yaml is quite right, but this version should simplify the
> debugging,
>
> Notice, I've added some optional properties just to help you in targeting
> your env correctly, like imageId or hardwareId.
>
> In particular, the devtest-compute assumes you want to use a floating IP so
> you need to discover your `networkId` and the `floating ip pool name`
> unless you want to run the test without the floating-ip by overriding the
> default with
>
> name: VM4
>
> services:
> - type: brooklyn.entity.basic.EmptySoftwareProcess
>
> location:
> jclouds:openstack-devtest-compute:
> endpoint: http://x.x.x.x:5000/v2.0/
> identity: "my-tenant:my-username"
> credential: my-password
> jclouds.openstack-nova.auto-create-floating-ips: false
>
> Best,
> Andrea
>
>
> On 21 June 2016 at 09:16, Gowri LN <[email protected]> wrote:
>
> > Hi All,
> >
> > I am trying to launch a very basic VM using Apache Brooklyn 0.9 on
> > OpenStack ( Liberty) setup. I tried the jclouds-openstack-devtest jar
> and
> > changed the location definition to openstack-devtest-compute ( as
> > suggested in - Stackoverflow-link
> > <
> >
> http://stackoverflow.com/questions/37652364/how-to-set-floating-ip-for-vm-using-apache-brooklyn-floating-ips-are-required/37655309?noredirect=1#comment62981578_37655309
> > >
> > ) but I get an error.
> >
> > Yaml -
> >
> > location:
> > jclouds:openstack-devtest-compute:http://x.x.x.x:5000/v2.0/:
> > identity: my-tenant:my-username
> > credential: my-password
> > name: VM4
> > services:
> > - type: brooklyn.entity.basic.EmptySoftwareProcess
> > name: Empty software process
> >
> > Error -
> >
> > > `Required entity not healthy: EmptySoftwareProcessImpl{id=lgMeL1qc}
> > >
> > > Failure running task invoking start[locations] on 1 node (HxHrFqvS):
> > Error
> > >> invoking start at EmptySoftwareProcessImpl{id=lgMeL1qc}: Unable to
> > access
> > >> cloud JcloudsLocation[openstack-devtest-compute:
> > >>
> >
> https://x.x.x.x:5000/v2.0/:my-tenant:my-password/openstack-devtest-compute:https://x.x.x.x:5000/v2.0/@cngl0O8K
> > ]
> > >> to resolve PortableTemplateBuilder[ports=[22], locationId=
> > >> https://x.x.x.x:5000/v2.0/,
> > >>
> >
> imageChooserFunction=org.apache.brooklyn.location.jclouds.BrooklynImageChooser$ImageChooserFromOrdering@4d3edd1d
> > ,
> > >> minRam=2048]:
> > >> com.google.common.util.concurrent.UncheckedExecutionException:
> > >> org.jclouds.http.HttpResponseException: Connection refused connecting
> to
> > >> POST https://127.0.0.1/identity/v2.0/tokens HTTP/1.1`
> > >
> > >
> > Any suggestions ?
> >
> > Thanks in advance!
> >
>
