Re: Failing to deploy

ment. >>>>>>>>>> The debug logs say: >>>>>>>>>> >>>>>>>>>> 017-04-17 05:18:36,258 DEBUG jclouds.compute >>>>>>>>>> [brooklyn-execmanager-ZM1RaPwv-3]: << matched >>

Re: Failing to deploy

;> > regionId/id > >> > >> > >> > >> > >> > >> > >> > >> > >> Maybe someone with a deeper understanding of Brooklyn with > >> > Openstack > >> > >> can >

Re: Failing to deploy

>> latest/ops/locations/index.htm >> > >> > >> l#os-setup >> > >> > >> >> > >> > >> On Mon, 17 Apr 2017 at 15:09 Rupinder Singh <rupi@gmail.com >> > >> > >> wrote: >> > >> &

Re: Failing to deploy

>> > >> On Mon, 17 Apr 2017 at 15:09 Rupinder Singh <rupi@gmail.com >> > >> > >> wrote: >> > >> > >> >> > >> > >> > Hi Thomas, >> > >> > >> > >> > >> >

Re: Failing to deploy

; >> > >> > happened to check TryStack dashboard moments ago. I noticed the > > >> Ubuntu > > >> > >> > intance running and active. However, it isn't accepting the > user > > >> login > > >> > >> or &

Re: Failing to deploy

, Apr 17, 2017 at 6:45 PM, Rupinder Singh < > >> rupi@gmail.com> > >> > >> > wrote: > >> > >> > > >> > >> > > Hi Thomas, > >> > >> > > > >> > >> > > I removed minRam in the

Re: Failing to deploy

> show running in TrySStack dashboard. However, it kept starting >> for >> > too >> > >> > long >> > >> > > and then crashed. The blueprint and logs are attached here. >> > >> > > >> > >> > > Rupinder >

Re: Failing to deploy

>> > >> > > >> > >> Looks like your Openstack does not have the minimum hardware > > >> > requirements > > >> > >> you specified in your blueprint: > > >> > >> > > >> > >> 2017-04-16 22:0

Re: Failing to deploy

obtained in 1ms;): Unable to match required VM > >> > >> template constraints PortableTemplateBuilder[ports=[22], > >> > >> imageId=RegionOne/76f5f4aa-a78f-4703-b738-cab967957431, > >> > >> imageChooserFunction=org.apache.brooklyn.location.j

Re: Failing to deploy

>> > >> BrooklynImageChooser$ImageChooserFromOrdering, >> > >> minRam=8000] when trying to provision VM in >> > >> JcloudsLocation[openstack-nova:http://8.43.86.2:5000/v2.0/: >> > >> facebook1939146382766976:facebook1939146382766976@c04b5y

Re: Failing to deploy

res(0.0),minRam(8000),minDisk(0.0)) > >> > >> > >> You should try to lower down the `minRam` or removing it entirely. If > >> that's not acceptable, I would suggest that you create your own image + > >> hardware to make sure it matches your requi

Re: Failing to deploy

your requirements. >> >> Best. >> >> On Sun, 16 Apr 2017 at 18:12 Rupinder Singh <rupi@gmail.com> wrote: >> >> > -- Forwarded message -- >> > From: Rupinder Singh <rupi@gmail.com> >> > Date: Sun, Apr 16, 2

Fwd: Failing to deploy

message -- > > From: Rupinder Singh <rupi@gmail.com> > > Date: Sun, Apr 16, 2017 at 10:28 PM > > Subject: Re: Failing to deploy > > To: dev@brooklyn.apache.org > > > > > > Hi Andrea, > > > > No problem! > > > > I t

Re: Failing to deploy

wrote: > -- Forwarded message -- > From: Rupinder Singh <rupi@gmail.com> > Date: Sun, Apr 16, 2017 at 10:28 PM > Subject: Re: Failing to deploy > To: dev@brooklyn.apache.org > > > Hi Andrea, > > No problem! > > I tried that. Blueprints and l

Re: Failing to deploy

Rupinder, I've noticed in your latest example location: jclouds:openstack-nova: ... osFamily: ubuntu imageId: RegionOne/76f5f4aa-a78f-4703-b738-cab967957431 ... Could you try the following: location: jclouds:openstack-nova: ... imageId:

Re: Failing to deploy

Thanks Thomas. Andrea. I'll try and get back. Rupinder On 16 Apr 2017 14:31, "Andrea Turli" wrote: > Hi, > > In addition to the very good suggestione from Thomas, you can also try by > adding > > imageId=RegionOne/76f5f4aa-a78f-4703-b738-cab967957431 > > to force

Re: Failing to deploy

Hi, In addition to the very good suggestione from Thomas, you can also try by adding imageId=RegionOne/76f5f4aa-a78f-4703-b738-cab967957431 to force Brooklyn to pick your Ubuntu 16.04 image. This will couple your blueprint to the specific image, if that is not accettable for you there is also

Re: Failing to deploy

Hi Rupinder. Looks like your Openstack mislabelled your ubuntu images as you can see in this log extract: 2017-04-15 19:40:06,274 INFO o.a.b.l.j.JcloudsLocation [brooklyn-execmanager-Nhwh8YHI-21]: Image: {id=RegionOne/b55d48a9-29af-490c-af8d-ff897f688f0c,

Re: Failing to deploy

Hi, For your localhost failure, the brooklyn output shows "Cannot establish ssh connection to ... 127.0.0.1:22". You said earlier that you were running on Windows 7. Therefore deploying to localhost will not work with this blueprint, as it does not support windows. You could instead try

Re: Failing to deploy

Hi, For the trystack deployment, your pastebin shows an exception while jclouds is trying to destroy the node (presumably because of an earlier error). It expects the VM's id to be in the format "regionId/id". It got this id by calling the OpenStack api's Get_Server_Details. Unfortunately

Re: Failing to deploy

Hi Guglielmo, For l localhost deployment, yaml: https://pastebin.com/BtuU74yG brooklun output: https://pastebin.com/REGwLnWz br output: https://pastebin.com/sihThbK1 Rupinder On Thu, Apr 13, 2017 at 2:22 PM, Guglielmo Nigri < guglielmo.ni...@cloudsoftcorp.com> wrote: > Hi Rupinder, > >

Re: Failing to deploy

Hi Rupinder, The yaml is missing, can you post it to pastebin as well, maybe? It would also help to see the logs for the localhost deployment, too. Cheers, Guglielmo On 13 April 2017 at 05:49, Rupinder Singh wrote: > Hi, > > I'm using 0.10.0 on windows 7. I'm trying to