[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 not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[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 this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[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 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
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[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
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[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 and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[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 appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[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 as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[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 not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[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 issue?


---
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
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[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 your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[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 project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[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 alpine linux, but still need to figure out 
how to run cloudstack as a single .war file.


---
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
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[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 
smaller than then full ubuntu:14.04


---
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
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[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 does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[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 by build_no):_ 
https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0


**Failed tests:**
* test_vpc_vpn.py

 * ContextSuite context=TestRVPCSite2SiteVpn>:setup Failing since 11 runs

 * ContextSuite context=TestVpcRemoteAccessVpn>:setup Failing since 11 runs

 * ContextSuite context=TestVpcSite2SiteVpn>:setup Failing since 11 runs

* test_volumes.py

 * test_06_download_detached_volume Failed

* test_vm_life_cycle.py

 * test_10_attachAndDetach_iso Failed


**Skipped tests:**
test_vm_nic_adapter_vmxnet3
test_static_role_account_acls
test_deploy_vgpu_enabled_vm

**Passed test suits:**
test_deploy_vm_with_userdata.py
test_affinity_groups_projects.py
test_portable_publicip.py
test_over_provisioning.py
test_global_settings.py
test_scale_vm.py
test_service_offerings.py
test_routers_iptables_default_policy.py
test_routers.py
test_reset_vm_on_reboot.py
test_snapshots.py
test_deploy_vms_with_varied_deploymentplanners.py
test_login.py
test_list_ids_parameter.py
test_public_ip_range.py
test_multipleips_per_nic.py
test_regions.py
test_affinity_groups.py
test_network_acl.py
test_pvlan.py
test_nic.py
test_deploy_vm_root_resize.py
test_resource_detail.py
test_secondary_storage.py
test_disk_offerings.py


---
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
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---