accenture / adop-aws Goto Github PK

I was working with the Adop Hardened Two-Tier CloudFormation templates and there is an issue with the adop-c (layer-2). It was taking too long to create the instance. I checked the error system logs and I found this:

pts/part-001: line 16: lvcreate: command not found
[  142.420238] cloud-init[3509]: /var/lib/cloud/instance/scripts/part-001: line 16: lvcreate: command not found
[  142.420633] cloud-init[3509]: /var/lib/cloud/instance/scripts/part-001: line 16: lvcreate: command not found
[  142.421080] cloud-init[3509]: /var/lib/cloud/instance/scripts/part-001: line 16: lvcreate: command not found
[  142.421515] cloud-init[3509]: /var/lib/cloud/instance/scripts/part-001: line 16: lvcreate: command not found
[  142.421969] cloud-init[3509]: /var/lib/cloud/instance/scripts/part-001: line 16: lvcreate: command not found
[  142.422417] cloud-init[3509]: /var/lib/cloud/instance/scripts/part-001: line 16: lvcreate: command not found
[  142.422854] cloud-init[3509]: /var/lib/cloud/instance/scripts/part-001: line 16: lvcreate: command not found
[  142.423297] cloud-init[3509]: /var/lib/cloud/instance/scripts/part-001: line 16: lvcreate: command not found
[  142.423728] cloud-init[3509]: /var/lib/cloud/instance/scripts/part-001: line 16: lvcreate: command not found
[  142.424176] cloud-init[3509]: /var/lib/cloud/instance/scripts/part-001: line 16: lvcreate: command not found
[  142.424609] cloud-init[3509]: /var/lib/cloud/instance/scripts/part-001: line 16: lvcreate: command not found
[  142.425041] cloud-init[3509]: /var/lib/cloud/instance/scripts/part-001: line 16: lvcreate: command not found
[  142.425488] cloud-init[3509]: /var/lib/cloud/instance/scripts/part-001: line 16: lvcreate: command not found
[  142.425912] cloud-init[3509]: /var/lib/cloud/instance/scripts/part-001: line 16: lvcreate: command not found
[  142.426363] cloud-init[3509]: /var/lib/cloud/instance/scripts/part-001: line 16: lvcreate: command not found
[  142.426804] cloud-init[3509]: /var/lib/cloud/instance/scripts/part-001: line 16: lvcreate: command not found
[  142.427260] cloud-init[3509]: /var/lib/cloud/instance/scripts/part-001: line 16: lvcreate: command not found
[  142.427683] cloud-init[3509]: /var/lib/cloud/instance/scripts/part-001: line 16: lvcreate: command not found
[  142.428145] cloud-init[3509]: /var/lib/cloud/instance/scripts/part-001: line 16: lvcreate: command not found
[  142.428572] cloud-init[[  142.000060] serial8250: too much work for irq4
3509]: /var/lib/cloud/instance/scripts/part-001: line 16: lvcreate: command not found 

In the UserData section the line 16:
while [ $(lvs vg-docker/data &> /dev/null; echo $?) -ne 0 ]; do lvcreate -l 95%VG -n data vg-docker; done

But this is weird because line 11 install the lvm2

yum -y install wget unzip git lvm2 docker-engine-1.12.6-1.el7.centos.x86_64 ntp

Whilst deploying OpenVPN in us-east-1 I had to change AMI for BYOL License type as it was deprecated.

Below error is being observed while running Generate Project job. Kindly help

++ rm -rf /workspace/myDAS/Project_Management/Generate_Project/tmp
Processing DSL script jobs.groovy
[WARN] ADOP_PLATFORM_MANAGEMENT_VERSION is set to '' which is not a valid hash - defaulting to '*/master'
Warning: (jobs.groovy, line 34) workflowJob is deprecated
[ssh-agent] Stopped.
ERROR: (jobs.groovy, line 42) No signature of method: groovyScript() is applicable for argument types: (jobs$_run_closure2$_closure4$_closure9$_closure11$_closure12$_closure13) values: [jobs$_run_closure2$_closure4$_closure9$_closure11$_closure12$_closure13@b8a85cb]
Possible solutions: scriptText(), defaultChoice(), usePredefinedVariables()
Finished: FAILURE

Hi,

I've recently come across an issue whereby I spin up the stack but then have to manually update the compose instance if I want to use a custom Domain with valid SSL certs.

Example:

• Spin up the 2 tiered Stack
• Define Domain in Route53
• Add record set to point the domain name adop.customdomain.com to the outer Proxy
• Add the SSL termination rules on the outer proxy
• Update the Stack: Need to update the tools Manually
  • doesn't get persisted and will revert on compose restart
• log in to the stack, change the PROXY_IP variables, re-run compose
  • might create inconsistent behaviour with some of the tools (need to test)

A way to get around this would be to change the setup order and spin up all of the infrastructure components before spinning up the stack. This will allow inputting a CUSTOM_URL to the compose start which will then be used at up time.

As detected in below line, latest code for "adop-docker-compose" is used directly instead of a specific Release tag, so it could be improved using "adop-docker-compose" latest tagged Release (detected in Accenture/adop-docker-compose#281 issue).

HI,

After restarting my aws adop instance all the containers are removed.
Docker images ls is empty.Please help me in this.I have restarted the docker engine.

I think the backup role: EBSBackupLambdaRole created here:
https://github.com/Accenture/adop-aws/blob/master/layer5-ebs-backups/ebs-backup-lambda-function.yaml#L28

Probably doesn't need full lambda access. Especially for people using lambda for more than backups.

https://docs.aws.amazon.com/lambda/latest/dg/access-control-identity-based.html

The layered cloud formation templates make provisioning the ADOP stack very simple. Expanding this functionality to include a single cloud formation template to provision the entire stack would reduce manual steps. This would make the provisioning process faster and remove many opportunities for human error.