[GitHub] cloudstack issue #1435: Dockerfile4.9

2016-12-02 Thread pdion891
Github user pdion891 commented on the issue: https://github.com/apache/cloudstack/pull/1435 This PR is not valid anymore replaced by Squashed: #1815 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does

[GitHub] cloudstack issue #1435: Dockerfile4.9

2016-12-01 Thread jburwell
Github user jburwell commented on the issue: https://github.com/apache/cloudstack/pull/1435 @pdion891 this [blog](https://ariejan.net/2011/07/05/git-squash-your-latests-commits-into-one/) is good description of squash process. --- If your project is set up for it, you can reply to

[GitHub] cloudstack issue #1435: Dockerfile4.9

2016-12-01 Thread pdion891
Github user pdion891 commented on the issue: https://github.com/apache/cloudstack/pull/1435 I've retested the management server, it work with Jenkins as the build is back online. @jburwell, do you know if there is a way to squash a commit within the same PR ? --- If your

[GitHub] cloudstack issue #1435: Dockerfile4.9

2016-12-01 Thread resmo
Github user resmo commented on the issue: https://github.com/apache/cloudstack/pull/1435 I used it for development and testing. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature

[GitHub] cloudstack issue #1435: Dockerfile4.9

2016-12-01 Thread jburwell
Github user jburwell commented on the issue: https://github.com/apache/cloudstack/pull/1435 @rhtyd agreed. I apologize for being unclear -- I would like to get this PR into 4.9.1.0, but it is not a release blocker. --- If your project is set up for it, you can reply to this email

[GitHub] cloudstack issue #1435: Dockerfile4.9

2016-12-01 Thread rhtyd
Github user rhtyd commented on the issue: https://github.com/apache/cloudstack/pull/1435 @jburwell good to have this, not sure how many people maybe using container/docker based mgmt servers? --- If your project is set up for it, you can reply to this email and have your reply

[GitHub] cloudstack issue #1435: Dockerfile4.9

2016-11-30 Thread jburwell
Github user jburwell commented on the issue: https://github.com/apache/cloudstack/pull/1435 @PaulAngus @rhtyd what are your thoughts on automating the testing of the Docker container? --- If your project is set up for it, you can reply to this email and have your reply appear on

[GitHub] cloudstack issue #1435: Dockerfile4.9

2016-11-30 Thread jburwell
Github user jburwell commented on the issue: https://github.com/apache/cloudstack/pull/1435 @pdion891 can you please investigate the Jenkins failure? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does

[GitHub] cloudstack issue #1435: Dockerfile4.9

2016-11-30 Thread jburwell
Github user jburwell commented on the issue: https://github.com/apache/cloudstack/pull/1435 @pdion891 if possible, I would like to get this merged for 4.9.1.0. How does this PR relate to #1789? Also, could you please investigate the Jenkins failure and create JIRA ticket for this

[GitHub] cloudstack issue #1435: Dockerfile4.9

2016-11-30 Thread pdion891
Github user pdion891 commented on the issue: https://github.com/apache/cloudstack/pull/1435 Hi @jburwell, do you think we can merge this in master or you are in a code freeze for 4.10.0.0 ? Thanks, --- If your project is set up for it, you can reply to this email and have

[GitHub] cloudstack issue #1435: Dockerfile4.9

2016-11-30 Thread pdion891
Github user pdion891 commented on the issue: https://github.com/apache/cloudstack/pull/1435 @resmo I've updated the PR. I've tested the simulator and marvin. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your

[GitHub] cloudstack issue #1435: Dockerfile4.9

2016-06-09 Thread pdion891
Github user pdion891 commented on the issue: https://github.com/apache/cloudstack/pull/1435 @runseb I agree, images must be smaller. for the simulator, it's kind of usefull to have everything in it but it's not container best practice for sure. other images, we could probably use

[GitHub] cloudstack issue #1435: Dockerfile4.9

2016-06-09 Thread runseb
Github user runseb commented on the issue: https://github.com/apache/cloudstack/pull/1435 LGTM I still think we need to put the db in another container, and start the whole thing with compose. Also we need to make the image smaller, maybe using Debian as base would be

[GitHub] cloudstack issue #1435: Dockerfile4.9

2016-06-08 Thread pdion891
Github user pdion891 commented on the issue: https://github.com/apache/cloudstack/pull/1435 @swill, @runseb does one of you could LGTM or comment thanks, --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project

[GitHub] cloudstack issue #1435: Dockerfile4.9

2016-06-06 Thread bvbharatk
Github user bvbharatk commented on the issue: https://github.com/apache/cloudstack/pull/1435 ### ACS CI BVT Run **Sumarry:** Build Number 146 Hypervisor xenserver NetworkType Advanced Passed=68 Failed=5 Skipped=3 _Link to logs Folder (search