end-of-game / cloudunit Goto Github PK

Need to set the link after deployment to the first alias "web" added by the user.

Add limits to both the daemon and the containers.

Display Cloudunit environment name in top bar: Dev, Integration, QA, production...

Verify that there is no user with User Root Privileges into Docker Container CloudUnit

Provide a generic way to add actions to CloudUnit Lifecycle

• when an user is created (CreateUserAction interface)
• when an user logs into CloudUnit (LoginAction interface)
• when an user is updated (UpdateUserAction interface)
• when an user is deleted (DeleteUserAction interface)
• when an application is created (CreateApplicationAction interface)
• when an application is modified (ModifyApplicationAction interface)
• when an application is deleted (DeleteApplicationAction interface)
• when a module is added (AddModuleAction)
• when a module is removed (DeleteModuleAction)

Class Actions should be implemented custom interface and will be called to provide new behaviour. 

For example if an user logs into CloudUnit, AOP should intercept this step and execute all class implementing LoginAction. Easier to maintain rather than create a lot of AOP Class.

Stability into MacOS Env
Add Volumes tests
Add a wrapper for user friendly usage

No way to download File on Safari on El Capitan.
No problem with Firefox or Chrome.

In dev branch commit 55049c8

In the overview, the password module is blank

The goal is to allow the use of multiple instance of CloudUnit that share the same database and the same docker registry.

Add a the name of the instance of CloudUnit in the configuration.properties file. The instance name will be something like DEV, QA, PROD but we must be able to write anything.

When an application is created the name of the tag must be assigned to the application in the database. The instance of CloudUnit must show only the application with the Tag name of the instance except for the snapshot feature.

The snapshot feature allow to create a new application in an other instance of CloudUnit, at this time the new application will have the new tag name of the CloudUnit instance.

update documentation for front-end set-up

when I setting JVM option on "JVM Configuration" tab on https://cu-tests.cloudunit.io/ and save changes, settings not displayed on field.

No error displayed when the password is wrong. No urgency

Thanks @TMAMychaL for the idea

http://stackoverflow.com/questions/29429073/spring-boot-logback-and-logging-config-property

Hi,

I've tried to install Cloud unit on a small VirtualBox Debian 8 server, and I'm facing a big problem.

Ansible tells me :

TASK: [docker-host | Copie des clés pour le serveur de dev] ****************** 
fatal: [CUserver] => error while evaluating conditional: cu_environment == "dev"

FATAL: all hosts have already failed -- aborting

Any clue ?

At each git tag, a Docker tag is created and these tagged images are used in CloudUnit. However, the Java code always uses the latest tag, whereas it should use the version tag.

Write the tests

A common way to push information to

• a custom APM included into CloudUnit built on Telegraf + InfluxDB + Grafana.
• commercials APM as Level5 or DataDog

Maybe create specific container included as volume and each container should contain specific agent.
So the user could enable/disable them into the UI (or CLI...)

A bunch of scripts enable to manage the platform. A command line tool with completion would be much more convenient.

• Replace timeline with basic card list. Display template name, origin, creation date.
• Search templates by name

EAR Tests are not written.

In order to leave Vagrant and use the Docker Stack with Docker Machine.
Nice dev in Golang to do

In commit 55049c8

It is no longer possible to remove a module with the web UI. No error message nothing happens.
I have not tested with the CLI.

When an application has an alias, it can't be restarted anymore. Due to a error in hipacheredisutils

Configure the automaticated build for all CU IMAGES for all branches and tags

Needed to use them into public platform for Tutum

Maven is not right used to set the place where logs should be.
It is not a problem for dev but yes for production.

Logback.xml must be corrected else no way to use it with Docker automaticated build

Add checkstyle plugin into maven build processus

Need to have a relation between git tag and docker tag
Because without the dockerhub automatic builds are false.

Snapshots are bound to user's rights. When we restore a template, we need to set up again the rights and create the new user.

As explained into Docker Documentation

http://docs.docker.com/engine/articles/https/

Warning: These TLS commands will only generate a working set of certificates on Linux. Mac OS X comes with a version of OpenSSL that is incompatible with the certificates that Docker requires.

So we need to have a HTTP mode only for Mac Developper.

When we change from GitLab to GitHub, a wrong and dangerous commit appeared : The docker-compose file previously modified by sed was commited. So many ports as Redis, MySQL was exposed into OVH and we lost security.

I think we could avoit it if

• we use a docker-compose.template to generate the raw docker-compose.xml
• we have many docker-compose file : one for dev, one for production.

I prefer the first one solution but tell me...

Just verify that "ports to open" are right removed when application is removed.

Verify if an alias as "www.foo.com" is equals or not "www.foo.com/"

These two entries should be simular so the second not allowed

Display in the dashboard the information about the origin snapshot when an application is created from a template.

Add a new Field into Application and persist it.

++

A stopped application could not restart after the changing of the JVM memory.

Do not purpose an alias suffix but leave it free for any value

In the Web App, Log's applications are mixed between applications.

The problem seems to be from the manager because the URLs called by the AngularJS application are different.

Pushing the sources is functional, the application is built with Maven (Successfully) but the application is not deployed on the server (no deployment in the manager, no history in timeline)

Conditions for the test:

• Server: Tomcat 8
• Module installed: MySQL

add origin property to application when created from a snapshot

Missing source server

Server validation error when a user must be added

When the user arrives the first time into Login Page without setting user/password, no message should be displayed.

At the moment, we have a wrong red box

This feature is associated with "Plugin feature".

When an user is created/deleted into CloudUnit, the action must be propagated to Gitlab through plugin.
Before any developpment, an analysis must be done about GitLab API and hooks about this platform.

Add or verify if already exist new icon for

• InfluxDB
• Elasticsearch
• SolR
• Redis

Server-side validation not working for app template (snapshot) name.
Add test