Re: [VOTE] Apache CloudStack 4.6.2

[Boris Schrijver]

Name:
test_02_reboot_router_after_addition_of_one_guest_network | Status : SUCCESS ===
ok
Test to change service offering of router after addition of one guest network
... === TestName: test_04_chg_srv_off_router_after_addition_of_one_guest_network
| Status : SUCCESS ===
ok
Test destroy of router after addition of one guest network ... === TestName:
test_05_destroy_router_after_addition_of_one_guest_network | Status : SUCCESS
===
ok
Test to stop and start router after creation of VPC ... === TestName:
test_01_stop_start_router_after_creating_vpc | Status : SUCCESS ===
ok
Test to reboot the router after creating a VPC ... === TestName:
test_02_reboot_router_after_creating_vpc | Status : SUCCESS ===
ok
Tests to change service offering of the Router after ... === TestName:
test_04_change_service_offerring_vpc | Status : SUCCESS ===
ok
Test to destroy the router after creating a VPC ... === TestName:
test_05_destroy_router_after_creating_vpc | Status : SUCCESS ===
ok

--
Ran 41 tests in 9763.101s

OK
```

-- 

Met vriendelijke groet / Kind regards,

Boris Schrijver

PCextreme B.V.

http://www.pcextreme.nl/contact
Tel direct: +31 (0) 118 700 215

> On December 15, 2015 at 7:18 AM Wilder Rodrigues
> <wrodrig...@schubergphilis.com> wrote:
> 
> 
> Hi all,
> 
> Test this RC yesterday and here goes my +1 (binding). Details below:
> 
> ACS 4.6.2
> 
> :: Environment 1 ::
> 
> * Hardware required: TRUE
> * Management Server + MySQL on CentOS 7.1
> * One KVM Host on CentOS 7.1
> * Agent + Common RPMs built from 4.6.2  source
> 
> 
> :: Tests Suites Executed ::
> 
> nosetests --with-marvin
> --marvin-config=/data/shared/marvin/mct-zone1-kvm1-ISOLATED.cfg -s -a
> tags=advanced,required_hardware=true smoke/test_privategw_acl.py
> component/test_routers_network_ops.py component/test_vpc_redundant.py
> component/test_routers_iptables_default_policy.py
> component/test_vpc_router_nics.py component/test_password_server.py
> component/test_router_dhcphosts.py smoke/test_loadbalance.py
> smoke/test_internal_lb.py smoke/test_ssvm.py smoke/test_vpc_vpn.py
> smoke/test_network.py
> 
> 
> :: Environment 2 ::
> 
> * Hardware required: FALSE
> * Management Server + MySQL on CentOS 7.1
> * One KVM Host on CentOS 7.1
> * Agent + Common RPMs built from 4.6.2 source
> 
> 
> :: Tests Suites Executed ::
> 
> nosetests --with-marvin
> --marvin-config=/data/shared/marvin/mct-zone1-kvm1-ISOLATED.cfg -s -a
> tags=advanced,required_hardware=false smoke/test_routers.py
> smoke/test_reset_vm_on_reboot.py smoke/test_vm_life_cycle.py
> component/test_vpc_routers.py smoke/test_service_offerings.py
> component/test_vpc_offerings.py smoke/test_network_acl.py
>  smoke/test_network.py
> 
> 
> :: Summary ::
> 
> * Tests executes: 79
> * Successfull tests: 78
> * Skipped tests: 1 (*)
> * Failed tests: 0
> 
> Test skipped because I used only 1 host.
> 
> 
> > On 13 Dec 2015, at 19:36, Remi Bergsma <rberg...@schubergphilis.com> wrote:
> > 
> > Hi all,
> > 
> > In the past two weeks (since 4.6.1), 23 pull [1] requests have been merged
> > to 4.6 branch and then to master/4.7.0. Therefore it makes sense to wrap-up
> > the 4.6 release cycle with a final release and bring all the improvements to
> > our users. Vote e-mail below. Later today we will send another RC for 4.7.0.
> > 
> > 
> > I've created a 4.6.2 release candidate, with the following artifacts up for
> > a vote:
> > 
> > Git Branch and Commit SH:
> > https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=4.6.2-RC20151213T1914
> > 
> > Commit: 10e0130dd6e0c06deae4f5ccfd43d5bcecea57b6
> > 
> > Source release (checksums and signatures are available at the same
> > location):
> > https://dist.apache.org/repos/dist/dev/cloudstack/4.6.2/
> > 
> > PGP release keys (signed using A47DDC4F):
> > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> > 
> > Vote will be open for at least 72 hours.
> > 
> > For sanity in tallying the vote, can PMC members please be sure to indicate
> > "(binding)" with their vote?
> > 
> > [ ] +1  approve
> > [ ] +0  no opinion
> > [ ] -1  disapprove (and reason why)
> > 
> > 
> > [1] git log --pretty=oneline --abbrev-commit 4.6.1..4.6.2-RC20151213T1914 |
> > grep "Merge pull request"
> > 
>

Re: [VOTE] Apache CloudStack 4.7.0

[Boris Schrijver]

Hi all,

Hereby my vote for the ACS 4.7.0 RC 1

Details:

Vote: +1

Besides the integration tests (which all ran fine) I've also tested the
following:

 - S3 Integration (Secondary Storage) with NFS Staging store
 - Ceph RBD storage (Primary Storage)
 - Basic networking with security groups 

-- 

Met vriendelijke groet / Kind regards,

Boris Schrijver

PCextreme B.V.

http://www.pcextreme.nl/contact
Tel direct: +31 (0) 118 700 215

> On December 16, 2015 at 12:34 AM Remi Bergsma <rberg...@schubergphilis.com>
> wrote:
> 
> 
> +1 (binding)
> 
> This vote is based on testing on a real cloud.
> 
> At Schuberg Philis we built a new cloud based on ACS 4.7.0RC1 (upgraded from
> 4.6). It runs XenServer 6.5 clusters, a CentOS 7 management cluster, Galera DB
> (also on CentOS 7), HA proxies (CentOS 7), NFS storage and Nicira/NSX for
> networking/SDN. Capacity to start with is about 12TB ram and 500+ cores.
> Secondary storage is an S3 compatible solution (Cloudian) with NFS staging
> store. Configured LDAP for authentication.
> 
> Before a go-live we always do thorough testing and try to break the setup
> emulating crashes and problems.
> 
> We successful executed these CloudStack related tests:
> 
>   *   crashed a hypervisor which was poolmaster and saw recovery in about 5
> min (tested with/without returning of the hypervisor)
>   *   crashed a hypervisor which was NOT poolmaster and saw recovery in about
> 5 min (tested with/without returning of the hypervisor)
>   *   crashed overbooked hypervisor in a cluster with too many VMs to run on
> the remaining hypervisors. Saw it recovered fully when crashed hypervisor
> returned. (this you don’t want to happen, but at least the recovery was
> automatic)
>   *   crashed one of the app servers; the other one continued and took over.
> No user impact.
>   *   crashed the main Galera DB node, the two remaining nodes survived and
> kept working. No CloudStack impact.
>   *   did performance tests and walked into the default 200mbps limit on
> tiers. When we removed it (aka configured it properly) we could use full
> 10gbps.
>   *   crashed the NFS staging store, could not deploy VM from template that
> was not already on primary storage. Recovered automatically when NFS returned
> and VM was started.
>   *   many functional tests, also covered In the integration tests (spin many
> VMs, migrate, make port forwardings etc).
>   *   executed patch round (live migrating vms around), rebooting all
> hypervisors without user impact.
> 
> Conclusion:
> It’s pretty solid, even with one management server and a degraded database we
> could still continue and operate existing VMs and start new ones. When the
> nodes returned recovery was automatic.
> We feel confident running production with Apache CloudStack 4.7 and will start
> doing so later today!
> 
> Regards,
> Remi
> 
> PS:
> The integration tests we run in the dev/test environments were also successful
> (the same I executed on the PRs that were merged).
> 
> 
> 
> From: Remi Bergsma
> <rberg...@schubergphilis.com<mailto:rberg...@schubergphilis.com>>
> Date: Sunday 13 December 2015 21:27
> To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>"
> <dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>>
> Subject: [VOTE] Apache CloudStack 4.7.0
> 
> Hi all,
> 
> Since our 4.6.0 release (on Nov 13th, exactly 1 month ago), we have merged
> 100+ pull requests [1] with lots of bug fixes, refactoring and of course new
> features. Time for a new release!
> 
> 
> I've created a 4.7.0 release candidate, with the following artifacts up for a
> vote:
> 
> Git Branch and Commit SH:
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=4.7.0-RC20151213T2109
> 
> Commit: 2f26a859a971a9852ed9f6f34fe35e52fe6028a9
> 
> Source release (checksums and signatures are available at the same location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.7.0/
> 
> PGP release keys (signed using A47DDC4F):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> 
> Vote will be open for at least 72 hours.
> 
> For sanity in tallying the vote, can PMC members please be sure to indicate
> "(binding)" with their vote?
> 
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
> 
> 
> [1] git log --pretty=oneline --abbrev-commit origin/4.6..4.7.0-RC20151213T2109
> | grep "Merge pull request"
>

Re: Preparing 4.6.0 for announce

[Boris Schrijver]

Hi,

Once branched and tagged, I'll create the packages and upload them to
cloudstack.apt-get.eu!

Already busy on 4.7!!

-- 

Met vriendelijke groet / Kind regards,

Boris Schrijver

PCextreme B.V.

http://www.pcextreme.nl/contact
Tel direct: +31 6 33784542

> On November 13, 2015 at 9:44 PM Remi Bergsma <rberg...@schubergphilis.com>
> wrote:
> 
> 
> Hi all,
> 
> Now that we have a 4.6.0 GA release, we need to do some extra work to get it
> to our users. Let’s share the load and make it happen fast!
> 
> What’s on my list:
> 
>   *   Release Notes for 4.6.0 (let’s list the cool new stuff)
>   *   Jira needs to be up2date (was everything tagged with fixed-version 4.6.0
> really fixed?)
>   *   Documentation needs to be updated (4.6 branch / sections)
>   *   API documentation needs to be published (we kicked off a Jenkins job, a
> PR needs to be sent to cloudstack-www)
>   *   Packages need to be prepared on cloudstack.apt-get.eu
>   *   Announcement on the website
>   *   Announcement e-mail (will do this once everything is in place)
> 
> Some of us already worked on this. Please reply with an update on the current
> status so we know what is still needed. I would aim for this to be ready on
> Monday or Tuesday the latest.
> 
> 
> Please also note:
> 
> I just pushed the 4.6.0 tag. I’m also preparing a 4.6 branch from which we can
> create 4.6.x releases and also will prepare master for 4.7. I will complete
> this work over the weekend.
> 
>   *   Update your Pull Requests where needed: Bug fixes that need to be fixed
> in 4.6.0 need a Pull Request against 4.6 and after it is merged, it will be
> forward merged to master (I’m sure John will love this!)
>   *   Any Pull Request (new features for example) to master will not be
> available in 4.6.x
> 
> Do NOT merge stuff to master yet, please.
> 
> I will send another mail over the weekend on how I think we should proceed,
> now we have a stable master and a first release off of it.
> 
> Have a nice weekend!
> 
> Regards,
> Remi
>

Re: [VOTE] Apache CloudStack 4.6.0 (round 2)

[Boris Schrijver]

Hi all,

Hereby my vote for ACS 4.6.0 based on branch 4.6.0-RC20151110T1545.

+1

Based on testing with:
 - KVM Ubuntu 14.04.3
 - Basic networking
 - Ceph (Primary storage)
 - S3 (Secondary storage)
 - NFS (Secondary storage / Staging store)

Tested the following:
 - Template Uploading / Downloading
 - VM Creation / Starting / Stopping / Destroying
 - VM Migration
 - Volume creation / attaching / detaching
 - Snapshot creation / restoring
 - DHCP
 - Metadata server / Password server / SSH keys
 - Security groups ingress- / egress-rules.

Known issues:
 - The folder /var/lib/cloudstack is owned by root, if the install is done by
root. Therefore, when ACS tries to create a directory within it, it will fail.
Setting correct permissions fixes it. chown cloud:cloud /var/lib/cloudstack/
 - Scripts inside
/usr/share/cloudstack-management/webapps/client/WEB-INF/classes/scripts/storage/secondary/
don't have execute permission. Set correct permission using: chmod + x
/usr/share/cloudstack-management/webapps/client/WEB-INF/classes/scripts/storage/secondary/*

Known issues are packaging related and not blocking. They will be fixed in ACS
4.6.1.

-- 

Met vriendelijke groet / Kind regards,

Boris Schrijver

PCextreme B.V.

http://www.pcextreme.nl/contact
Tel direct: +31 6 33784542

> On November 10, 2015 at 4:03 PM Remi Bergsma <rberg...@schubergphilis.com>
> wrote:
> 
> 
> Hi all,
> 
> I've created a 4.6.0 release candidate, with the following artifacts up for a
> vote:
> 
> Git Branch and Commit SH:
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=4.6.0-RC20151110T1545
> 
> Commit: e31ade03c66368c64f0cd66cb7b0b754cddfb79d
> 
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.6.0/
> 
> PGP release keys (signed using A47DDC4F):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> 
> Vote will be open for at least 72 hours.
> 
> For sanity in tallying the vote, can PMC members please be sure to indicate
> "(binding)" with their vote?
> 
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>

Re: [ANNOUNCE] New committer: Boris Schrijver

[Boris Schrijver]

Thanks all! Now the real work begins... ;)

-- 

Met vriendelijke groet / Kind regards,

Boris Schrijver

PCextreme B.V.

http://www.pcextreme.nl/contact
Tel direct: +31 6 33784542

> On November 10, 2015 at 6:09 AM Jayapal Reddy Uradi
> <jayapalreddy.ur...@citrix.com> wrote:
> 
> 
> Congrats Boris !
> 
> -Jayapal
> 
> > On 09-Nov-2015, at 12:01 pm, Rajani Karuturi <raj...@apache.org> wrote:
> > 
> > The Project Management Committee (PMC) for Apache CloudStack
> > has asked Boris Schrijver to become a committer and we are pleased to
> > announce that he has accepted.
> > 
> > Boris is an active code contributor, tester.
> > Helps resolving issues, reviewing PRs and testing them.
> > 
> > Being a committer allows many contributors to contribute more
> > autonomously. For developers, it makes it easier to submit changes and
> > eliminates the need to have contributions reviewed via the patch
> > submission process. Whether contributions are development-related or
> > otherwise, it is a recognition of a contributor's participation in the
> > project and commitment to the project and the Apache Way.
> > 
> > Please join me in congratulating Boris
> > 
> > on behalf of the CloudStack PMC,
> > 
> > ~Rajani
>

Re: [VOTE] Apache CloudStack 4.6.0 (round 2)

[Boris Schrijver]

Hi,

I've build the DEB packages for Ubuntu Trusty Tahr (14.04). They are available
here:

https://cloudstack.o.auroraobjects.eu/trusty/cloudstack-agent_4.6.0_all.deb
https://cloudstack.o.auroraobjects.eu/trusty/cloudstack-cli_4.6.0_all.deb
https://cloudstack.o.auroraobjects.eu/trusty/cloudstack-common_4.6.0_all.deb
https://cloudstack.o.auroraobjects.eu/trusty/cloudstack-docs_4.6.0_all.deb
https://cloudstack.o.auroraobjects.eu/trusty/cloudstack-management_4.6.0_all.deb
https://cloudstack.o.auroraobjects.eu/trusty/cloudstack-usage_4.6.0_all.deb

-- 

Met vriendelijke groet / Kind regards,

Boris Schrijver

PCextreme B.V.

http://www.pcextreme.nl/contact
Tel direct: +31 6 33784542

> On November 10, 2015 at 4:16 PM Remi Bergsma <rberg...@schubergphilis.com>
> wrote:
> 
> 
> FYI: Jenkins was so kind to build us some packages, should we want to use
> them:
> 
> CentOS 7 packages
> http://jenkins.buildacloud.org/view/parameterized/job/cloudstack-rpm-packages-with-branch-parameter-centos7/3/
> 
> CentOS 6 packages
> http://jenkins.buildacloud.org/view/parameterized/job/cloudstack-rpm-packages-with-branch-parameter/22/
> 
> Maybe Boris can build some Ubuntu packages, please?
> 
> 
> Regards,
> Remi
> 
> 
> 
> 
> On 10/11/15 16:03, "Remi Bergsma" <rberg...@schubergphilis.com> wrote:
> 
> >Hi all,
> >
> >I've created a 4.6.0 release candidate, with the following artifacts up for a
> >vote:
> >
> >Git Branch and Commit SH:
> >https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=4.6.0-RC20151110T1545
> >
> >Commit: e31ade03c66368c64f0cd66cb7b0b754cddfb79d
> >
> >Source release (checksums and signatures are available at the same
> >location):
> >https://dist.apache.org/repos/dist/dev/cloudstack/4.6.0/
> >
> >PGP release keys (signed using A47DDC4F):
> >https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> >
> >Vote will be open for at least 72 hours.
> >
> >For sanity in tallying the vote, can PMC members please be sure to indicate
> >"(binding)" with their vote?
> >
> >[ ] +1  approve
> >[ ] +0  no opinion
> >[ ] -1  disapprove (and reason why)
> >

Re: Debian packages 4.6 RC1

[Boris Schrijver]

I've repackaged them as Remi requested. It includes my fix for Tomcat.

They are packaged for Trusty from the following commit:
https://github.com/borisroman/cloudstack/commit/20134ccf31e1b0114876eacf1fa081322ce9a6ac

https://cloudstack.o.auroraobjects.eu/trusty/fix/cloudstack-agent_4.6.0_all.deb
https://cloudstack.o.auroraobjects.eu/trusty/fix/cloudstack-cli_4.6.0_all.deb
https://cloudstack.o.auroraobjects.eu/trusty/fix/cloudstack-common_4.6.0_all.deb
https://cloudstack.o.auroraobjects.eu/trusty/fix/cloudstack-docs_4.6.0_all.deb
https://cloudstack.o.auroraobjects.eu/trusty/fix/cloudstack-management_4.6.0_all.deb
https://cloudstack.o.auroraobjects.eu/trusty/fix/cloudstack-usage_4.6.0_all.deb

-- 

Met vriendelijke groet / Kind regards,

Boris Schrijver

PCextreme B.V.

http://www.pcextreme.nl/contact
Tel direct: +31 6 33784542

> On November 5, 2015 at 11:10 AM Boris Schrijver <bo...@pcextreme.nl> wrote:
> 
> 
> Hi all!
> 
> I've made the DEB packages of the 4.6.0-RC20151104T1522 publicly available
> here:
> 
> https://cloudstack.o.auroraobjects.eu/precise/cloudstack-agent_4.6.0_all.deb
> https://cloudstack.o.auroraobjects.eu/precise/cloudstack-cli_4.6.0_all.deb
> https://cloudstack.o.auroraobjects.eu/precise/cloudstack-common_4.6.0_all.deb
> https://cloudstack.o.auroraobjects.eu/precise/cloudstack-docs_4.6.0_all.deb
> https://cloudstack.o.auroraobjects.eu/precise/cloudstack-management_4.6.0_all.deb
> https://cloudstack.o.auroraobjects.eu/precise/cloudstack-usage_4.6.0_all.deb
> https://cloudstack.o.auroraobjects.eu/trusty/cloudstack-agent_4.6.0_all.deb
> https://cloudstack.o.auroraobjects.eu/trusty/cloudstack-cli_4.6.0_all.deb
> https://cloudstack.o.auroraobjects.eu/trusty/cloudstack-common_4.6.0_all.deb
> https://cloudstack.o.auroraobjects.eu/trusty/cloudstack-docs_4.6.0_all.deb
> https://cloudstack.o.auroraobjects.eu/trusty/cloudstack-management_4.6.0_all.deb
> https://cloudstack.o.auroraobjects.eu/trusty/cloudstack-usage_4.6.0_all.deb
> 
> -- 
> 
> Met vriendelijke groet / Kind regards,
> 
> Boris Schrijver
> 
> PCextreme B.V.
> 
> http://www.pcextreme.nl/contact
> Tel direct: +31 6 33784542

RE: [VOTE] Apache CloudStack 4.6.0

[Boris Schrijver]

Same tomcat6 issue?

-- 

Met vriendelijke groet / Kind regards,

Boris Schrijver

PCextreme B.V.

http://www.pcextreme.nl/contact
Tel direct: +31 6 33784542

> On November 6, 2015 at 2:49 PM Paul Angus <paul.an...@shapeblue.com> wrote:
> 
> 
> Sorry guys.  CentOS 7 install is NOT fixed in 4.6.0-RC20151104T1522.
> 
> 
> Sorry had to fly out to client in Kenya, so not been able to work on it
> recently.
> 
> -1
> 
> [root@CentOS7ACSTest ~]# cloudstack-setup-management
> Starting to configure CloudStack Management Server:
> Configure Firewall ...[OK]
> Configure CloudStack Management Server ...[Failed]
> Cannot find /etc/cloudstack/management/server-nonssl.xml or
> /etc/cloudstack/management/tomcat6-nonssl.conf, https enables failed
> Try to restore your system:
> Restore Firewall ...  [OK]
> Restore CloudStack Management Server ...[OK]
> 
> 
> 
> 
> Regards,
> 
> Paul Angus
> VP Technology/Cloud Architect
> S: +44 20 3603 0540 | M: +447711418784 | T: CloudyAngus
> paul.an...@shapeblue.com
> 
> -Original Message-
> From: Remi Bergsma [mailto:rberg...@schubergphilis.com]
> Sent: 06 November 2015 13:33
> To: dev@cloudstack.apache.org
> Subject: Re: [VOTE] Apache CloudStack 4.6.0
> 
> Hi Raja,
> 
> Thanks for the report. Most of these seem test-case related. For any issue you
> doubt this, can you please verify them manually?
> 
> If it doesn’t work, please file a Jira issue (with details and stept) and set
> it to critical. It will then show up on the list of issues and we can discuss
> how to proceed.
> 
> https://issues.apache.org/jira/issues/?filter=12332940 (requires login)
> 
> 
> Regards,
> Remi
> 
> 
> 
> 
> On 06/11/15 12:07, "Raja Pullela" <raja.pull...@citrix.com> wrote:
> 
> >Here is the BVT report on the RC
> >KVM Basic – 98.6% , one test failed//test case issue KVM Adv – 96.3%,
> >four tests failed //couple due to VM deployment and couple due to test
> >case issue XS Basic – 97.2%, two tests failed//test case issues XS Adv
> >– 93.5%, seven tests failed //4 due to VM deployment and 3 due to test
> >case issues HyperV – 93.3%, seven tests failed Simulator – need to run
> >them… will report later today/tomorrow.
> >
> >
> >Failed test cases:
> >·
> >
> > integration.smoke.test_vpc_vpn.TestVpcRemoteAccessVpn.test_vpc_remote_access_vpn
> >//failed due to VM deployment
> >·
> >
> > integration.smoke.test_vpc_vpn.TestVpcSite2SiteVpn.test_vpc_site2site_vpn
> >//failed due to VM deployment
> >·
> >
> > integration.smoke.test_internal_lb.TestInternalLb.test02_internallb_haproxy_stats_on_all_interfaces
> >//failed due to VM deployment
> >·
> >
> > integration.smoke.test_internal_lb.TestInternalLb.test_01_internallb_roundrobin_1VPC_3VM_HTTP_port80
> >//failed due to VM deployment
> >·
> >
> > integration.smoke.test_over_provisioning.TestUpdateOverProvision.test_UpdateStorageOverProvisioningFactor
> >//test case issue
> >·
> >
> > integration.smoke.test_vm_snapshots.TestSnapshots.test_01_test_vm_volume_snapshot
> >//test case issue
> >· integration.smoke.test_iso.TestISO.test_07_list_default_iso //test
> >case issue
> >:setup  //test
> >case issue
> >
> >From: Raja Pullela [mailto:raja.pull...@citrix.com]
> >Sent: Friday, November 6, 2015 4:30 PM
> >To: dev@cloudstack.apache.org
> >Subject: RE: [VOTE] Apache CloudStack 4.6.0
> >
> >
> >Here is the BVT report on the RC -
> >
> >[cid:image001.png@01D118B0.21037340]
> >
> >
> >
> >
> >
> >-Original Message-
> >From: Wilder Rodrigues [mailto:wrodrig...@schubergphilis.com]
> >Sent: Friday, November 6, 2015 4:19 PM
> >To: dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>
> >Subject: Re: [VOTE] Apache CloudStack 4.6.0
> >
> >
> >
> >Thanks again, Lucian!
> >
> >
> >
> >I’m already working on 9015 and testing few things, hope to get it fixed
> >soon, but not for 4.6.0.
> >
> >
> >
> >If we kan keep the good work in terms of writing/executing tests - which will
> >help keeping Master stable - and also avoid merges that don’t follow the
> >rule(*), we can have a 4.6.1/4.7.0 (new features) within two month from now.
> >
> >
> >
> >So, let us all keep the great work concerning tests/quality/stability.
> >
> >
> >
> >Cheers,
> >
> >Wilder
> >
> >
> >
> >* 2 LGTMs 

Re: git tags on cloudstack repo

[Boris Schrijver]

Good point! Hadn't looked there. I don't think we should tag an RC as it's still
under active development.

-- 

Met vriendelijke groet / Kind regards,

Boris Schrijver

PCextreme B.V.

http://www.pcextreme.nl/contact
Tel direct: +31 6 33784542

> On November 5, 2015 at 9:47 AM Rene Moser <m...@renemoser.net> wrote:
> 
> 
> On 11/05/2015 09:45 AM, Erik Weber wrote:
> 
> > Unless I'm seeing wrong, we have a branch, and it's called
> 
> I am not seeing it on github yet, but on here
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=tags
>

Re: git tags on cloudstack repo

[Boris Schrijver]

I don't see a tag either. When the RC passes its vote, then a tag and
corresponding release will be created. Until then, we just have the rc branch.

-- 

Met vriendelijke groet / Kind regards,

Boris Schrijver

PCextreme B.V.

http://www.pcextreme.nl/contact
Tel direct: +31 6 33784542

> On November 5, 2015 at 9:45 AM Erik Weber <terbol...@gmail.com> wrote:
> 
> 
> On Thu, Nov 5, 2015 at 9:34 AM, Rene Moser <m...@renemoser.net> wrote:
> 
> > Hi
> >
> > I have kind of a question about the tagging policy in cloudstack git repo:
> >
> > We now have tag 4.6.0 but we call it an RC. This raises 2 problems:
> >
> >
> Unless I'm seeing wrong, we have a branch, and it's called
> '4.6.0-RC20151104T1522'
> 
> https://github.com/apache/cloudstack/tree/4.6.0-RC20151104T1522
> 
> Where are you seeing the 4.6.0 tag?
> 
> -- 
> Erik

Debian packages 4.6 RC1

[Boris Schrijver]

Hi all!

I've made the DEB packages of the 4.6.0-RC20151104T1522 publicly available here:

https://cloudstack.o.auroraobjects.eu/precise/cloudstack-agent_4.6.0_all.deb
https://cloudstack.o.auroraobjects.eu/precise/cloudstack-cli_4.6.0_all.deb
https://cloudstack.o.auroraobjects.eu/precise/cloudstack-common_4.6.0_all.deb
https://cloudstack.o.auroraobjects.eu/precise/cloudstack-docs_4.6.0_all.deb
https://cloudstack.o.auroraobjects.eu/precise/cloudstack-management_4.6.0_all.deb
https://cloudstack.o.auroraobjects.eu/precise/cloudstack-usage_4.6.0_all.deb
https://cloudstack.o.auroraobjects.eu/trusty/cloudstack-agent_4.6.0_all.deb
https://cloudstack.o.auroraobjects.eu/trusty/cloudstack-cli_4.6.0_all.deb
https://cloudstack.o.auroraobjects.eu/trusty/cloudstack-common_4.6.0_all.deb
https://cloudstack.o.auroraobjects.eu/trusty/cloudstack-docs_4.6.0_all.deb
https://cloudstack.o.auroraobjects.eu/trusty/cloudstack-management_4.6.0_all.deb
https://cloudstack.o.auroraobjects.eu/trusty/cloudstack-usage_4.6.0_all.deb

-- 

Met vriendelijke groet / Kind regards,

Boris Schrijver

PCextreme B.V.

http://www.pcextreme.nl/contact
Tel direct: +31 6 33784542

Re: New PMC member: Erik Weber

[Boris Schrijver]

Congrats Erik!

-- 

Met vriendelijke groet / Kind regards,

Boris Schrijver

PCextreme B.V.

http://www.pcextreme.nl/contact
Tel direct: +31 6 33784542

> On November 3, 2015 at 9:05 AM Erik Weber <terbol...@gmail.com> wrote:
> 
> 
> Thanks again all :-)
> 
> Erik
> 
> On Sat, Oct 31, 2015 at 7:06 PM, Jan-Arve Nygård <jan.arve.nyg...@gmail.com>
> wrote:
> 
> > Congratulations Erik, well deserved :)
> >
> > Den fredag 30. oktober 2015 skrev Milamber <milam...@apache.org> følgende:
> >
> > >
> > > Congrats Erik! Good works!
> > >
> > > On 30/10/2015 14:01, Giles Sirett wrote:
> > >
> > >> All
> > >> The PMC is delighted to announce that we have asked Erik weber to join
> > >> the PMC and he has accepted
> > >>
> > >> Please join me in congratulating Erik
> > >>
> > >> Kind Regards
> > >> Giles
> > >>
> > >> D: +44 20 3603 0541<tel:+44%2020%203603%200541> | M: +44 796 111
> > >> 2055<tel:+44%20796%20111%202055>
> > >> giles.sir...@shapeblue.com<mailto:giles.sir...@shapeblue.com>
> > >> Find out more about ShapeBlue and our range of CloudStack related
> > services
> > >>
> > >> IaaS Cloud Design & Build<
> > >> http://shapeblue.com/iaas-cloud-design-and-build//>
> > >> CSForge – rapid IaaS deployment framework<http://shapeblue.com/csforge/
> > >
> > >> CloudStack Consulting<http://shapeblue.com/cloudstack-consultancy/>
> > >> CloudStack Software Engineering<
> > >> http://shapeblue.com/cloudstack-software-engineering/>
> > >> CloudStack Infrastructure Support<
> > >> http://shapeblue.com/cloudstack-infrastructure-support/>
> > >> CloudStack Bootcamp Training Courses<
> > >> http://shapeblue.com/cloudstack-training/>
> > >>
> > >> This email and any attachments to it may be confidential and are
> > intended
> > >> solely for the use of the individual to whom it is addressed. Any views
> > or
> > >> opinions expressed are solely those of the author and do not necessarily
> > >> represent those of Shape Blue Ltd or related companies. If you are not
> > the
> > >> intended recipient of this email, you must neither take any action based
> > >> upon its contents, nor copy or show it to anyone. Please contact the
> > sender
> > >> if you believe you have received this email in error. Shape Blue Ltd is
> > a
> > >> company incorporated in England & Wales. ShapeBlue Services India LLP
> > is a
> > >> company incorporated in India and is operated under license from Shape
> > Blue
> > >> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in
> > Brasil
> > >> and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd
> > is
> > >> a company registered by The Republic of South Africa and is traded under
> > >> license from Shape Blue Ltd. ShapeBlue is a registered trademark.
> > >>
> > >
> > >
> > >
> >

Re: [4.6] Can't create template or volume from snapshot

[Boris Schrijver]

As long as it's functional logging, GOOD IDEA!

> On October 23, 2015 at 4:03 PM Funs Kessen  wrote:
> 
> 
> Perhaps it would be nice to put the logging in all the GURUs so you can
> actually see which
> ones are used, and how it is used ?
> 
> Cheers,
> 
> Funs
> 
> > On 23 Oct 2015, at 11:21, Wei ZHOU  wrote:
> > 
> > As I said in previous mail, the request should be sent to
> > KVMHypervisorGuru, not others.
> > Mike, can you try my PR:  https://github.com/apache/cloudstack/pull/954
> > 
> > 2015-10-23 8:49 GMT+02:00 Rajani Karuturi :
> > 
> >> Interesting. Incase of KVM, its the reverse. The command which is supposed
> >> to goto SSVM ended up on KVM host.
> >> 
> >> ~Rajani
> >> 
> >> 
> >> 
> >> On 23-Oct-2015, at 10:49 am, Mike Tutkowski 
> >> wrote:
> >> 
> >>> Hi Rajani,
> >>> 
> >>> I seem to get the same error.
> >>> 
> >>> "Are you sure you got the right type of server?" is listed again in the
> >>> output.
> >>> 
> >>> It seems VMwareGuru is invoked and it passes the CopyCommand on to the
> >>> SSVM, which claims it doesn't support the command.
> >>> 
> >>> Thanks,
> >>> Mike
> >>> 
> >>> On Thu, Oct 22, 2015 at 10:56 PM, Rajani Karuturi <
> >>> rajani.karut...@citrix.com> wrote:
> >>> 
>  Yes. This is the pr.  We have some design issues to fix to make sure
>  hypervisor gurus doesn't cross boundaries. But, until then, we have to
> >> fix
>  the respective hv gurus. You can find more details on the bug which nux
>  shared.
>  
>  You could also test with hypervisor gurus exclude global Param and
> >> exclude
>  ovm3guru to be sure that this is the issue. (exact configuration and its
>  value is on bug comments)
>  
>  ~Rajani
>  Sent from my Windows Phone
>  
>  From: Mike Tutkowski
>  Sent: ‎23-‎10-‎15 09:56
>  To: dev@cloudstack.apache.org
>  Subject: Re: [4.6] Can't create template or volume from snapshot
>  
>  Hi Rajani,
>  
>  Just checking to make sure this is the PR you intended. It looks
> >> related to
>  OVM3 only.
>  
>  Thanks!
>  Mike
>  
>  On Thu, Oct 22, 2015 at 9:39 PM, Rajani Karuturi <
>  rajani.karut...@citrix.com
> > wrote:
>  
> > Mike,
> > Can you please test on PR
> >> https://github.com/apache/cloudstack/pull/962?
> > It fixes this issue.
> > 
> > ~Rajani
> > 
> > 
> > 
> > On 23-Oct-2015, at 7:29 am, Mike Tutkowski <
> >> mike.tutkow...@solidfire.com
> > 
> > wrote:
> > 
> >> I guess I should point out that my system VMs are all running on
> > XenServer,
> >> but I don't think that should be a problem.
> >> 
> >> On Thu, Oct 22, 2015 at 7:57 PM, Mike Tutkowski <
> >> mike.tutkow...@solidfire.com> wrote:
> >> 
> >>> I seem to be having a similar problem with deploying a VM on VMware
>  (on
> >>> 4.6). I first tried with my (SolidFire) plug-in and then with just
>  local
> >>> storage. In both cases, I get an error saying "Are you sure you got
>  the
> >>> right type of server?"
> >>> 
> >>> On Sun, Oct 18, 2015 at 2:29 AM, Nux!  wrote:
> >>> 
>  All I get is a "Are you sure you got the right type of server?"
>  
>  More info at https://issues.apache.org/jira/browse/CLOUDSTACK-8964
>  
>  Lucian
>  
>  --
>  Sent from the Delta quadrant using Borg technology!
>  
>  Nux!
>  www.nux.ro
>  
> >>> 
> >>> 
> >>> 
> >>> --
> >>> *Mike Tutkowski*
> >>> *Senior CloudStack Developer, SolidFire Inc.*
> >>> e: mike.tutkow...@solidfire.com
> >>> o: 303.746.7302
> >>> Advancing the way the world uses the cloud
> >>> *™*
> >>> 
> >> 
> >> 
> >> 
> >> --
> >> *Mike Tutkowski*
> >> *Senior CloudStack Developer, SolidFire Inc.*
> >> e: mike.tutkow...@solidfire.com
> >> o: 303.746.7302
> >> Advancing the way the world uses the cloud
> >> *™*
> > 
> > 
>  
>  
>  --
>  *Mike Tutkowski*
>  *Senior CloudStack Developer, SolidFire Inc.*
>  e: mike.tutkow...@solidfire.com
>  o: 303.746.7302
>  Advancing the way the world uses the cloud
>  *™*
>  
> >>> 
> >>> 
> >>> 
> >>> --
> >>> *Mike Tutkowski*
> >>> *Senior CloudStack Developer, SolidFire Inc.*
> >>> e: mike.tutkow...@solidfire.com
> >>> o: 303.746.7302
> >>> Advancing the way the world uses the cloud
> >>> *™*
> >> 
> >> 
>

Re: Time to create 4.6 branch ?

[Boris Schrijver]

Dear Wei.

In the new release process we are releasing directly from master. So no 4.6
branch will be created.

As we are releasing directly from master, it is now frozen till release.

-- 

Met vriendelijke groet / Kind regards,

Boris Schrijver

PCextreme B.V.

http://www.pcextreme.nl/contact
Tel direct: +31 6 33784542

> 
> On October 13, 2015 at 9:26 PM Wei ZHOU <ustcweiz...@gmail.com> wrote:
> 
> 
> Guys,
> 
> As I know, 4.6 will be close to RC. I am wondering if it is time to create
> 4.6 branch, so that we can add the upgrade path to next version and new
> features/improvements can be merged into master branch (to keep a clean
> 4.6
> branch).
> 
> By the way, which is the new version? 4.7 or 5.0 ?
> 
> 
> -Wei
> 

Re: Build failed in Jenkins: build-master-jdk18 #363

[Boris Schrijver]

It fails due to the checkVolumeFileForActivityTest randomly failing on JDK1.8

org.apache.cloudstack.utils.hypervisor.HypervisorUtilsTest.checkVolumeFileForActivityTest(HypervisorUtilsTest.java:70

-- 

Met vriendelijke groet / Kind regards,

Boris Schrijver

PCextreme B.V.

http://www.pcextreme.nl/contact
Tel direct: +31 6 33784542

> 
> On October 9, 2015 at 3:02 PM jenk...@cloudstack.org wrote:
> 
> 
> See <http://jenkins.buildacloud.org/job/build-master-jdk18/363/changes>
> 
> Changes:
> 
> [wido] CLOUDSTACK-8879: Depend in rados-java 0.2.0
> 
> --
> [...truncated 398 lines...]
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.029 sec
> - in com.cloud.utils.UuidUtilsTest
> Running com.cloud.utils.crypto.RSAHelperTest
> 2015-10-09 13:08:13,522 INFO [utils.crypt.RSAHelper] (main:)
> [ignored]error during public key encryption: Unsupported format
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.164 sec
> - in com.cloud.utils.crypto.RSAHelperTest
> Running com.cloud.utils.crypto.EncryptionSecretKeyCheckerTest
> 2015-10-09 13:08:13,896 DEBUG [utils.crypt.EncryptionSecretKeyChecker]
> (main:) Encryption Type: null
> 2015-10-09 13:08:13,897 DEBUG [utils.crypt.EncryptionSecretKeyChecker]
> (main:) Encryption Type: file
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.089 sec
> - in com.cloud.utils.crypto.EncryptionSecretKeyCheckerTest
> Running com.cloud.utils.PropertiesUtilsTest
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.029 sec
> - in com.cloud.utils.PropertiesUtilsTest
> Running com.cloud.utils.exception.ExceptionUtilTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec
> - in com.cloud.utils.exception.ExceptionUtilTest
> Running com.cloud.utils.storage.QCOW2UtilsTest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec
> - in com.cloud.utils.storage.QCOW2UtilsTest
> Running com.cloud.utils.encoding.UrlEncoderTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec
> - in com.cloud.utils.encoding.UrlEncoderTest
> Running com.cloud.utils.UriUtilsTest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.06 sec -
> in com.cloud.utils.UriUtilsTest
> Running com.cloud.utils.HttpUtilsTest
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.054 sec
> - in com.cloud.utils.HttpUtilsTest
> Running com.cloud.utils.backoff.impl.ConstantTimeBackoffTest
> 2015-10-09 13:08:14,183 INFO [backoff.impl.ConstantTimeBackoff]
> (Thread-1:) Thread Thread-1 interrupted while waiting for retry
> 2015-10-09 13:08:14,286 DEBUG [backoff.impl.ConstantTimeBackoffTest]
> (main:) thread started
> 2015-10-09 13:08:14,286 DEBUG [backoff.impl.ConstantTimeBackoffTest]
> (Thread-2:) before
> 2015-10-09 13:08:14,389 DEBUG [backoff.impl.ConstantTimeBackoffTest]
> (main:) testing wakeup
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.317 sec
> - in com.cloud.utils.backoff.impl.ConstantTimeBackoffTest
> Running com.cloud.utils.ProcessUtilTest
> 2015-10-09 13:08:14,390 INFO [backoff.impl.ConstantTimeBackoff]
> (Thread-2:) Thread Thread-2 interrupted while waiting for retry
> 2015-10-09 13:08:14,390 DEBUG [backoff.impl.ConstantTimeBackoffTest]
> (Thread-2:) after
> 2015-10-09 13:08:14,396 DEBUG [cloud.utils.ProcessUtil] (main:)
> environment.properties could not be opened
> 2015-10-09 13:08:14,401 DEBUG [cloud.utils.ProcessUtil] (main:)
> environment.properties could not be opened
> 2015-10-09 13:08:14,401 DEBUG [cloud.utils.ProcessUtil] (main:) Executing:
> bash -c ps -p 123456
> 2015-10-09 13:08:14,472 DEBUG [cloud.utils.ProcessUtil] (main:) Exit value
> is 1
> 2015-10-09 13:08:14,473 DEBUG [cloud.utils.ProcessUtil] (main:) PID TTY
> TIME CMD
> 2015-10-09 13:08:14,474 DEBUG [cloud.utils.ProcessUtil] (main:) Executing:
> bash -c echo $PPID
> 2015-10-09 13:08:14,480 DEBUG [cloud.utils.ProcessUtil] (main:) Execution
> is successful.
> 2015-10-09 13:08:14,509 DEBUG [cloud.utils.ProcessUtil] (main:)
> environment.properties could not be opened
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.117 sec
> - in com.cloud.utils.ProcessUtilTest
> Running com.cloud.utils.PasswordGeneratorTest
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec
> - in com.cloud.utils.PasswordGeneratorTest
> Running com.cloud.utils.rest.HttpUriRequestBuilderTest
> Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.054 sec
&

Re: [VOTE] jenkins jobs removal

[Boris Schrijver]

Hi,

+1 on all.

-- 

Met vriendelijke groet / Kind regards,

Boris Schrijver

PCextreme B.V.

http://www.pcextreme.nl/contact
Tel direct: +31 6 33784542

> 
> On October 2, 2015 at 8:47 AM Remi Bergsma <rberg...@schubergphilis.com>
> wrote:
> 
> 
> +1 on 4.3 jobs, although I'd like to hear from Rohit to confirm
> 
> +0 on the rest as I cannot judge it.
> 
> Regards, Remi
> 
> Sent from my iPhone
> 
> > On 02 Oct 2015, at 02:44, Pierre-Luc Dion <pdion...@apache.org> wrote:
> >
> > Following Jenkins jobs on j.bac.o will be deleted doing the following
> > tasks:
> > 1. backup of the jobs configuration will be taken:
> > tar -zcvf j.bac.o_jobs-archive_20151005.tgz ~jenkins/jobs
> > 2. job will be deleted from jenkins
> > 3. workspaces will be deleted from jenkins master server to free up disk
> > space.
> >
> >
> > VIEW | NAME |
> > STATE | LAST_SUCCESS
> > 
> -|---|--|--
> > 4.3 | cloudstack-4.3-maven-build | blue
> > | 2015-08-14 01:59:15
> > 4.3 | cloudstack-4.3-maven-build-noredist |
> > aborted | 2015-03-11 08:11:01
> > 4.3 | cloudstack-4.3-package-deb | blue
> > | 2015-08-14 02:04:39
> > 4.3 | cloudstack-4.3-package-rpm | blue
> > | 2015-03-11 08:11:01
> > 4.3 | cloudstack-4.3-package-rpm-noredist | blue
> > | 2014-09-02 10:29:12
> > 4.3 | cloudstack-4.3-systemvm | blue
> > | 2015-01-28 15:33:09
> > 4.3 | cloudstack-4.3-systemvm64 | blue
> > | 2015-01-28 13:25:12
> > 4.3 | HyperVAgent4.3 | blue
> > | 2014-12-04 11:27:14
> > disabled | build-docs-admin-master |
> > disabled | 2014-03-25 13:20:25
> > disabled | build-docs-devguide-master |
> > disabled | 2014-03-25 13:26:51
> > disabled | build-docs-install-master |
> > disabled | 2014-03-25 13:26:51
> > disabled | build-docs-midonet-master |
> > disabled | 2014-02-06 06:44:22
> > disabled | build-docs-niciranvp-master |
> > disabled | 2014-02-06 06:42:37
> > disabled | build-docs-release-notes-master |
> > disabled | 2014-02-06 06:48:51
> > disabled | build-docs-vxlan-master |
> > disabled | 2014-02-06 06:26:57
> > disabled | build-test-centos-builtin |
> > disabled | n/a
> > disabled | built-test-archive |
> > disabled | 2014-06-06 01:38:51
> > disabled | cloudstack-4.4-auto-marvin |
> > disabled | 2015-06-15 13:28:22
> > disabled | docs-4.3-gsoc-guide |
> > disabled | 2015-03-08 18:20:07
> > disabled | Master - Python Static Code Analysis |
> > disabled | n/a
> > disabled | mgmt-build-reviewboard-requests |
> > disabled | n/a
> > disabled | run-checkin-tests |
> > disabled | n/a
> > disabled | simulator-build |
> > disabled | 2014-07-31 09:47:03
> > disabled | simulator-deploydb |
> > disabled | 2014-02-12 19:50:50
> > disabled | simulator-gate |
> > disabled | 2014-01-23 04:18:31
> > disabled | simulator-singlerun |
> > disabled | 2015-05-01 10:30:28
> > disabled | start-jetty |
> > disabled | 2014-02-12 19:23:03
> > disabled | stop-jetty |
> > disabled | 2013-11-20 08:14:46
> > disabled | test-matrix-4.4 |
> > disabled | n/a
> > disabled | test-matrix-extended-4.4 |
> > disabled | n/a
> > disabled | test-matrix-extended-master |
> > disabled | 2014-02-21 04:35:36
> > disabled | test-matrix-master |
> > disabled | n/a
> > disabled | test-smoke-matrix-master |
> > disabled | 2014-12-21 10:39:18
> > disabled | test-yumrepo-refresh-4.4 |
> > disabled | 2014-10-21 09:43:33
> > disabled | test-yumrepo-refresh-master |
> > disabled | 2014-11-21 05:32:00
> > management | mgmt-build-reviewboard-requests |
> > disabled | n/a
> > master | build-systemvm64-master-with-debian8 | red
> > | n/a
> > master | cloudstack-rpm-packages-with-branch-parameter |
> > notbuilt | n/a
> > master | pull-requests |
> > notbuilt | n/a
> > parameterized | cloudstack-rpm-packages-with-branch-parameter |
> > notbuilt | n/a
> > parameterized | parameterized-slowbuild |
> > notbuilt | n/a
> > parameterized | parameterized-sytemvm |
> > notbuilt | n/a
> > simulator | fastsimulatorbuild | red
> > | n/a
> > simulator | simulator-4.4-integration-tests |
> > yellow | 2014-12-16 06:13:20
> > simulator | simulator-4.5-singlerun | red
> > | 2015-05-01 11:29:29
> >
> >
> > Voting ends 3 days from today, i.e. midnight UTC on 2015-10-05
> > http://www.timeanddate.com/countdown/to?year=2015=10=05
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -0 don't delete the following job(s) ...
> > [ ] -1 disapprove (and reason why)
> >
> >
> > Regards,
> >
> > Pierre-Luc
> 

RE: new colleagues

[Boris Schrijver]

Congrats Daan!

Best regards,

Boris Schrijver

TEL: +31633784542
MAIL: bo...@pcextreme.nl

> 
> On October 1, 2015 at 12:47 PM Giles Sirett <giles.sir...@shapeblue.com>
> wrote:
> 
> 
> Great to hear that you're staying in the family Daan
> 
> And good news that I get a running partner in Dublin (as Sebastien usually
> doesn't get out of bed for our runs !)
> 
> 
> 
> Regards
> 
> Giles
> 
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: 01 October 2015 11:07
> To: dev <dev@cloudstack.apache.org>
> Subject: new colleagues
> 
> Hello fellow stackers,
> 
> This to let you know that I just entered the building of Leaseweb, in
> order to be working there for the next couple of years. You know them via Whei
> Zou, who will be my close colleague. I had a great time with Schuberg Philis
> as you might know and am confident the same will happen here. I will continue
> to use personal email addresses so I want to let you this way that my
> motivation has changed ever so slightly.
> 
> I didn't plan to go to Dublin yet, but as Makesh my new colleague
> threatened to mention me in his session [1], I will try to be there for damage
> control.
> 
> [1] http://sched.co/44T2
> 
> hoping to contribute a lot more,
> --
> Daan
> Find out more about ShapeBlue and our range of CloudStack related services
> 
> IaaS Cloud Design &
> Build<http://shapeblue.com/iaas-cloud-design-and-build//>
> CSForge – rapid IaaS deployment framework<http://shapeblue.com/csforge/>
> CloudStack Consulting<http://shapeblue.com/cloudstack-consultancy/>
> CloudStack Software
> Engineering<http://shapeblue.com/cloudstack-software-engineering/>
> CloudStack Infrastructure
> Support<http://shapeblue.com/cloudstack-infrastructure-support/>
> CloudStack Bootcamp Training
> Courses<http://shapeblue.com/cloudstack-training/>
> 
> This email and any attachments to it may be confidential and are intended
> solely for the use of the individual to whom it is addressed. Any views or
> opinions expressed are solely those of the author and do not necessarily
> represent those of Shape Blue Ltd or related companies. If you are not the
> intended recipient of this email, you must neither take any action based upon
> its contents, nor copy or show it to anyone. Please contact the sender if you
> believe you have received this email in error. Shape Blue Ltd is a company
> incorporated in England & Wales. ShapeBlue Services India LLP is a company
> incorporated in India and is operated under license from Shape Blue Ltd. Shape
> Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is
> operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company
> registered by The Republic of South Africa and is traded under license from
> Shape Blue Ltd. ShapeBlue is a registered trademark.
>

Citrix References in Marvin

[Boris Schrijver]

Dear Rajani,

During some tests I stumbled upon something. While running smoke tests for KVM
basic zones the following occured:

=== TestName: test_deploy_vm_from_iso | Status : EXCEPTION ===

This is not due to the component not working, it was because the ISO wasn't
available! I then went to the Marvin test data and it tried to download it from
10.147.40.145 [1] which I guess is an (old) internal Citrix storage location. I
then looked a bit further an saw a lot of other references to internal Citrix
locations. [2] Even a few with your name in it! [3]

Would you please be so kind to make these publicly available, or point them to
already publicly available material, so one could run these tests out of the
box.

[1]
https://github.com/apache/cloudstack/blob/master/tools/marvin/marvin/config/test_data.py#L1658
<https://github.com/apache/cloudstack/blob/master/tools/marvin/marvin/config/test_data.py#L1658>
 
[2]
https://github.com/apache/cloudstack/blob/master/tools/marvin/marvin/config/test_data.py#L1673

[3]
https://github.com/apache/cloudstack/blob/master/tools/marvin/marvin/config/test_data.py#L1544


Best regards,

Boris Schrijver

TEL: +31633784542
MAIL: bo...@pcextreme.nl

Failing test checkVolumeFileForActivity()

[Boris Schrijver]

Dear Rohit,

The unit test you've written a couple of weeks ago seems to fail randomly. I've
experienced it a few times locally. I also have seen some builds fail on Jenkins
and Travis due to it. So either it's the test or the method it's testing that's
failing.

Would you please have a look?

org.apache.cloudstack.utils.hypervisor.HypervisorUtilsTestcheckVolumeFileForActivityTest()

Examples:

https://travis-ci.org/apache/cloudstack/jobs/83159879

http://jenkins.buildacloud.org/job/build-master-jdk18/358/testReport/junit/org.apache.cloudstack.utils.hypervisor/HypervisorUtilsTest/checkVolumeFileForActivityTest/

-- 

Met vriendelijke groet / Kind regards,

Boris Schrijver

PCextreme B.V.

http://www.pcextreme.nl/contact
Tel direct: +31 6 33784542

Re: [4.6] Master fails to add secondary storage network, deployment fails [Unknown parameters : zoneid]

[Boris Schrijver]

Hi Nux,

The only thing I can say right now; that Jenkins job didn't run for the past
week. So maybe it has already been fixed, maybe not. Could you try package it
yourself and deploy again? That way you know the problem still persists. And if
it does, please file a Jira ticket!

Best regards,

Boris Schrijver

TEL: +31633784542
MAIL: bo...@pcextreme.nl

> 
> On September 28, 2015 at 11:51 PM Nux! <n...@li.nux.ro> wrote:
> 
> 
> Any ideas?
> 
> --
> Sent from the Delta quadrant using Borg technology!
> 
> Nux!
> www.nux.ro
> 
> - Original Message -
> > From: "Nux!" <n...@li.nux.ro>
> > To: "dev" <dev@cloudstack.apache.org>
> > Sent: Monday, 28 September, 2015 19:39:43
> > Subject: [4.6] Master fails to add secondary storage network, deployment
> > fails
> 
> > Hello,
> >
> > Am testing 4.6 master with CentOS 6 HVs.
> > After installing 4.6 from yum repo at
> > http://jenkins.buildacloud.org/view/4.6/job/package-centos6-4.6/ and
> > running
> > the initial setup, it fails at the end because "unknwon parameters
> > zoneid" ...
> > :
> >
> > 2015-09-28 19:34:15,072 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> > (API-Job-Executor-25:ctx-e08dd156 job-27) Executing AsyncJobVO {id:27,
> > userId:
> > 2, accountId: 2, instanceType: None, instanceId: null, cmd:
> > 
> org.apache.cloudstack.api.command.admin.network.CreateStorageNetworkIpRangeCmd,
> > cmdInfo: {"response":"json","ctxDetails":"{\"interface
> > 
> com.cloud.dc.Pod\":\"b1c7836b-3bae-4d83-b113-b8308cea57ab\"}","cmdEventType":"STORAGE.IP.RANGE.CREATE","ctxUserId":"2","gateway":"192.168.200.67","podid":"b1c7836b-3bae-4d83-b113-b8308cea57ab","zoneid":"d08602b2-2ec6-4fd0-9dbb-5eca2d9b7c63","startip":"192.168.200.200","vlan":"123","httpmethod":"GET","_":"1443465255029","ctxAccountId":"2","ctxStartEventId":"68","netmask":"255.255.255.0","endip":"192.168.200.222"},
> > cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0,
> > result:
> > null, initMsid: 266785867798693, completeMsid: null, lastUpdated: null,
> > lastPolled: null, created: null}
> > 2015-09-28 19:34:15,073 DEBUG [c.c.a.ApiServlet]
> > (catalina-exec-24:ctx-def815dc
> > ctx-c4ca8865) ===END=== 85.13.192.198 -- GET
> > 
> command=createStorageNetworkIpRange=json=192.168.200.67=255.255.255.0=123=192.168.200.200=192.168.200.222=d08602b2-2ec6-4fd0-9dbb-5eca2d9b7c63=b1c7836b-3bae-4d83-b113-b8308cea57ab&_=1443465255029
> > 2015-09-28 19:34:15,075 WARN [c.c.a.d.ParamGenericValidationWorker]
> > (API-Job-Executor-25:ctx-e08dd156 job-27 ctx-4198e321) Received unknown
> > parameters for command createStorageNetworkIpRange. Unknown parameters :
> > zoneid
> > 2015-09-28 19:34:15,122 WARN
> > [o.a.c.a.c.a.n.CreateStorageNetworkIpRangeCmd]
> > (API-Job-Executor-25:ctx-e08dd156 job-27 ctx-4198e321) Create storage
> > network
> > IP range failed
> > com.cloud.utils.exception.CloudRuntimeException: Unable to commit or
> > close the
> > connection.
> > at
> > com.cloud.utils.db.TransactionLegacy.commit(TransactionLegacy.java:730)
> > at com.cloud.utils.db.Transaction.execute(Transaction.java:46)
> > at
> > 
> com.cloud.network.StorageNetworkManagerImpl.createIpRange(StorageNetworkManagerImpl.java:229)
> > at
> > 
> org.apache.cloudstack.api.command.admin.network.CreateStorageNetworkIpRangeCmd.execute(CreateStorageNetworkIpRangeCmd.java:118)
> > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:150)
> > at
> > 
> com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
> > at
> > 
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:537)
> > at
> > 
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> > at
> > 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> > at
> > 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(Defaul

Re: [j.bac.o] Jenkins jobs cleanup

[Boris Schrijver]

Hi Pierre-Luc,

I've no objections.

Besides the jobs for 4.3 and 4.4 I think there is need for some more cleanup on
jenkins.buildacloud.org. We will need to index all current build jobs and reason
or vote if the job is still wanted or necessary. I'm seeing a lot of jobs
failing or not even running for the past months. 

Best regards,

Boris Schrijver

TEL: +31633784542
MAIL: bo...@pcextreme.nl

> 
> On September 27, 2015 at 4:38 PM Pierre-Luc Dion <pd...@cloudops.com>
> wrote:
> 
> 
> Hi,
> 
> We recently ran out of space on jenkins master of j.bac.o [1]. Does anyone
> would object if we removed all jobs for 4.3 builds ? I did some build jobs
> for 4.6, I'll remove them as it look like we are using master for 4.6
> builds for now.
> 
> Any other suggestions?
> 
> Thanks,
> 
> [1] http://markmail.org/message/zxb3khnxrrkazmpq
> 

Re: Zone in RegisterTemplateCmd API

[Boris Schrijver]

Hi Patrick,

We're using S3 and are facing the same issues.

This would indeed be a very good idea. Though I think it will also remove a kind
of safety check by making it optional.

The solution would be to make zoneId optional and add a optional boolean
variable crossZones.

If zoneId is empty and crossZones is not set, or not set to true, then fail.
If zoneId is empty and crossZones is set to true then succeed and add -1 in the
background (for now, maybe add a boolean crossZones to the template as well.)
If zoneId is set and crossZones is not set, or not set to true, then succeed.
If zoneId is set and crossZones is set to true, then fail

Even add a check if zoneId is set to -1 and crossZones is set to true, then
still succeed. And the other way around.

This way it doesn't alter the default behavior.

Any opinions?  

Best regards,

Boris Schrijver

TEL: +31633784542
MAIL: bo...@pcextreme.nl

> 
> On September 25, 2015 at 9:32 PM Patrick Dube <patrickdub...@gmail.com>
> wrote:
> 
> 
> Hey guys/gals,
> 
> I am using Swift as secondary storage, which is cross zones. To register
> templates, there is a mandatory zoneid field. I have found that if i put
> zoneid=-1, it will work (mark the templates as cross zones), but it is
> very
> unintuitive. This also causes problems using a tool like Terraform, which
> expects the zoneid in the response (since it is a required field). What do
> you think about rendering the zone field optional (defaulting to -1 on the
> server)? This would simplify the API and make region wide templates more
> intuitive.
> 
> Thank you,
> 
> Patrick
> 

Re: Proposal to get to 100% passrate on BVTs

[Boris Schrijver]

Hi,

Good idea!

I'll pickup CLOUDSTACK-8883!

Best regards,

Boris Schrijver

TEL: +31633784542
MAIL: bo...@pcextreme.nl

> 
> On September 18, 2015 at 1:59 PM Daan Hoogland <daan.hoogl...@gmail.com>
> wrote:
> 
> 
> Raja, great initiative. I don't think we should wait with the back out
> part
> unitll we are at 100%. We can start backing out any commit that reduces
> the
> pass rate in any way right now.
> 
> €0,02
> 
> On Fri, Sep 18, 2015 at 1:55 PM, Raja Pullela <raja.pull...@citrix.com>
> wrote:
> 
> > Hi,
> >
> > We have been having steady rate of blocker issues/breakages. I am
> > proposing to see if we can get to a 100% passrate on BVTs by next
> > Friday,
> > Sep 25th or sooner.
> >
> > Once we reach 100% passrate, we should closely monitor BVTs and back out
> > commits that we think have broken BVTs.
> > I will report the BVTs passrate on a daily basis. Also, working with
> > Kishan to see a way to make the data available online?
> >
> > Here is the latest status on the BVTs -
> > XS Basic - 93% / CLOUDSTACK-8843<
> > https://issues.apache.org/jira/browse/CLOUDSTACK-8843> (in the process
> > of
> > testing Jayapal's fix),
> > XS Adv - 81.8% / CLOUDSTACK-8881<
> > https://issues.apache.org/jira/browse/CLOUDSTACK-8881>, CLOUDSTACK-8697<
> > https://issues.apache.org/jira/browse/CLOUDSTACK-8697>
> >
> > KVM Basic - Deployment failure / CLOUDSTACK-8883<
> > https://issues.apache.org/jira/browse/CLOUDSTACK-8883>
> >
> > KVM Adv - Deployment failure / CLOUDSTACK-8883<
> > https://issues.apache.org/jira/browse/CLOUDSTACK-8883>, CLOUDSTACK-8881<
> > https://issues.apache.org/jira/browse/CLOUDSTACK-8881>, CLOUDSTACK-8697
> >
> > BTW - currently, no one has picked up CLOUDSTACK-8883<
> > https://issues.apache.org/jira/browse/CLOUDSTACK-8883> yet,
> >
> > best,
> > Raja
> >
> >
> 
> 
> --
> Daan
>

Re: Build failed in Jenkins: build-master-slowbuild #2302

[Boris Schrijver]

Dear Rajani,

Will check now.

Best regards,

Boris Schrijver

TEL: +31633784542
MAIL: bo...@pcextreme.nl

> 
> On September 14, 2015 at 7:32 AM Rajani Karuturi <raj...@apache.org>
> wrote:
> 
> 
> slow build is broken due to a new findbugs warning
> I think its not really new but, its reported maybe because of some
> reformatting.
> It maybe due to changes from commit
> 1c6378ec0056e8c75990a4a0c15e99b2df162a75 and PR 795
> @borisroman @widodh can you take a look at the slow build please?
> 
> ~Rajani
> 
> On Mon, Sep 14, 2015 at 10:45 AM, <jenk...@cloudstack.org> wrote:
> 
> > See <http://jenkins.buildacloud.org/job/build-master-slowbuild/2302/>
> >
> > --
> > [...truncated 27639 lines...]
> > [INFO] --- maven-compiler-plugin:3.2:compile (default-compile) @
> > cloud-quickcloud ---
> > [INFO] No sources to compile
> > [INFO]
> > [INFO] >>> findbugs-maven-plugin:3.0.1:check (cloudstack-findbugs) @
> > cloud-quickcloud >>>
> > [INFO]
> > [INFO] --- findbugs-maven-plugin:3.0.1:findbugs (findbugs) @
> > cloud-quickcloud ---
> > [INFO]
> > [INFO] <<< findbugs-maven-plugin:3.0.1:check (cloudstack-findbugs) @
> > cloud-quickcloud <<<
> > [INFO]
> > [INFO] --- findbugs-maven-plugin:3.0.1:check (cloudstack-findbugs) @
> > cloud-quickcloud ---
> > [INFO]
> > [INFO] --- cobertura-maven-plugin:2.6:instrument (default-cli) @
> > cloud-quickcloud ---
> > [WARNING] No files to instrument.
> > [INFO] NOT adding cobertura ser file to attached artifacts list.
> > [INFO]
> > [INFO] --- maven-resources-plugin:2.5:testResources
> > (default-testResources) @ cloud-quickcloud ---
> > [debug] execute contextualize
> > [INFO] Using 'UTF-8' encoding to copy filtered resources.
> > [INFO] skip non existing resourceDirectory <
> > 
> http://jenkins.buildacloud.org/job/build-master-slowbuild/ws/quickcloud/src/test/resources
> > >
> > [INFO] Copying 3 resources
> > [INFO] Copying 3 resources
> > [INFO]
> > [INFO] --- maven-compiler-plugin:3.2:testCompile (default-testCompile) @
> > cloud-quickcloud ---
> > [INFO] No sources to compile
> > [INFO]
> > [INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @
> > cloud-quickcloud ---
> > [INFO]
> > [INFO] <<< cobertura-maven-plugin:2.6:cobertura (default-cli) @
> > cloud-quickcloud <<<
> > [INFO]
> > [INFO] --- cobertura-maven-plugin:2.6:cobertura (default-cli) @
> > cloud-quickcloud ---
> > [INFO]
> > 
> > [INFO] Reactor Summary:
> > [INFO]
> > [INFO] Apache CloudStack Developer Tools - Checkstyle Configuration
> > SUCCESS [1.796s]
> > [INFO] Apache CloudStack . SUCCESS
> > [3.473s]
> > [INFO] Apache CloudStack Maven Conventions Parent  SUCCESS
> > [1.274s]
> > [INFO] Apache CloudStack Framework - Managed Context . SUCCESS
> > [22.052s]
> > [INFO] Apache CloudStack Utils ... SUCCESS
> > [1:30.918s]
> > [INFO] Apache CloudStack Framework ... SUCCESS
> > [0.105s]
> > [INFO] Apache CloudStack Framework - Event Notification .. SUCCESS
> > [54.435s]
> > [INFO] Apache CloudStack Framework - Configuration ... SUCCESS
> > [26.977s]
> > [INFO] Apache CloudStack API . SUCCESS
> > [1:50.696s]
> > [INFO] Apache CloudStack Framework - REST  SUCCESS
> > [17.338s]
> > [INFO] Apache CloudStack Framework - IPC . SUCCESS
> > [29.849s]
> > [INFO] Apache CloudStack Cloud Engine  SUCCESS
> > [0.098s]
> > [INFO] Apache CloudStack Cloud Engine API  SUCCESS
> > [27.425s]
> > [INFO] Apache CloudStack Framework - Security  SUCCESS
> > [25.286s]
> > [INFO] Apache CloudStack Core  SUCCESS
> > [1:16.123s]
> > [INFO] Apache CloudStack Agents .. SUCCESS
> > [34.427s]
> > [INFO] Apache CloudStack Framework - Clustering .. SUCCESS
> > [36.891s]
>

Re: Weird Eclipse Issues around com.cloud.utils

[Boris Schrijver]

Hi Mike,

I had the same problem a couple of days ago, it was due to a refactor of the
utils package:
https://github.com/apache/cloudstack/commit/83fd8f60f3c503cf6fda7833b0f45c23a215f559

Removing the utils project and importing it again would have solved the issue.
Removing all project wasn't necessary.

Best regards,

Boris Schrijver

TEL: +31633784542
MAIL: bo...@pcextreme.nl

> 
> On September 4, 2015 at 6:26 AM Mike Tutkowski
> <mike.tutkow...@solidfire.com> wrote:
> 
> 
> OK, ridiculous, but removing all of my projects (again), shutting down
> Eclipse (which I don't think I tried last time I had removed all of my
> projects), re-starting it, then re-importing all of the projects fixed the
> problem.
> 
> On Thu, Sep 3, 2015 at 9:56 PM, Mike Tutkowski
> <mike.tutkow...@solidfire.com
> > wrote:
> 
> > Also, weird warnings like commenting about lack of type safety here:
> >
> > List volumes = _volumeDao.findByPoolId(storagePoolId, null);
> >
> > findByPoolId here returns type List.
> >
> > On Thu, Sep 3, 2015 at 9:43 PM, Mike Tutkowski <
> > mike.tutkow...@solidfire.com> wrote:
> >
> >> Hi,
> >>
> >> After I recently rebased my master branch, I noticed some weird issues
> >> in
> >> Eclipse such as the following:
> >>
> >> http://i.imgur.com/UPFu33u.png
> >>
> >> In that image, it shows that Eclipse claims it can't find
> >> CloudRuntimeException's package (com.cloud.utils.exception).
> >>
> >> The weird part is that the project that contains this package is in my
> >> workspace (as usual).
> >>
> >> Another example is the Pair class that Eclipse says it can't find
> >> because
> >> it can't find a related package (com.cloud.utils).
> >>
> >> When I build from the command line, I don't encounter any errors.
> >>
> >> Does anyone know why Eclipse might be having this problem? I've
> >> completely re-imported all of the necessary projects and performed
> >> several
> >> refreshes within Eclipse, but the problems persist.
> >>
> >> Thanks!
> >>
> >> --
> >> *Mike Tutkowski*
> >> *Senior CloudStack Developer, SolidFire Inc.*
> >> e: mike.tutkow...@solidfire.com
> >> o: 303.746.7302
> >> Advancing the way the world uses the cloud
> >> <http://solidfire.com/solution/overview/?video=play>*™*
> >>
> >
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkow...@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the cloud
> > <http://solidfire.com/solution/overview/?video=play>*™*
> >
> 
> 
> 
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the cloud
> <http://solidfire.com/solution/overview/?video=play>*™*
>

Apache Confluence Access

[Boris Schrijver]

Hi all,

I wanted to update some parts of Confluence. Pages regarding network
infrastructure and database access.

My username is borisroman, email: bo...@pcextreme.nl.

Best regards,

Boris Schrijver

TEL: +31633784542
MAIL: bo...@pcextreme.nl

IPv6 in ACS and Basic Zones

[Boris Schrijver]

Hi all,

The first steps toward IPv6 support [0] had been taken by Sheng Yang in late
2012 / early 2013. [1][2] Since then it has been awfully quite around IPv6. Remi
Bergsma from Schuberg Philis created a design document for IPv6 in VPCs but had
not implemented it yet. [3] I'm going to give a try at implementing IPv6 for
basic zones and lay a good base for IPv6 in VPC's, although the latter will not
be my main concern right now. [4]

In my opinion the code written for IPv6 in the ACS project is a not of very much
help and misses a few concepts. (Besides the basic implementation) MySQL tables
where created for IPv6 in ACS version 4.1 and have thereafter never been
changed.

The question which I would like to ask to all developers:

Do any of you use IPv6 in ACS or know people/parties who use it? The code from
Sheng Yang his ipv6 branch, not a custom implementation.

If none use it I will rewrite it the IPv6 part entirely and start a firm and
clean base, this will include restructuring the IPv6 database tables, concepts
and layout.

Best regards,

Boris Schrijver

TEL: +31633784542
MAIL: bo...@pcextreme.nl mailto:bo...@pcextreme.nl

[0] https://issues.apache.org/jira/browse/CLOUDSTACK-452
[1] https://issues.apache.org/jira/browse/CLOUDSTACK-673
[2] https://github.com/apache/cloudstack/commits/ipv6
[3] https://cwiki.apache.org/confluence/display/CLOUDSTACK/IPv6+in+VPC+Router
[4] https://issues.apache.org/jira/browse/CLOUDSTACK-674

Re: Build failed in Jenkins: build-master-slowbuild #2082

[Boris Schrijver]

Hi all,

The error occurring is because the methods which are called had been renamed.
I've fixed this in a new PR: https://github.com/apache/cloudstack/pull/707/.

Fix:
https://github.com/borisroman/cloudstack/blob/0e518f004fdd9eaa0b39be1e3c4eb391ea07e7cc/plugins/network-elements/nuage-vsp/src/com/cloud/network/guru/NuageVspGuestNetworkGuru.java#L291

No idea why it slipped through. Travis-CI did build just fine.
https://travis-ci.org/apache/cloudstack/builds/75928535

Best regards,

Boris Schrijver

TEL: +31633784542
MAIL: bo...@pcextreme.nl

 
 On August 17, 2015 at 7:07 PM jenk...@cloudstack.org wrote:
 
 
 See
 http://jenkins.buildacloud.org/job/build-master-slowbuild/2082/changes
 
 Changes:
 
 [Boris Schrijver] Refactored NicProfile.java for readability.
 
 --
 [...truncated 25932 lines...]
 [INFO] Nothing to compile - all classes are up to date
 [INFO]
 [INFO]  findbugs-maven-plugin:3.0.1:check (cloudstack-findbugs) @
 cloud-plugin-network-srx 
 [INFO]
 [INFO] --- findbugs-maven-plugin:3.0.1:findbugs (findbugs) @
 cloud-plugin-network-srx ---
 [INFO] Fork Value is true
 [INFO] Done FindBugs Analysis
 [INFO]
 [INFO]  findbugs-maven-plugin:3.0.1:check (cloudstack-findbugs) @
 cloud-plugin-network-srx 
 [INFO]
 [INFO] --- findbugs-maven-plugin:3.0.1:check (cloudstack-findbugs) @
 cloud-plugin-network-srx ---
 [INFO] BugInstance size is 0
 [INFO] Error size is 0
 [INFO] No errors/warnings found
 [INFO]
 [INFO] --- cobertura-maven-plugin:2.6:instrument (default-cli) @
 cloud-plugin-network-srx ---
 [INFO] Cobertura 2.0.3 - GNU GPL License (NO WARRANTY) - See COPYRIGHT
 file
 
 [ERROR] Aug 17, 2015 5:11:13 PM
 net.sourceforge.cobertura.coveragedata.CoverageDataFileHandler
 saveCoverageData
 INFO: Cobertura: Saved information on 21 classes.
 
 [INFO] Instrumentation was successful.
 [INFO] NOT adding cobertura ser file to attached artifacts list.
 [INFO]
 [INFO] --- maven-resources-plugin:2.5:testResources
 (default-testResources) @ cloud-plugin-network-srx ---
 [debug] execute contextualize
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] skip non existing resourceDirectory
 http://jenkins.buildacloud.org/job/build-master-slowbuild/ws/plugins/network-elements/juniper-srx/test/resources
 [INFO] Copying 3 resources
 [INFO] Copying 3 resources
 [INFO]
 [INFO] --- maven-compiler-plugin:3.2:testCompile (default-testCompile) @
 cloud-plugin-network-srx ---
 [INFO] No sources to compile
 [INFO]
 [INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @
 cloud-plugin-network-srx ---
 [INFO]
 [INFO]  cobertura-maven-plugin:2.6:cobertura (default-cli) @
 cloud-plugin-network-srx 
 [INFO]
 [INFO] --- cobertura-maven-plugin:2.6:cobertura (default-cli) @
 cloud-plugin-network-srx ---
 [INFO] Cobertura 2.0.3 - GNU GPL License (NO WARRANTY) - See COPYRIGHT
 file
 [cobertura] INFO [main]
 net.sourceforge.cobertura.reporting.html.HTMLReport - Data file does not
 contain instrumentation information for the file
 com/cloud/network/element/JuniperSRXFirewallElementService.java. Ensure this
 class was instrumented, and this data file contains the instrumentation
 information.
 Report time: 1131ms
 
 [ERROR] Aug 17, 2015 5:11:14 PM
 net.sourceforge.cobertura.coveragedata.CoverageDataFileHandler
 loadCoverageData
 INFO: Cobertura: Loaded information on 21 classes.
 
 [INFO] Cobertura Report generation was successful.
 [INFO] Cobertura 2.0.3 - GNU GPL License (NO WARRANTY) - See COPYRIGHT
 file
 Report time: 1211ms
 
 [ERROR] Aug 17, 2015 5:11:16 PM
 net.sourceforge.cobertura.coveragedata.CoverageDataFileHandler
 loadCoverageData
 INFO: Cobertura: Loaded information on 21 classes.
 
 [INFO] Cobertura Report generation was successful.
 [INFO]
 [INFO]
 
 [INFO] Building Apache CloudStack Plugin - Nuage VSP 4.6.0-SNAPSHOT
 [INFO]
 
 [WARNING] The POM for org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 is
 missing, no dependency information available
 [WARNING] Failed to retrieve plugin descriptor for
 org.eclipse.m2e:lifecycle-mapping:1.0.0: Plugin
 org.eclipse.m2e:lifecycle-mapping:1.0.0 or one of its dependencies could not
 be resolved: Failed to read artifact descriptor for
 org.eclipse.m2e:lifecycle-mapping:jar:1.0.0
 [INFO]
 [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @
 cloud-plugin-network-vsp ---
 [INFO] Deleting
 http://jenkins.buildacloud.org/job/build-master-slowbuild/ws/plugins/network-elements/nuage-vsp/target
 (includes = [**/*], excludes = [])
 [INFO] Deleting
 http://jenkins.buildacloud.org/job/build-master-slowbuild/ws/plugins/network-elements

RE: [PROPOSAL] Closing PRs older than 1 month and without activity

[Boris Schrijver]

Remi,

Would it be possible to give the closed PRs which are not merged due to
inactivity or unfinished code-work a label? So the can be recognized when they
are closed? 

Best regards,

Boris Schrijver

TEL: +31633784542
MAIL: bo...@pcextreme.nl

 
 On August 17, 2015 at 5:49 PM Somesh Naidu somesh.na...@citrix.com
 wrote:
 
 
 +1
 
 Regards,
 Somesh
 
 
 -Original Message-
 From: Remi Bergsma [mailto:rberg...@schubergphilis.com]
 Sent: Monday, August 17, 2015 10:26 AM
 To: dev@cloudstack.apache.org
 Subject: [PROPOSAL] Closing PRs older than 1 month and without activity
 
 Hi all,
 
 There are several PRs that are quite old. They haven't been updated by
 their author for over a month and there was no response to comments made.
 
 As a RM, I want to maintain an as-short-as-possible list of PRs that is
 actively worked on. It is perfectly fine if a PR is open for a longer time, as
 long as it is actively maintained (or has a comment that explains why there is
 a delay). Long lists of open PRs don't give the impression we actively work on
 them and might keep people from contributing.
 
 Proposal:
 Let's close PRs where the author did not respond for over a month.
 
 How?
 For now, I'll manually select the PRs that I propose to close. Next, I
 make a PR with an empty commit that closes the PRs by triggering asfbot (as we
 cannot otherwise close PRs due to it being read-only for committers). By using
 a PR, it should be visible which PRs will get closed (after 2x LGTM and no
 -1). I’ll send an example PR with link to this thread after I've sent this
 e-mail.
 
 Work lost?
 The work done in a PR is not lost by closing the PR! If someone wants to
 take over, this is how you can merge the work in a new branch (keeping author
 and commit hashes the same) and add more commits on top of it. You can then
 send it as a new PR.
 
 Example:
 prId=12345
 git fetch origin pull/${prId}/head:pr/${prId}
 git merge --no-ff --log -m Merging PR ${prId} and continuing the work
 pr/${prId}
 git commit --amend -s --allow-empty-message -m ''
 
 
 Please let me know what you think: +1 or -1?
 
 If -1, what should we do instead?
 
 Regards,
 Remi
 

[PROPOSE] IPv4 renaming effort.

[Boris Schrijver]

Dear all,

I'll give a try at implementing IPv6 in basic zones in the next couple of weeks.
So that's what got the next thing started:

I did some looking through the code and noticed the difference between IPv6 and
IPv4 naming conventions in methods, variables and classes. IPv6 is always
clearly marked as IPv6, while IPv4 is most of the time just called IP. This of
course has historical reasons, as only one type was actively in use when
Cloudstack was first developed. As both are now widely and actively in use, to
aid readability, I would like to propose the following:

- IPv4 specific methods, variables and classes to be named IPv4 instead of IP.
- IPv6 specific methods, variables and classes to be named IPv6.
- Non-type-specific methods, variables and classes to be named IP.

- Of course adhering to the checkstyle naming conventions for methods, variables
and classes.
- Wait until the next major release (maybe 5.0) with renaming the external api
fields.

In my opinion this would aid readability a lot.

Best regards,

Boris Schrijver

TEL: +31633784542
MAIL: bo...@pcextreme.nl

Domain admins should be able to create/edit domains within the domain they are assigned to.

[Boris Schrijver]

Hi all,

A domain admin should be able to create, edit and remove domains within the
domain they are assigned to. Currently only root admins can do this.

Any objections to why this should not be implemented?

https://issues.apache.org/jira/browse/CLOUDSTACK-8734

Best regards,

Boris Schrijver

TEL: +31633784542
MAIL: bo...@pcextreme.nl

Re: Domain admins should be able to create/edit domains within the domain they are assigned to.

[Boris Schrijver]

Updated Jira ticket based on input.

Daan Hoogland mentioned this feature would complement uncontrolled growth. But
adding an option to make it configurable will counteract this. Right Daan?

Best regards,

Boris Schrijver

TEL: +31633784542
MAIL: bo...@pcextreme.nl

 
 On August 14, 2015 at 2:48 PM Wido den Hollander w...@widodh.nl wrote:
 
 
 
 
 On 14-08-15 14:47, Erik Weber wrote:
  On Fri, Aug 14, 2015 at 2:14 PM, Boris Schrijver bo...@pcextreme.nl
  wrote:
 
  Hi all,
 
  A domain admin should be able to create, edit and remove domains within
  the
  domain they are assigned to. Currently only root admins can do this.
 
  Any objections to why this should not be implemented?
 
  https://issues.apache.org/jira/browse/CLOUDSTACK-8734
 
 
 
  Would it make sense/be possible to make this configurable on a per
  domain/account basis?
  You could for instance add a checkbox to the domain admin to specify
  whether or not it is allowed to create subdomains.
 
 
 Makes sense indeed. This way you can control who's allowed to do this.
 
 Wido
 

RE: Remi Bergsma joins the PMC

[Boris Schrijver]

Congrats Remi!

Best regards,

Boris Schrijver

TEL: +31633784542
MAIL: bo...@pcextreme.nl

 
 On August 10, 2015 at 8:57 PM Somesh Naidu somesh.na...@citrix.com
 wrote:
 
 
 Congratulations Remi!
 
 Regards,
 Somesh
 
 
 -Original Message-
 From: Erik Weber [mailto:terbol...@gmail.com]
 Sent: Monday, August 10, 2015 2:13 PM
 To: dev
 Subject: Re: Remi Bergsma joins the PMC
 
 On Mon, Aug 10, 2015 at 7:08 PM, Daan Hoogland daan.hoogl...@gmail.com
 wrote:
 
  LS,
 
  Today the PMC has invited Remi Bergsma to join its ranks. I am happy to
  say
  that he accepted. Please join me in congratulating Remi.
 
 
 Congratulations Remi :-)
 
 --
 Erik
 

Jenkins at buildacloud.org

[Boris Schrijver]

Hi David, dev@,

Yesterday I spoke with Daan about jenkins.buildacloud.org, who maintains it and
who has ownership. As I would like to add a couple of jobs and automate some
things around packaging and syncing against the cloudstack.apt-get.eu repo. To
not stress any of the current maintainers I would like to ask access to commit
the changes myself.

Current list of jobs I want to add / change:

- Sync nightly package builds of master and the 4.5 branch to
cloudstack.apt-get.eu
- Add a job for packaging the 4.5 branch for Centos 7
- Fix the Centos packages on cloudstack.apt-get.eu as they are now branded
Shapeblue.

If any questions or remarks rise or exist, please ask!

Best regards,

Boris Schrijver

TEL: +31633784542
MAIL: bo...@pcextreme.nl

Revert AWS SDK to 1.3.22

[Boris Schrijver]

Hi all,

This PR (https://github.com/apache/cloudstack/pull/647) has two LGTM's so it
should be good to merge.

Together with this PR (https://github.com/apache/cloudstack/pull/651) it will
fix the current issues with the S3 platform.

In the coming weeks I will revise the entire S3 implementation and update the
Amazon AWS SDK to the latest version. In the coming revision I will also add
catching all exceptions thrown by the Amazon AWS SDK and implementing new
methods.

Best regards,

Boris Schrijver

TEL: +31633784542
MAIL: bo...@pcextreme.nl

Re: [DISCUSS][PROPOSAL] cleanup repo

[Boris Schrijver]

+1


Best regards,

Boris Schrijver

TEL: +31633784542
MAIL: bo...@pcextreme.nl

 
 On August 2, 2015 at 5:17 PM Wido den Hollander w...@widodh.nl wrote:
 
 
 
 
 On 08/02/2015 03:46 PM, Daan Hoogland wrote:
  As we are changing our review process I want to clean up the
  repository at apache getting rid of stale branches. Of course the
  release branches of old releases should stay, but a lot of old
  branches have been merged at unknown places in the master or old
  release branches. I want to propose to delete them as much as
  possible.
 
  - I want to delete any branch that has no commits newer then one year
  old
  - I want to ask the last commiter on any branch with commits newer
  then one year to review if 'their' branch can be removed
  - All branches that are merged back are to remain untouched.
 
  ideally only the branches 4.0, 4.1, 4.2, 4.3, 4.4, 4.5 and master will
  remain as branches HEAD. This is unfortunately not true for some older
  releases that were never merged back into their respective release
  branches. Any work in progress will of course not be touched.
 
  comments?
 
 
 Nope, a good idea. We should remove old branches. I'd say that
 everything over 6 months is also old.
 
 Wido
 

RE: [PROPOSAL] drop old upgrade code

[Boris Schrijver]

+1 on dropping the pre-4.x upgrade code, if done in a documented manner. Instead
of voting to drop it now shall we vote to drop it in a future release with
documentation and put it on the roadmap? Like:

At release 4.6: Initial notice to drop pre-4.x upgrade code at release 5.0.
At release 4.6: Suppress pre-4.x upgrade code from coverity scan.
At release 5.0: Drop pre-4.x upgrade code entirely.
At release 5.0: Create documentation to show upgrade path from pre-4.x to 5.0.

Best regards,

Boris Schrijver

 
 On July 22, 2015 at 11:42 AM Koushik Das koushik@citrix.com wrote:
 
 
 -1 to dropping pre-4.x upgrade code. If possible we should suppress the
 old upgrade files from coverity scan.
 
 Reasons:
 There may be users on pre-4.x versions.
 Removing a functionality should be associated with proper documentation
 and an advanced notification in some prior releases. This is similar to the
 way some API is deprecated and then eventually removed.
 
 -Koushik
 
 -Original Message-
 From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
 Sent: Monday, 20 July 2015 17:19
 To: dev
 Subject: [PROPOSAL] drop old upgrade code
 
 LS,
 
 In coverity the only remaining high impact issues are concerned with
 upgrade code. Some of it is in 4.3 and 4.5 code but most in pre-4 upgrades.
 
 I addressed the file Upgrade218to22.java in a PR [1] and I move that we
 don't pull it but instead drop the file altogether together with all upgrade
 code dating prior to 4.0.0. anybody on older versions can still upgrade to any
 version between 4.0 and 4.5 and move on from there.
 
 My objective is to have no high impact issues remaining so we clearly see
 when we are digressing beit by hand or in an automated way.
 
 +1?
 
 [1] https://github.com/apache/cloudstack/pull/603
 --
 Daan
 

RE: Introducing Boris Schrijver

[Boris Schrijver]

Hi all,

Thanks for the warm welcome! I've setup my development environment and I'm ready
to rock!

Best regards,

Boris Schrijver

PCextreme B.V.

MAIL: bo...@pcextreme.nl

 
 On July 10, 2015 at 10:15 AM Giles Sirett giles.sir...@shapeblue.com
 wrote:
 
 
 Welcome Boris
 
 
 Kind Regards
 Giles
 
 D: +44 20 3603 0541 | M: +44 796 111 2055
 giles.sir...@shapeblue.com
 
 
 
 
  -Original Message-
  From: Wido den Hollander [mailto:w...@widodh.nl]
  Sent: 08 July 2015 16:08
  To: dev@cloudstack.apache.org
  Cc: bo...@pcextreme.nl
  Subject: Introducing Boris Schrijver
 
  Hi all,
 
  As you might know, we at PCextreme are using CloudStack for our public
  cloud
  offering and have been looking for a CloudStack dev for a long time.
 
  We found one; so let me introduce Boris Schrijver.
 
  Boris will be our fulltime CloudStack developer with no other purpose
  then
  making CloudStack better :)
 
  CloudStack is a Apache project, so it will be Boris contributing to
  CloudStack and
  NOT PCextreme as a company. He might become a committer one day, who
  knows.
 
  Today is his first day, so it will take a bit before you'll see the
  first PR coming in.
 
  Wido
 
 Find out more about ShapeBlue and our range of CloudStack related services
 
 IaaS Cloud Design 
 Buildhttp://shapeblue.com/iaas-cloud-design-and-build//
 CSForge – rapid IaaS deployment frameworkhttp://shapeblue.com/csforge/
 CloudStack Consultinghttp://shapeblue.com/cloudstack-consultancy/
 CloudStack Software
 Engineeringhttp://shapeblue.com/cloudstack-software-engineering/
 CloudStack Infrastructure
 Supporthttp://shapeblue.com/cloudstack-infrastructure-support/
 CloudStack Bootcamp Training
 Courseshttp://shapeblue.com/cloudstack-training/
 
 This email and any attachments to it may be confidential and are intended
 solely for the use of the individual to whom it is addressed. Any views or
 opinions expressed are solely those of the author and do not necessarily
 represent those of Shape Blue Ltd or related companies. If you are not the
 intended recipient of this email, you must neither take any action based upon
 its contents, nor copy or show it to anyone. Please contact the sender if you
 believe you have received this email in error. Shape Blue Ltd is a company
 incorporated in England  Wales. ShapeBlue Services India LLP is a company
 incorporated in India and is operated under license from Shape Blue Ltd. Shape
 Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is
 operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company
 registered by The Republic of South Africa and is traded under license from
 Shape Blue Ltd. ShapeBlue is a registered trademark.