Quantcast

[cf-lattice] 0% [Connecting to ...] messages on AWS install

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[cf-lattice] 0% [Connecting to ...] messages on AWS install

Cornelia Davis
Hi all.

I'm deploying lattice to AWS and am getting a whole lot of messages like this: 

...
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
...

When they were first happening with the lattice brain I thought something was awry but the brain eventually seems to have finished initialization. Now I am getting all of the same messages from the cells I am standing up. Is this expected?

Thanks,
Cornelia

_______________________________________________
cf-lattice mailing list
[hidden email]
https://lists.cloudfoundry.org/mailman/listinfo/cf-lattice
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [cf-lattice] 0% [Connecting to ...] messages on AWS install

Cornelia Davis
This is not expected, or good. 

This issue was that no egress rules were set for the lattice security group, hence none of the nodes could access the resources needed for install. I'm still troubleshooting the terraform config (and my process around using it) but what has worked for me in the mean time is to start the "terraform apply" and then set the egress rules on the security group through the EC2 console. More to come but for now I have a lattice cluster on AWS!!

Cornelia

On Sun, May 17, 2015 at 4:58 PM, Cornelia Davis <[hidden email]> wrote:
Hi all.

I'm deploying lattice to AWS and am getting a whole lot of messages like this: 

...
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
...

When they were first happening with the lattice brain I thought something was awry but the brain eventually seems to have finished initialization. Now I am getting all of the same messages from the cells I am standing up. Is this expected?

Thanks,
Cornelia


_______________________________________________
cf-lattice mailing list
[hidden email]
https://lists.cloudfoundry.org/mailman/listinfo/cf-lattice
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [cf-lattice] 0% [Connecting to ...] messages on AWS install

Marco Nicosia
Thanks for the feedback, Cornelia!

Can I double check what version of Lattice you specified in your Terraform config? We have a new version coming out soon (early this coming week) which may considerably change your experience.

Regardless, I'd like to learn more about how your security group came to be set that way. It's not typical of versions I've tried.

-- Marco N.

On Sunday, May 17, 2015, Cornelia Davis <[hidden email]> wrote:
This is not expected, or good. 

This issue was that no egress rules were set for the lattice security group, hence none of the nodes could access the resources needed for install. I'm still troubleshooting the terraform config (and my process around using it) but what has worked for me in the mean time is to start the "terraform apply" and then set the egress rules on the security group through the EC2 console. More to come but for now I have a lattice cluster on AWS!!

Cornelia

On Sun, May 17, 2015 at 4:58 PM, Cornelia Davis <<a href="javascript:_e(%7B%7D,&#39;cvml&#39;,&#39;cdavis@pivotal.io&#39;);" target="_blank">cdavis@...> wrote:
Hi all.

I'm deploying lattice to AWS and am getting a whole lot of messages like this: 

...
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
...

When they were first happening with the lattice brain I thought something was awry but the brain eventually seems to have finished initialization. Now I am getting all of the same messages from the cells I am standing up. Is this expected?

Thanks,
Cornelia



--
--
  Marco Nicosia
  Product Manager
  Pivotal Software, Inc.
  c: 650-796-2948



_______________________________________________
cf-lattice mailing list
[hidden email]
https://lists.cloudfoundry.org/mailman/listinfo/cf-lattice
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [cf-lattice] 0% [Connecting to ...] messages on AWS install

Cornelia Davis
Hi Marco,

Tried both     


and


Oddly, 


also did not set the egress - the terraform output just showed:

...
module.lattice-aws.aws_security_group.lattice-network: Creating...
  description:                          "" => "lattice security group"
  egress.#:                             "" => "<computed>"
  ingress.#:                            "" => "2"
  ingress.1377569725.cidr_blocks.#:     "" => "1"
  ingress.1377569725.cidr_blocks.0:     "" => "0.0.0.0/0"
  ingress.1377569725.from_port:         "" => "1"
  ingress.1377569725.protocol:          "" => "tcp"
  ingress.1377569725.security_groups.#: "" => "0"
  ingress.1377569725.self:              "" => "0"
  ingress.1377569725.to_port:           "" => "65535"
  ingress.2101722032.cidr_blocks.#:     "" => "1"
  ingress.2101722032.cidr_blocks.0:     "" => "0.0.0.0/0"
  ingress.2101722032.from_port:         "" => "1"
  ingress.2101722032.protocol:          "" => "udp"
  ingress.2101722032.security_groups.#: "" => "0"
  ingress.2101722032.self:              "" => "0"
  ingress.2101722032.to_port:           "" => "65535"
  name:                                 "" => "lattice"
  owner_id:                             "" => "<computed>"
  tags.#:                               "" => "1"
  tags.Name:                            "" => "lattice"
  vpc_id:                               "" => "vpc-b72711d2"
...

On Sun, May 17, 2015 at 7:56 PM, Marco Nicosia <[hidden email]> wrote:
Thanks for the feedback, Cornelia!

Can I double check what version of Lattice you specified in your Terraform config? We have a new version coming out soon (early this coming week) which may considerably change your experience.

Regardless, I'd like to learn more about how your security group came to be set that way. It's not typical of versions I've tried.

-- Marco N.


On Sunday, May 17, 2015, Cornelia Davis <[hidden email]> wrote:
This is not expected, or good. 

This issue was that no egress rules were set for the lattice security group, hence none of the nodes could access the resources needed for install. I'm still troubleshooting the terraform config (and my process around using it) but what has worked for me in the mean time is to start the "terraform apply" and then set the egress rules on the security group through the EC2 console. More to come but for now I have a lattice cluster on AWS!!

Cornelia

On Sun, May 17, 2015 at 4:58 PM, Cornelia Davis <[hidden email]> wrote:
Hi all.

I'm deploying lattice to AWS and am getting a whole lot of messages like this: 

...
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
...

When they were first happening with the lattice brain I thought something was awry but the brain eventually seems to have finished initialization. Now I am getting all of the same messages from the cells I am standing up. Is this expected?

Thanks,
Cornelia



--
--
  Marco Nicosia
  Product Manager
  Pivotal Software, Inc.
  c: <a href="tel:650-796-2948" value="+16507962948" target="_blank">650-796-2948




_______________________________________________
cf-lattice mailing list
[hidden email]
https://lists.cloudfoundry.org/mailman/listinfo/cf-lattice
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [cf-lattice] 0% [Connecting to ...] messages on AWS install

Marco Nicosia
Cornelia,

Short version: When you change the source ref, you need to additionally do a "terraform get -update" before "terraform apply." This should help set the egress rules.

We have some work to do on the upgrade process. Right now, our instructions don't cover how to make changes in the Terraform file. (Which is oddly appropriate, because that's the correct version for that Terraform file.)

--
  Marco Nicosia
  Product Manager
  Pivotal Software, Inc.
  c: 650-796-2948


On Sun, May 17, 2015 at 8:00 PM, Cornelia Davis <[hidden email]> wrote:
Hi Marco,

Tried both     


and


Oddly, 


also did not set the egress - the terraform output just showed:

...
module.lattice-aws.aws_security_group.lattice-network: Creating...
  description:                          "" => "lattice security group"
  egress.#:                             "" => "<computed>"
  ingress.#:                            "" => "2"
  ingress.1377569725.cidr_blocks.#:     "" => "1"
  ingress.1377569725.cidr_blocks.0:     "" => "0.0.0.0/0"
  ingress.1377569725.from_port:         "" => "1"
  ingress.1377569725.protocol:          "" => "tcp"
  ingress.1377569725.security_groups.#: "" => "0"
  ingress.1377569725.self:              "" => "0"
  ingress.1377569725.to_port:           "" => "65535"
  ingress.2101722032.cidr_blocks.#:     "" => "1"
  ingress.2101722032.cidr_blocks.0:     "" => "0.0.0.0/0"
  ingress.2101722032.from_port:         "" => "1"
  ingress.2101722032.protocol:          "" => "udp"
  ingress.2101722032.security_groups.#: "" => "0"
  ingress.2101722032.self:              "" => "0"
  ingress.2101722032.to_port:           "" => "65535"
  name:                                 "" => "lattice"
  owner_id:                             "" => "<computed>"
  tags.#:                               "" => "1"
  tags.Name:                            "" => "lattice"
  vpc_id:                               "" => "vpc-b72711d2"
...

On Sun, May 17, 2015 at 7:56 PM, Marco Nicosia <[hidden email]> wrote:
Thanks for the feedback, Cornelia!

Can I double check what version of Lattice you specified in your Terraform config? We have a new version coming out soon (early this coming week) which may considerably change your experience.

Regardless, I'd like to learn more about how your security group came to be set that way. It's not typical of versions I've tried.

-- Marco N.


On Sunday, May 17, 2015, Cornelia Davis <[hidden email]> wrote:
This is not expected, or good. 

This issue was that no egress rules were set for the lattice security group, hence none of the nodes could access the resources needed for install. I'm still troubleshooting the terraform config (and my process around using it) but what has worked for me in the mean time is to start the "terraform apply" and then set the egress rules on the security group through the EC2 console. More to come but for now I have a lattice cluster on AWS!!

Cornelia

On Sun, May 17, 2015 at 4:58 PM, Cornelia Davis <[hidden email]> wrote:
Hi all.

I'm deploying lattice to AWS and am getting a whole lot of messages like this: 

...
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
...

When they were first happening with the lattice brain I thought something was awry but the brain eventually seems to have finished initialization. Now I am getting all of the same messages from the cells I am standing up. Is this expected?

Thanks,
Cornelia



--
--
  Marco Nicosia
  Product Manager
  Pivotal Software, Inc.
  c: <a href="tel:650-796-2948" value="+16507962948" target="_blank">650-796-2948





_______________________________________________
cf-lattice mailing list
[hidden email]
https://lists.cloudfoundry.org/mailman/listinfo/cf-lattice
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [cf-lattice] 0% [Connecting to ...] messages on AWS install

Marco Nicosia
Hi Cornelia,

Just checking in with you, did our suggestion resolve your problem?


--
  Marco Nicosia
  Product Manager
  Pivotal Software, Inc.
  c: 650-796-2948


On Mon, May 18, 2015 at 7:38 AM, Marco Nicosia <[hidden email]> wrote:
Cornelia,

Short version: When you change the source ref, you need to additionally do a "terraform get -update" before "terraform apply." This should help set the egress rules.

We have some work to do on the upgrade process. Right now, our instructions don't cover how to make changes in the Terraform file. (Which is oddly appropriate, because that's the correct version for that Terraform file.)

--
  Marco Nicosia
  Product Manager
  Pivotal Software, Inc.
  c: <a href="tel:650-796-2948" value="+16507962948" target="_blank">650-796-2948


On Sun, May 17, 2015 at 8:00 PM, Cornelia Davis <[hidden email]> wrote:
Hi Marco,

Tried both     


and


Oddly, 


also did not set the egress - the terraform output just showed:

...
module.lattice-aws.aws_security_group.lattice-network: Creating...
  description:                          "" => "lattice security group"
  egress.#:                             "" => "<computed>"
  ingress.#:                            "" => "2"
  ingress.1377569725.cidr_blocks.#:     "" => "1"
  ingress.1377569725.cidr_blocks.0:     "" => "0.0.0.0/0"
  ingress.1377569725.from_port:         "" => "1"
  ingress.1377569725.protocol:          "" => "tcp"
  ingress.1377569725.security_groups.#: "" => "0"
  ingress.1377569725.self:              "" => "0"
  ingress.1377569725.to_port:           "" => "65535"
  ingress.2101722032.cidr_blocks.#:     "" => "1"
  ingress.2101722032.cidr_blocks.0:     "" => "0.0.0.0/0"
  ingress.2101722032.from_port:         "" => "1"
  ingress.2101722032.protocol:          "" => "udp"
  ingress.2101722032.security_groups.#: "" => "0"
  ingress.2101722032.self:              "" => "0"
  ingress.2101722032.to_port:           "" => "65535"
  name:                                 "" => "lattice"
  owner_id:                             "" => "<computed>"
  tags.#:                               "" => "1"
  tags.Name:                            "" => "lattice"
  vpc_id:                               "" => "vpc-b72711d2"
...

On Sun, May 17, 2015 at 7:56 PM, Marco Nicosia <[hidden email]> wrote:
Thanks for the feedback, Cornelia!

Can I double check what version of Lattice you specified in your Terraform config? We have a new version coming out soon (early this coming week) which may considerably change your experience.

Regardless, I'd like to learn more about how your security group came to be set that way. It's not typical of versions I've tried.

-- Marco N.


On Sunday, May 17, 2015, Cornelia Davis <[hidden email]> wrote:
This is not expected, or good. 

This issue was that no egress rules were set for the lattice security group, hence none of the nodes could access the resources needed for install. I'm still troubleshooting the terraform config (and my process around using it) but what has worked for me in the mean time is to start the "terraform apply" and then set the egress rules on the security group through the EC2 console. More to come but for now I have a lattice cluster on AWS!!

Cornelia

On Sun, May 17, 2015 at 4:58 PM, Cornelia Davis <[hidden email]> wrote:
Hi all.

I'm deploying lattice to AWS and am getting a whole lot of messages like this: 

...
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
...

When they were first happening with the lattice brain I thought something was awry but the brain eventually seems to have finished initialization. Now I am getting all of the same messages from the cells I am standing up. Is this expected?

Thanks,
Cornelia



--
--
  Marco Nicosia
  Product Manager
  Pivotal Software, Inc.
  c: <a href="tel:650-796-2948" value="+16507962948" target="_blank">650-796-2948






_______________________________________________
cf-lattice mailing list
[hidden email]
https://lists.cloudfoundry.org/mailman/listinfo/cf-lattice
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [cf-lattice] 0% [Connecting to ...] messages on AWS install

Cornelia Davis
I FINALLY had a chance to look back at this and no, doing the terraform get -update after editing the terraform config file did not do the trick. I just bumped everything to v0.2.5 and it seems to have resolved the problem. I am (and was even with my 2.4 attempt) running Terraform v0.5.3 and just found the comment in https://github.com/cloudfoundry-incubator/lattice/releases/tag/v0.2.4 that the aws deploy wouldn't work properly with terraform 0.5.0+ so perhaps that was the cause?

On Wed, May 20, 2015 at 8:45 AM, Marco Nicosia <[hidden email]> wrote:
Hi Cornelia,

Just checking in with you, did our suggestion resolve your problem?


--
  Marco Nicosia
  Product Manager
  Pivotal Software, Inc.
  c: <a href="tel:650-796-2948" value="+16507962948" target="_blank">650-796-2948


On Mon, May 18, 2015 at 7:38 AM, Marco Nicosia <[hidden email]> wrote:
Cornelia,

Short version: When you change the source ref, you need to additionally do a "terraform get -update" before "terraform apply." This should help set the egress rules.

We have some work to do on the upgrade process. Right now, our instructions don't cover how to make changes in the Terraform file. (Which is oddly appropriate, because that's the correct version for that Terraform file.)

--
  Marco Nicosia
  Product Manager
  Pivotal Software, Inc.
  c: <a href="tel:650-796-2948" value="+16507962948" target="_blank">650-796-2948


On Sun, May 17, 2015 at 8:00 PM, Cornelia Davis <[hidden email]> wrote:
Hi Marco,

Tried both     


and


Oddly, 


also did not set the egress - the terraform output just showed:

...
module.lattice-aws.aws_security_group.lattice-network: Creating...
  description:                          "" => "lattice security group"
  egress.#:                             "" => "<computed>"
  ingress.#:                            "" => "2"
  ingress.1377569725.cidr_blocks.#:     "" => "1"
  ingress.1377569725.cidr_blocks.0:     "" => "0.0.0.0/0"
  ingress.1377569725.from_port:         "" => "1"
  ingress.1377569725.protocol:          "" => "tcp"
  ingress.1377569725.security_groups.#: "" => "0"
  ingress.1377569725.self:              "" => "0"
  ingress.1377569725.to_port:           "" => "65535"
  ingress.2101722032.cidr_blocks.#:     "" => "1"
  ingress.2101722032.cidr_blocks.0:     "" => "0.0.0.0/0"
  ingress.2101722032.from_port:         "" => "1"
  ingress.2101722032.protocol:          "" => "udp"
  ingress.2101722032.security_groups.#: "" => "0"
  ingress.2101722032.self:              "" => "0"
  ingress.2101722032.to_port:           "" => "65535"
  name:                                 "" => "lattice"
  owner_id:                             "" => "<computed>"
  tags.#:                               "" => "1"
  tags.Name:                            "" => "lattice"
  vpc_id:                               "" => "vpc-b72711d2"
...

On Sun, May 17, 2015 at 7:56 PM, Marco Nicosia <[hidden email]> wrote:
Thanks for the feedback, Cornelia!

Can I double check what version of Lattice you specified in your Terraform config? We have a new version coming out soon (early this coming week) which may considerably change your experience.

Regardless, I'd like to learn more about how your security group came to be set that way. It's not typical of versions I've tried.

-- Marco N.


On Sunday, May 17, 2015, Cornelia Davis <[hidden email]> wrote:
This is not expected, or good. 

This issue was that no egress rules were set for the lattice security group, hence none of the nodes could access the resources needed for install. I'm still troubleshooting the terraform config (and my process around using it) but what has worked for me in the mean time is to start the "terraform apply" and then set the egress rules on the security group through the EC2 console. More to come but for now I have a lattice cluster on AWS!!

Cornelia

On Sun, May 17, 2015 at 4:58 PM, Cornelia Davis <[hidden email]> wrote:
Hi all.

I'm deploying lattice to AWS and am getting a whole lot of messages like this: 

...
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
...

When they were first happening with the lattice brain I thought something was awry but the brain eventually seems to have finished initialization. Now I am getting all of the same messages from the cells I am standing up. Is this expected?

Thanks,
Cornelia



--
--
  Marco Nicosia
  Product Manager
  Pivotal Software, Inc.
  c: <a href="tel:650-796-2948" value="+16507962948" target="_blank">650-796-2948







_______________________________________________
cf-lattice mailing list
[hidden email]
https://lists.cloudfoundry.org/mailman/listinfo/cf-lattice
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [cf-lattice] 0% [Connecting to ...] messages on AWS install

Marco Nicosia
Well shucks, it doesn't sound like it's worth trying to replicate your issue at this point - especially since you're not having it after upgrading.

I think we're going to have to consider it a mystery. Thanks for getting back to us; and do continue to use the list or GitHub to report any issues in the future!

--
  Marco Nicosia
  Product Manager
  Pivotal Software, Inc.


On Wed, Jun 10, 2015 at 9:06 PM, Cornelia Davis <[hidden email]> wrote:
I FINALLY had a chance to look back at this and no, doing the terraform get -update after editing the terraform config file did not do the trick. I just bumped everything to v0.2.5 and it seems to have resolved the problem. I am (and was even with my 2.4 attempt) running Terraform v0.5.3 and just found the comment in https://github.com/cloudfoundry-incubator/lattice/releases/tag/v0.2.4 that the aws deploy wouldn't work properly with terraform 0.5.0+ so perhaps that was the cause?

On Wed, May 20, 2015 at 8:45 AM, Marco Nicosia <[hidden email]> wrote:
Hi Cornelia,

Just checking in with you, did our suggestion resolve your problem?


--
  Marco Nicosia
  Product Manager
  Pivotal Software, Inc.
  c: <a href="tel:650-796-2948" value="+16507962948" target="_blank">650-796-2948


On Mon, May 18, 2015 at 7:38 AM, Marco Nicosia <[hidden email]> wrote:
Cornelia,

Short version: When you change the source ref, you need to additionally do a "terraform get -update" before "terraform apply." This should help set the egress rules.

We have some work to do on the upgrade process. Right now, our instructions don't cover how to make changes in the Terraform file. (Which is oddly appropriate, because that's the correct version for that Terraform file.)

--
  Marco Nicosia
  Product Manager
  Pivotal Software, Inc.
  c: <a href="tel:650-796-2948" value="+16507962948" target="_blank">650-796-2948


On Sun, May 17, 2015 at 8:00 PM, Cornelia Davis <[hidden email]> wrote:
Hi Marco,

Tried both     


and


Oddly, 


also did not set the egress - the terraform output just showed:

...
module.lattice-aws.aws_security_group.lattice-network: Creating...
  description:                          "" => "lattice security group"
  egress.#:                             "" => "<computed>"
  ingress.#:                            "" => "2"
  ingress.1377569725.cidr_blocks.#:     "" => "1"
  ingress.1377569725.cidr_blocks.0:     "" => "0.0.0.0/0"
  ingress.1377569725.from_port:         "" => "1"
  ingress.1377569725.protocol:          "" => "tcp"
  ingress.1377569725.security_groups.#: "" => "0"
  ingress.1377569725.self:              "" => "0"
  ingress.1377569725.to_port:           "" => "65535"
  ingress.2101722032.cidr_blocks.#:     "" => "1"
  ingress.2101722032.cidr_blocks.0:     "" => "0.0.0.0/0"
  ingress.2101722032.from_port:         "" => "1"
  ingress.2101722032.protocol:          "" => "udp"
  ingress.2101722032.security_groups.#: "" => "0"
  ingress.2101722032.self:              "" => "0"
  ingress.2101722032.to_port:           "" => "65535"
  name:                                 "" => "lattice"
  owner_id:                             "" => "<computed>"
  tags.#:                               "" => "1"
  tags.Name:                            "" => "lattice"
  vpc_id:                               "" => "vpc-b72711d2"
...

On Sun, May 17, 2015 at 7:56 PM, Marco Nicosia <[hidden email]> wrote:
Thanks for the feedback, Cornelia!

Can I double check what version of Lattice you specified in your Terraform config? We have a new version coming out soon (early this coming week) which may considerably change your experience.

Regardless, I'd like to learn more about how your security group came to be set that way. It's not typical of versions I've tried.

-- Marco N.


On Sunday, May 17, 2015, Cornelia Davis <[hidden email]> wrote:
This is not expected, or good. 

This issue was that no egress rules were set for the lattice security group, hence none of the nodes could access the resources needed for install. I'm still troubleshooting the terraform config (and my process around using it) but what has worked for me in the mean time is to start the "terraform apply" and then set the egress rules on the security group through the EC2 console. More to come but for now I have a lattice cluster on AWS!!

Cornelia

On Sun, May 17, 2015 at 4:58 PM, Cornelia Davis <[hidden email]> wrote:
Hi all.

I'm deploying lattice to AWS and am getting a whole lot of messages like this: 

...
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.3 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.226.56.59)]
module.lattice-aws.aws_instance.cell.4 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.1 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.0 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.205.195.154)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
module.lattice-aws.aws_instance.cell.2 (remote-exec): 0% [Connecting to us-east-1.ec2.archive.ubuntu.com (54.87.136.115)]
...

When they were first happening with the lattice brain I thought something was awry but the brain eventually seems to have finished initialization. Now I am getting all of the same messages from the cells I am standing up. Is this expected?

Thanks,
Cornelia



--
--
  Marco Nicosia
  Product Manager
  Pivotal Software, Inc.
  c: <a href="tel:650-796-2948" value="+16507962948" target="_blank">650-796-2948








_______________________________________________
cf-lattice mailing list
[hidden email]
https://lists.cloudfoundry.org/mailman/listinfo/cf-lattice
Loading...