cloudcaptainsh / cloudcaptain Goto Github PK

The Boxfuse website currently only displays the convention properties exposed by the Gradle plugin. It should also display what properties are available on the tasks themselves because it's common to customise these in a build file.

Here are a couple of reasons why:

• You can't lazily configure tasks through convention properties, changing the values based on other aspects of the build.
• It's awkward to have multiple configurations for a task. I want to specify different environment variables for the run task depending on whether it's going to AWS or Virtual Box.

Ideally we'd be able to create our own instances of the tasks and not just rely on the task instances created by the plugin.

After changing the name of the project directory to talksubmissions to work around #31, I once again tried the boxfuseLs task. Unfortunately it's not displaying anything. Just to check I also ran:

boxfuse ls --app talksubmissions

which displayed the expected list of images.

Scope: EC2 instances

Tag name: Name
Tag value: boxfuse user/app:version@env
Example: boxfuse myuser/myapp:1.2.3@test

From a user perspective, it is currently not entirely clear which AWS IAM policies should be assigned to the Boxfuse user.

This should be made clearer and/or a copy-pastable example policy should be provided.

Currently when you create an an application with Boxfuse you have to specify that your app is either a single instance or load balanced.

It should be possible to set this up at an environment level instead. For example the 'test' environment would just be a single instance whereas the 'prod' environment would be load balanced.

Would it be possible for boxfuse to enable enhanced networking on supported ec2 instances?
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/enhanced-networking.html

What settings does the boxfuse OS have for file descriptors, socket reuse, max connections etc?

Currently copy-pasting them invokes them against the default platform (VirtualBox), which means they break when running against AWS.

Add Google Login support, in addition to the existing Amazon option.

Currently I do not see the option to deploy without using an Elastic IP.
Here is my use case:

1. I deploy many micro servers with different services
2. They all communicate via SQS
3. Health checks can be done via Spring Actuator
4. I only need Elastic IP's for the public facing server

I am running out of Elastic IP's (I can ask for more, but I shouldn't need to).

Is this possible already and I am just missing it?

I have setup my load balancer to accept SSL connections in order for this to connect to my boxfuse app I had to modify the associated security group to allow the inbound HTTPS on 443. Which worked fine.

The problem I have is that every time I redeploy my app the security group is recreated and the HTTPS mapping is lost. So I need to manually make this change again. Is there a way to facilitate this?

I have spent all day trying to get SSL to work on my boxfuse instance as per your instruction here. https://boxfuse.com/docs/payloads/springboot.html. The app starts up correctly and I can see that Tomcat is listening on port 443, but I can never get it to pass the health check.. Tbh though I dont think I really need this anyway, SSL connection to the load balancer only is good enough for me.

Currently items on the get started page, do not refresh automatically. It would be nicer and less confusing if they would refresh automatically without page reload based on client actions.

I can't work out how to get the same output from the boxfuseLs task as the boxfuse ls command. The former always seems to limit the images to the current project version.

Is it possible to create scalable applications but without the Amazon Elastic Load balancer?
When all my microservice applications launch they register with a self hosted DNS(https://github.com/Netflix/eureka). This handles the routing of requests to app instances and the Elastic load balancer is not hit at all.

For legacy frameworks that do not support session sharing via cookies, memcache or DB

Should be wget-able

I have a project directory with the name talk-submissions, which is invalid for Boxfuse, so I added this configuration block:

boxfuse {
    app = "talksubmissions"
    user = project.'boxfuse.user'
    secret = project.'boxfuse.secret'
}

but when I execute the boxfuseLs task, I'm seeing the following error:

* What went wrong:
Execution failed for task ':boxfuseLs'.
> ERROR: Invalid App name (may only contain lowercase letters and numbers): 
   talk-submissions => set boxfuse.app or boxfuse.image to a known App name to fix

This happens for names with German umlauts like Grün.

Support case opened with Amazon. They currently send data in an encoding that is different from their Content-Type HTTP header.

Status: waiting for Amazon reply.

This can happen when the application is deployed in version X and then again in version X+1 with a different health check config. The original ELB health check config created for X is then not updated for X+1. This should at least issue a warning and instruct the user how to fix this.

I just started to experiment with load balanced projects.

It works really well but it would be even better if you could attach auto scaling policies. You can add some manually but they get lost the next time you update the build.

Our projects will get usage spikes where we have CPU utilisation triggers to bring new instances online and then reduce over time as the utilisation drops.

The current example requires Maven and Git to be installed. Provide an alternative where this isn't necessary.

Or auto-terminate instance

VirtualBox currently doesn't support nested VT: https://www.virtualbox.org/ticket/4032

Boxfuse should detect that a user is attempting to launch an Instance on VirtualBox inside a VirtualBox VM (typically Vagrant + Ubuntu) and issue a warning/error that things most likely will not work.

Instructions for this are provided on the plugin portal. This makes it easier to include the plugin in a build.

For Team/ACL permissions including the ability to

• restrict deploying to certain environments for certain team members
• assign roles to individual team members (admin/developer/readonly)
• display an activity trail to audit actions (user X did Y)

Currently one must use the console to find out

Amazon provide a tool to monitor logs to detect errors and whatnot. This will be very useful to me so I can be sure my application is working properly.

This requires an agent to be running on your EC2 instance and looks fairly straightforward. https://docs.aws.amazon.com/AmazonCloudWatch/latest/DeveloperGuide/QuickStartEC2Instance.html

Could you look into this or provide an alternate solution?

Currently this is only supported when run is invoked against a payload. This would enable support for images as well.

Roles and interactions between S3, EC2 AMI, EC2 Instance, ...

I have noticed that I have many duplicate security groups. It seems each time an application redeploys a new security group is created. Can the previous group be deleted at this time?

Either via the CLI or the Console

Tasks include:

• deployments
• app configuration changes

For DW support this could be implemented as

• looking for boxfuse-test.yml or boxfuse-prod.yml first,
• if not found fallback to boxfuse.yml
• if not found assume user has configured everything manually

My software follows a microservice pattern, as part of that our software is broken down into a load of separate apps that all talk to each other.
Over time I will update each app and introduce breaking changes that will require the app connecting to it to update as well. A simple way around this would be to allow multiple software versions of the same app to be deployed. That way i will have no application downtime either.

Is this a possible update to Boxfuse in the future?

A big improvement in day to day use would be to support faster uploads. I have a 50Mbps up and down connection but my 200MB image takes around 45 minutes to upload.

Including tasks with AWS regions, security groups, vpcs, buckets, ami and instance types, ...