Re: Problem bootstraping FreeBSD on EC2

2016-01-28 Thread cen
Even using full path for the command it still doesn't work. It's like I'm in SSH limbo with access completely restricted. I'll play around with it a bit more but I think I will ultimately create my own AMI with sudo and bash preinstalled. Ignasi Barrera je 28. 01. 2016 ob 11:12 napisal: I

Re: Problem bootstraping FreeBSD on EC2

2016-01-28 Thread cen
Found the solution. If I execute commands in a single line using &&, written as a java string they work as expected. But reading them from a file where I write them line by line it cause the problems mentioned previously: Files.toString(file, Charsets.UTF_8) If I write them in a single line

Re: Group name not set for new nodes on EC2

2016-03-19 Thread cen
g the node, not when creating the group. After changing the group name in template to "jclouds#crossbuild" it started working. On 16. 03. 2016 18:12, Ignasi Barrera wrote: > Hi Cen, > > I'll have a look at this and the security group thing later today. > > Apologies for the lat

Re: Group name not set for new nodes on EC2

2016-03-19 Thread cen
Yeah sure. This is my final code to create the security group: AWSEC2SecurityGroupExtension client = (AWSEC2SecurityGroupExtension)compute.getSecurityGroupExtension().get(); SecurityGroup sg = client.createSecurityGroup("crossbuild", CLOUD_REGION); Builder b =

Group name not set for new nodes on EC2

2016-03-19 Thread cen
Hi For some reason the new nodes I create on EC2 are missing the group names. NodeMetadata node = getOnlyElement(compute.createNodesInGroup(vmSettings.getGroupName(), 1, template)); logger.info("New node " + node.getId() + " " + concat(node.getPrivateAddresses(), node.getPublicAddresses())+" in

Re: Group name not set for new nodes on EC2

2016-03-20 Thread cen
Agree with both statements. If there was documentation about this on createSecurityGroup I'd knew instantly what is going on. It could even be a generic statement that a certain method adheres to GroupNamingConvention. The pattern does not really match my use case because I create a single

Re: Group name not set for new nodes on EC2

2016-03-21 Thread cen
a/org/jclouds/ec2/compute/functions/RunningInstanceToNodeMetadata.java#L186-L194 > [2] https://issues.apache.org/jira/browse/JCLOUDS > > On 20 March 2016 at 13:31, Andrew Phillips <andr...@apache.org> wrote: >> >> >> On 2016-03-20 10:00, cen wrote: >>> >&

S3 bucket policies

2017-01-24 Thread cen
. If this exists an example would be most welcome. Best regards, cen

Re: JClouds TLS SNI support?

2016-09-15 Thread cen
. Ignasi Barrera je 15. 09. 2016 ob 12:06 napisal: Thanks for the feedback and all the details cen! Would you mind opening an issue in our JIRA so we can track and fix the Apache driver? On 15 September 2016 at 11:17, cen <imba...@gmail.com> wrote: Hi Default driver and Apache

Re: move jclouds to the attic?

2022-10-16 Thread cen
That is quite sad to hear but not entirely unexpected. I've been using jclouds on and off for the past 5 years, mainly for cloud storage and some cloud VM management. Nowadays for the IaC use case, to me at least, the declarative tools such as Terraform make more sense. I would like to