Re: Review Request 18623: CLOUDSTACK-6147: Adding first set of test cases for Dynamic Compute Offering feature

[Gaurav Aradhye]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/18623/
---

(Updated March 7, 2014, 2:38 p.m.)


Review request for cloudstack, Santhosh Edukulla and SrikanteswaraRao Talluri.


Changes
---

Talluri, can you please commit this to master branch?


Bugs: CLOUDSTACK-6147
https://issues.apache.org/jira/browse/CLOUDSTACK-6147


Repository: cloudstack-git


Description
---

Adding first set of automation test cases for Dynamic Compute Offering Feature.


Diffs
-

  test/integration/component/test_dynamic_compute_offering.py PRE-CREATION 
  tools/marvin/marvin/integration/lib/base.py 0a7ad94 
  tools/marvin/marvin/integration/lib/common.py b2da3ff 

Diff: https://reviews.apache.org/r/18623/diff/


Testing
---

Yes.

Log:
Deploy VM with dynamic service offering and check VM stats ... ok
Deploy VM with dynamic service offering and check VM stats ... ok
Create dynamic compute offering with cpunumber, cpuspeed and memory ... ok
Create dynamic compute offering with only cpunumber unspecified ... ok
Create dynamic compute offering with only cpuspeed unspecified ... ok
Create dynamic compute offering with only memory unspecified ... ok
Create normal compute offering with non zero values for cpu, ... ok
Test deploy VM with dynamic compute offering ... ok
Test deploy VM with dynamic compute offering ... ok
Test deploy VM with static offering ... ok
Test deploy VM with static offering ... ok
--
Ran 11 tests in 794.431s

OK


Thanks,

Gaurav Aradhye

Re: Just checked in a minor change to the DB

[Daan Hoogland]

Thanks for the heads up Mike,

As discussed in your thread [1]. You are eating your own dogfood here.
I was checking in a minor change to the upgrade handling yesterday and
decided not to bother everyone with it. evil me. In that thread we
didn't dicide on a tag, yet.

I would suggest
[DB-CHANGE] and
[BEHAVIORAL-CHANGE]

[1] http://markmail.org/message/r7wv36o356nolq7f

On Thu, Mar 6, 2014 at 9:05 PM, Mike Tutkowski
 wrote:
> Hi everyone,
>
> Just wanted to give you a heads up that I made a minor change to two views
> in the DB in 9b66866dc2085486f465159cbd446ac03e266a2c:
>
> service_offering_view and disk_offering_view
>
> I added some columns to these views so I could present additional info in
> the GUI.
>
> If you want to bring these two views up to date, just run the following SQL:
>
> DROP VIEW IF EXISTS `cloud`.`disk_offering_view`;
> CREATE VIEW `cloud`.`disk_offering_view` AS
> select
> disk_offering.id,
> disk_offering.uuid,
> disk_offering.name,
> disk_offering.display_text,
> disk_offering.disk_size,
> disk_offering.min_iops,
> disk_offering.max_iops,
> disk_offering.created,
> disk_offering.tags,
> disk_offering.customized,
> disk_offering.customized_iops,
> disk_offering.removed,
> disk_offering.use_local_storage,
> disk_offering.system_use,
> disk_offering.hv_ss_reserve,
> disk_offering.bytes_read_rate,
> disk_offering.bytes_write_rate,
> disk_offering.iops_read_rate,
> disk_offering.iops_write_rate,
> disk_offering.cache_mode,
> disk_offering.sort_key,
> disk_offering.type,
> disk_offering.display_offering,
> domain.id domain_id,
> domain.uuid domain_uuid,
> domain.name domain_name,
> domain.path domain_path
> from
> `cloud`.`disk_offering`
> left join
> `cloud`.`domain` ON disk_offering.domain_id = domain.id
> where
> disk_offering.state='ACTIVE';
>
> DROP VIEW IF EXISTS `cloud`.`service_offering_view`;
> CREATE VIEW `cloud`.`service_offering_view` AS
> select
> service_offering.id,
> disk_offering.uuid,
> disk_offering.name,
> disk_offering.display_text,
> disk_offering.created,
> disk_offering.tags,
> disk_offering.removed,
> disk_offering.use_local_storage,
> disk_offering.system_use,
> disk_offering.customized_iops,
> disk_offering.min_iops,
> disk_offering.max_iops,
> disk_offering.hv_ss_reserve,
> disk_offering.bytes_read_rate,
> disk_offering.bytes_write_rate,
> disk_offering.iops_read_rate,
> disk_offering.iops_write_rate,
> disk_offering.cache_mode,
> service_offering.cpu,
> service_offering.speed,
> service_offering.ram_size,
> service_offering.nw_rate,
> service_offering.mc_rate,
> service_offering.ha_enabled,
> service_offering.limit_cpu_use,
> service_offering.host_tag,
> service_offering.default_use,
> service_offering.vm_type,
> service_offering.sort_key,
> service_offering.is_volatile,
> service_offering.deployment_planner,
> domain.id domain_id,
> domain.uuid domain_uuid,
> domain.name domain_name,
> domain.path domain_path
> from
> `cloud`.`service_offering`
> inner join
> `cloud`.`disk_offering` ON service_offering.id = disk_offering.id
> left join
> `cloud`.`domain` ON disk_offering.domain_id = domain.id
> where
> disk_offering.state='Active';
>
> 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
> *(tm)*



-- 
Daan

RE: Just checked in a minor change to the DB

[Rajesh Battala]

Hi Mike, 
This change is for master right?

Thanks
Rajesh Battala

-Original Message-
From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] 
Sent: Friday, March 7, 2014 1:36 AM
To: dev@cloudstack.apache.org
Subject: Just checked in a minor change to the DB

Hi everyone,

Just wanted to give you a heads up that I made a minor change to two views in 
the DB in 9b66866dc2085486f465159cbd446ac03e266a2c:

service_offering_view and disk_offering_view

I added some columns to these views so I could present additional info in the 
GUI.

If you want to bring these two views up to date, just run the following SQL:

DROP VIEW IF EXISTS `cloud`.`disk_offering_view`; CREATE VIEW 
`cloud`.`disk_offering_view` AS
select
disk_offering.id,
disk_offering.uuid,
disk_offering.name,
disk_offering.display_text,
disk_offering.disk_size,
disk_offering.min_iops,
disk_offering.max_iops,
disk_offering.created,
disk_offering.tags,
disk_offering.customized,
disk_offering.customized_iops,
disk_offering.removed,
disk_offering.use_local_storage,
disk_offering.system_use,
disk_offering.hv_ss_reserve,
disk_offering.bytes_read_rate,
disk_offering.bytes_write_rate,
disk_offering.iops_read_rate,
disk_offering.iops_write_rate,
disk_offering.cache_mode,
disk_offering.sort_key,
disk_offering.type,
disk_offering.display_offering,
domain.id domain_id,
domain.uuid domain_uuid,
domain.name domain_name,
domain.path domain_path
from
`cloud`.`disk_offering`
left join
`cloud`.`domain` ON disk_offering.domain_id = domain.id
where
disk_offering.state='ACTIVE';

DROP VIEW IF EXISTS `cloud`.`service_offering_view`; CREATE VIEW 
`cloud`.`service_offering_view` AS
select
service_offering.id,
disk_offering.uuid,
disk_offering.name,
disk_offering.display_text,
disk_offering.created,
disk_offering.tags,
disk_offering.removed,
disk_offering.use_local_storage,
disk_offering.system_use,
disk_offering.customized_iops,
disk_offering.min_iops,
disk_offering.max_iops,
disk_offering.hv_ss_reserve,
disk_offering.bytes_read_rate,
disk_offering.bytes_write_rate,
disk_offering.iops_read_rate,
disk_offering.iops_write_rate,
disk_offering.cache_mode,
service_offering.cpu,
service_offering.speed,
service_offering.ram_size,
service_offering.nw_rate,
service_offering.mc_rate,
service_offering.ha_enabled,
service_offering.limit_cpu_use,
service_offering.host_tag,
service_offering.default_use,
service_offering.vm_type,
service_offering.sort_key,
service_offering.is_volatile,
service_offering.deployment_planner,
domain.id domain_id,
domain.uuid domain_uuid,
domain.name domain_name,
domain.path domain_path
from
`cloud`.`service_offering`
inner join
`cloud`.`disk_offering` ON service_offering.id = disk_offering.id
left join
`cloud`.`domain` ON disk_offering.domain_id = domain.id
where
disk_offering.state='Active';

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
*(tm)*

Re: Review Request 18016: CLOUDSTACK-5626: Simplifying VM Migrate code

[Gaurav Aradhye]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/18016/
---

(Updated March 7, 2014, 3:06 p.m.)


Review request for cloudstack, Girish Shilamkar, Santhosh Edukulla, and 
SrikanteswaraRao Talluri.


Changes
---

Rebased and tested with latest master. Talluri, can you please commit this?


Bugs: CLOUDSTACK-5626
https://issues.apache.org/jira/browse/CLOUDSTACK-5626


Repository: cloudstack-git


Description
---

Removing different ways of obtaining suitable hosts. Used built in API 
"findHostsForMigration" and skipped the test if suitable host is not found 
instead of throwing assertion error.
Removed unnecessary common function.


Diffs (updated)
-

  test/integration/component/test_cpu_domain_limits.py c427e4f 
  test/integration/component/test_cpu_limits.py bdf2869 
  test/integration/component/test_cpu_project_limits.py a8a1b3c 
  test/integration/component/test_memory_limits.py 7921e4b 
  test/integration/component/test_mm_domain_limits.py 68660c1 
  test/integration/component/test_mm_project_limits.py c314011 
  test/integration/component/test_vpc_vm_life_cycle.py 01373ac 
  tools/marvin/marvin/codes.py 3882f0d 
  tools/marvin/marvin/integration/lib/common.py b2da3ff 

Diff: https://reviews.apache.org/r/18016/diff/


Testing
---

Yes.


Thanks,

Gaurav Aradhye

Re: Review Request 18844: Amended review request (origin: https://reviews.apache.org/r/17531/)

[Daan Hoogland]

no problem, thanks

On Thu, Mar 6, 2014 at 11:06 PM, Alex Hitchins
 wrote:
> Ah, sorry - I'll delete this one and add to the original.
>
>
> Regards
>
> Alex Hitchins
>
> D: +44 1892 523 587 | S: +44 2036 030 540 | M: +44 7788 423 969
>
> alex.hitch...@shapeblue.com
>
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: 06 March 2014 17:39
> To: dev; Alex Hitchins
> Cc: Devdeep Singh
> Subject: Re: Review Request 18844: Amended review request (origin: 
> https://reviews.apache.org/r/17531/)
>
> Alex, you don't have to create a new review request for this. If you upload a 
> new version of the patch we can see the diff online and decide more easily 
> that concerns were met and no new concerns where introduced.
>
> On Thu, Mar 6, 2014 at 3:59 PM, Alexander Hitchins 
>  wrote:
>>
>> ---
>> This is an automatically generated e-mail. To reply, visit:
>> https://reviews.apache.org/r/18844/
>> ---
>>
>> Review request for cloudstack and Devdeep Singh.
>>
>>
>> Bugs: cloudstack-5440
>> https://issues.apache.org/jira/browse/cloudstack-5440
>>
>>
>> Repository: cloudstack-git
>>
>>
>> Description
>> ---
>>
>> Please see amended script to add new os types. 32 & 64 bit separated and 
>> hard coded to specific Id numbers.
>>
>>
>> Diffs
>> -
>>
>>   setup/db/db/schema-430to440.sql acc7e21
>>
>> Diff: https://reviews.apache.org/r/18844/diff/
>>
>>
>> Testing
>> ---
>>
>> Ran SQL, changes applied with no errors.
>>
>>
>> Thanks,
>>
>> Alexander Hitchins
>>
>
>
>
> --
> Daan
> Need Enterprise Grade Support for Apache CloudStack?
> Our CloudStack Infrastructure 
> Support offers the 
> best 24/7 SLA for CloudStack Environments.
>
> Apache CloudStack Bootcamp training courses
>
> **NEW!** CloudStack 4.2.1 training
> 18th-19th February 2014, Brazil. 
> Classroom
> 17th-23rd March 2014, Region A. Instructor led, 
> On-line
> 24th-28th March 2014, Region B. Instructor led, 
> On-line
> 16th-20th June 2014, Region A. Instructor led, 
> On-line
> 23rd-27th June 2014, Region B. Instructor led, 
> On-line
>
> 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 is a registered 
> trademark.



-- 
Daan

Re: CLOUDSTACK-5641

[Nitin Mehta]

Apologies for having missed this.
Please find details in the bug.

Thanks,
-Nitin

From: Namita Chaudhari 
mailto:namita.chaudh...@sungard.com>>
Reply-To: "dev@cloudstack.apache.org" 
mailto:dev@cloudstack.apache.org>>
Date: Thursday 6 March 2014 11:19 PM
To: "dev@cloudstack.apache.org" 
mailto:dev@cloudstack.apache.org>>
Subject: Re: CLOUDSTACK-5641

Hi Nitin,

Regarding CLOUDSTACK-5641, can you please verify the screenshot and let me know 
that is it the same local storage you are looking for in UI?
Please let me know your comments.


Thanks and Regards,
Namita


On Tue, Feb 25, 2014 at 7:11 PM, Namita Chaudhari 
mailto:namita.chaudh...@sungard.com>> wrote:
Hi All,

I started looking at https://issues.apache.org/jira/browse/CLOUDSTACK-5641
If anybody is working on it please let me know.


Nitin,
I tried this issue on master and I see the local storage is displayed in the 
admin's webui. In the storage pool view, though the capacity_type = 3, it does 
not affect the local storage that is displayed in the UI as shown in the 
screenshot attached to the jira.
I was trying to figure out that is there any other view from which we get this 
data.

Can you please verify the screenshot and let me know is it the same local 
storage you are looking for in UI?
Please let me know your comments.

Thanks and Regards,
--

Namita Chaudhari ● Associate Engineer- Product Development ● SunGard 
Availability Services, India ● Mobile: +91 9762922138 ● Email: 
namita.chaudh...@sungard.com

[AS_yt][AS_twitter][AS_in][AS_gplus][AS_fb][AS_ss]



--

Namita Chaudhari ● Associate Engineer- Product Development ● SunGard 
Availability Services, India ● Mobile: +91 9762922138 ● Email: 
namita.chaudh...@sungard.com

[AS_yt][AS_twitter][AS_in][AS_gplus][AS_fb][AS_ss]

Review Request 18902: CLOUDSTACK-6211: Xenserver - HA - SSVM fails to start due to running out of management Ip ranges when testing host down scenarios

[Harikrishna Patnala]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/18902/
---

Review request for cloudstack and Koushik Das.


Bugs: CLOUDSTACK-6211
https://issues.apache.org/jira/browse/CLOUDSTACK-6211


Repository: cloudstack-git


Description
---

CLOUDSTACK-6211: Xenserver - HA - SSVM fails to start due to running out of 
management Ip ranges when testing host down scenarios


Diffs
-

  engine/orchestration/src/com/cloud/vm/VirtualMachineManagerImpl.java be05cd9 

Diff: https://reviews.apache.org/r/18902/diff/


Testing
---


Thanks,

Harikrishna Patnala

Re: Review Request 18902: CLOUDSTACK-6211: Xenserver - HA - SSVM fails to start due to running out of management Ip ranges when testing host down scenarios

[Harikrishna Patnala]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/18902/
---

(Updated March 7, 2014, 11:04 a.m.)


Review request for cloudstack and Koushik Das.


Bugs: CLOUDSTACK-6211
https://issues.apache.org/jira/browse/CLOUDSTACK-6211


Repository: cloudstack-git


Description
---

CLOUDSTACK-6211: Xenserver - HA - SSVM fails to start due to running out of 
management Ip ranges when testing host down scenarios


Diffs (updated)
-

  engine/orchestration/src/com/cloud/vm/VirtualMachineManagerImpl.java be05cd9 

Diff: https://reviews.apache.org/r/18902/diff/


Testing
---


Thanks,

Harikrishna Patnala

Re: jenkins job for the developer build

[chris snow]

Ah, thanks for the tip.

On Thu, Mar 6, 2014 at 9:21 AM, Hugo Trippaers  wrote:
> The Jenkins builds do mvn -Pawsapi,systemvm clean install.
>
> I'm not using the developer profile there thats just for Marvin and Apidocs. 
> Those are built separately. You can have a fully functional cloud dev 
> environment without the developer profile.
>
> Cheers,
>
> Hugo
>
> Sent from my iPhone
>
>> On 6 mrt. 2014, at 06:01, chris snow  wrote:
>>
>> Is there a jenkins job for the developer's build, i.e. mvn clean
>> install -P developer,systemvm?  As a newbie cloudstack developer, when
>> the build fails locally it's difficult to know whether the problem is
>> because I am doing something wrong, or if the problem is due to a bad
>> commit.



-- 
Check out my professional profile and connect with me on LinkedIn.
http://lnkd.in/cw5k69

Re: [DISCUSS] realhostip.com going away

[France]

Hi all.

Are we going to have a solution for older versions like 4.1.1?
I think we can already change that domain to something different 
currently in settings. Hopefully it's not "hardcoded" anywhere else. Is it?


I think it's the right thing to move away from such solution in future 
versions, but just killing the service with 4 months notice, is not a 
way to go about in enterprise world. How expensive can it be to keep 
providing it?


If someone needs to take over realhostip.com, we can offer our 
datacenter resources too.


Regards,
F.

Re: Just checked in a minor change to the DB

[Mike Tutkowski]

Good point! :) I should have said what branch it was in. You are correct it
was master.


On Fri, Mar 7, 2014 at 2:33 AM, Rajesh Battala wrote:

> Hi Mike,
> This change is for master right?
>
> Thanks
> Rajesh Battala
>
> -Original Message-
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: Friday, March 7, 2014 1:36 AM
> To: dev@cloudstack.apache.org
> Subject: Just checked in a minor change to the DB
>
> Hi everyone,
>
> Just wanted to give you a heads up that I made a minor change to two views
> in the DB in 9b66866dc2085486f465159cbd446ac03e266a2c:
>
> service_offering_view and disk_offering_view
>
> I added some columns to these views so I could present additional info in
> the GUI.
>
> If you want to bring these two views up to date, just run the following
> SQL:
>
> DROP VIEW IF EXISTS `cloud`.`disk_offering_view`; CREATE VIEW
> `cloud`.`disk_offering_view` AS
> select
> disk_offering.id,
> disk_offering.uuid,
> disk_offering.name,
> disk_offering.display_text,
> disk_offering.disk_size,
> disk_offering.min_iops,
> disk_offering.max_iops,
> disk_offering.created,
> disk_offering.tags,
> disk_offering.customized,
> disk_offering.customized_iops,
> disk_offering.removed,
> disk_offering.use_local_storage,
> disk_offering.system_use,
> disk_offering.hv_ss_reserve,
> disk_offering.bytes_read_rate,
> disk_offering.bytes_write_rate,
> disk_offering.iops_read_rate,
> disk_offering.iops_write_rate,
> disk_offering.cache_mode,
> disk_offering.sort_key,
> disk_offering.type,
> disk_offering.display_offering,
> domain.id domain_id,
> domain.uuid domain_uuid,
> domain.name domain_name,
> domain.path domain_path
> from
> `cloud`.`disk_offering`
> left join
> `cloud`.`domain` ON disk_offering.domain_id = domain.id
> where
> disk_offering.state='ACTIVE';
>
> DROP VIEW IF EXISTS `cloud`.`service_offering_view`; CREATE VIEW
> `cloud`.`service_offering_view` AS
> select
> service_offering.id,
> disk_offering.uuid,
> disk_offering.name,
> disk_offering.display_text,
> disk_offering.created,
> disk_offering.tags,
> disk_offering.removed,
> disk_offering.use_local_storage,
> disk_offering.system_use,
> disk_offering.customized_iops,
> disk_offering.min_iops,
> disk_offering.max_iops,
> disk_offering.hv_ss_reserve,
> disk_offering.bytes_read_rate,
> disk_offering.bytes_write_rate,
> disk_offering.iops_read_rate,
> disk_offering.iops_write_rate,
> disk_offering.cache_mode,
> service_offering.cpu,
> service_offering.speed,
> service_offering.ram_size,
> service_offering.nw_rate,
> service_offering.mc_rate,
> service_offering.ha_enabled,
> service_offering.limit_cpu_use,
> service_offering.host_tag,
> service_offering.default_use,
> service_offering.vm_type,
> service_offering.sort_key,
> service_offering.is_volatile,
> service_offering.deployment_planner,
> domain.id domain_id,
> domain.uuid domain_uuid,
> domain.name domain_name,
> domain.path domain_path
> from
> `cloud`.`service_offering`
> inner join
> `cloud`.`disk_offering` ON service_offering.id = disk_offering.id
> left join
> `cloud`.`domain` ON disk_offering.domain_id = domain.id
> where
> disk_offering.state='Active';
>
> 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
> *(tm)*
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud
*(tm)*

Re: Just checked in a minor change to the DB

[Mike Tutkowski]

I like either tag.

Since DB changes are the most likely to lead to breaking other people's
environments, maybe we should go with that one:

[DB-CHANGE]

Ideally we'd provide the branch, commit SHA, and a manual way around it, if
there is something simple (like in my case yesterday, simply deleting and
re-creating two views). If there's no easy way around it, then don't bother
providing that.

Sound reasonable?


On Fri, Mar 7, 2014 at 2:12 AM, Daan Hoogland wrote:

> Thanks for the heads up Mike,
>
> As discussed in your thread [1]. You are eating your own dogfood here.
> I was checking in a minor change to the upgrade handling yesterday and
> decided not to bother everyone with it. evil me. In that thread we
> didn't dicide on a tag, yet.
>
> I would suggest
> [DB-CHANGE] and
> [BEHAVIORAL-CHANGE]
>
> [1] http://markmail.org/message/r7wv36o356nolq7f
>
> On Thu, Mar 6, 2014 at 9:05 PM, Mike Tutkowski
>  wrote:
> > Hi everyone,
> >
> > Just wanted to give you a heads up that I made a minor change to two
> views
> > in the DB in 9b66866dc2085486f465159cbd446ac03e266a2c:
> >
> > service_offering_view and disk_offering_view
> >
> > I added some columns to these views so I could present additional info in
> > the GUI.
> >
> > If you want to bring these two views up to date, just run the following
> SQL:
> >
> > DROP VIEW IF EXISTS `cloud`.`disk_offering_view`;
> > CREATE VIEW `cloud`.`disk_offering_view` AS
> > select
> > disk_offering.id,
> > disk_offering.uuid,
> > disk_offering.name,
> > disk_offering.display_text,
> > disk_offering.disk_size,
> > disk_offering.min_iops,
> > disk_offering.max_iops,
> > disk_offering.created,
> > disk_offering.tags,
> > disk_offering.customized,
> > disk_offering.customized_iops,
> > disk_offering.removed,
> > disk_offering.use_local_storage,
> > disk_offering.system_use,
> > disk_offering.hv_ss_reserve,
> > disk_offering.bytes_read_rate,
> > disk_offering.bytes_write_rate,
> > disk_offering.iops_read_rate,
> > disk_offering.iops_write_rate,
> > disk_offering.cache_mode,
> > disk_offering.sort_key,
> > disk_offering.type,
> > disk_offering.display_offering,
> > domain.id domain_id,
> > domain.uuid domain_uuid,
> > domain.name domain_name,
> > domain.path domain_path
> > from
> > `cloud`.`disk_offering`
> > left join
> > `cloud`.`domain` ON disk_offering.domain_id = domain.id
> > where
> > disk_offering.state='ACTIVE';
> >
> > DROP VIEW IF EXISTS `cloud`.`service_offering_view`;
> > CREATE VIEW `cloud`.`service_offering_view` AS
> > select
> > service_offering.id,
> > disk_offering.uuid,
> > disk_offering.name,
> > disk_offering.display_text,
> > disk_offering.created,
> > disk_offering.tags,
> > disk_offering.removed,
> > disk_offering.use_local_storage,
> > disk_offering.system_use,
> > disk_offering.customized_iops,
> > disk_offering.min_iops,
> > disk_offering.max_iops,
> > disk_offering.hv_ss_reserve,
> > disk_offering.bytes_read_rate,
> > disk_offering.bytes_write_rate,
> > disk_offering.iops_read_rate,
> > disk_offering.iops_write_rate,
> > disk_offering.cache_mode,
> > service_offering.cpu,
> > service_offering.speed,
> > service_offering.ram_size,
> > service_offering.nw_rate,
> > service_offering.mc_rate,
> > service_offering.ha_enabled,
> > service_offering.limit_cpu_use,
> > service_offering.host_tag,
> > service_offering.default_use,
> > service_offering.vm_type,
> > service_offering.sort_key,
> > service_offering.is_volatile,
> > service_offering.deployment_planner,
> > domain.id domain_id,
> > domain.uuid domain_uuid,
> > domain.name domain_name,
> > domain.path domain_path
> > from
> > `cloud`.`service_offering`
> > inner join
> > `cloud`.`disk_offering` ON service_offering.id =
> disk_offering.id
> > left join
> > `cloud`.`domain` ON disk_offering.domain_id = domain.id
> > where
> > disk_offering.state='Active';
> >
> > 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
> > *(tm)*
>
>
>
> --
> Daan
>



-- 
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkow...@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud
*(tm)*

Re: Review Request 17888: Dispatcher corrections, refactoring and tests. Corrects problems from previous attempt

[Antonio Fornie]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/17888/
---

(Updated March 7, 2014, 3:38 p.m.)


Review request for cloudstack, Alena Prokharchyk, daan Hoogland, and Hugo 
Trippaers.


Changes
---

Fix conflicts with last master


Repository: cloudstack-git


Description
---

Dispatcher corrections, refactoring and tests. Corrects problems from previous 
attempts that were reverted by Alena. Most of the changes are the same, but 
this one is not creating conflicts of Map types for Aync Commands or for 
parameters as Lists or Maps.


Diffs (updated)
-

  api/src/org/apache/cloudstack/api/ApiConstants.java 14df653 
  api/src/org/apache/cloudstack/api/BaseCmd.java e869ddf 
  api/src/org/apache/cloudstack/api/BaseListCmd.java c1a4b4c 
  api/test/org/apache/cloudstack/api/BaseCmdTest.java PRE-CREATION 
  server/resources/META-INF/cloudstack/core/spring-server-core-misc-context.xml 
fd2f5fb 
  server/src/com/cloud/api/ApiDispatcher.java 5bdefe7 
  server/src/com/cloud/api/ApiServer.java 7e29324 
  server/src/com/cloud/api/ApiServlet.java 46f7eba 
  server/src/com/cloud/api/dispatch/CommandCreationWorker.java PRE-CREATION 
  server/src/com/cloud/api/dispatch/DispatchChain.java PRE-CREATION 
  server/src/com/cloud/api/dispatch/DispatchChainFactory.java PRE-CREATION 
  server/src/com/cloud/api/dispatch/DispatchTask.java PRE-CREATION 
  server/src/com/cloud/api/dispatch/DispatchWorker.java PRE-CREATION 
  server/src/com/cloud/api/dispatch/ParamGenericValidationWorker.java 
PRE-CREATION 
  server/src/com/cloud/api/dispatch/ParamProcessWorker.java PRE-CREATION 
  server/src/com/cloud/api/dispatch/ParamUnpackWorker.java PRE-CREATION 
  server/src/com/cloud/api/dispatch/SpecificCmdValidationWorker.java 
PRE-CREATION 
  server/src/com/cloud/network/as/AutoScaleManagerImpl.java 208b4a4 
  server/src/com/cloud/network/router/VirtualNetworkApplianceManagerImpl.java 
37171f5 
  server/src/com/cloud/storage/snapshot/SnapshotSchedulerImpl.java a85c052 
  server/test/com/cloud/api/ApiDispatcherTest.java 7314a57 
  server/test/com/cloud/api/dispatch/CommandCreationWorkerTest.java 
PRE-CREATION 
  server/test/com/cloud/api/dispatch/DispatchChainFactoryTest.java PRE-CREATION 
  server/test/com/cloud/api/dispatch/ParamGenericValidationWorkerTest.java 
PRE-CREATION 
  server/test/com/cloud/api/dispatch/ParamProcessWorkerTest.java PRE-CREATION 
  server/test/com/cloud/api/dispatch/ParamSemanticValidationWorkerTest.java 
PRE-CREATION 

Diff: https://reviews.apache.org/r/17888/diff/


Testing
---

Full build and test plus manually testing many features. Also including 
CreateTagsCommand that failed in previous commit.

All unit and integration tests.

Test CS Web UI with the browser going through several use cases.

Also use the CS API by sending HTTP requests generated manually including 
requests for Async Commands with Map parameters and during these tests apart 
fromtesting correct functionality I also debugged to check that Maps created 
correctly where they should but also that in the cases where the async command 
must be persisted and later on retrieved and deserialized by gson everything 
works ok and does what and where is expected. An example based on the comment 
by Alena:
http://localhost:8096/client/api?command=createTags&resourceids=ids&resourcetype=type&tags[0].key=region&tags[0].value=canada
Also other examples like
http://localhost:8096/client/api?command=createSecondaryStagingStore&url=httpbla&details[0].key=region&details[0].value=canada&details[1].key=element&details[1].value=fire


Thanks,

Antonio Fornie

Re: Review Request 17888: Dispatcher corrections, refactoring and tests. Corrects problems from previous attempt

[Antonio Fornie]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/17888/
---

(Updated March 7, 2014, 3:41 p.m.)


Review request for cloudstack, Alena Prokharchyk, daan Hoogland, and Hugo 
Trippaers.


Changes
---

Resolve conflicts with master.


Repository: cloudstack-git


Description
---

Dispatcher corrections, refactoring and tests. Corrects problems from previous 
attempts that were reverted by Alena. Most of the changes are the same, but 
this one is not creating conflicts of Map types for Aync Commands or for 
parameters as Lists or Maps.


Diffs
-

  api/src/org/apache/cloudstack/api/ApiConstants.java 14df653 
  api/src/org/apache/cloudstack/api/BaseCmd.java e869ddf 
  api/src/org/apache/cloudstack/api/BaseListCmd.java c1a4b4c 
  api/test/org/apache/cloudstack/api/BaseCmdTest.java PRE-CREATION 
  server/resources/META-INF/cloudstack/core/spring-server-core-misc-context.xml 
fd2f5fb 
  server/src/com/cloud/api/ApiDispatcher.java 5bdefe7 
  server/src/com/cloud/api/ApiServer.java 7e29324 
  server/src/com/cloud/api/ApiServlet.java 46f7eba 
  server/src/com/cloud/api/dispatch/CommandCreationWorker.java PRE-CREATION 
  server/src/com/cloud/api/dispatch/DispatchChain.java PRE-CREATION 
  server/src/com/cloud/api/dispatch/DispatchChainFactory.java PRE-CREATION 
  server/src/com/cloud/api/dispatch/DispatchTask.java PRE-CREATION 
  server/src/com/cloud/api/dispatch/DispatchWorker.java PRE-CREATION 
  server/src/com/cloud/api/dispatch/ParamGenericValidationWorker.java 
PRE-CREATION 
  server/src/com/cloud/api/dispatch/ParamProcessWorker.java PRE-CREATION 
  server/src/com/cloud/api/dispatch/ParamUnpackWorker.java PRE-CREATION 
  server/src/com/cloud/api/dispatch/SpecificCmdValidationWorker.java 
PRE-CREATION 
  server/src/com/cloud/network/as/AutoScaleManagerImpl.java 208b4a4 
  server/src/com/cloud/network/router/VirtualNetworkApplianceManagerImpl.java 
37171f5 
  server/src/com/cloud/storage/snapshot/SnapshotSchedulerImpl.java a85c052 
  server/test/com/cloud/api/ApiDispatcherTest.java 7314a57 
  server/test/com/cloud/api/dispatch/CommandCreationWorkerTest.java 
PRE-CREATION 
  server/test/com/cloud/api/dispatch/DispatchChainFactoryTest.java PRE-CREATION 
  server/test/com/cloud/api/dispatch/ParamGenericValidationWorkerTest.java 
PRE-CREATION 
  server/test/com/cloud/api/dispatch/ParamProcessWorkerTest.java PRE-CREATION 
  server/test/com/cloud/api/dispatch/ParamSemanticValidationWorkerTest.java 
PRE-CREATION 

Diff: https://reviews.apache.org/r/17888/diff/


Testing
---

Full build and test plus manually testing many features. Also including 
CreateTagsCommand that failed in previous commit.

All unit and integration tests.

Test CS Web UI with the browser going through several use cases.

Also use the CS API by sending HTTP requests generated manually including 
requests for Async Commands with Map parameters and during these tests apart 
fromtesting correct functionality I also debugged to check that Maps created 
correctly where they should but also that in the cases where the async command 
must be persisted and later on retrieved and deserialized by gson everything 
works ok and does what and where is expected. An example based on the comment 
by Alena:
http://localhost:8096/client/api?command=createTags&resourceids=ids&resourcetype=type&tags[0].key=region&tags[0].value=canada
Also other examples like
http://localhost:8096/client/api?command=createSecondaryStagingStore&url=httpbla&details[0].key=region&details[0].value=canada&details[1].key=element&details[1].value=fire


Thanks,

Antonio Fornie

Re: Review Request 17888: Dispatcher corrections, refactoring and tests. Corrects problems from previous attempt

[Antonio Fornie]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/17888/
---

(Updated March 7, 2014, 3:45 p.m.)


Review request for cloudstack, Alena Prokharchyk, daan Hoogland, and Hugo 
Trippaers.


Changes
---

Problems updating previous patch


Repository: cloudstack-git


Description
---

Dispatcher corrections, refactoring and tests. Corrects problems from previous 
attempts that were reverted by Alena. Most of the changes are the same, but 
this one is not creating conflicts of Map types for Aync Commands or for 
parameters as Lists or Maps.


Diffs (updated)
-

  api/src/org/apache/cloudstack/api/ApiConstants.java 14df653 
  api/src/org/apache/cloudstack/api/BaseCmd.java e869ddf 
  api/src/org/apache/cloudstack/api/BaseListCmd.java c1a4b4c 
  api/test/org/apache/cloudstack/api/BaseCmdTest.java PRE-CREATION 
  server/resources/META-INF/cloudstack/core/spring-server-core-misc-context.xml 
fd2f5fb 
  server/src/com/cloud/api/ApiDispatcher.java 5bdefe7 
  server/src/com/cloud/api/ApiServer.java 7e29324 
  server/src/com/cloud/api/ApiServlet.java 46f7eba 
  server/src/com/cloud/api/dispatch/CommandCreationWorker.java PRE-CREATION 
  server/src/com/cloud/api/dispatch/DispatchChain.java PRE-CREATION 
  server/src/com/cloud/api/dispatch/DispatchChainFactory.java PRE-CREATION 
  server/src/com/cloud/api/dispatch/DispatchTask.java PRE-CREATION 
  server/src/com/cloud/api/dispatch/DispatchWorker.java PRE-CREATION 
  server/src/com/cloud/api/dispatch/ParamGenericValidationWorker.java 
PRE-CREATION 
  server/src/com/cloud/api/dispatch/ParamProcessWorker.java PRE-CREATION 
  server/src/com/cloud/api/dispatch/ParamUnpackWorker.java PRE-CREATION 
  server/src/com/cloud/api/dispatch/SpecificCmdValidationWorker.java 
PRE-CREATION 
  server/src/com/cloud/network/as/AutoScaleManagerImpl.java 208b4a4 
  server/src/com/cloud/network/router/VirtualNetworkApplianceManagerImpl.java 
8486f06 
  server/src/com/cloud/storage/snapshot/SnapshotSchedulerImpl.java a85c052 
  server/test/com/cloud/api/ApiDispatcherTest.java 7314a57 
  server/test/com/cloud/api/dispatch/CommandCreationWorkerTest.java 
PRE-CREATION 
  server/test/com/cloud/api/dispatch/DispatchChainFactoryTest.java PRE-CREATION 
  server/test/com/cloud/api/dispatch/ParamGenericValidationWorkerTest.java 
PRE-CREATION 
  server/test/com/cloud/api/dispatch/ParamProcessWorkerTest.java PRE-CREATION 
  server/test/com/cloud/api/dispatch/SpecificCmdValidationWorkerTest.java 
PRE-CREATION 

Diff: https://reviews.apache.org/r/17888/diff/


Testing
---

Full build and test plus manually testing many features. Also including 
CreateTagsCommand that failed in previous commit.

All unit and integration tests.

Test CS Web UI with the browser going through several use cases.

Also use the CS API by sending HTTP requests generated manually including 
requests for Async Commands with Map parameters and during these tests apart 
fromtesting correct functionality I also debugged to check that Maps created 
correctly where they should but also that in the cases where the async command 
must be persisted and later on retrieved and deserialized by gson everything 
works ok and does what and where is expected. An example based on the comment 
by Alena:
http://localhost:8096/client/api?command=createTags&resourceids=ids&resourcetype=type&tags[0].key=region&tags[0].value=canada
Also other examples like
http://localhost:8096/client/api?command=createSecondaryStagingStore&url=httpbla&details[0].key=region&details[0].value=canada&details[1].key=element&details[1].value=fire


Thanks,

Antonio Fornie

Re: Review Request 17888: Dispatcher corrections, refactoring and tests. Corrects problems from previous attempt

[Antonio Fornie]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/17888/
---

(Updated March 7, 2014, 3:59 p.m.)


Review request for cloudstack, Alena Prokharchyk, daan Hoogland, and Hugo 
Trippaers.


Changes
---

Correct header for CommandCreationWorker


Repository: cloudstack-git


Description
---

Dispatcher corrections, refactoring and tests. Corrects problems from previous 
attempts that were reverted by Alena. Most of the changes are the same, but 
this one is not creating conflicts of Map types for Aync Commands or for 
parameters as Lists or Maps.


Diffs (updated)
-

  api/src/org/apache/cloudstack/api/ApiConstants.java 14df653 
  api/src/org/apache/cloudstack/api/BaseCmd.java e869ddf 
  api/src/org/apache/cloudstack/api/BaseListCmd.java c1a4b4c 
  api/test/org/apache/cloudstack/api/BaseCmdTest.java PRE-CREATION 
  server/resources/META-INF/cloudstack/core/spring-server-core-misc-context.xml 
fd2f5fb 
  server/src/com/cloud/api/ApiDispatcher.java 5bdefe7 
  server/src/com/cloud/api/ApiServer.java 7e29324 
  server/src/com/cloud/api/ApiServlet.java 46f7eba 
  server/src/com/cloud/api/dispatch/CommandCreationWorker.java PRE-CREATION 
  server/src/com/cloud/api/dispatch/DispatchChain.java PRE-CREATION 
  server/src/com/cloud/api/dispatch/DispatchChainFactory.java PRE-CREATION 
  server/src/com/cloud/api/dispatch/DispatchTask.java PRE-CREATION 
  server/src/com/cloud/api/dispatch/DispatchWorker.java PRE-CREATION 
  server/src/com/cloud/api/dispatch/ParamGenericValidationWorker.java 
PRE-CREATION 
  server/src/com/cloud/api/dispatch/ParamProcessWorker.java PRE-CREATION 
  server/src/com/cloud/api/dispatch/ParamUnpackWorker.java PRE-CREATION 
  server/src/com/cloud/api/dispatch/SpecificCmdValidationWorker.java 
PRE-CREATION 
  server/src/com/cloud/network/as/AutoScaleManagerImpl.java 208b4a4 
  server/src/com/cloud/network/router/VirtualNetworkApplianceManagerImpl.java 
8486f06 
  server/src/com/cloud/storage/snapshot/SnapshotSchedulerImpl.java a85c052 
  server/test/com/cloud/api/ApiDispatcherTest.java 7314a57 
  server/test/com/cloud/api/dispatch/CommandCreationWorkerTest.java 
PRE-CREATION 
  server/test/com/cloud/api/dispatch/DispatchChainFactoryTest.java PRE-CREATION 
  server/test/com/cloud/api/dispatch/ParamGenericValidationWorkerTest.java 
PRE-CREATION 
  server/test/com/cloud/api/dispatch/ParamProcessWorkerTest.java PRE-CREATION 
  server/test/com/cloud/api/dispatch/SpecificCmdValidationWorkerTest.java 
PRE-CREATION 

Diff: https://reviews.apache.org/r/17888/diff/


Testing
---

Full build and test plus manually testing many features. Also including 
CreateTagsCommand that failed in previous commit.

All unit and integration tests.

Test CS Web UI with the browser going through several use cases.

Also use the CS API by sending HTTP requests generated manually including 
requests for Async Commands with Map parameters and during these tests apart 
fromtesting correct functionality I also debugged to check that Maps created 
correctly where they should but also that in the cases where the async command 
must be persisted and later on retrieved and deserialized by gson everything 
works ok and does what and where is expected. An example based on the comment 
by Alena:
http://localhost:8096/client/api?command=createTags&resourceids=ids&resourcetype=type&tags[0].key=region&tags[0].value=canada
Also other examples like
http://localhost:8096/client/api?command=createSecondaryStagingStore&url=httpbla&details[0].key=region&details[0].value=canada&details[1].key=element&details[1].value=fire


Thanks,

Antonio Fornie

Re: Just checked in a minor change to the DB

[Daan Hoogland]

Absolutaly,

But I meant for us to use both tags. I checked in a commit (that I
didn't give a head up on) for a colleague in which a
CloudRuntimeException was removed to be more consistent with the rest
of the code. It was only effecting th upgrade process in this case but
still;
[BEHAVIORAL-CHANGE] was caused. Of course these heads-up will always
be an inter developer courtesy but here is mine (hidden in some one
elses thread;)

so in short i meant and and not or,
Daan


On Fri, Mar 7, 2014 at 4:20 PM, Mike Tutkowski
 wrote:
> I like either tag.
>
> Since DB changes are the most likely to lead to breaking other people's
> environments, maybe we should go with that one:
>
> [DB-CHANGE]
>
> Ideally we'd provide the branch, commit SHA, and a manual way around it, if
> there is something simple (like in my case yesterday, simply deleting and
> re-creating two views). If there's no easy way around it, then don't bother
> providing that.
>
> Sound reasonable?
>
>
> On Fri, Mar 7, 2014 at 2:12 AM, Daan Hoogland wrote:
>
>> Thanks for the heads up Mike,
>>
>> As discussed in your thread [1]. You are eating your own dogfood here.
>> I was checking in a minor change to the upgrade handling yesterday and
>> decided not to bother everyone with it. evil me. In that thread we
>> didn't dicide on a tag, yet.
>>
>> I would suggest
>> [DB-CHANGE] and
>> [BEHAVIORAL-CHANGE]
>>
>> [1] http://markmail.org/message/r7wv36o356nolq7f
>>
>> On Thu, Mar 6, 2014 at 9:05 PM, Mike Tutkowski
>>  wrote:
>> > Hi everyone,
>> >
>> > Just wanted to give you a heads up that I made a minor change to two
>> views
>> > in the DB in 9b66866dc2085486f465159cbd446ac03e266a2c:
>> >
>> > service_offering_view and disk_offering_view
>> >
>> > I added some columns to these views so I could present additional info in
>> > the GUI.
>> >
>> > If you want to bring these two views up to date, just run the following
>> SQL:
>> >
>> > DROP VIEW IF EXISTS `cloud`.`disk_offering_view`;
>> > CREATE VIEW `cloud`.`disk_offering_view` AS
>> > select
>> > disk_offering.id,
>> > disk_offering.uuid,
>> > disk_offering.name,
>> > disk_offering.display_text,
>> > disk_offering.disk_size,
>> > disk_offering.min_iops,
>> > disk_offering.max_iops,
>> > disk_offering.created,
>> > disk_offering.tags,
>> > disk_offering.customized,
>> > disk_offering.customized_iops,
>> > disk_offering.removed,
>> > disk_offering.use_local_storage,
>> > disk_offering.system_use,
>> > disk_offering.hv_ss_reserve,
>> > disk_offering.bytes_read_rate,
>> > disk_offering.bytes_write_rate,
>> > disk_offering.iops_read_rate,
>> > disk_offering.iops_write_rate,
>> > disk_offering.cache_mode,
>> > disk_offering.sort_key,
>> > disk_offering.type,
>> > disk_offering.display_offering,
>> > domain.id domain_id,
>> > domain.uuid domain_uuid,
>> > domain.name domain_name,
>> > domain.path domain_path
>> > from
>> > `cloud`.`disk_offering`
>> > left join
>> > `cloud`.`domain` ON disk_offering.domain_id = domain.id
>> > where
>> > disk_offering.state='ACTIVE';
>> >
>> > DROP VIEW IF EXISTS `cloud`.`service_offering_view`;
>> > CREATE VIEW `cloud`.`service_offering_view` AS
>> > select
>> > service_offering.id,
>> > disk_offering.uuid,
>> > disk_offering.name,
>> > disk_offering.display_text,
>> > disk_offering.created,
>> > disk_offering.tags,
>> > disk_offering.removed,
>> > disk_offering.use_local_storage,
>> > disk_offering.system_use,
>> > disk_offering.customized_iops,
>> > disk_offering.min_iops,
>> > disk_offering.max_iops,
>> > disk_offering.hv_ss_reserve,
>> > disk_offering.bytes_read_rate,
>> > disk_offering.bytes_write_rate,
>> > disk_offering.iops_read_rate,
>> > disk_offering.iops_write_rate,
>> > disk_offering.cache_mode,
>> > service_offering.cpu,
>> > service_offering.speed,
>> > service_offering.ram_size,
>> > service_offering.nw_rate,
>> > service_offering.mc_rate,
>> > service_offering.ha_enabled,
>> > service_offering.limit_cpu_use,
>> > service_offering.host_tag,
>> > service_offering.default_use,
>> > service_offering.vm_type,
>> > service_offering.sort_key,
>> > service_offering.is_volatile,
>> > service_offering.deployment_planner,
>> > domain.id domain_id,
>> > domain.uuid domain_uuid,
>> > domain.name domain_name,
>> > domain.path domain_path
>> > from
>> > `cloud`.`service_offering`
>> > inner join
>> > `cloud`.`disk_offering` ON service_offering.id =
>> disk_offering.id
>> > left join
>> >

Re: 4.3 vote

[John Kinsella]

I have a review request sitting at https://reviews.apache.org/r/18392/ - that 
works for me but I don’t know if it’s breaking AWSAPI functionality. Would love 
it if somebody more familiar with that module could test. I’d rather not just 
check that in and see what happens.

Animesh, I know you put a ton of work into these RCs and I hate holding you up, 
but here’s my train of thought: packaging/centos63/package.sh is broken because 
one of the RPMs it attempts to build is for awsapi. No self-respecting 
enterprise (I hope, dream) is going to drop non-packaged (deb, rpm, whatever) 
code on production systems. So if that packaging ability is broken, there’s a 
good chance enterprises can’t use the new code.

Just got an idea to see if Apache’s Sonatype has a valid mirror, and it does, 
at least for some[1]. So I’ll go down that path this AM as well, in case my 
patch above doesn’t work.

John
1: https://repository.apache.org/index.html#nexus-search;quick~mex

On Mar 6, 2014, at 11:04 PM, Animesh Chaturvedi  
wrote:

> Ok so how do we get past this? This should have been pre-existing as 
> dependency has been broken for a long time and I am not sure if this should 
> block our next RC.
> 
>> -Original Message-
>> From: John Kinsella [mailto:j...@stratosec.co]
>> Sent: Thursday, March 06, 2014 4:14 PM
>> To: dev@cloudstack.apache.org
>> Subject: Re: 4.3 vote
>> 
>> David was seeing this as well. This is is a documented problem at
>> https://issues.apache.org/jira/browse/RAMPART-393.
>> 
>> I just spun up a VM at AWS using a 64 bit amazon linux api. Ran the
>> commands below, got same errors:
>> 
>>1  sudo yum update
>>2  yum install git java-1.7.0-openjdk-devel
>>3  git clone https://git-wip-us.apache.org/repos/asf/cloudstack.git
>>4  wget http://www.dsgnwrld.com/am/maven/maven-
>> 3/3.2.1/binaries/apache-maven-3.2.1-bin.tar.gz
>>5  tar xvf apache-maven-3.2.1-bin.tar.gz
>>6  export PATH=$PATH:~/apache-maven-3.2.1/bin/
>>7  cd cloudstack/
>>8  mvn -P deps
>>9  mvn clean install -Pawsapi
>> 
>> I suspect the Citrix devs are sitting behind Nexus or other maven mirror?
>> 
>> John
>> 
>> On Mar 6, 2014, at 3:13 PM, Animesh Chaturvedi
>> mailto:animesh.chaturv...@citrix.com>>
>> wrote:
>> 
>> Folks anyone else seeing this? I want to build RC soon and wanted to
>> confirm if this is an issue or not and if so if we can get a fix right away
>> 
>> -Original Message-
>> From: Prachi Damle [mailto:prachi.da...@citrix.com]
>> Sent: Thursday, March 06, 2014 1:20 PM
>> To: dev@cloudstack.apache.org
>> Subject: RE: 4.3 vote
>> 
>> John,
>> 
>> I could not reproduce this broken build on 4.3 after wiping out my entire
>> repository.
>> 1.  rm -rf ~/.m2/repository
>> 2. mvn clean install -Pawsapi
>> 
>> My build is successful.
>> 
>> Can someone who is able to reproduce this check this further?
>> 
>> Prachi
>> 
>> 
>> [INFO] 
>> 
>> [INFO] Reactor Summary:
>> [INFO]
>> [INFO] Apache CloudStack . SUCCESS 
>> [1:53.957s] [INFO]
>> Apache CloudStack Maven Conventions Parent  SUCCESS [0.089s] [INFO]
>> Apache CloudStack Framework - Managed Context . SUCCESS [28.189s]
>> [INFO] Apache CloudStack Utils ... SUCCESS 
>> [1:06.368s] [INFO]
>> Apache CloudStack Framework ... SUCCESS [0.303s] [INFO]
>> Apache CloudStack Framework - Event Notification .. SUCCESS [27.125s]
>> [INFO] Apache CloudStack Framework - Configuration ... SUCCESS [5.878s]
>> [INFO] Apache CloudStack API . SUCCESS [55.346s] 
>> [INFO]
>> Apache CloudStack Framework - REST  SUCCESS [16.891s] [INFO]
>> Apache CloudStack Framework - IPC . SUCCESS [11.845s] [INFO]
>> Apache CloudStack Cloud Engine  SUCCESS [0.072s] [INFO]
>> Apache CloudStack Cloud Engine API  SUCCESS [10.641s] [INFO]
>> Apache CloudStack Core  SUCCESS [30.300s] [INFO] 
>> Apache
>> CloudStack Agents .. SUCCESS [22.533s] [INFO] Apache
>> CloudStack Framework - Clustering .. SUCCESS [8.801s] [INFO] Apache
>> CloudStack Framework - Jobs  SUCCESS [9.251s] [INFO] Apache
>> CloudStack Cloud Engine Schema Component ... SUCCESS [39.764s] [INFO]
>> Apache CloudStack Framework - Event Notification .. SUCCESS [2.761s] [INFO]
>> Apache CloudStack Cloud Engine Internal Components API  SUCCESS [6.014s]
>> [INFO] Apache CloudStack Server .. SUCCESS 
>> [1:23.722s] [INFO]
>> Apache CloudStack Usage Server  SUCCESS [9.872s] [INFO]
>> Apache XenSource XAPI . SUCCESS [17.003s] [INFO] 
>> Apache
>> CloudStack Cloud Engine Orchestration Component  SUCCESS [16.774s]
>> 
>> [INFO] Apache CloudStack Cloud Services .. SUCCES

RE: Just checked in a minor change to the DB

[Rajesh Battala]

That's really great idea. In fact long back I had started a similar thread to 
inform any schema changes so that ppl can changed the schema manually without 
disturbing the setups. 
It would be great if all of us follow with [DB-CHANGE] subject  tag.

Thanks
Rajesh Battala

-Original Message-
From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] 
Sent: Friday, March 7, 2014 8:50 PM
To: dev@cloudstack.apache.org
Subject: Re: Just checked in a minor change to the DB

I like either tag.

Since DB changes are the most likely to lead to breaking other people's 
environments, maybe we should go with that one:

[DB-CHANGE]

Ideally we'd provide the branch, commit SHA, and a manual way around it, if 
there is something simple (like in my case yesterday, simply deleting and 
re-creating two views). If there's no easy way around it, then don't bother 
providing that.

Sound reasonable?


On Fri, Mar 7, 2014 at 2:12 AM, Daan Hoogland wrote:

> Thanks for the heads up Mike,
>
> As discussed in your thread [1]. You are eating your own dogfood here.
> I was checking in a minor change to the upgrade handling yesterday and 
> decided not to bother everyone with it. evil me. In that thread we 
> didn't dicide on a tag, yet.
>
> I would suggest
> [DB-CHANGE] and
> [BEHAVIORAL-CHANGE]
>
> [1] http://markmail.org/message/r7wv36o356nolq7f
>
> On Thu, Mar 6, 2014 at 9:05 PM, Mike Tutkowski 
>  wrote:
> > Hi everyone,
> >
> > Just wanted to give you a heads up that I made a minor change to two
> views
> > in the DB in 9b66866dc2085486f465159cbd446ac03e266a2c:
> >
> > service_offering_view and disk_offering_view
> >
> > I added some columns to these views so I could present additional 
> > info in the GUI.
> >
> > If you want to bring these two views up to date, just run the 
> > following
> SQL:
> >
> > DROP VIEW IF EXISTS `cloud`.`disk_offering_view`; CREATE VIEW 
> > `cloud`.`disk_offering_view` AS
> > select
> > disk_offering.id,
> > disk_offering.uuid,
> > disk_offering.name,
> > disk_offering.display_text,
> > disk_offering.disk_size,
> > disk_offering.min_iops,
> > disk_offering.max_iops,
> > disk_offering.created,
> > disk_offering.tags,
> > disk_offering.customized,
> > disk_offering.customized_iops,
> > disk_offering.removed,
> > disk_offering.use_local_storage,
> > disk_offering.system_use,
> > disk_offering.hv_ss_reserve,
> > disk_offering.bytes_read_rate,
> > disk_offering.bytes_write_rate,
> > disk_offering.iops_read_rate,
> > disk_offering.iops_write_rate,
> > disk_offering.cache_mode,
> > disk_offering.sort_key,
> > disk_offering.type,
> > disk_offering.display_offering,
> > domain.id domain_id,
> > domain.uuid domain_uuid,
> > domain.name domain_name,
> > domain.path domain_path
> > from
> > `cloud`.`disk_offering`
> > left join
> > `cloud`.`domain` ON disk_offering.domain_id = domain.id
> > where
> > disk_offering.state='ACTIVE';
> >
> > DROP VIEW IF EXISTS `cloud`.`service_offering_view`; CREATE VIEW 
> > `cloud`.`service_offering_view` AS
> > select
> > service_offering.id,
> > disk_offering.uuid,
> > disk_offering.name,
> > disk_offering.display_text,
> > disk_offering.created,
> > disk_offering.tags,
> > disk_offering.removed,
> > disk_offering.use_local_storage,
> > disk_offering.system_use,
> > disk_offering.customized_iops,
> > disk_offering.min_iops,
> > disk_offering.max_iops,
> > disk_offering.hv_ss_reserve,
> > disk_offering.bytes_read_rate,
> > disk_offering.bytes_write_rate,
> > disk_offering.iops_read_rate,
> > disk_offering.iops_write_rate,
> > disk_offering.cache_mode,
> > service_offering.cpu,
> > service_offering.speed,
> > service_offering.ram_size,
> > service_offering.nw_rate,
> > service_offering.mc_rate,
> > service_offering.ha_enabled,
> > service_offering.limit_cpu_use,
> > service_offering.host_tag,
> > service_offering.default_use,
> > service_offering.vm_type,
> > service_offering.sort_key,
> > service_offering.is_volatile,
> > service_offering.deployment_planner,
> > domain.id domain_id,
> > domain.uuid domain_uuid,
> > domain.name domain_name,
> > domain.path domain_path
> > from
> > `cloud`.`service_offering`
> > inner join
> > `cloud`.`disk_offering` ON service_offering.id =
> disk_offering.id
> > left join
> > `cloud`.`domain` ON disk_offering.domain_id = domain.id
> > where
> > disk_offering.state='Active';
> >
> > Thanks!
> >
> > --
> > *Mike Tutkowski*
> > *Senior

Re: Review Request 18894: CLOUDSTACK-6210 LDAP:listLdapUsers api throws exception when we click on "Add LDAP Account"

[Ian Duffy]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/18894/#review36534
---

Ship it!


Ship It!

- Ian Duffy


On March 7, 2014, 6:10 a.m., Rajani Karuturi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/18894/
> ---
> 
> (Updated March 7, 2014, 6:10 a.m.)
> 
> 
> Review request for cloudstack, Abhinandan Prateek and Ian Duffy.
> 
> 
> Bugs: CLOUDSTACK-6210
> https://issues.apache.org/jira/browse/CLOUDSTACK-6210
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> This occurs when ldap basedn is not configured.
> Throwing an IAE and a proper message is returned from the api call
> 
> The api call response earlier was
> { "ldapuserresponse" : {"uuidList":[],"errorcode":530,"cserrorcode":} }
> now it is as follows
> { "ldapuserresponse" : 
> {"uuidList":[],"errorcode":431,"cserrorcode":,"errortext":"ldap basedn is 
> not configured"} }
> 
> 
> Diffs
> -
> 
>   
> plugins/user-authenticators/ldap/src/org/apache/cloudstack/ldap/LdapUserManager.java
>  2dacafe 
>   
> plugins/user-authenticators/ldap/test/groovy/org/apache/cloudstack/ldap/LdapUserManagerSpec.groovy
>  fa735d3 
> 
> Diff: https://reviews.apache.org/r/18894/diff/
> 
> 
> Testing
> ---
> 
> unittested by adding a new test case "test searchUsers when ldap basedn in 
> not set" in LdapUserManagerSpec.groovy which reproduces this case 
> 
> manually tested the api call as well
> 
> 
> Thanks,
> 
> Rajani Karuturi
> 
>

Re: Review Request 18894: CLOUDSTACK-6210 LDAP:listLdapUsers api throws exception when we click on "Add LDAP Account"

[ASF Subversion and Git Services]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/18894/#review36535
---


Commit 4552ec632201e7432afae7770f5854aaa244267c in cloudstack's branch 
refs/heads/master from Rajani Karuturi
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4552ec6 ]

Fixed CLOUDSTACK-6210 LDAP:listLdapUsers api throws exception when we click on 
"Add LDAP Account" This occurs when ldap basedn is not configured. Throwing an 
IAE and a proper message is returned from the api call

Signed-off-by: Ian Duffy 


- ASF Subversion and Git Services


On March 7, 2014, 6:10 a.m., Rajani Karuturi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/18894/
> ---
> 
> (Updated March 7, 2014, 6:10 a.m.)
> 
> 
> Review request for cloudstack, Abhinandan Prateek and Ian Duffy.
> 
> 
> Bugs: CLOUDSTACK-6210
> https://issues.apache.org/jira/browse/CLOUDSTACK-6210
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> This occurs when ldap basedn is not configured.
> Throwing an IAE and a proper message is returned from the api call
> 
> The api call response earlier was
> { "ldapuserresponse" : {"uuidList":[],"errorcode":530,"cserrorcode":} }
> now it is as follows
> { "ldapuserresponse" : 
> {"uuidList":[],"errorcode":431,"cserrorcode":,"errortext":"ldap basedn is 
> not configured"} }
> 
> 
> Diffs
> -
> 
>   
> plugins/user-authenticators/ldap/src/org/apache/cloudstack/ldap/LdapUserManager.java
>  2dacafe 
>   
> plugins/user-authenticators/ldap/test/groovy/org/apache/cloudstack/ldap/LdapUserManagerSpec.groovy
>  fa735d3 
> 
> Diff: https://reviews.apache.org/r/18894/diff/
> 
> 
> Testing
> ---
> 
> unittested by adding a new test case "test searchUsers when ldap basedn in 
> not set" in LdapUserManagerSpec.groovy which reproduces this case 
> 
> manually tested the api call as well
> 
> 
> Thanks,
> 
> Rajani Karuturi
> 
>

devcloud2 java

[Marcus]

Hi guys,
   Trying to get back into the Xen devcloud for a few things, and
following the instructions it seems that the existing devcloud2 is
missing java 7. Do our docs point to an old image, or are we just
installing that manually?

Re: Just checked in a minor change to the DB

[Mike Tutkowski]

That sounds good, Daan.

Let's use both tags.

Thanks!


On Fri, Mar 7, 2014 at 9:33 AM, Daan Hoogland wrote:

> Absolutaly,
>
> But I meant for us to use both tags. I checked in a commit (that I
> didn't give a head up on) for a colleague in which a
> CloudRuntimeException was removed to be more consistent with the rest
> of the code. It was only effecting th upgrade process in this case but
> still;
> [BEHAVIORAL-CHANGE] was caused. Of course these heads-up will always
> be an inter developer courtesy but here is mine (hidden in some one
> elses thread;)
>
> so in short i meant and and not or,
> Daan
>
>
> On Fri, Mar 7, 2014 at 4:20 PM, Mike Tutkowski
>  wrote:
> > I like either tag.
> >
> > Since DB changes are the most likely to lead to breaking other people's
> > environments, maybe we should go with that one:
> >
> > [DB-CHANGE]
> >
> > Ideally we'd provide the branch, commit SHA, and a manual way around it,
> if
> > there is something simple (like in my case yesterday, simply deleting and
> > re-creating two views). If there's no easy way around it, then don't
> bother
> > providing that.
> >
> > Sound reasonable?
> >
> >
> > On Fri, Mar 7, 2014 at 2:12 AM, Daan Hoogland  >wrote:
> >
> >> Thanks for the heads up Mike,
> >>
> >> As discussed in your thread [1]. You are eating your own dogfood here.
> >> I was checking in a minor change to the upgrade handling yesterday and
> >> decided not to bother everyone with it. evil me. In that thread we
> >> didn't dicide on a tag, yet.
> >>
> >> I would suggest
> >> [DB-CHANGE] and
> >> [BEHAVIORAL-CHANGE]
> >>
> >> [1] http://markmail.org/message/r7wv36o356nolq7f
> >>
> >> On Thu, Mar 6, 2014 at 9:05 PM, Mike Tutkowski
> >>  wrote:
> >> > Hi everyone,
> >> >
> >> > Just wanted to give you a heads up that I made a minor change to two
> >> views
> >> > in the DB in 9b66866dc2085486f465159cbd446ac03e266a2c:
> >> >
> >> > service_offering_view and disk_offering_view
> >> >
> >> > I added some columns to these views so I could present additional
> info in
> >> > the GUI.
> >> >
> >> > If you want to bring these two views up to date, just run the
> following
> >> SQL:
> >> >
> >> > DROP VIEW IF EXISTS `cloud`.`disk_offering_view`;
> >> > CREATE VIEW `cloud`.`disk_offering_view` AS
> >> > select
> >> > disk_offering.id,
> >> > disk_offering.uuid,
> >> > disk_offering.name,
> >> > disk_offering.display_text,
> >> > disk_offering.disk_size,
> >> > disk_offering.min_iops,
> >> > disk_offering.max_iops,
> >> > disk_offering.created,
> >> > disk_offering.tags,
> >> > disk_offering.customized,
> >> > disk_offering.customized_iops,
> >> > disk_offering.removed,
> >> > disk_offering.use_local_storage,
> >> > disk_offering.system_use,
> >> > disk_offering.hv_ss_reserve,
> >> > disk_offering.bytes_read_rate,
> >> > disk_offering.bytes_write_rate,
> >> > disk_offering.iops_read_rate,
> >> > disk_offering.iops_write_rate,
> >> > disk_offering.cache_mode,
> >> > disk_offering.sort_key,
> >> > disk_offering.type,
> >> > disk_offering.display_offering,
> >> > domain.id domain_id,
> >> > domain.uuid domain_uuid,
> >> > domain.name domain_name,
> >> > domain.path domain_path
> >> > from
> >> > `cloud`.`disk_offering`
> >> > left join
> >> > `cloud`.`domain` ON disk_offering.domain_id = domain.id
> >> > where
> >> > disk_offering.state='ACTIVE';
> >> >
> >> > DROP VIEW IF EXISTS `cloud`.`service_offering_view`;
> >> > CREATE VIEW `cloud`.`service_offering_view` AS
> >> > select
> >> > service_offering.id,
> >> > disk_offering.uuid,
> >> > disk_offering.name,
> >> > disk_offering.display_text,
> >> > disk_offering.created,
> >> > disk_offering.tags,
> >> > disk_offering.removed,
> >> > disk_offering.use_local_storage,
> >> > disk_offering.system_use,
> >> > disk_offering.customized_iops,
> >> > disk_offering.min_iops,
> >> > disk_offering.max_iops,
> >> > disk_offering.hv_ss_reserve,
> >> > disk_offering.bytes_read_rate,
> >> > disk_offering.bytes_write_rate,
> >> > disk_offering.iops_read_rate,
> >> > disk_offering.iops_write_rate,
> >> > disk_offering.cache_mode,
> >> > service_offering.cpu,
> >> > service_offering.speed,
> >> > service_offering.ram_size,
> >> > service_offering.nw_rate,
> >> > service_offering.mc_rate,
> >> > service_offering.ha_enabled,
> >> > service_offering.limit_cpu_use,
> >> > service_offering.host_tag,
> >> > service_offering.default_use,
> >> > service_offering.vm_type,
> >> > service_offering.sort_key,
> >> > service_offering.is_volatile,
> >> > se

Re: Just checked in a minor change to the DB

[Mike Tutkowski]

Does anyone know if our e-mail tags are documented on the Wiki?


On Fri, Mar 7, 2014 at 11:36 AM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> That sounds good, Daan.
>
> Let's use both tags.
>
> Thanks!
>
>
> On Fri, Mar 7, 2014 at 9:33 AM, Daan Hoogland wrote:
>
>> Absolutaly,
>>
>> But I meant for us to use both tags. I checked in a commit (that I
>> didn't give a head up on) for a colleague in which a
>> CloudRuntimeException was removed to be more consistent with the rest
>> of the code. It was only effecting th upgrade process in this case but
>> still;
>> [BEHAVIORAL-CHANGE] was caused. Of course these heads-up will always
>> be an inter developer courtesy but here is mine (hidden in some one
>> elses thread;)
>>
>> so in short i meant and and not or,
>> Daan
>>
>>
>> On Fri, Mar 7, 2014 at 4:20 PM, Mike Tutkowski
>>  wrote:
>> > I like either tag.
>> >
>> > Since DB changes are the most likely to lead to breaking other people's
>> > environments, maybe we should go with that one:
>> >
>> > [DB-CHANGE]
>> >
>> > Ideally we'd provide the branch, commit SHA, and a manual way around
>> it, if
>> > there is something simple (like in my case yesterday, simply deleting
>> and
>> > re-creating two views). If there's no easy way around it, then don't
>> bother
>> > providing that.
>> >
>> > Sound reasonable?
>> >
>> >
>> > On Fri, Mar 7, 2014 at 2:12 AM, Daan Hoogland > >wrote:
>> >
>> >> Thanks for the heads up Mike,
>> >>
>> >> As discussed in your thread [1]. You are eating your own dogfood here.
>> >> I was checking in a minor change to the upgrade handling yesterday and
>> >> decided not to bother everyone with it. evil me. In that thread we
>> >> didn't dicide on a tag, yet.
>> >>
>> >> I would suggest
>> >> [DB-CHANGE] and
>> >> [BEHAVIORAL-CHANGE]
>> >>
>> >> [1] http://markmail.org/message/r7wv36o356nolq7f
>> >>
>> >> On Thu, Mar 6, 2014 at 9:05 PM, Mike Tutkowski
>> >>  wrote:
>> >> > Hi everyone,
>> >> >
>> >> > Just wanted to give you a heads up that I made a minor change to two
>> >> views
>> >> > in the DB in 9b66866dc2085486f465159cbd446ac03e266a2c:
>> >> >
>> >> > service_offering_view and disk_offering_view
>> >> >
>> >> > I added some columns to these views so I could present additional
>> info in
>> >> > the GUI.
>> >> >
>> >> > If you want to bring these two views up to date, just run the
>> following
>> >> SQL:
>> >> >
>> >> > DROP VIEW IF EXISTS `cloud`.`disk_offering_view`;
>> >> > CREATE VIEW `cloud`.`disk_offering_view` AS
>> >> > select
>> >> > disk_offering.id,
>> >> > disk_offering.uuid,
>> >> > disk_offering.name,
>> >> > disk_offering.display_text,
>> >> > disk_offering.disk_size,
>> >> > disk_offering.min_iops,
>> >> > disk_offering.max_iops,
>> >> > disk_offering.created,
>> >> > disk_offering.tags,
>> >> > disk_offering.customized,
>> >> > disk_offering.customized_iops,
>> >> > disk_offering.removed,
>> >> > disk_offering.use_local_storage,
>> >> > disk_offering.system_use,
>> >> > disk_offering.hv_ss_reserve,
>> >> > disk_offering.bytes_read_rate,
>> >> > disk_offering.bytes_write_rate,
>> >> > disk_offering.iops_read_rate,
>> >> > disk_offering.iops_write_rate,
>> >> > disk_offering.cache_mode,
>> >> > disk_offering.sort_key,
>> >> > disk_offering.type,
>> >> > disk_offering.display_offering,
>> >> > domain.id domain_id,
>> >> > domain.uuid domain_uuid,
>> >> > domain.name domain_name,
>> >> > domain.path domain_path
>> >> > from
>> >> > `cloud`.`disk_offering`
>> >> > left join
>> >> > `cloud`.`domain` ON disk_offering.domain_id = domain.id
>> >> > where
>> >> > disk_offering.state='ACTIVE';
>> >> >
>> >> > DROP VIEW IF EXISTS `cloud`.`service_offering_view`;
>> >> > CREATE VIEW `cloud`.`service_offering_view` AS
>> >> > select
>> >> > service_offering.id,
>> >> > disk_offering.uuid,
>> >> > disk_offering.name,
>> >> > disk_offering.display_text,
>> >> > disk_offering.created,
>> >> > disk_offering.tags,
>> >> > disk_offering.removed,
>> >> > disk_offering.use_local_storage,
>> >> > disk_offering.system_use,
>> >> > disk_offering.customized_iops,
>> >> > disk_offering.min_iops,
>> >> > disk_offering.max_iops,
>> >> > disk_offering.hv_ss_reserve,
>> >> > disk_offering.bytes_read_rate,
>> >> > disk_offering.bytes_write_rate,
>> >> > disk_offering.iops_read_rate,
>> >> > disk_offering.iops_write_rate,
>> >> > disk_offering.cache_mode,
>> >> > service_offering.cpu,
>> >> > service_offering.speed,
>> >> > service_offering.ram_size,
>> >> > service_offering.nw_rate,
>> >> > service_offering.mc_rate,
>> >> > servic

Re: devcloud2 java

[Marcus]

I manually installed java 7, but I'm beginning to think I've got the
wrong version of devcloud, as I can't add the host.

Caused by: java.io.IOException: Error during SCP transfer.
at com.trilead.ssh2.SCPClient.put(SCPClient.java:592)
at com.trilead.ssh2.SCPClient.put(SCPClient.java:547)
at com.trilead.ssh2.SCPClient.put(SCPClient.java:434)
at 
com.cloud.hypervisor.xen.resource.CitrixResourceBase.setupServer(CitrixResourceBase.java:4766)
... 17 more
Caused by: java.io.IOException: Remote scp terminated with error (scp:
/etc/xensource: No such file or directory).
at com.trilead.ssh2.SCPClient.readResponse(SCPClient.java:59)
at com.trilead.ssh2.SCPClient.sendFiles(SCPClient.java:166)
at com.trilead.ssh2.SCPClient.put(SCPClient.java:588)
... 20 more



On Fri, Mar 7, 2014 at 10:54 AM, Marcus  wrote:
> Hi guys,
>Trying to get back into the Xen devcloud for a few things, and
> following the instructions it seems that the existing devcloud2 is
> missing java 7. Do our docs point to an old image, or are we just
> installing that manually?

Re: Review Request 16385: Fix for CloudStack JIRA 4406

[Daan Hoogland]

On Fri, Mar 7, 2014 at 7:31 PM, Alena Prokharchyk
 wrote:
> And the defaults should be false,


I don't agree, The true case does nothing if no fields are recognized
as sensitive, but it the flase case skips sensitive data containing
log messages. The only consquence of true as default is a performance
penalty that we were paying in the old case anyhow.

-- 
Daan

Re: Just checked in a minor change to the DB

[Daan Hoogland]

No, but I do know that it might be useful to use them in commit
comments as well. If you so feel inclined you can refer to that as
well

On Fri, Mar 7, 2014 at 7:41 PM, Mike Tutkowski
 wrote:
> Does anyone know if our e-mail tags are documented on the Wiki?
>
>
> On Fri, Mar 7, 2014 at 11:36 AM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
>> That sounds good, Daan.
>>
>> Let's use both tags.
>>
>> Thanks!
>>
>>
>> On Fri, Mar 7, 2014 at 9:33 AM, Daan Hoogland wrote:
>>
>>> Absolutaly,
>>>
>>> But I meant for us to use both tags. I checked in a commit (that I
>>> didn't give a head up on) for a colleague in which a
>>> CloudRuntimeException was removed to be more consistent with the rest
>>> of the code. It was only effecting th upgrade process in this case but
>>> still;
>>> [BEHAVIORAL-CHANGE] was caused. Of course these heads-up will always
>>> be an inter developer courtesy but here is mine (hidden in some one
>>> elses thread;)
>>>
>>> so in short i meant and and not or,
>>> Daan
>>>
>>>
>>> On Fri, Mar 7, 2014 at 4:20 PM, Mike Tutkowski
>>>  wrote:
>>> > I like either tag.
>>> >
>>> > Since DB changes are the most likely to lead to breaking other people's
>>> > environments, maybe we should go with that one:
>>> >
>>> > [DB-CHANGE]
>>> >
>>> > Ideally we'd provide the branch, commit SHA, and a manual way around
>>> it, if
>>> > there is something simple (like in my case yesterday, simply deleting
>>> and
>>> > re-creating two views). If there's no easy way around it, then don't
>>> bother
>>> > providing that.
>>> >
>>> > Sound reasonable?
>>> >
>>> >
>>> > On Fri, Mar 7, 2014 at 2:12 AM, Daan Hoogland >> >wrote:
>>> >
>>> >> Thanks for the heads up Mike,
>>> >>
>>> >> As discussed in your thread [1]. You are eating your own dogfood here.
>>> >> I was checking in a minor change to the upgrade handling yesterday and
>>> >> decided not to bother everyone with it. evil me. In that thread we
>>> >> didn't dicide on a tag, yet.
>>> >>
>>> >> I would suggest
>>> >> [DB-CHANGE] and
>>> >> [BEHAVIORAL-CHANGE]
>>> >>
>>> >> [1] http://markmail.org/message/r7wv36o356nolq7f
>>> >>
>>> >> On Thu, Mar 6, 2014 at 9:05 PM, Mike Tutkowski
>>> >>  wrote:
>>> >> > Hi everyone,
>>> >> >
>>> >> > Just wanted to give you a heads up that I made a minor change to two
>>> >> views
>>> >> > in the DB in 9b66866dc2085486f465159cbd446ac03e266a2c:
>>> >> >
>>> >> > service_offering_view and disk_offering_view
>>> >> >
>>> >> > I added some columns to these views so I could present additional
>>> info in
>>> >> > the GUI.
>>> >> >
>>> >> > If you want to bring these two views up to date, just run the
>>> following
>>> >> SQL:
>>> >> >
>>> >> > DROP VIEW IF EXISTS `cloud`.`disk_offering_view`;
>>> >> > CREATE VIEW `cloud`.`disk_offering_view` AS
>>> >> > select
>>> >> > disk_offering.id,
>>> >> > disk_offering.uuid,
>>> >> > disk_offering.name,
>>> >> > disk_offering.display_text,
>>> >> > disk_offering.disk_size,
>>> >> > disk_offering.min_iops,
>>> >> > disk_offering.max_iops,
>>> >> > disk_offering.created,
>>> >> > disk_offering.tags,
>>> >> > disk_offering.customized,
>>> >> > disk_offering.customized_iops,
>>> >> > disk_offering.removed,
>>> >> > disk_offering.use_local_storage,
>>> >> > disk_offering.system_use,
>>> >> > disk_offering.hv_ss_reserve,
>>> >> > disk_offering.bytes_read_rate,
>>> >> > disk_offering.bytes_write_rate,
>>> >> > disk_offering.iops_read_rate,
>>> >> > disk_offering.iops_write_rate,
>>> >> > disk_offering.cache_mode,
>>> >> > disk_offering.sort_key,
>>> >> > disk_offering.type,
>>> >> > disk_offering.display_offering,
>>> >> > domain.id domain_id,
>>> >> > domain.uuid domain_uuid,
>>> >> > domain.name domain_name,
>>> >> > domain.path domain_path
>>> >> > from
>>> >> > `cloud`.`disk_offering`
>>> >> > left join
>>> >> > `cloud`.`domain` ON disk_offering.domain_id = domain.id
>>> >> > where
>>> >> > disk_offering.state='ACTIVE';
>>> >> >
>>> >> > DROP VIEW IF EXISTS `cloud`.`service_offering_view`;
>>> >> > CREATE VIEW `cloud`.`service_offering_view` AS
>>> >> > select
>>> >> > service_offering.id,
>>> >> > disk_offering.uuid,
>>> >> > disk_offering.name,
>>> >> > disk_offering.display_text,
>>> >> > disk_offering.created,
>>> >> > disk_offering.tags,
>>> >> > disk_offering.removed,
>>> >> > disk_offering.use_local_storage,
>>> >> > disk_offering.system_use,
>>> >> > disk_offering.customized_iops,
>>> >> > disk_offering.min_iops,
>>> >> > disk_offering.max_iops,
>>> >> > disk_offering.hv_ss_reserve,
>>> >> > disk_offering.bytes_read_rate,
>>> >> > disk_offering.bytes_write_rate,
>>> >> > disk_offeri

Re: Just checked in a minor change to the DB

[Daan Hoogland]

I had a quick look. Nothing found but a lot of hits on tags of course.
I'll try to find a place to create the page and start chapters on Dev
and Users


On Fri, Mar 7, 2014 at 7:54 PM, Daan Hoogland  wrote:
> No, but I do know that it might be useful to use them in commit
> comments as well. If you so feel inclined you can refer to that as
> well
>
> On Fri, Mar 7, 2014 at 7:41 PM, Mike Tutkowski
>  wrote:
>> Does anyone know if our e-mail tags are documented on the Wiki?
>>
>>
>> On Fri, Mar 7, 2014 at 11:36 AM, Mike Tutkowski <
>> mike.tutkow...@solidfire.com> wrote:
>>
>>> That sounds good, Daan.
>>>
>>> Let's use both tags.
>>>
>>> Thanks!
>>>
>>>
>>> On Fri, Mar 7, 2014 at 9:33 AM, Daan Hoogland 
>>> wrote:
>>>
 Absolutaly,

 But I meant for us to use both tags. I checked in a commit (that I
 didn't give a head up on) for a colleague in which a
 CloudRuntimeException was removed to be more consistent with the rest
 of the code. It was only effecting th upgrade process in this case but
 still;
 [BEHAVIORAL-CHANGE] was caused. Of course these heads-up will always
 be an inter developer courtesy but here is mine (hidden in some one
 elses thread;)

 so in short i meant and and not or,
 Daan


 On Fri, Mar 7, 2014 at 4:20 PM, Mike Tutkowski
  wrote:
 > I like either tag.
 >
 > Since DB changes are the most likely to lead to breaking other people's
 > environments, maybe we should go with that one:
 >
 > [DB-CHANGE]
 >
 > Ideally we'd provide the branch, commit SHA, and a manual way around
 it, if
 > there is something simple (like in my case yesterday, simply deleting
 and
 > re-creating two views). If there's no easy way around it, then don't
 bother
 > providing that.
 >
 > Sound reasonable?
 >
 >
 > On Fri, Mar 7, 2014 at 2:12 AM, Daan Hoogland >>> >wrote:
 >
 >> Thanks for the heads up Mike,
 >>
 >> As discussed in your thread [1]. You are eating your own dogfood here.
 >> I was checking in a minor change to the upgrade handling yesterday and
 >> decided not to bother everyone with it. evil me. In that thread we
 >> didn't dicide on a tag, yet.
 >>
 >> I would suggest
 >> [DB-CHANGE] and
 >> [BEHAVIORAL-CHANGE]
 >>
 >> [1] http://markmail.org/message/r7wv36o356nolq7f
 >>
 >> On Thu, Mar 6, 2014 at 9:05 PM, Mike Tutkowski
 >>  wrote:
 >> > Hi everyone,
 >> >
 >> > Just wanted to give you a heads up that I made a minor change to two
 >> views
 >> > in the DB in 9b66866dc2085486f465159cbd446ac03e266a2c:
 >> >
 >> > service_offering_view and disk_offering_view
 >> >
 >> > I added some columns to these views so I could present additional
 info in
 >> > the GUI.
 >> >
 >> > If you want to bring these two views up to date, just run the
 following
 >> SQL:
 >> >
 >> > DROP VIEW IF EXISTS `cloud`.`disk_offering_view`;
 >> > CREATE VIEW `cloud`.`disk_offering_view` AS
 >> > select
 >> > disk_offering.id,
 >> > disk_offering.uuid,
 >> > disk_offering.name,
 >> > disk_offering.display_text,
 >> > disk_offering.disk_size,
 >> > disk_offering.min_iops,
 >> > disk_offering.max_iops,
 >> > disk_offering.created,
 >> > disk_offering.tags,
 >> > disk_offering.customized,
 >> > disk_offering.customized_iops,
 >> > disk_offering.removed,
 >> > disk_offering.use_local_storage,
 >> > disk_offering.system_use,
 >> > disk_offering.hv_ss_reserve,
 >> > disk_offering.bytes_read_rate,
 >> > disk_offering.bytes_write_rate,
 >> > disk_offering.iops_read_rate,
 >> > disk_offering.iops_write_rate,
 >> > disk_offering.cache_mode,
 >> > disk_offering.sort_key,
 >> > disk_offering.type,
 >> > disk_offering.display_offering,
 >> > domain.id domain_id,
 >> > domain.uuid domain_uuid,
 >> > domain.name domain_name,
 >> > domain.path domain_path
 >> > from
 >> > `cloud`.`disk_offering`
 >> > left join
 >> > `cloud`.`domain` ON disk_offering.domain_id = domain.id
 >> > where
 >> > disk_offering.state='ACTIVE';
 >> >
 >> > DROP VIEW IF EXISTS `cloud`.`service_offering_view`;
 >> > CREATE VIEW `cloud`.`service_offering_view` AS
 >> > select
 >> > service_offering.id,
 >> > disk_offering.uuid,
 >> > disk_offering.name,
 >> > disk_offering.display_text,
 >> > disk_offering.created,
 >> > disk_offering.tags,
 >> > disk_offering.removed,
 >> > disk_offering.use_loca

Re: Just checked in a minor change to the DB

[Daan Hoogland]

I created 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/mail+tags+to+use+to+help+each+other
below the path
Apache Cloudstack / Home / Community / Getting Help


On Fri, Mar 7, 2014 at 8:03 PM, Daan Hoogland  wrote:
> I had a quick look. Nothing found but a lot of hits on tags of course.
> I'll try to find a place to create the page and start chapters on Dev
> and Users
>
>
> On Fri, Mar 7, 2014 at 7:54 PM, Daan Hoogland  wrote:
>> No, but I do know that it might be useful to use them in commit
>> comments as well. If you so feel inclined you can refer to that as
>> well
>>
>> On Fri, Mar 7, 2014 at 7:41 PM, Mike Tutkowski
>>  wrote:
>>> Does anyone know if our e-mail tags are documented on the Wiki?
>>>
>>>
>>> On Fri, Mar 7, 2014 at 11:36 AM, Mike Tutkowski <
>>> mike.tutkow...@solidfire.com> wrote:
>>>
 That sounds good, Daan.

 Let's use both tags.

 Thanks!


 On Fri, Mar 7, 2014 at 9:33 AM, Daan Hoogland 
 wrote:

> Absolutaly,
>
> But I meant for us to use both tags. I checked in a commit (that I
> didn't give a head up on) for a colleague in which a
> CloudRuntimeException was removed to be more consistent with the rest
> of the code. It was only effecting th upgrade process in this case but
> still;
> [BEHAVIORAL-CHANGE] was caused. Of course these heads-up will always
> be an inter developer courtesy but here is mine (hidden in some one
> elses thread;)
>
> so in short i meant and and not or,
> Daan
>
>
> On Fri, Mar 7, 2014 at 4:20 PM, Mike Tutkowski
>  wrote:
> > I like either tag.
> >
> > Since DB changes are the most likely to lead to breaking other people's
> > environments, maybe we should go with that one:
> >
> > [DB-CHANGE]
> >
> > Ideally we'd provide the branch, commit SHA, and a manual way around
> it, if
> > there is something simple (like in my case yesterday, simply deleting
> and
> > re-creating two views). If there's no easy way around it, then don't
> bother
> > providing that.
> >
> > Sound reasonable?
> >
> >
> > On Fri, Mar 7, 2014 at 2:12 AM, Daan Hoogland  >wrote:
> >
> >> Thanks for the heads up Mike,
> >>
> >> As discussed in your thread [1]. You are eating your own dogfood here.
> >> I was checking in a minor change to the upgrade handling yesterday and
> >> decided not to bother everyone with it. evil me. In that thread we
> >> didn't dicide on a tag, yet.
> >>
> >> I would suggest
> >> [DB-CHANGE] and
> >> [BEHAVIORAL-CHANGE]
> >>
> >> [1] http://markmail.org/message/r7wv36o356nolq7f
> >>
> >> On Thu, Mar 6, 2014 at 9:05 PM, Mike Tutkowski
> >>  wrote:
> >> > Hi everyone,
> >> >
> >> > Just wanted to give you a heads up that I made a minor change to two
> >> views
> >> > in the DB in 9b66866dc2085486f465159cbd446ac03e266a2c:
> >> >
> >> > service_offering_view and disk_offering_view
> >> >
> >> > I added some columns to these views so I could present additional
> info in
> >> > the GUI.
> >> >
> >> > If you want to bring these two views up to date, just run the
> following
> >> SQL:
> >> >
> >> > DROP VIEW IF EXISTS `cloud`.`disk_offering_view`;
> >> > CREATE VIEW `cloud`.`disk_offering_view` AS
> >> > select
> >> > disk_offering.id,
> >> > disk_offering.uuid,
> >> > disk_offering.name,
> >> > disk_offering.display_text,
> >> > disk_offering.disk_size,
> >> > disk_offering.min_iops,
> >> > disk_offering.max_iops,
> >> > disk_offering.created,
> >> > disk_offering.tags,
> >> > disk_offering.customized,
> >> > disk_offering.customized_iops,
> >> > disk_offering.removed,
> >> > disk_offering.use_local_storage,
> >> > disk_offering.system_use,
> >> > disk_offering.hv_ss_reserve,
> >> > disk_offering.bytes_read_rate,
> >> > disk_offering.bytes_write_rate,
> >> > disk_offering.iops_read_rate,
> >> > disk_offering.iops_write_rate,
> >> > disk_offering.cache_mode,
> >> > disk_offering.sort_key,
> >> > disk_offering.type,
> >> > disk_offering.display_offering,
> >> > domain.id domain_id,
> >> > domain.uuid domain_uuid,
> >> > domain.name domain_name,
> >> > domain.path domain_path
> >> > from
> >> > `cloud`.`disk_offering`
> >> > left join
> >> > `cloud`.`domain` ON disk_offering.domain_id = domain.id
> >> > where
> >> > disk_offering.state='ACTIVE';
> >> >
> >> > DROP VIEW IF EXISTS `cloud`.`service_offering_view`;
> >> > CREATE VIEW `cloud`.`ser

Re: [DISCUSS] realhostip.com going away

[Nux!]

On 07.03.2014 14:55, France wrote:

Hi all.

Are we going to have a solution for older versions like 4.1.1?
I think we can already change that domain to something different
currently in settings. Hopefully it's not "hardcoded" anywhere else.
Is it?

I think it's the right thing to move away from such solution in
future versions, but just killing the service with 4 months notice, is
not a way to go about in enterprise world. How expensive can it be to
keep providing it?

If someone needs to take over realhostip.com, we can offer our
datacenter resources too.

Regards,
F.


It would be interesting to change the NS to 3-4 different Cloudstack 
users/backers. Even I could run an instance.


France, here's how to run your own (excuse the formatting, was written 
in a hurry):

http://www.nux.ro/archive/2014/03/Run_your_own_realhostip.html

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

Re: Review Request 16385: Fix for CloudStack JIRA 4406

[Alena Prokharchyk]

Daan, if the default comes as true for the command, I assume that the user
won¹t see the command logged at all? Unless he overrides it.
I assume sensitive=³true² means not ³analyze the command² but rather
³don¹t log the command². That doesn¹t seem right to me.

True would seem right to me if the parameter is defined on both
parameter/command level (which is not how it works today). Then parameter
in @ApiCommand annotation will just trigger the analyze for sensitive
parameters, and the parameter in the @Parameter will tell whether to log
the parameter itself.


-Alena.

On 3/7/14, 10:51 AM, "Daan Hoogland"  wrote:

>On Fri, Mar 7, 2014 at 7:31 PM, Alena Prokharchyk
> wrote:
>> And the defaults should be false,
>
>
>I don't agree, The true case does nothing if no fields are recognized
>as sensitive, but it the flase case skips sensitive data containing
>log messages. The only consquence of true as default is a performance
>penalty that we were paying in the old case anyhow.
>
>-- 
>Daan

Re: [DISCUSS] realhostip.com going away

[Amogh Vasekar]

Hi,

The design on 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Realhost+IP+changes
(big thanks to Kelven!) mentions a third work mode, that would use a load
balancer as the front for CPVMs. Since this is an exact address, it would
not need a wildcard cert and (hopefully) make it a little more easier and
affordable?

Thanks,
Amogh

On 2/28/14 2:03 PM, "Nux!"  wrote:

>and a wildcard cert which is a pain imho and
>not everyone can afford it so easily.

Re: Review Request 16385: Fix for CloudStack JIRA 4406

[Daan Hoogland]

Alena, I can see I am not being clear because what you say is the
sensible way and apart from the parameter level exactly what happens.

The parameter thing is an enhancement that we can make on top of this.
At the moment it only obfuscate a set of parameters with a fixed set
of names. We will have to have a new discussion of what the desirable
default is however. I say security first. but let's not have that
discussion in this thread.

Hope this clarifies,
Daan

On Fri, Mar 7, 2014 at 8:21 PM, Alena Prokharchyk
 wrote:
> Daan, if the default comes as true for the command, I assume that the user
> won¹t see the command logged at all? Unless he overrides it.
> I assume sensitive=³true² means not ³analyze the command² but rather
> ³don¹t log the command². That doesn¹t seem right to me.
>
> True would seem right to me if the parameter is defined on both
> parameter/command level (which is not how it works today). Then parameter
> in @ApiCommand annotation will just trigger the analyze for sensitive
> parameters, and the parameter in the @Parameter will tell whether to log
> the parameter itself.
>
>
> -Alena.
>
> On 3/7/14, 10:51 AM, "Daan Hoogland"  wrote:
>
>>On Fri, Mar 7, 2014 at 7:31 PM, Alena Prokharchyk
>> wrote:
>>> And the defaults should be false,
>>
>>
>>I don't agree, The true case does nothing if no fields are recognized
>>as sensitive, but it the flase case skips sensitive data containing
>>log messages. The only consquence of true as default is a performance
>>penalty that we were paying in the old case anyhow.
>>
>>--
>>Daan
>



-- 
Daan

Re: Review Request 16385: Fix for CloudStack JIRA 4406

[Alena Prokharchyk]

Ok, got it, somehow missed the “hardcoded” parameters part. In this case
true is fine as the parameter in @ApiCommand just triggers the validation.
We only have to fix one part - instead of hardcoding the parameter(s) to
hide, we have to come up with the new parameter in @Parameter to trigger
the exclusion from the logs.

Thank you,
Alena.

On 3/7/14, 11:32 AM, "Daan Hoogland"  wrote:

>Alena, I can see I am not being clear because what you say is the
>sensible way and apart from the parameter level exactly what happens.
>
>The parameter thing is an enhancement that we can make on top of this.
>At the moment it only obfuscate a set of parameters with a fixed set
>of names. We will have to have a new discussion of what the desirable
>default is however. I say security first. but let's not have that
>discussion in this thread.
>
>Hope this clarifies,
>Daan
>
>On Fri, Mar 7, 2014 at 8:21 PM, Alena Prokharchyk
> wrote:
>> Daan, if the default comes as true for the command, I assume that the
>>user
>> won¹t see the command logged at all? Unless he overrides it.
>> I assume sensitive=³true² means not ³analyze the command² but rather
>> ³don¹t log the command². That doesn¹t seem right to me.
>>
>> True would seem right to me if the parameter is defined on both
>> parameter/command level (which is not how it works today). Then
>>parameter
>> in @ApiCommand annotation will just trigger the analyze for sensitive
>> parameters, and the parameter in the @Parameter will tell whether to log
>> the parameter itself.
>>
>>
>> -Alena.
>>
>> On 3/7/14, 10:51 AM, "Daan Hoogland"  wrote:
>>
>>>On Fri, Mar 7, 2014 at 7:31 PM, Alena Prokharchyk
>>> wrote:
 And the defaults should be false,
>>>
>>>
>>>I don't agree, The true case does nothing if no fields are recognized
>>>as sensitive, but it the flase case skips sensitive data containing
>>>log messages. The only consquence of true as default is a performance
>>>penalty that we were paying in the old case anyhow.
>>>
>>>--
>>>Daan
>>
>
>
>
>-- 
>Daan

Re: Just checked in a minor change to the DB

[Mike Tutkowski]

Great! Thanks, Daan

I also agree that it would be useful info to have in commit messages.


On Fri, Mar 7, 2014 at 12:14 PM, Daan Hoogland wrote:

> I created
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/mail+tags+to+use+to+help+each+other
> below the path
> Apache Cloudstack / Home / Community / Getting Help
>
>
> On Fri, Mar 7, 2014 at 8:03 PM, Daan Hoogland 
> wrote:
> > I had a quick look. Nothing found but a lot of hits on tags of course.
> > I'll try to find a place to create the page and start chapters on Dev
> > and Users
> >
> >
> > On Fri, Mar 7, 2014 at 7:54 PM, Daan Hoogland 
> wrote:
> >> No, but I do know that it might be useful to use them in commit
> >> comments as well. If you so feel inclined you can refer to that as
> >> well
> >>
> >> On Fri, Mar 7, 2014 at 7:41 PM, Mike Tutkowski
> >>  wrote:
> >>> Does anyone know if our e-mail tags are documented on the Wiki?
> >>>
> >>>
> >>> On Fri, Mar 7, 2014 at 11:36 AM, Mike Tutkowski <
> >>> mike.tutkow...@solidfire.com> wrote:
> >>>
>  That sounds good, Daan.
> 
>  Let's use both tags.
> 
>  Thanks!
> 
> 
>  On Fri, Mar 7, 2014 at 9:33 AM, Daan Hoogland <
> daan.hoogl...@gmail.com>wrote:
> 
> > Absolutaly,
> >
> > But I meant for us to use both tags. I checked in a commit (that I
> > didn't give a head up on) for a colleague in which a
> > CloudRuntimeException was removed to be more consistent with the rest
> > of the code. It was only effecting th upgrade process in this case
> but
> > still;
> > [BEHAVIORAL-CHANGE] was caused. Of course these heads-up will always
> > be an inter developer courtesy but here is mine (hidden in some one
> > elses thread;)
> >
> > so in short i meant and and not or,
> > Daan
> >
> >
> > On Fri, Mar 7, 2014 at 4:20 PM, Mike Tutkowski
> >  wrote:
> > > I like either tag.
> > >
> > > Since DB changes are the most likely to lead to breaking other
> people's
> > > environments, maybe we should go with that one:
> > >
> > > [DB-CHANGE]
> > >
> > > Ideally we'd provide the branch, commit SHA, and a manual way
> around
> > it, if
> > > there is something simple (like in my case yesterday, simply
> deleting
> > and
> > > re-creating two views). If there's no easy way around it, then
> don't
> > bother
> > > providing that.
> > >
> > > Sound reasonable?
> > >
> > >
> > > On Fri, Mar 7, 2014 at 2:12 AM, Daan Hoogland <
> daan.hoogl...@gmail.com
> > >wrote:
> > >
> > >> Thanks for the heads up Mike,
> > >>
> > >> As discussed in your thread [1]. You are eating your own dogfood
> here.
> > >> I was checking in a minor change to the upgrade handling
> yesterday and
> > >> decided not to bother everyone with it. evil me. In that thread we
> > >> didn't dicide on a tag, yet.
> > >>
> > >> I would suggest
> > >> [DB-CHANGE] and
> > >> [BEHAVIORAL-CHANGE]
> > >>
> > >> [1] http://markmail.org/message/r7wv36o356nolq7f
> > >>
> > >> On Thu, Mar 6, 2014 at 9:05 PM, Mike Tutkowski
> > >>  wrote:
> > >> > Hi everyone,
> > >> >
> > >> > Just wanted to give you a heads up that I made a minor change
> to two
> > >> views
> > >> > in the DB in 9b66866dc2085486f465159cbd446ac03e266a2c:
> > >> >
> > >> > service_offering_view and disk_offering_view
> > >> >
> > >> > I added some columns to these views so I could present
> additional
> > info in
> > >> > the GUI.
> > >> >
> > >> > If you want to bring these two views up to date, just run the
> > following
> > >> SQL:
> > >> >
> > >> > DROP VIEW IF EXISTS `cloud`.`disk_offering_view`;
> > >> > CREATE VIEW `cloud`.`disk_offering_view` AS
> > >> > select
> > >> > disk_offering.id,
> > >> > disk_offering.uuid,
> > >> > disk_offering.name,
> > >> > disk_offering.display_text,
> > >> > disk_offering.disk_size,
> > >> > disk_offering.min_iops,
> > >> > disk_offering.max_iops,
> > >> > disk_offering.created,
> > >> > disk_offering.tags,
> > >> > disk_offering.customized,
> > >> > disk_offering.customized_iops,
> > >> > disk_offering.removed,
> > >> > disk_offering.use_local_storage,
> > >> > disk_offering.system_use,
> > >> > disk_offering.hv_ss_reserve,
> > >> > disk_offering.bytes_read_rate,
> > >> > disk_offering.bytes_write_rate,
> > >> > disk_offering.iops_read_rate,
> > >> > disk_offering.iops_write_rate,
> > >> > disk_offering.cache_mode,
> > >> > disk_offering.sort_key,
> > >> > disk_offering.type,
> > >> > disk_offering.display_offering,
> > >> > domain.id domain_id,
> >>

Re: [PROPOSAL][QUESTION] Map parameters in API Commands

[Marcus]

Any suggestion? Do we go forward assuming that the correct parameter
for resize on deploy is:

deployVirtualMachine&details[0].rootdisksize=3

or do we change it to

deployVirtualMachine&rootdisksize=3

On Tue, Mar 4, 2014 at 4:14 PM, Marcus  wrote:
> Ok, sounds like there needs to be some work done to make these more
> consistent, perhaps. Can you comment on why rootdisksize was made from
> a parameter into a part of the details map?
>
> On Tue, Mar 4, 2014 at 3:12 AM, Bharat Kumar  wrote:
>> Hi ALL,
>> There are many other APIs that use Map like createNetworkOffering,
>> updateZone, createTemplate, in most of the cases we do not
>> say how to use maps, one way would be to write this in the description or to
>> use the same way to access maps of all APIs.
>>
>> BTW the way to use details in deploy vm API is
>> details[0].foo=bar&details[1].baz=12 where foo and baz are keys.
>>
>> Also  if we want to use the regix protected static final String
>> MAP_KEY_PATTERN_EXPRESSION = "^([^\\[^\\]]+)\\[(\\d+)\\]\\.key$";
>>protected static final
>> String MAP_VALUE_PATTERN_EXPRESSION = "^[^\\[^\\]]+\\[\\d+\\]\\.value$";
>>
>> wil this work in the following case. I believe service is the key here which
>> repeats.
>> http://10.147.59.119:8080/client/api?command=createNetworkOffering&response=json&sessionkey=/kGFJDXFmMQU8JZnnC7QFfj3tV8=&name=bharat&displayText=bharat&guestIpType=Isolated&lbType=publicLb&;
>> servicecapabilitylist[0].service=SourceNat&servicecapabilitylist[0].capabilitytype=SupportedSourceNatTypes&
>> servicecapabilitylist[0].capabilityvalue=peraccount&
>> servicecapabilitylist[1].service=lb&servicecapabilitylist[1].capabilitytype=SupportedLbIsolation&
>> servicecapabilitylist[1].capabilityvalue=dedicated&availability=Optional&egresspolicy=ALLOW&state=Creating&status=Creating&allocationstate=Creating&supportedServices=Vpn,Dhcp,Dns,Firewall,Lb,UserData,SourceNat,StaticNat,PortForwarding&specifyIpRanges=false&specifyVlan=false&isPersistent=false&conservemode=false&serviceProviderList[0].service=Vpn&serviceProviderList[0].provider=VirtualRouter&serviceProviderList[1].service=Dhcp&serviceProviderList[1].provider=VirtualRouter&serviceProviderList[2].service=Dns&serviceProviderList[2].provider=VirtualRouter&serviceProviderList[3].service=Firewall&serviceProviderList[3].provider=VirtualRouter&serviceProviderList[4].service=Lb&serviceProviderList[4].provider=VirtualRouter&serviceProviderList[5].service=UserData&serviceProviderList[5].provider=VirtualRouter&serviceProviderList[6].service=SourceNat&serviceProviderList[6].provider=JuniperSRX&serviceProviderList[7].service=StaticNat&serviceProviderList[7].provider=JuniperSRX&serviceProviderList[8].service=PortForwarding&serviceProviderList[8].provider=JuniperSRX&egressdefaultpolicy=true&traffictype=GUEST&_=1393925230248
>>
>>
>>
>> On 04-Mar-2014, at 2:30 am, Marcus  wrote:
>>
>> Along these lines, the details parameter in deployVirtualMachine seems
>> broken. If I call "details[0].key=foo,details[0].value=bar", it stores
>> entries in the database like this:
>>
>> id | vmid | name | value | display
>>
>> 12 | 25   |  value | bar   | 1
>> 13 | 25   |  key   | foo   | 1
>>
>> It seems as though this might be correct per Alena's email, but I
>> don't understand how this can be reconstructed into foo=bar when
>> there's no binding between the two rows. Perhaps details are supposed
>> to be passed differently than the resource tags, because if I do
>> "details[0].foo=bar&details[1].baz=12", I get:
>>
>> id | vmid | name | value | display
>>
>> 12 | 25   |  foo| bar| 1
>> 13 | 25   |  baz   | 12 | 1
>>
>> And indeed there is code utilizing these details already committed
>> that expects this format, as deployVirtualMachines getDetails() only
>> seems to pass a correct Map with Key, Value if I use
>> this format.
>>
>> On Mon, Mar 3, 2014 at 11:48 AM, Antonio Fornié Casarrubios
>>  wrote:
>>
>> Hi Alena,
>>
>> Of course, the API will not have any changes. This is not a functional
>> change, just some refactoring. The problem is there are many things in CS
>> that really need some refactoring otherwise the problem will continue
>> growing more and more, but doing the change and above all making sure it
>> all works afterwards is not simple.
>>
>> I will make sure that everything works exactly the same way and that the
>> data returned is also the same.
>>
>> Thanks. Cheers
>> Antonio
>>
>>
>> 2014-03-03 18:48 GMT+01:00 Alena Prokharchyk :
>>
>> Antonio, sure I will review the patch. But please make sure that API
>> backwards compatibly is intact, otherwise the fix won¹t be accepted.
>>
>> -Alena.
>>
>>
>> On 3/2/14, 4:31 PM, "Antonio Fornié Casarrubios"
>>  wrote:
>>
>> Hi Alena,
>>
>> The reasons for this strange format? I don't know. There doesn't seem to
>> be
>> one. After asking on my team and in the dev list I thought perhaps you
>> could know. It

Re: [DISCUSS] realhostip.com going away

[Chiradeep Vittal]

You could use this article as well:
http://support.citrix.com/article/CTX133468
Does not require you to use the java solution.

On 3/7/14, 11:19 AM, "Nux!"  wrote:

>On 07.03.2014 14:55, France wrote:
>> Hi all.
>> 
>> Are we going to have a solution for older versions like 4.1.1?
>> I think we can already change that domain to something different
>> currently in settings. Hopefully it's not "hardcoded" anywhere else.
>> Is it?
>> 
>> I think it's the right thing to move away from such solution in
>> future versions, but just killing the service with 4 months notice, is
>> not a way to go about in enterprise world. How expensive can it be to
>> keep providing it?
>> 
>> If someone needs to take over realhostip.com, we can offer our
>> datacenter resources too.
>> 
>> Regards,
>> F.
>
>It would be interesting to change the NS to 3-4 different Cloudstack
>users/backers. Even I could run an instance.
>
>France, here's how to run your own (excuse the formatting, was written
>in a hurry):
>http://www.nux.ro/archive/2014/03/Run_your_own_realhostip.html
>
>-- 
>Sent from the Delta quadrant using Borg technology!
>
>Nux!
>www.nux.ro

Re: [DISCUSS] realhostip.com going away

[John Kinsella]

Soo…I’d recommend against something like Nux’s suggestion below. I’ve only 
looked briefly at VirtualDNS.java, and it looks fine from a glance, but I’m 
willing to bet I can a) DOS it, and b) use it for a reflection attack. I could 
be wrong, don’t really have time to look closely, but based on it looking like 
the design pattern for a basic UDP server, I wouldn’t recommend the community 
to build a network of those.

4 months is not a huge period of time, but I think if somebody can’t apply a 
patch within 4 months they need to consider if they should be running that 
service. If this was a critical security vulnerability and folks couldn’t patch 
it within a few weeks of notification, I’d have a hard time feeling sorry for 
them.

I do concur that we should back port the patch.

John

On Mar 7, 2014, at 11:19 AM, Nux!  wrote:

> On 07.03.2014 14:55, France wrote:
>> Hi all.
>> Are we going to have a solution for older versions like 4.1.1?
>> I think we can already change that domain to something different
>> currently in settings. Hopefully it's not "hardcoded" anywhere else.
>> Is it?
>> I think it's the right thing to move away from such solution in
>> future versions, but just killing the service with 4 months notice, is
>> not a way to go about in enterprise world. How expensive can it be to
>> keep providing it?
>> If someone needs to take over realhostip.com, we can offer our
>> datacenter resources too.
>> Regards,
>> F.
> 
> It would be interesting to change the NS to 3-4 different Cloudstack 
> users/backers. Even I could run an instance.
> 
> France, here's how to run your own (excuse the formatting, was written in a 
> hurry):
> http://www.nux.ro/archive/2014/03/Run_your_own_realhostip.html
> 
> -- 
> Sent from the Delta quadrant using Borg technology!
> 
> Nux!
> www.nux.ro

Stratosec - Compliance as a Service
o: 415.315.9385
@johnlkinsella

Re: Just checked in a minor change to the DB

[Mike Tutkowski]

I went ahead and added to the Wiki page you created a few more tags that
I've seen us use from time to time.


On Fri, Mar 7, 2014 at 12:37 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> Great! Thanks, Daan
>
> I also agree that it would be useful info to have in commit messages.
>
>
> On Fri, Mar 7, 2014 at 12:14 PM, Daan Hoogland wrote:
>
>> I created
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/mail+tags+to+use+to+help+each+other
>> below the path
>> Apache Cloudstack / Home / Community / Getting Help
>>
>>
>> On Fri, Mar 7, 2014 at 8:03 PM, Daan Hoogland 
>> wrote:
>> > I had a quick look. Nothing found but a lot of hits on tags of course.
>> > I'll try to find a place to create the page and start chapters on Dev
>> > and Users
>> >
>> >
>> > On Fri, Mar 7, 2014 at 7:54 PM, Daan Hoogland 
>> wrote:
>> >> No, but I do know that it might be useful to use them in commit
>> >> comments as well. If you so feel inclined you can refer to that as
>> >> well
>> >>
>> >> On Fri, Mar 7, 2014 at 7:41 PM, Mike Tutkowski
>> >>  wrote:
>> >>> Does anyone know if our e-mail tags are documented on the Wiki?
>> >>>
>> >>>
>> >>> On Fri, Mar 7, 2014 at 11:36 AM, Mike Tutkowski <
>> >>> mike.tutkow...@solidfire.com> wrote:
>> >>>
>>  That sounds good, Daan.
>> 
>>  Let's use both tags.
>> 
>>  Thanks!
>> 
>> 
>>  On Fri, Mar 7, 2014 at 9:33 AM, Daan Hoogland <
>> daan.hoogl...@gmail.com>wrote:
>> 
>> > Absolutaly,
>> >
>> > But I meant for us to use both tags. I checked in a commit (that I
>> > didn't give a head up on) for a colleague in which a
>> > CloudRuntimeException was removed to be more consistent with the
>> rest
>> > of the code. It was only effecting th upgrade process in this case
>> but
>> > still;
>> > [BEHAVIORAL-CHANGE] was caused. Of course these heads-up will always
>> > be an inter developer courtesy but here is mine (hidden in some one
>> > elses thread;)
>> >
>> > so in short i meant and and not or,
>> > Daan
>> >
>> >
>> > On Fri, Mar 7, 2014 at 4:20 PM, Mike Tutkowski
>> >  wrote:
>> > > I like either tag.
>> > >
>> > > Since DB changes are the most likely to lead to breaking other
>> people's
>> > > environments, maybe we should go with that one:
>> > >
>> > > [DB-CHANGE]
>> > >
>> > > Ideally we'd provide the branch, commit SHA, and a manual way
>> around
>> > it, if
>> > > there is something simple (like in my case yesterday, simply
>> deleting
>> > and
>> > > re-creating two views). If there's no easy way around it, then
>> don't
>> > bother
>> > > providing that.
>> > >
>> > > Sound reasonable?
>> > >
>> > >
>> > > On Fri, Mar 7, 2014 at 2:12 AM, Daan Hoogland <
>> daan.hoogl...@gmail.com
>> > >wrote:
>> > >
>> > >> Thanks for the heads up Mike,
>> > >>
>> > >> As discussed in your thread [1]. You are eating your own dogfood
>> here.
>> > >> I was checking in a minor change to the upgrade handling
>> yesterday and
>> > >> decided not to bother everyone with it. evil me. In that thread
>> we
>> > >> didn't dicide on a tag, yet.
>> > >>
>> > >> I would suggest
>> > >> [DB-CHANGE] and
>> > >> [BEHAVIORAL-CHANGE]
>> > >>
>> > >> [1] http://markmail.org/message/r7wv36o356nolq7f
>> > >>
>> > >> On Thu, Mar 6, 2014 at 9:05 PM, Mike Tutkowski
>> > >>  wrote:
>> > >> > Hi everyone,
>> > >> >
>> > >> > Just wanted to give you a heads up that I made a minor change
>> to two
>> > >> views
>> > >> > in the DB in 9b66866dc2085486f465159cbd446ac03e266a2c:
>> > >> >
>> > >> > service_offering_view and disk_offering_view
>> > >> >
>> > >> > I added some columns to these views so I could present
>> additional
>> > info in
>> > >> > the GUI.
>> > >> >
>> > >> > If you want to bring these two views up to date, just run the
>> > following
>> > >> SQL:
>> > >> >
>> > >> > DROP VIEW IF EXISTS `cloud`.`disk_offering_view`;
>> > >> > CREATE VIEW `cloud`.`disk_offering_view` AS
>> > >> > select
>> > >> > disk_offering.id,
>> > >> > disk_offering.uuid,
>> > >> > disk_offering.name,
>> > >> > disk_offering.display_text,
>> > >> > disk_offering.disk_size,
>> > >> > disk_offering.min_iops,
>> > >> > disk_offering.max_iops,
>> > >> > disk_offering.created,
>> > >> > disk_offering.tags,
>> > >> > disk_offering.customized,
>> > >> > disk_offering.customized_iops,
>> > >> > disk_offering.removed,
>> > >> > disk_offering.use_local_storage,
>> > >> > disk_offering.system_use,
>> > >> > disk_offering.hv_ss_reserve,
>> > >> > disk_offering.bytes_read_rate,
>> > >> > disk_offering.by

Re: [DISCUSS] realhostip.com going away

[Nux!]

On 07.03.2014 20:28, John Kinsella wrote:

Soo…I’d recommend against something like Nux’s suggestion below. I’ve
only looked briefly at VirtualDNS.java, and it looks fine from a
glance, but I’m willing to bet I can a) DOS it, and b) use it for a
reflection attack. I could be wrong, don’t really have time to look
closely, but based on it looking like the design pattern for a basic
UDP server, I wouldn’t recommend the community to build a network of
those.


I'd love not having to run that java DNS server, but the alternative is 
to add records for all IPs that I am going to use for guest network, 
which I imagine will keep increasing in time and this would be difficult 
and probably messy.
Isn't realhostip service that Java thing now? How is the name 
translation done, if not?


--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

Re: [DISCUSS] realhostip.com going away

[Nux!]

On 07.03.2014 20:19, Chiradeep Vittal wrote:

You could use this article as well:
http://support.citrix.com/article/CTX133468
Does not require you to use the java solution.


Thanks, I've updated my post with it.


--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

Build failed in Jenkins: build-master-slowbuild #379

[jenkins]

See 

Changes:

[Daan Hoogland] Dispatcher corrections, refactoring and tests

[Daan Hoogland] rats

[Alena Prokharchyk] Removed unused methods from BaseCmd class. Moved some 
helper methods to AccountManagerImpl class

[brian.federle] Update plugins side nav icon

--
[...truncated 18097 lines...]

Tests run: 4, Failures: 0, Errors: 0, Skipped: 0

[INFO] 
[INFO] <<< cobertura-maven-plugin:2.6:cobertura (default-cli) @ cloud-awsapi <<<
[INFO] 
[INFO] --- cobertura-maven-plugin:2.6:cobertura (default-cli) @ cloud-awsapi ---
[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/amazon/ec2/AmazonEC2SkeletonInterface.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/amazon/s3/AmazonS3SkeletonInterface.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/model/SAcl.java.  Ensure this class was instrumented, and this 
data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/model/SBucket.java.  Ensure this class was instrumented, and 
this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/model/SHost.java.  Ensure this class was instrumented, and 
this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/BucketPolicyDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackAccountDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackConfigurationDao.java.  Ensure this 
class was instrumented, and this data file contains the instrumentation 
information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackSvcOfferingDao.java.  Ensure this class 
was instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackUserDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MHostDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MHostMountDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MultiPartPartsDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MultiPartUploadsDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation infor

RE: 4.3 vote

[Animesh Chaturvedi]

> -Original Message-
> From: John Kinsella [mailto:j...@stratosec.co]
> Sent: Friday, March 07, 2014 8:41 AM
> To: dev@cloudstack.apache.org
> Subject: Re: 4.3 vote
> 
> I have a review request sitting at https://reviews.apache.org/r/18392/ - that
> works for me but I don't know if it's breaking AWSAPI functionality. Would
> love it if somebody more familiar with that module could test. I'd rather not
> just check that in and see what happens.
[Animesh] I agree we cannot checkin especially so late in release unless we are 
absolutely sure. 
> 
> Animesh, I know you put a ton of work into these RCs and I hate holding you
> up, 
[Animesh] Well you are not holding me up. It's a community release not just 
mine :)

but here's my train of thought: packaging/centos63/package.sh is broken
> because one of the RPMs it attempts to build is for awsapi. No self-
> respecting enterprise (I hope, dream) is going to drop non-packaged (deb,
> rpm, whatever) code on production systems. So if that packaging ability is
> broken, there's a good chance enterprises can't use the new code.


[Animesh] John while you can reproduce the issue but  
http://jenkins.buildacloud.org/view/4.3/job/cloudstack-4.3-package-rpm/ has 
been building successfully.   Can we not use that? I guess this may have been 
an issue for prior releases too but has not blocked folks.

> 
> Just got an idea to see if Apache's Sonatype has a valid mirror, and it does,
> at least for some[1]. So I'll go down that path this AM as well, in case my
> patch above doesn't work.
> 
> John
> 1: https://repository.apache.org/index.html#nexus-search;quick~mex
> 
> On Mar 6, 2014, at 11:04 PM, Animesh Chaturvedi
>  wrote:
> 
> > Ok so how do we get past this? This should have been pre-existing as
> dependency has been broken for a long time and I am not sure if this should
> block our next RC.
> >
> >> -Original Message-
> >> From: John Kinsella [mailto:j...@stratosec.co]
> >> Sent: Thursday, March 06, 2014 4:14 PM
> >> To: dev@cloudstack.apache.org
> >> Subject: Re: 4.3 vote
> >>
> >> David was seeing this as well. This is is a documented problem at
> >> https://issues.apache.org/jira/browse/RAMPART-393.
> >>
> >> I just spun up a VM at AWS using a 64 bit amazon linux api. Ran the
> >> commands below, got same errors:
> >>
> >>1  sudo yum update
> >>2  yum install git java-1.7.0-openjdk-devel
> >>3  git clone https://git-wip-us.apache.org/repos/asf/cloudstack.git
> >>4  wget http://www.dsgnwrld.com/am/maven/maven-
> >> 3/3.2.1/binaries/apache-maven-3.2.1-bin.tar.gz
> >>5  tar xvf apache-maven-3.2.1-bin.tar.gz
> >>6  export PATH=$PATH:~/apache-maven-3.2.1/bin/
> >>7  cd cloudstack/
> >>8  mvn -P deps
> >>9  mvn clean install -Pawsapi
> >>
> >> I suspect the Citrix devs are sitting behind Nexus or other maven mirror?
> >>
> >> John
> >>
> >> On Mar 6, 2014, at 3:13 PM, Animesh Chaturvedi
> >> mailto:animesh.chaturv...@citrix.com>>
> >> wrote:
> >>
> >> Folks anyone else seeing this? I want to build RC soon and wanted to
> >> confirm if this is an issue or not and if so if we can get a fix
> >> right away
> >>
> >> -Original Message-
> >> From: Prachi Damle [mailto:prachi.da...@citrix.com]
> >> Sent: Thursday, March 06, 2014 1:20 PM
> >> To: dev@cloudstack.apache.org
> >> Subject: RE: 4.3 vote
> >>
> >> John,
> >>
> >> I could not reproduce this broken build on 4.3 after wiping out my
> >> entire repository.
> >> 1.  rm -rf ~/.m2/repository
> >> 2. mvn clean install -Pawsapi
> >>
> >> My build is successful.
> >>
> >> Can someone who is able to reproduce this check this further?
> >>
> >> Prachi
> >>
> >>
> >> [INFO]
> >> -
> >> ---
> >> [INFO] Reactor Summary:
> >> [INFO]
> >> [INFO] Apache CloudStack . SUCCESS
> >> [1:53.957s] [INFO] Apache CloudStack Maven Conventions Parent
> >>  SUCCESS [0.089s] [INFO] Apache CloudStack Framework -
> >> Managed Context . SUCCESS [28.189s] [INFO] Apache CloudStack
> >> Utils ... SUCCESS [1:06.368s] [INFO] Apache
> >> CloudStack Framework ... SUCCESS [0.303s] [INFO]
> >> Apache CloudStack Framework - Event Notification .. SUCCESS [27.125s]
> >> [INFO] Apache CloudStack Framework - Configuration ... SUCCESS
> >> [5.878s] [INFO] Apache CloudStack API .
> >> SUCCESS [55.346s] [INFO] Apache CloudStack Framework - REST
> >>  SUCCESS [16.891s] [INFO] Apache CloudStack Framework
> >> - IPC . SUCCESS [11.845s] [INFO] Apache CloudStack
> >> Cloud Engine  SUCCESS [0.072s] [INFO] Apache
> >> CloudStack Cloud Engine API  SUCCESS [10.641s] [INFO]
> >> Apache CloudStack Core  SUCCESS [30.300s]
> >> [INFO] Apache CloudStack Agents .. SUCCESS
> >> [22.5

Re: [DISCUSS] realhostip.com going away

[Chiradeep Vittal]

You should require 1 record for the ACTUAL public IP used by the
ConsoleProxy VM.

On 3/7/14, 12:39 PM, "Nux!"  wrote:

>On 07.03.2014 20:28, John Kinsella wrote:
>> SooŠI¹d recommend against something like Nux¹s suggestion below. I¹ve
>> only looked briefly at VirtualDNS.java, and it looks fine from a
>> glance, but I¹m willing to bet I can a) DOS it, and b) use it for a
>> reflection attack. I could be wrong, don¹t really have time to look
>> closely, but based on it looking like the design pattern for a basic
>> UDP server, I wouldn¹t recommend the community to build a network of
>> those.
>
>I'd love not having to run that java DNS server, but the alternative is
>to add records for all IPs that I am going to use for guest network,
>which I imagine will keep increasing in time and this would be difficult
>and probably messy.
>Isn't realhostip service that Java thing now? How is the name
>translation done, if not?
>
>-- 
>Sent from the Delta quadrant using Borg technology!
>
>Nux!
>www.nux.ro

Re: [DISCUSS] realhostip.com going away

[Nux!]

On 07.03.2014 21:30, Chiradeep Vittal wrote:

You should require 1 record for the ACTUAL public IP used by the
ConsoleProxy VM.


I know, but if the VM is destroyed or an additional one is spawned it 
could have ANY IP.. I mean, I really don't want to track this kind of 
stuff, doesn't "scale".
Maybe the Java DNS server could be replaced by Powerdns+pipe backend, 
will have to dig into this.


--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

Re: Review Request 16385: Fix for CloudStack JIRA 4406

[Daan Hoogland]

no problem, glad we agree.

On Fri, Mar 7, 2014 at 8:38 PM, Alena Prokharchyk
 wrote:
> Ok, got it, somehow missed the "hardcoded" parameters part. In this case
> true is fine as the parameter in @ApiCommand just triggers the validation.
> We only have to fix one part - instead of hardcoding the parameter(s) to
> hide, we have to come up with the new parameter in @Parameter to trigger
> the exclusion from the logs.
>
> Thank you,
> Alena.
>
> On 3/7/14, 11:32 AM, "Daan Hoogland"  wrote:
>
>>Alena, I can see I am not being clear because what you say is the
>>sensible way and apart from the parameter level exactly what happens.
>>
>>The parameter thing is an enhancement that we can make on top of this.
>>At the moment it only obfuscate a set of parameters with a fixed set
>>of names. We will have to have a new discussion of what the desirable
>>default is however. I say security first. but let's not have that
>>discussion in this thread.
>>
>>Hope this clarifies,
>>Daan
>>
>>On Fri, Mar 7, 2014 at 8:21 PM, Alena Prokharchyk
>> wrote:
>>> Daan, if the default comes as true for the command, I assume that the
>>>user
>>> won¹t see the command logged at all? Unless he overrides it.
>>> I assume sensitive=³true² means not ³analyze the command² but rather
>>> ³don¹t log the command². That doesn¹t seem right to me.
>>>
>>> True would seem right to me if the parameter is defined on both
>>> parameter/command level (which is not how it works today). Then
>>>parameter
>>> in @ApiCommand annotation will just trigger the analyze for sensitive
>>> parameters, and the parameter in the @Parameter will tell whether to log
>>> the parameter itself.
>>>
>>>
>>> -Alena.
>>>
>>> On 3/7/14, 10:51 AM, "Daan Hoogland"  wrote:
>>>
On Fri, Mar 7, 2014 at 7:31 PM, Alena Prokharchyk
 wrote:
> And the defaults should be false,


I don't agree, The true case does nothing if no fields are recognized
as sensitive, but it the flase case skips sensitive data containing
log messages. The only consquence of true as default is a performance
penalty that we were paying in the old case anyhow.

--
Daan
>>>
>>
>>
>>
>>--
>>Daan
>



-- 
Daan

Re: Just checked in a minor change to the DB

[Daan Hoogland]

saw, good, will do some more if I think of them as well, as well as
add to the descriptions

On Fri, Mar 7, 2014 at 9:29 PM, Mike Tutkowski
 wrote:
> I went ahead and added to the Wiki page you created a few more tags that
> I've seen us use from time to time.
>
>
> On Fri, Mar 7, 2014 at 12:37 PM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
>> Great! Thanks, Daan
>>
>> I also agree that it would be useful info to have in commit messages.
>>
>>
>> On Fri, Mar 7, 2014 at 12:14 PM, Daan Hoogland 
>> wrote:
>>
>>> I created
>>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/mail+tags+to+use+to+help+each+other
>>> below the path
>>> Apache Cloudstack / Home / Community / Getting Help
>>>
>>>
>>> On Fri, Mar 7, 2014 at 8:03 PM, Daan Hoogland 
>>> wrote:
>>> > I had a quick look. Nothing found but a lot of hits on tags of course.
>>> > I'll try to find a place to create the page and start chapters on Dev
>>> > and Users
>>> >
>>> >
>>> > On Fri, Mar 7, 2014 at 7:54 PM, Daan Hoogland 
>>> wrote:
>>> >> No, but I do know that it might be useful to use them in commit
>>> >> comments as well. If you so feel inclined you can refer to that as
>>> >> well
>>> >>
>>> >> On Fri, Mar 7, 2014 at 7:41 PM, Mike Tutkowski
>>> >>  wrote:
>>> >>> Does anyone know if our e-mail tags are documented on the Wiki?
>>> >>>
>>> >>>
>>> >>> On Fri, Mar 7, 2014 at 11:36 AM, Mike Tutkowski <
>>> >>> mike.tutkow...@solidfire.com> wrote:
>>> >>>
>>>  That sounds good, Daan.
>>> 
>>>  Let's use both tags.
>>> 
>>>  Thanks!
>>> 
>>> 
>>>  On Fri, Mar 7, 2014 at 9:33 AM, Daan Hoogland <
>>> daan.hoogl...@gmail.com>wrote:
>>> 
>>> > Absolutaly,
>>> >
>>> > But I meant for us to use both tags. I checked in a commit (that I
>>> > didn't give a head up on) for a colleague in which a
>>> > CloudRuntimeException was removed to be more consistent with the
>>> rest
>>> > of the code. It was only effecting th upgrade process in this case
>>> but
>>> > still;
>>> > [BEHAVIORAL-CHANGE] was caused. Of course these heads-up will always
>>> > be an inter developer courtesy but here is mine (hidden in some one
>>> > elses thread;)
>>> >
>>> > so in short i meant and and not or,
>>> > Daan
>>> >
>>> >
>>> > On Fri, Mar 7, 2014 at 4:20 PM, Mike Tutkowski
>>> >  wrote:
>>> > > I like either tag.
>>> > >
>>> > > Since DB changes are the most likely to lead to breaking other
>>> people's
>>> > > environments, maybe we should go with that one:
>>> > >
>>> > > [DB-CHANGE]
>>> > >
>>> > > Ideally we'd provide the branch, commit SHA, and a manual way
>>> around
>>> > it, if
>>> > > there is something simple (like in my case yesterday, simply
>>> deleting
>>> > and
>>> > > re-creating two views). If there's no easy way around it, then
>>> don't
>>> > bother
>>> > > providing that.
>>> > >
>>> > > Sound reasonable?
>>> > >
>>> > >
>>> > > On Fri, Mar 7, 2014 at 2:12 AM, Daan Hoogland <
>>> daan.hoogl...@gmail.com
>>> > >wrote:
>>> > >
>>> > >> Thanks for the heads up Mike,
>>> > >>
>>> > >> As discussed in your thread [1]. You are eating your own dogfood
>>> here.
>>> > >> I was checking in a minor change to the upgrade handling
>>> yesterday and
>>> > >> decided not to bother everyone with it. evil me. In that thread
>>> we
>>> > >> didn't dicide on a tag, yet.
>>> > >>
>>> > >> I would suggest
>>> > >> [DB-CHANGE] and
>>> > >> [BEHAVIORAL-CHANGE]
>>> > >>
>>> > >> [1] http://markmail.org/message/r7wv36o356nolq7f
>>> > >>
>>> > >> On Thu, Mar 6, 2014 at 9:05 PM, Mike Tutkowski
>>> > >>  wrote:
>>> > >> > Hi everyone,
>>> > >> >
>>> > >> > Just wanted to give you a heads up that I made a minor change
>>> to two
>>> > >> views
>>> > >> > in the DB in 9b66866dc2085486f465159cbd446ac03e266a2c:
>>> > >> >
>>> > >> > service_offering_view and disk_offering_view
>>> > >> >
>>> > >> > I added some columns to these views so I could present
>>> additional
>>> > info in
>>> > >> > the GUI.
>>> > >> >
>>> > >> > If you want to bring these two views up to date, just run the
>>> > following
>>> > >> SQL:
>>> > >> >
>>> > >> > DROP VIEW IF EXISTS `cloud`.`disk_offering_view`;
>>> > >> > CREATE VIEW `cloud`.`disk_offering_view` AS
>>> > >> > select
>>> > >> > disk_offering.id,
>>> > >> > disk_offering.uuid,
>>> > >> > disk_offering.name,
>>> > >> > disk_offering.display_text,
>>> > >> > disk_offering.disk_size,
>>> > >> > disk_offering.min_iops,
>>> > >> > disk_offering.max_iops,
>>> > >> > disk_offering.created,
>>> > >> > disk_offering.tags,
>>> > >> > disk_offering.customized,
>>> > >> > disk_offering.custo

Re: devcloud2 java

[Daan Hoogland]

Marcus, I saw a template definition in the tools/appliance directory
for devcloud. I have build it succesfully but never ran it yet.
Millage unknown.

Daan

On Fri, Mar 7, 2014 at 7:46 PM, Marcus  wrote:
> I manually installed java 7, but I'm beginning to think I've got the
> wrong version of devcloud, as I can't add the host.
>
> Caused by: java.io.IOException: Error during SCP transfer.
> at com.trilead.ssh2.SCPClient.put(SCPClient.java:592)
> at com.trilead.ssh2.SCPClient.put(SCPClient.java:547)
> at com.trilead.ssh2.SCPClient.put(SCPClient.java:434)
> at 
> com.cloud.hypervisor.xen.resource.CitrixResourceBase.setupServer(CitrixResourceBase.java:4766)
> ... 17 more
> Caused by: java.io.IOException: Remote scp terminated with error (scp:
> /etc/xensource: No such file or directory).
> at com.trilead.ssh2.SCPClient.readResponse(SCPClient.java:59)
> at com.trilead.ssh2.SCPClient.sendFiles(SCPClient.java:166)
> at com.trilead.ssh2.SCPClient.put(SCPClient.java:588)
> ... 20 more
>
>
>
> On Fri, Mar 7, 2014 at 10:54 AM, Marcus  wrote:
>> Hi guys,
>>Trying to get back into the Xen devcloud for a few things, and
>> following the instructions it seems that the existing devcloud2 is
>> missing java 7. Do our docs point to an old image, or are we just
>> installing that manually?



-- 
Daan

Re: Review Request 16385: Fix for CloudStack JIRA 4406

[Alena Prokharchyk]

And here is the Jira ticket:

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

"Add new field to API @Parameter indicating if the param should be skipped
from logs”

-Alena.

On 3/7/14, 1:47 PM, "Daan Hoogland"  wrote:

>no problem, glad we agree.
>
>On Fri, Mar 7, 2014 at 8:38 PM, Alena Prokharchyk
> wrote:
>> Ok, got it, somehow missed the "hardcoded" parameters part. In this case
>> true is fine as the parameter in @ApiCommand just triggers the
>>validation.
>> We only have to fix one part - instead of hardcoding the parameter(s) to
>> hide, we have to come up with the new parameter in @Parameter to trigger
>> the exclusion from the logs.
>>
>> Thank you,
>> Alena.
>>
>> On 3/7/14, 11:32 AM, "Daan Hoogland"  wrote:
>>
>>>Alena, I can see I am not being clear because what you say is the
>>>sensible way and apart from the parameter level exactly what happens.
>>>
>>>The parameter thing is an enhancement that we can make on top of this.
>>>At the moment it only obfuscate a set of parameters with a fixed set
>>>of names. We will have to have a new discussion of what the desirable
>>>default is however. I say security first. but let's not have that
>>>discussion in this thread.
>>>
>>>Hope this clarifies,
>>>Daan
>>>
>>>On Fri, Mar 7, 2014 at 8:21 PM, Alena Prokharchyk
>>> wrote:
 Daan, if the default comes as true for the command, I assume that the
user
 won¹t see the command logged at all? Unless he overrides it.
 I assume sensitive=³true² means not ³analyze the command² but rather
 ³don¹t log the command². That doesn¹t seem right to me.

 True would seem right to me if the parameter is defined on both
 parameter/command level (which is not how it works today). Then
parameter
 in @ApiCommand annotation will just trigger the analyze for sensitive
 parameters, and the parameter in the @Parameter will tell whether to
log
 the parameter itself.


 -Alena.

 On 3/7/14, 10:51 AM, "Daan Hoogland"  wrote:

>On Fri, Mar 7, 2014 at 7:31 PM, Alena Prokharchyk
> wrote:
>> And the defaults should be false,
>
>
>I don't agree, The true case does nothing if no fields are recognized
>as sensitive, but it the flase case skips sensitive data containing
>log messages. The only consquence of true as default is a performance
>penalty that we were paying in the old case anyhow.
>
>--
>Daan

>>>
>>>
>>>
>>>--
>>>Daan
>>
>
>
>
>-- 
>Daan

Re: Review Request 16385: Fix for CloudStack JIRA 4406

[Daan Hoogland]

Mandar, you want to take it?

On Fri, Mar 7, 2014 at 11:12 PM, Alena Prokharchyk
 wrote:
> And here is the Jira ticket:
>
> https://issues.apache.org/jira/browse/CLOUDSTACK-6213
>
> "Add new field to API @Parameter indicating if the param should be skipped
> from logs"
>
> -Alena.
>
> On 3/7/14, 1:47 PM, "Daan Hoogland"  wrote:
>
>>no problem, glad we agree.
>>
>>On Fri, Mar 7, 2014 at 8:38 PM, Alena Prokharchyk
>> wrote:
>>> Ok, got it, somehow missed the "hardcoded" parameters part. In this case
>>> true is fine as the parameter in @ApiCommand just triggers the
>>>validation.
>>> We only have to fix one part - instead of hardcoding the parameter(s) to
>>> hide, we have to come up with the new parameter in @Parameter to trigger
>>> the exclusion from the logs.
>>>
>>> Thank you,
>>> Alena.
>>>
>>> On 3/7/14, 11:32 AM, "Daan Hoogland"  wrote:
>>>
Alena, I can see I am not being clear because what you say is the
sensible way and apart from the parameter level exactly what happens.

The parameter thing is an enhancement that we can make on top of this.
At the moment it only obfuscate a set of parameters with a fixed set
of names. We will have to have a new discussion of what the desirable
default is however. I say security first. but let's not have that
discussion in this thread.

Hope this clarifies,
Daan

On Fri, Mar 7, 2014 at 8:21 PM, Alena Prokharchyk
 wrote:
> Daan, if the default comes as true for the command, I assume that the
>user
> won¹t see the command logged at all? Unless he overrides it.
> I assume sensitive=³true² means not ³analyze the command² but rather
> ³don¹t log the command². That doesn¹t seem right to me.
>
> True would seem right to me if the parameter is defined on both
> parameter/command level (which is not how it works today). Then
>parameter
> in @ApiCommand annotation will just trigger the analyze for sensitive
> parameters, and the parameter in the @Parameter will tell whether to
>log
> the parameter itself.
>
>
> -Alena.
>
> On 3/7/14, 10:51 AM, "Daan Hoogland"  wrote:
>
>>On Fri, Mar 7, 2014 at 7:31 PM, Alena Prokharchyk
>> wrote:
>>> And the defaults should be false,
>>
>>
>>I don't agree, The true case does nothing if no fields are recognized
>>as sensitive, but it the flase case skips sensitive data containing
>>log messages. The only consquence of true as default is a performance
>>penalty that we were paying in the old case anyhow.
>>
>>--
>>Daan
>



--
Daan
>>>
>>
>>
>>
>>--
>>Daan
>



-- 
Daan

Fwd: Build failed in Jenkins: cloudstack-rat-master #4166

[Mike Tutkowski]

Hi,

I'm not that familiar with reading these reports, but it claims there was a
Jenkins build failure due to code I checked in.

I ran a full build locally using mvn -P developer,systemvm clean install
and then tested before checking the code in. Perhaps there is a regression
test on Jenkins that no longer functions now?

Thanks!
Mike

-- Forwarded message --
From: Apache Jenkins Server 
Date: Fri, Mar 7, 2014 at 3:55 PM
Subject: Build failed in Jenkins: cloudstack-rat-master #4166
To: cloudstack-comm...@incubator.apache.org, mike.tutkow...@solidfire.com


See 

Changes:

[mike.tutkowski] CLOUDSTACK-6170

--
Started by an SCM change
Started by an SCM change
Building remotely on ubuntu6 in workspace <
https://builds.apache.org/job/cloudstack-rat-master/ws/>
Fetching changes from the remote Git repository
Fetching upstream changes from
https://git-wip-us.apache.org/repos/asf/cloudstack.git
Checking out Revision c427e8db1c4294bec93aa9295052950888c0fecf
(origin/master)
[cloudstack-rat-master] $ /bin/bash -xe /tmp/hudson6721284311782327396.sh
+ /home/jenkins/tools/maven/latest2/bin/mvn
--projects=org.apache.cloudstack:cloudstack
org.apache.rat:apache-rat-plugin:0.10:check
[INFO] Scanning for projects...
[INFO]

[INFO] Building Apache CloudStack
[INFO]task-segment: [org.apache.rat:apache-rat-plugin:0.10:check]
[INFO]

[INFO] [apache-rat:check {execution: default-cli}]
[INFO] 51 implicit excludes (use -debug for more details).
[INFO] Exclude: CHANGES
[INFO] Exclude: INSTALL.md
[INFO] Exclude: .idea/
[INFO] Exclude: **/*.log
[INFO] Exclude: **/*.patch
[INFO] Exclude: **/.classpath
[INFO] Exclude: **/.project
[INFO] Exclude: **/.idea/**
[INFO] Exclude: **/*.iml
[INFO] Exclude: **/.settings/**
[INFO] Exclude: .metadata/**
[INFO] Exclude: .git/**
[INFO] Exclude: .gitignore
[INFO] Exclude: **/*.crt
[INFO] Exclude: **/*.csr
[INFO] Exclude: **/*.key
[INFO] Exclude: **/authorized_keys
[INFO] Exclude: **/*.war
[INFO] Exclude: **/*.mar
[INFO] Exclude: **/*.jar
[INFO] Exclude: **/*.iso
[INFO] Exclude: **/*.tgz
[INFO] Exclude: **/*.zip
[INFO] Exclude: **/target/**
[INFO] Exclude: **/.vagrant
[INFO] Exclude: awsapi/overlays/**
[INFO] Exclude: build/build.number
[INFO] Exclude: services/console-proxy/server/js/jquery.js
[INFO] Exclude: debian/compat
[INFO] Exclude: debian/control
[INFO] Exclude: debian/dirs
[INFO] Exclude: debian/rules
[INFO] Exclude: deps/XenServerJava/src/com/xensource/xenapi/*.java
[INFO] Exclude: deps/XenServerJava/BSD
[INFO] Exclude: deps/XenServerJava/Makefile
[INFO] Exclude: dist/console-proxy/js/jquery.js
[INFO] Exclude:
plugins/hypervisors/hyperv/DotNet/ServerResource/ServerResource.sln
[INFO] Exclude: plugins/hypervisors/hyperv/DotNet/ServerResource/packages/**
[INFO] Exclude: plugins/hypervisors/hyperv/DotNet/ServerResource/.nuget/**
[INFO] Exclude: plugins/hypervisors/hyperv/DotNet/ServerResource/**/obj/**
[INFO] Exclude: plugins/hypervisors/hyperv/DotNet/ServerResource/**/bin/**
[INFO] Exclude:
plugins/hypervisors/hyperv/DotNet/ServerResource/**/packages.config
[INFO] Exclude:
plugins/hypervisors/hyperv/DotNet/ServerResource/**/App.config
[INFO] Exclude: plugins/hypervisors/hyperv/DotNet/ServerResource/**/*.csproj
[INFO] Exclude: plugins/hypervisors/hyperv/conf/agent.properties
[INFO] Exclude: scripts/vm/systemvm/id_rsa.cloud
[INFO] Exclude: services/console-proxy/server/conf/agent.properties
[INFO] Exclude: services/console-proxy/server/conf/environment.properties
[INFO] Exclude: services/secondary-storage/conf/agent.properties
[INFO] Exclude: services/secondary-storage/conf/environment.properties
[INFO] Exclude:
tools/devcloud/basebuild/puppet-devcloudinitial/files/network.conf
[INFO] Exclude: tools/appliance/definitions/devcloud/*
[INFO] Exclude: tools/appliance/definitions/systemvmtemplate/*
[INFO] Exclude: tools/appliance/definitions/systemvm64template/*
[INFO] Exclude: tools/appliance/definitions/builtin/*
[INFO] Exclude: tools/cli/cloudmonkey.egg-info/*
[INFO] Exclude: tools/devcloud/src/deps/boxes/basebox-build/definition.rb
[INFO] Exclude: tools/devcloud/src/deps/boxes/basebox-build/preseed.cfg
[INFO] Exclude: tools/marvin/Marvin.egg-info/*
[INFO] Exclude: ui/lib/flot/jquery.colorhelpers.js
[INFO] Exclude: ui/lib/flot/jquery.flot.crosshair.js
[INFO] Exclude: ui/lib/flot/jquery.flot.fillbetween.js
[INFO] Exclude: ui/lib/flot/jquery.flot.image.js
[INFO] Exclude: ui/lib/flot/jquery.flot.js
[INFO] Exclude: ui/lib/flot/jquery.flot.navigate.js
[INFO] Exclude: ui/lib/flot/jquery.flot.pie.js
[INFO] Exclude: ui/lib/flot/jquery.flot.resize.js
[INFO] Exclude: ui/lib/flot/jquery.flot.selection.js
[INFO] Exclude: ui/lib/flot/jquery.flot.stack.js
[INFO] Exclude: ui/lib/flot/jquery.flot.symbol.js
[INFO] Exclude: ui/lib/flot/jquery.flot.t

Re: Build failed in Jenkins: cloudstack-rat-master #4166

[Nitin Mehta]

There is a RAT build failure. Check the link [1] for the file that misses
license header. Checking whether RAT build works for your machine at [2]

[1] 
https://builds.apache.org/job/cloudstack-rat-master/4166/artifact/target/ra
t.txt
[2] 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudSt
ack#HowtobuildCloudStack-RAT:ASFLicenseChecking

On 07/03/14 3:03 PM, "Mike Tutkowski"  wrote:

>Hi,
>
>I'm not that familiar with reading these reports, but it claims there was
>a
>Jenkins build failure due to code I checked in.
>
>I ran a full build locally using mvn -P developer,systemvm clean install
>and then tested before checking the code in. Perhaps there is a regression
>test on Jenkins that no longer functions now?
>
>Thanks!
>Mike
>
>-- Forwarded message --
>From: Apache Jenkins Server 
>Date: Fri, Mar 7, 2014 at 3:55 PM
>Subject: Build failed in Jenkins: cloudstack-rat-master #4166
>To: cloudstack-comm...@incubator.apache.org, mike.tutkow...@solidfire.com
>
>
>See 
>
>Changes:
>
>[mike.tutkowski] CLOUDSTACK-6170
>
>--
>Started by an SCM change
>Started by an SCM change
>Building remotely on ubuntu6 in workspace <
>https://builds.apache.org/job/cloudstack-rat-master/ws/>
>Fetching changes from the remote Git repository
>Fetching upstream changes from
>https://git-wip-us.apache.org/repos/asf/cloudstack.git
>Checking out Revision c427e8db1c4294bec93aa9295052950888c0fecf
>(origin/master)
>[cloudstack-rat-master] $ /bin/bash -xe /tmp/hudson6721284311782327396.sh
>+ /home/jenkins/tools/maven/latest2/bin/mvn
>--projects=org.apache.cloudstack:cloudstack
>org.apache.rat:apache-rat-plugin:0.10:check
>[INFO] Scanning for projects...
>[INFO]
>
>[INFO] Building Apache CloudStack
>[INFO]task-segment: [org.apache.rat:apache-rat-plugin:0.10:check]
>[INFO]
>
>[INFO] [apache-rat:check {execution: default-cli}]
>[INFO] 51 implicit excludes (use -debug for more details).
>[INFO] Exclude: CHANGES
>[INFO] Exclude: INSTALL.md
>[INFO] Exclude: .idea/
>[INFO] Exclude: **/*.log
>[INFO] Exclude: **/*.patch
>[INFO] Exclude: **/.classpath
>[INFO] Exclude: **/.project
>[INFO] Exclude: **/.idea/**
>[INFO] Exclude: **/*.iml
>[INFO] Exclude: **/.settings/**
>[INFO] Exclude: .metadata/**
>[INFO] Exclude: .git/**
>[INFO] Exclude: .gitignore
>[INFO] Exclude: **/*.crt
>[INFO] Exclude: **/*.csr
>[INFO] Exclude: **/*.key
>[INFO] Exclude: **/authorized_keys
>[INFO] Exclude: **/*.war
>[INFO] Exclude: **/*.mar
>[INFO] Exclude: **/*.jar
>[INFO] Exclude: **/*.iso
>[INFO] Exclude: **/*.tgz
>[INFO] Exclude: **/*.zip
>[INFO] Exclude: **/target/**
>[INFO] Exclude: **/.vagrant
>[INFO] Exclude: awsapi/overlays/**
>[INFO] Exclude: build/build.number
>[INFO] Exclude: services/console-proxy/server/js/jquery.js
>[INFO] Exclude: debian/compat
>[INFO] Exclude: debian/control
>[INFO] Exclude: debian/dirs
>[INFO] Exclude: debian/rules
>[INFO] Exclude: deps/XenServerJava/src/com/xensource/xenapi/*.java
>[INFO] Exclude: deps/XenServerJava/BSD
>[INFO] Exclude: deps/XenServerJava/Makefile
>[INFO] Exclude: dist/console-proxy/js/jquery.js
>[INFO] Exclude:
>plugins/hypervisors/hyperv/DotNet/ServerResource/ServerResource.sln
>[INFO] Exclude: 
>plugins/hypervisors/hyperv/DotNet/ServerResource/packages/**
>[INFO] Exclude: plugins/hypervisors/hyperv/DotNet/ServerResource/.nuget/**
>[INFO] Exclude: plugins/hypervisors/hyperv/DotNet/ServerResource/**/obj/**
>[INFO] Exclude: plugins/hypervisors/hyperv/DotNet/ServerResource/**/bin/**
>[INFO] Exclude:
>plugins/hypervisors/hyperv/DotNet/ServerResource/**/packages.config
>[INFO] Exclude:
>plugins/hypervisors/hyperv/DotNet/ServerResource/**/App.config
>[INFO] Exclude: 
>plugins/hypervisors/hyperv/DotNet/ServerResource/**/*.csproj
>[INFO] Exclude: plugins/hypervisors/hyperv/conf/agent.properties
>[INFO] Exclude: scripts/vm/systemvm/id_rsa.cloud
>[INFO] Exclude: services/console-proxy/server/conf/agent.properties
>[INFO] Exclude: services/console-proxy/server/conf/environment.properties
>[INFO] Exclude: services/secondary-storage/conf/agent.properties
>[INFO] Exclude: services/secondary-storage/conf/environment.properties
>[INFO] Exclude:
>tools/devcloud/basebuild/puppet-devcloudinitial/files/network.conf
>[INFO] Exclude: tools/appliance/definitions/devcloud/*
>[INFO] Exclude: tools/appliance/definitions/systemvmtemplate/*
>[INFO] Exclude: tools/appliance/definitions/systemvm64template/*
>[INFO] Exclude: tools/appliance/definitions/builtin/*
>[INFO] Exclude: tools/cli/cloudmonkey.egg-info/*
>[INFO] Exclude: tools/devcloud/src/deps/boxes/basebox-build/definition.rb
>[INFO] Exclude: tools/devcloud/src/deps/boxes/basebox-build/preseed.cfg
>[INFO] Exclude: tools/marvin/Marvin.egg-info/*
>[INFO] Exclude: ui/lib/flot/jquery.colorhelpers.js
>[INFO] Exclu

Re: Build failed in Jenkins: cloudstack-rat-master #4166

[Marcus]

Link says this new file is missing license:

Unapproved licenses:

  api/src/com/cloud/offering/DiskOfferingInfo.java

On Fri, Mar 7, 2014 at 4:14 PM, Nitin Mehta  wrote:
> There is a RAT build failure. Check the link [1] for the file that misses
> license header. Checking whether RAT build works for your machine at [2]
>
> [1]
> https://builds.apache.org/job/cloudstack-rat-master/4166/artifact/target/ra
> t.txt
> [2]
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudSt
> ack#HowtobuildCloudStack-RAT:ASFLicenseChecking
>
> On 07/03/14 3:03 PM, "Mike Tutkowski"  wrote:
>
>>Hi,
>>
>>I'm not that familiar with reading these reports, but it claims there was
>>a
>>Jenkins build failure due to code I checked in.
>>
>>I ran a full build locally using mvn -P developer,systemvm clean install
>>and then tested before checking the code in. Perhaps there is a regression
>>test on Jenkins that no longer functions now?
>>
>>Thanks!
>>Mike
>>
>>-- Forwarded message --
>>From: Apache Jenkins Server 
>>Date: Fri, Mar 7, 2014 at 3:55 PM
>>Subject: Build failed in Jenkins: cloudstack-rat-master #4166
>>To: cloudstack-comm...@incubator.apache.org, mike.tutkow...@solidfire.com
>>
>>
>>See 
>>
>>Changes:
>>
>>[mike.tutkowski] CLOUDSTACK-6170
>>
>>--
>>Started by an SCM change
>>Started by an SCM change
>>Building remotely on ubuntu6 in workspace <
>>https://builds.apache.org/job/cloudstack-rat-master/ws/>
>>Fetching changes from the remote Git repository
>>Fetching upstream changes from
>>https://git-wip-us.apache.org/repos/asf/cloudstack.git
>>Checking out Revision c427e8db1c4294bec93aa9295052950888c0fecf
>>(origin/master)
>>[cloudstack-rat-master] $ /bin/bash -xe /tmp/hudson6721284311782327396.sh
>>+ /home/jenkins/tools/maven/latest2/bin/mvn
>>--projects=org.apache.cloudstack:cloudstack
>>org.apache.rat:apache-rat-plugin:0.10:check
>>[INFO] Scanning for projects...
>>[INFO]
>>
>>[INFO] Building Apache CloudStack
>>[INFO]task-segment: [org.apache.rat:apache-rat-plugin:0.10:check]
>>[INFO]
>>
>>[INFO] [apache-rat:check {execution: default-cli}]
>>[INFO] 51 implicit excludes (use -debug for more details).
>>[INFO] Exclude: CHANGES
>>[INFO] Exclude: INSTALL.md
>>[INFO] Exclude: .idea/
>>[INFO] Exclude: **/*.log
>>[INFO] Exclude: **/*.patch
>>[INFO] Exclude: **/.classpath
>>[INFO] Exclude: **/.project
>>[INFO] Exclude: **/.idea/**
>>[INFO] Exclude: **/*.iml
>>[INFO] Exclude: **/.settings/**
>>[INFO] Exclude: .metadata/**
>>[INFO] Exclude: .git/**
>>[INFO] Exclude: .gitignore
>>[INFO] Exclude: **/*.crt
>>[INFO] Exclude: **/*.csr
>>[INFO] Exclude: **/*.key
>>[INFO] Exclude: **/authorized_keys
>>[INFO] Exclude: **/*.war
>>[INFO] Exclude: **/*.mar
>>[INFO] Exclude: **/*.jar
>>[INFO] Exclude: **/*.iso
>>[INFO] Exclude: **/*.tgz
>>[INFO] Exclude: **/*.zip
>>[INFO] Exclude: **/target/**
>>[INFO] Exclude: **/.vagrant
>>[INFO] Exclude: awsapi/overlays/**
>>[INFO] Exclude: build/build.number
>>[INFO] Exclude: services/console-proxy/server/js/jquery.js
>>[INFO] Exclude: debian/compat
>>[INFO] Exclude: debian/control
>>[INFO] Exclude: debian/dirs
>>[INFO] Exclude: debian/rules
>>[INFO] Exclude: deps/XenServerJava/src/com/xensource/xenapi/*.java
>>[INFO] Exclude: deps/XenServerJava/BSD
>>[INFO] Exclude: deps/XenServerJava/Makefile
>>[INFO] Exclude: dist/console-proxy/js/jquery.js
>>[INFO] Exclude:
>>plugins/hypervisors/hyperv/DotNet/ServerResource/ServerResource.sln
>>[INFO] Exclude:
>>plugins/hypervisors/hyperv/DotNet/ServerResource/packages/**
>>[INFO] Exclude: plugins/hypervisors/hyperv/DotNet/ServerResource/.nuget/**
>>[INFO] Exclude: plugins/hypervisors/hyperv/DotNet/ServerResource/**/obj/**
>>[INFO] Exclude: plugins/hypervisors/hyperv/DotNet/ServerResource/**/bin/**
>>[INFO] Exclude:
>>plugins/hypervisors/hyperv/DotNet/ServerResource/**/packages.config
>>[INFO] Exclude:
>>plugins/hypervisors/hyperv/DotNet/ServerResource/**/App.config
>>[INFO] Exclude:
>>plugins/hypervisors/hyperv/DotNet/ServerResource/**/*.csproj
>>[INFO] Exclude: plugins/hypervisors/hyperv/conf/agent.properties
>>[INFO] Exclude: scripts/vm/systemvm/id_rsa.cloud
>>[INFO] Exclude: services/console-proxy/server/conf/agent.properties
>>[INFO] Exclude: services/console-proxy/server/conf/environment.properties
>>[INFO] Exclude: services/secondary-storage/conf/agent.properties
>>[INFO] Exclude: services/secondary-storage/conf/environment.properties
>>[INFO] Exclude:
>>tools/devcloud/basebuild/puppet-devcloudinitial/files/network.conf
>>[INFO] Exclude: tools/appliance/definitions/devcloud/*
>>[INFO] Exclude: tools/appliance/definitions/systemvmtemplate/*
>>[INFO] Exclude: tools/appliance/definitions/systemvm64template/*
>>[INFO] Exclude: tools/appliance/definitions/builtin/*
>>[INFO] Excl

libvirt-java upgrade

[Marcus]

Wido,
I'm seeing this in Ubuntu 12.04 after commit



2014-02-10 01:19:16,793 DEBUG [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-2:null) Volume
/mnt/2fe9a944-505e-38cb-bf87-72623634be4a/e47e6501-c8ae-41a7-9abc-0f7fdad5fb30
can be resized by libvirt. Asking libvirt to resize the volume.
2014-02-10 01:19:16,800 WARN  [cloud.agent.Agent]
(agentRequest-Handler-2:null) Caught:
java.lang.UnsatisfiedLinkError: Error looking up function
'virStorageVolResize': /usr/lib/libvirt.so.0.9.8: undefined symbol:
virStorageVolResize
at com.sun.jna.Function.(Function.java:208)
at com.sun.jna.NativeLibrary.getFunction(NativeLibrary.java:536)
at com.sun.jna.NativeLibrary.getFunction(NativeLibrary.java:513)
at com.sun.jna.NativeLibrary.getFunction(NativeLibrary.java:499)
at com.sun.jna.Library$Handler.invoke(Library.java:199)
at com.sun.proxy.$Proxy0.virStorageVolResize(Unknown Source)
at org.libvirt.StorageVol.resize(Unknown Source)
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:1808)
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1331)
at com.cloud.agent.Agent.processRequest(Agent.java:501)
at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808)
at com.cloud.utils.nio.Task.run(Task.java:84)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)

Re: libvirt-java upgrade

[Marcus]

Hrm... sent instead of pasted. Commit

commit 3989d6c48118f31464c87c71b6279a11eb13eb35
Author: Wido den Hollander 
Date:   Mon Feb 3 17:04:11 2014 +0100

kvm: Resize volumes using libvirt

virsh blockresize works on this system, so I can only assume that the
libvirt.so.0.9.8 that ships with Ubuntu 12.04 doesn't support
virStorageVolResize.

# strings /usr/lib/libvirt.so.0.9.8  | grep virStorageVolR
virStorageVolRef
virStorageVolRef
virStorageVolRef

On Fri, Mar 7, 2014 at 4:28 PM, Marcus  wrote:
> Wido,
> I'm seeing this in Ubuntu 12.04 after commit
>
>
>
> 2014-02-10 01:19:16,793 DEBUG [kvm.resource.LibvirtComputingResource]
> (agentRequest-Handler-2:null) Volume
> /mnt/2fe9a944-505e-38cb-bf87-72623634be4a/e47e6501-c8ae-41a7-9abc-0f7fdad5fb30
> can be resized by libvirt. Asking libvirt to resize the volume.
> 2014-02-10 01:19:16,800 WARN  [cloud.agent.Agent]
> (agentRequest-Handler-2:null) Caught:
> java.lang.UnsatisfiedLinkError: Error looking up function
> 'virStorageVolResize': /usr/lib/libvirt.so.0.9.8: undefined symbol:
> virStorageVolResize
> at com.sun.jna.Function.(Function.java:208)
> at com.sun.jna.NativeLibrary.getFunction(NativeLibrary.java:536)
> at com.sun.jna.NativeLibrary.getFunction(NativeLibrary.java:513)
> at com.sun.jna.NativeLibrary.getFunction(NativeLibrary.java:499)
> at com.sun.jna.Library$Handler.invoke(Library.java:199)
> at com.sun.proxy.$Proxy0.virStorageVolResize(Unknown Source)
> at org.libvirt.StorageVol.resize(Unknown Source)
> at 
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:1808)
> at 
> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1331)
> at com.cloud.agent.Agent.processRequest(Agent.java:501)
> at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808)
> at com.cloud.utils.nio.Task.run(Task.java:84)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:744)

master issue calling volume resize via libvirt - Was: libvirt-java upgrade

[Marcus]

On Fri, Mar 7, 2014 at 4:30 PM, Marcus  wrote:
> Hrm... sent instead of pasted. Commit
>
> commit 3989d6c48118f31464c87c71b6279a11eb13eb35
> Author: Wido den Hollander 
> Date:   Mon Feb 3 17:04:11 2014 +0100
>
> kvm: Resize volumes using libvirt
>
> virsh blockresize works on this system, so I can only assume that the
> libvirt.so.0.9.8 that ships with Ubuntu 12.04 doesn't support
> virStorageVolResize.
>
> # strings /usr/lib/libvirt.so.0.9.8  | grep virStorageVolR
> virStorageVolRef
> virStorageVolRef
> virStorageVolRef
>
> On Fri, Mar 7, 2014 at 4:28 PM, Marcus  wrote:
>> Wido,
>> I'm seeing this in Ubuntu 12.04 after commit
>>
>>
>>
>> 2014-02-10 01:19:16,793 DEBUG [kvm.resource.LibvirtComputingResource]
>> (agentRequest-Handler-2:null) Volume
>> /mnt/2fe9a944-505e-38cb-bf87-72623634be4a/e47e6501-c8ae-41a7-9abc-0f7fdad5fb30
>> can be resized by libvirt. Asking libvirt to resize the volume.
>> 2014-02-10 01:19:16,800 WARN  [cloud.agent.Agent]
>> (agentRequest-Handler-2:null) Caught:
>> java.lang.UnsatisfiedLinkError: Error looking up function
>> 'virStorageVolResize': /usr/lib/libvirt.so.0.9.8: undefined symbol:
>> virStorageVolResize
>> at com.sun.jna.Function.(Function.java:208)
>> at com.sun.jna.NativeLibrary.getFunction(NativeLibrary.java:536)
>> at com.sun.jna.NativeLibrary.getFunction(NativeLibrary.java:513)
>> at com.sun.jna.NativeLibrary.getFunction(NativeLibrary.java:499)
>> at com.sun.jna.Library$Handler.invoke(Library.java:199)
>> at com.sun.proxy.$Proxy0.virStorageVolResize(Unknown Source)
>> at org.libvirt.StorageVol.resize(Unknown Source)
>> at 
>> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(LibvirtComputingResource.java:1808)
>> at 
>> com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1331)
>> at com.cloud.agent.Agent.processRequest(Agent.java:501)
>> at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808)
>> at com.cloud.utils.nio.Task.run(Task.java:84)
>> at 
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>> at 
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> at java.lang.Thread.run(Thread.java:744)

Re: Build failed in Jenkins: cloudstack-rat-master #4166

[Mike Tutkowski]

Great, guys - thanks!

That makes sense. I added a small class to wrap some commonly passed
parameters and didn't add the license header.


On Fri, Mar 7, 2014 at 4:21 PM, Marcus  wrote:

> Link says this new file is missing license:
>
> Unapproved licenses:
>
>   api/src/com/cloud/offering/DiskOfferingInfo.java
>
> On Fri, Mar 7, 2014 at 4:14 PM, Nitin Mehta 
> wrote:
> > There is a RAT build failure. Check the link [1] for the file that misses
> > license header. Checking whether RAT build works for your machine at [2]
> >
> > [1]
> >
> https://builds.apache.org/job/cloudstack-rat-master/4166/artifact/target/ra
> > t.txt
> > [2]
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudSt
> > ack#HowtobuildCloudStack-RAT:ASFLicenseChecking
> >
> > On 07/03/14 3:03 PM, "Mike Tutkowski" 
> wrote:
> >
> >>Hi,
> >>
> >>I'm not that familiar with reading these reports, but it claims there was
> >>a
> >>Jenkins build failure due to code I checked in.
> >>
> >>I ran a full build locally using mvn -P developer,systemvm clean install
> >>and then tested before checking the code in. Perhaps there is a
> regression
> >>test on Jenkins that no longer functions now?
> >>
> >>Thanks!
> >>Mike
> >>
> >>-- Forwarded message --
> >>From: Apache Jenkins Server 
> >>Date: Fri, Mar 7, 2014 at 3:55 PM
> >>Subject: Build failed in Jenkins: cloudstack-rat-master #4166
> >>To: cloudstack-comm...@incubator.apache.org,
> mike.tutkow...@solidfire.com
> >>
> >>
> >>See 
> >>
> >>Changes:
> >>
> >>[mike.tutkowski] CLOUDSTACK-6170
> >>
> >>--
> >>Started by an SCM change
> >>Started by an SCM change
> >>Building remotely on ubuntu6 in workspace <
> >>https://builds.apache.org/job/cloudstack-rat-master/ws/>
> >>Fetching changes from the remote Git repository
> >>Fetching upstream changes from
> >>https://git-wip-us.apache.org/repos/asf/cloudstack.git
> >>Checking out Revision c427e8db1c4294bec93aa9295052950888c0fecf
> >>(origin/master)
> >>[cloudstack-rat-master] $ /bin/bash -xe /tmp/hudson6721284311782327396.sh
> >>+ /home/jenkins/tools/maven/latest2/bin/mvn
> >>--projects=org.apache.cloudstack:cloudstack
> >>org.apache.rat:apache-rat-plugin:0.10:check
> >>[INFO] Scanning for projects...
> >>[INFO]
> >>
> >>[INFO] Building Apache CloudStack
> >>[INFO]task-segment: [org.apache.rat:apache-rat-plugin:0.10:check]
> >>[INFO]
> >>
> >>[INFO] [apache-rat:check {execution: default-cli}]
> >>[INFO] 51 implicit excludes (use -debug for more details).
> >>[INFO] Exclude: CHANGES
> >>[INFO] Exclude: INSTALL.md
> >>[INFO] Exclude: .idea/
> >>[INFO] Exclude: **/*.log
> >>[INFO] Exclude: **/*.patch
> >>[INFO] Exclude: **/.classpath
> >>[INFO] Exclude: **/.project
> >>[INFO] Exclude: **/.idea/**
> >>[INFO] Exclude: **/*.iml
> >>[INFO] Exclude: **/.settings/**
> >>[INFO] Exclude: .metadata/**
> >>[INFO] Exclude: .git/**
> >>[INFO] Exclude: .gitignore
> >>[INFO] Exclude: **/*.crt
> >>[INFO] Exclude: **/*.csr
> >>[INFO] Exclude: **/*.key
> >>[INFO] Exclude: **/authorized_keys
> >>[INFO] Exclude: **/*.war
> >>[INFO] Exclude: **/*.mar
> >>[INFO] Exclude: **/*.jar
> >>[INFO] Exclude: **/*.iso
> >>[INFO] Exclude: **/*.tgz
> >>[INFO] Exclude: **/*.zip
> >>[INFO] Exclude: **/target/**
> >>[INFO] Exclude: **/.vagrant
> >>[INFO] Exclude: awsapi/overlays/**
> >>[INFO] Exclude: build/build.number
> >>[INFO] Exclude: services/console-proxy/server/js/jquery.js
> >>[INFO] Exclude: debian/compat
> >>[INFO] Exclude: debian/control
> >>[INFO] Exclude: debian/dirs
> >>[INFO] Exclude: debian/rules
> >>[INFO] Exclude: deps/XenServerJava/src/com/xensource/xenapi/*.java
> >>[INFO] Exclude: deps/XenServerJava/BSD
> >>[INFO] Exclude: deps/XenServerJava/Makefile
> >>[INFO] Exclude: dist/console-proxy/js/jquery.js
> >>[INFO] Exclude:
> >>plugins/hypervisors/hyperv/DotNet/ServerResource/ServerResource.sln
> >>[INFO] Exclude:
> >>plugins/hypervisors/hyperv/DotNet/ServerResource/packages/**
> >>[INFO] Exclude:
> plugins/hypervisors/hyperv/DotNet/ServerResource/.nuget/**
> >>[INFO] Exclude:
> plugins/hypervisors/hyperv/DotNet/ServerResource/**/obj/**
> >>[INFO] Exclude:
> plugins/hypervisors/hyperv/DotNet/ServerResource/**/bin/**
> >>[INFO] Exclude:
> >>plugins/hypervisors/hyperv/DotNet/ServerResource/**/packages.config
> >>[INFO] Exclude:
> >>plugins/hypervisors/hyperv/DotNet/ServerResource/**/App.config
> >>[INFO] Exclude:
> >>plugins/hypervisors/hyperv/DotNet/ServerResource/**/*.csproj
> >>[INFO] Exclude: plugins/hypervisors/hyperv/conf/agent.properties
> >>[INFO] Exclude: scripts/vm/systemvm/id_rsa.cloud
> >>[INFO] Exclude: services/console-proxy/server/conf/agent.properties
> >>[INFO] Exclude: services/console-proxy/server/conf/environment.properties
> >>[INFO] Exclude: services/secondary-s

Re: Build failed in Jenkins: cloudstack-rat-master #4166

[Nitin Mehta]

It would make sense to have one single command which could do it all for
the devs, before committing code.

On 07/03/14 3:41 PM, "Mike Tutkowski"  wrote:

>Great, guys - thanks!
>
>That makes sense. I added a small class to wrap some commonly passed
>parameters and didn't add the license header.
>
>
>On Fri, Mar 7, 2014 at 4:21 PM, Marcus  wrote:
>
>> Link says this new file is missing license:
>>
>> Unapproved licenses:
>>
>>   api/src/com/cloud/offering/DiskOfferingInfo.java
>>
>> On Fri, Mar 7, 2014 at 4:14 PM, Nitin Mehta 
>> wrote:
>> > There is a RAT build failure. Check the link [1] for the file that
>>misses
>> > license header. Checking whether RAT build works for your machine at
>>[2]
>> >
>> > [1]
>> >
>> 
>>https://builds.apache.org/job/cloudstack-rat-master/4166/artifact/target/
>>ra
>> > t.txt
>> > [2]
>> >
>> 
>>https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+Cloud
>>St
>> > ack#HowtobuildCloudStack-RAT:ASFLicenseChecking
>> >
>> > On 07/03/14 3:03 PM, "Mike Tutkowski" 
>> wrote:
>> >
>> >>Hi,
>> >>
>> >>I'm not that familiar with reading these reports, but it claims there
>>was
>> >>a
>> >>Jenkins build failure due to code I checked in.
>> >>
>> >>I ran a full build locally using mvn -P developer,systemvm clean
>>install
>> >>and then tested before checking the code in. Perhaps there is a
>> regression
>> >>test on Jenkins that no longer functions now?
>> >>
>> >>Thanks!
>> >>Mike
>> >>
>> >>-- Forwarded message --
>> >>From: Apache Jenkins Server 
>> >>Date: Fri, Mar 7, 2014 at 3:55 PM
>> >>Subject: Build failed in Jenkins: cloudstack-rat-master #4166
>> >>To: cloudstack-comm...@incubator.apache.org,
>> mike.tutkow...@solidfire.com
>> >>
>> >>
>> >>See 
>> >>
>> >>Changes:
>> >>
>> >>[mike.tutkowski] CLOUDSTACK-6170
>> >>
>> >>--
>> >>Started by an SCM change
>> >>Started by an SCM change
>> >>Building remotely on ubuntu6 in workspace <
>> >>https://builds.apache.org/job/cloudstack-rat-master/ws/>
>> >>Fetching changes from the remote Git repository
>> >>Fetching upstream changes from
>> >>https://git-wip-us.apache.org/repos/asf/cloudstack.git
>> >>Checking out Revision c427e8db1c4294bec93aa9295052950888c0fecf
>> >>(origin/master)
>> >>[cloudstack-rat-master] $ /bin/bash -xe
>>/tmp/hudson6721284311782327396.sh
>> >>+ /home/jenkins/tools/maven/latest2/bin/mvn
>> >>--projects=org.apache.cloudstack:cloudstack
>> >>org.apache.rat:apache-rat-plugin:0.10:check
>> >>[INFO] Scanning for projects...
>> >>[INFO]
>> 
---
-
>> >>[INFO] Building Apache CloudStack
>> >>[INFO]task-segment: [org.apache.rat:apache-rat-plugin:0.10:check]
>> >>[INFO]
>> 
---
-
>> >>[INFO] [apache-rat:check {execution: default-cli}]
>> >>[INFO] 51 implicit excludes (use -debug for more details).
>> >>[INFO] Exclude: CHANGES
>> >>[INFO] Exclude: INSTALL.md
>> >>[INFO] Exclude: .idea/
>> >>[INFO] Exclude: **/*.log
>> >>[INFO] Exclude: **/*.patch
>> >>[INFO] Exclude: **/.classpath
>> >>[INFO] Exclude: **/.project
>> >>[INFO] Exclude: **/.idea/**
>> >>[INFO] Exclude: **/*.iml
>> >>[INFO] Exclude: **/.settings/**
>> >>[INFO] Exclude: .metadata/**
>> >>[INFO] Exclude: .git/**
>> >>[INFO] Exclude: .gitignore
>> >>[INFO] Exclude: **/*.crt
>> >>[INFO] Exclude: **/*.csr
>> >>[INFO] Exclude: **/*.key
>> >>[INFO] Exclude: **/authorized_keys
>> >>[INFO] Exclude: **/*.war
>> >>[INFO] Exclude: **/*.mar
>> >>[INFO] Exclude: **/*.jar
>> >>[INFO] Exclude: **/*.iso
>> >>[INFO] Exclude: **/*.tgz
>> >>[INFO] Exclude: **/*.zip
>> >>[INFO] Exclude: **/target/**
>> >>[INFO] Exclude: **/.vagrant
>> >>[INFO] Exclude: awsapi/overlays/**
>> >>[INFO] Exclude: build/build.number
>> >>[INFO] Exclude: services/console-proxy/server/js/jquery.js
>> >>[INFO] Exclude: debian/compat
>> >>[INFO] Exclude: debian/control
>> >>[INFO] Exclude: debian/dirs
>> >>[INFO] Exclude: debian/rules
>> >>[INFO] Exclude: deps/XenServerJava/src/com/xensource/xenapi/*.java
>> >>[INFO] Exclude: deps/XenServerJava/BSD
>> >>[INFO] Exclude: deps/XenServerJava/Makefile
>> >>[INFO] Exclude: dist/console-proxy/js/jquery.js
>> >>[INFO] Exclude:
>> >>plugins/hypervisors/hyperv/DotNet/ServerResource/ServerResource.sln
>> >>[INFO] Exclude:
>> >>plugins/hypervisors/hyperv/DotNet/ServerResource/packages/**
>> >>[INFO] Exclude:
>> plugins/hypervisors/hyperv/DotNet/ServerResource/.nuget/**
>> >>[INFO] Exclude:
>> plugins/hypervisors/hyperv/DotNet/ServerResource/**/obj/**
>> >>[INFO] Exclude:
>> plugins/hypervisors/hyperv/DotNet/ServerResource/**/bin/**
>> >>[INFO] Exclude:
>> >>plugins/hypervisors/hyperv/DotNet/ServerResource/**/packages.config
>> >>[INFO] Exclude:
>> >>plugins/hypervisors/hyperv/DotNet/ServerResource/**/App.config
>> >>[INFO] Exclude:
>> >>plugins/hypervisors/hyperv/DotNet/ServerResour

Build failed in Jenkins: build-master-slowbuild #380

[jenkins]

See 

Changes:

[mike.tutkowski] CLOUDSTACK-6170

--
[...truncated 18117 lines...]

Tests run: 4, Failures: 0, Errors: 0, Skipped: 0

[INFO] 
[INFO] <<< cobertura-maven-plugin:2.6:cobertura (default-cli) @ cloud-awsapi <<<
[INFO] 
[INFO] --- cobertura-maven-plugin:2.6:cobertura (default-cli) @ cloud-awsapi ---
[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/amazon/ec2/AmazonEC2SkeletonInterface.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/amazon/s3/AmazonS3SkeletonInterface.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/model/SAcl.java.  Ensure this class was instrumented, and this 
data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/model/SBucket.java.  Ensure this class was instrumented, and 
this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/model/SHost.java.  Ensure this class was instrumented, and 
this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/BucketPolicyDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackAccountDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackConfigurationDao.java.  Ensure this 
class was instrumented, and this data file contains the instrumentation 
information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackSvcOfferingDao.java.  Ensure this class 
was instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackUserDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MHostDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MHostMountDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MultiPartPartsDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MultiPartUploadsDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MultipartMetaDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cob

unable to schedule async job, duplicate primary key

[Marcus]

I've been randomly hitting this with my master testing, and I'm unsure
if it's something strange in my test environment, or if somebody has
been working on the async job handler and there's some sort of race
condition. I saw it first when trying to destroy a vm, then during a
test run with volume detach.

2014-02-10 02:29:10,865 WARN  [jobs.impl.AsyncJobManagerImpl]
(Job-Executor-92:Job-159 ctx-7198b697) Unable to schedule async job
for command com.cloud.storage.VmWorkDetachVolume, unexpected
exception.
javax.persistence.EntityExistsException: Entity already exists:
at com.cloud.utils.db.GenericDaoBase.persist(GenericDaoBase.java:1398)
at 
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$1.doInTransaction(AsyncJobManagerImpl.java:193)
at 
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$1.doInTransaction(AsyncJobManagerImpl.java:189)
at com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:49)
at com.cloud.utils.db.Transaction.execute(Transaction.java:37)
at com.cloud.utils.db.Transaction.execute(Transaction.java:46)
at 
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl.submitAsyncJob(AsyncJobManagerImpl.java:189)
at 
com.cloud.storage.VolumeApiServiceImpl$4.doInTransaction(VolumeApiServiceImpl.java:2215)
at 
com.cloud.storage.VolumeApiServiceImpl$4.doInTransaction(VolumeApiServiceImpl.java:2191)
at com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:49)
at com.cloud.utils.db.Transaction.execute(Transaction.java:37)
at com.cloud.utils.db.Transaction.execute(Transaction.java:46)
at 
com.cloud.storage.VolumeApiServiceImpl.detachVolumeFromVmThroughJobQueue(VolumeApiServiceImpl.java:2191)
at 
com.cloud.storage.VolumeApiServiceImpl.detachVolumeFromVM(VolumeApiServiceImpl.java:1349)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at 
org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
at com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
at 
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:91)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at 
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at com.sun.proxy.$Proxy179.detachVolumeFromVM(Unknown Source)
at 
org.apache.cloudstack.api.command.user.volume.DetachVolumeCmd.execute(DetachVolumeCmd.java:138)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:168)
at com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:100)
at 
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:488)
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(DefaultManagedContext.java:103)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at 
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:445)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: 
com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException:
Duplicate entry '160' for key 'PRIMARY'
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at com.mysql.jdbc.Ut

Re: [DISCUSS] realhostip.com going away

[Erik Weber]

I planned on looking at the Lua part of PowerDNS for this :-)

-- 
Erik Weber
7. mars 2014 22:48 skrev "Nux!"  følgende:

> On 07.03.2014 21:30, Chiradeep Vittal wrote:
>
>> You should require 1 record for the ACTUAL public IP used by the
>> ConsoleProxy VM.
>>
>
> I know, but if the VM is destroyed or an additional one is spawned it
> could have ANY IP.. I mean, I really don't want to track this kind of
> stuff, doesn't "scale".
> Maybe the Java DNS server could be replaced by Powerdns+pipe backend, will
> have to dig into this.
>
> --
> Sent from the Delta quadrant using Borg technology!
>
> Nux!
> www.nux.ro
>

cherry-pick to 4.3 request

[Alena Prokharchyk]

Animesh, could you please cherry-pick one more commit for VPC, from forward to 
4.3 branch?

164ea3e84f6f282006e66725f22cd2246f0be8f8

CloudStackCLOUDSTACK-6214
VPC: when guest network is in Setup state, on its initial nicPlug to the VR, 
corresponding network rules are not getting applied

-Alena.

Build failed in Jenkins: build-master-slowbuild #381

[jenkins]

See 

Changes:

[mike.tutkowski] Adding license header

[nitin.mehta] CLOUDSTACK-5478: Enable publishing uuid for all the async apis in 
the CallContext.

--
[...truncated 18097 lines...]

Tests run: 4, Failures: 0, Errors: 0, Skipped: 0

[INFO] 
[INFO] <<< cobertura-maven-plugin:2.6:cobertura (default-cli) @ cloud-awsapi <<<
[INFO] 
[INFO] --- cobertura-maven-plugin:2.6:cobertura (default-cli) @ cloud-awsapi ---
[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/amazon/ec2/AmazonEC2SkeletonInterface.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/amazon/s3/AmazonS3SkeletonInterface.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/model/SAcl.java.  Ensure this class was instrumented, and this 
data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/model/SBucket.java.  Ensure this class was instrumented, and 
this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/model/SHost.java.  Ensure this class was instrumented, and 
this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/BucketPolicyDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackAccountDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackConfigurationDao.java.  Ensure this 
class was instrumented, and this data file contains the instrumentation 
information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackSvcOfferingDao.java.  Ensure this class 
was instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackUserDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MHostDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MHostMountDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MultiPartPartsDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MultiPartUploadsDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MultipartMetaDao.java.  Ensure this class was 
instrumented, 

RE: Just checked in a minor change to the DB

[Rajesh Battala]

Just a thought, instead of sending mail manually, can't we have a git hook to 
send out mail to dev list when there is a commit to schema files.
So that git will take care of informing the dev about new schema changes.!

Thanks
Rajesh Battala

-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] 
Sent: Saturday, March 8, 2014 3:21 AM
To: dev
Subject: Re: Just checked in a minor change to the DB

saw, good, will do some more if I think of them as well, as well as add to the 
descriptions

On Fri, Mar 7, 2014 at 9:29 PM, Mike Tutkowski  
wrote:
> I went ahead and added to the Wiki page you created a few more tags 
> that I've seen us use from time to time.
>
>
> On Fri, Mar 7, 2014 at 12:37 PM, Mike Tutkowski < 
> mike.tutkow...@solidfire.com> wrote:
>
>> Great! Thanks, Daan
>>
>> I also agree that it would be useful info to have in commit messages.
>>
>>
>> On Fri, Mar 7, 2014 at 12:14 PM, Daan Hoogland 
>> wrote:
>>
>>> I created
>>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/mail+tags+to+
>>> use+to+help+each+other
>>> below the path
>>> Apache Cloudstack / Home / Community / Getting Help
>>>
>>>
>>> On Fri, Mar 7, 2014 at 8:03 PM, Daan Hoogland 
>>> 
>>> wrote:
>>> > I had a quick look. Nothing found but a lot of hits on tags of course.
>>> > I'll try to find a place to create the page and start chapters on 
>>> > Dev and Users
>>> >
>>> >
>>> > On Fri, Mar 7, 2014 at 7:54 PM, Daan Hoogland 
>>> > 
>>> wrote:
>>> >> No, but I do know that it might be useful to use them in commit 
>>> >> comments as well. If you so feel inclined you can refer to that 
>>> >> as well
>>> >>
>>> >> On Fri, Mar 7, 2014 at 7:41 PM, Mike Tutkowski 
>>> >>  wrote:
>>> >>> Does anyone know if our e-mail tags are documented on the Wiki?
>>> >>>
>>> >>>
>>> >>> On Fri, Mar 7, 2014 at 11:36 AM, Mike Tutkowski < 
>>> >>> mike.tutkow...@solidfire.com> wrote:
>>> >>>
>>>  That sounds good, Daan.
>>> 
>>>  Let's use both tags.
>>> 
>>>  Thanks!
>>> 
>>> 
>>>  On Fri, Mar 7, 2014 at 9:33 AM, Daan Hoogland <
>>> daan.hoogl...@gmail.com>wrote:
>>> 
>>> > Absolutaly,
>>> >
>>> > But I meant for us to use both tags. I checked in a commit 
>>> > (that I didn't give a head up on) for a colleague in which a 
>>> > CloudRuntimeException was removed to be more consistent with 
>>> > the
>>> rest
>>> > of the code. It was only effecting th upgrade process in this 
>>> > case
>>> but
>>> > still;
>>> > [BEHAVIORAL-CHANGE] was caused. Of course these heads-up will 
>>> > always be an inter developer courtesy but here is mine (hidden 
>>> > in some one elses thread;)
>>> >
>>> > so in short i meant and and not or, Daan
>>> >
>>> >
>>> > On Fri, Mar 7, 2014 at 4:20 PM, Mike Tutkowski
>>> >  wrote:
>>> > > I like either tag.
>>> > >
>>> > > Since DB changes are the most likely to lead to breaking other
>>> people's
>>> > > environments, maybe we should go with that one:
>>> > >
>>> > > [DB-CHANGE]
>>> > >
>>> > > Ideally we'd provide the branch, commit SHA, and a manual way
>>> around
>>> > it, if
>>> > > there is something simple (like in my case yesterday, simply
>>> deleting
>>> > and
>>> > > re-creating two views). If there's no easy way around it, then
>>> don't
>>> > bother
>>> > > providing that.
>>> > >
>>> > > Sound reasonable?
>>> > >
>>> > >
>>> > > On Fri, Mar 7, 2014 at 2:12 AM, Daan Hoogland <
>>> daan.hoogl...@gmail.com
>>> > >wrote:
>>> > >
>>> > >> Thanks for the heads up Mike,
>>> > >>
>>> > >> As discussed in your thread [1]. You are eating your own dogfood
>>> here.
>>> > >> I was checking in a minor change to the upgrade handling
>>> yesterday and
>>> > >> decided not to bother everyone with it. evil me. In that thread
>>> we
>>> > >> didn't dicide on a tag, yet.
>>> > >>
>>> > >> I would suggest
>>> > >> [DB-CHANGE] and
>>> > >> [BEHAVIORAL-CHANGE]
>>> > >>
>>> > >> [1] http://markmail.org/message/r7wv36o356nolq7f
>>> > >>
>>> > >> On Thu, Mar 6, 2014 at 9:05 PM, Mike Tutkowski
>>> > >>  wrote:
>>> > >> > Hi everyone,
>>> > >> >
>>> > >> > Just wanted to give you a heads up that I made a minor change
>>> to two
>>> > >> views
>>> > >> > in the DB in 9b66866dc2085486f465159cbd446ac03e266a2c:
>>> > >> >
>>> > >> > service_offering_view and disk_offering_view
>>> > >> >
>>> > >> > I added some columns to these views so I could present
>>> additional
>>> > info in
>>> > >> > the GUI.
>>> > >> >
>>> > >> > If you want to bring these two views up to date, just run the
>>> > following
>>> > >> SQL:
>>> > >> >
>>> > >> > DROP VIEW IF EXISTS `cloud`.`disk_offering_view`;
>>> > >> > CREATE VIEW `cloud`.`disk_offering_view` AS
>>> > >> > select
>>> > >> > disk_offe

Build failed in Jenkins: build-master-slowbuild #382

[jenkins]

See 

--
[...truncated 18097 lines...]

Tests run: 4, Failures: 0, Errors: 0, Skipped: 0

[INFO] 
[INFO] <<< cobertura-maven-plugin:2.6:cobertura (default-cli) @ cloud-awsapi <<<
[INFO] 
[INFO] --- cobertura-maven-plugin:2.6:cobertura (default-cli) @ cloud-awsapi ---
[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/amazon/ec2/AmazonEC2SkeletonInterface.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/amazon/s3/AmazonS3SkeletonInterface.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/model/SAcl.java.  Ensure this class was instrumented, and this 
data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/model/SBucket.java.  Ensure this class was instrumented, and 
this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/model/SHost.java.  Ensure this class was instrumented, and 
this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/BucketPolicyDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackAccountDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackConfigurationDao.java.  Ensure this 
class was instrumented, and this data file contains the instrumentation 
information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackSvcOfferingDao.java.  Ensure this class 
was instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/CloudStackUserDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MHostDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MHostMountDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MultiPartPartsDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MultiPartUploadsDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does not contain instrumentation information for the file 
com/cloud/bridge/persist/dao/MultipartMetaDao.java.  Ensure this class was 
instrumented, and this data file contains the instrumentation information.
[cobertura] INFO  [main] net.sourceforge.cobertura.reporting.html.HTMLReport - 
Data file does 

Re: Just checked in a minor change to the DB

[Mike Tutkowski]

We could, but some schema changes won't impact others.

For example, if I removed a column and took out the corresponding Java code
and you updated your code, the new code wouldn't fail against your old
schema.

People might also update the schema and check it in, but not update the
Java code until later.

Perhaps these are corner cases and it would be fine to have Git notify us?

What do people think?


On Fri, Mar 7, 2014 at 10:51 PM, Rajesh Battala
wrote:

> Just a thought, instead of sending mail manually, can't we have a git hook
> to send out mail to dev list when there is a commit to schema files.
> So that git will take care of informing the dev about new schema changes.!
>
> Thanks
> Rajesh Battala
>
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Saturday, March 8, 2014 3:21 AM
> To: dev
> Subject: Re: Just checked in a minor change to the DB
>
> saw, good, will do some more if I think of them as well, as well as add to
> the descriptions
>
> On Fri, Mar 7, 2014 at 9:29 PM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
> > I went ahead and added to the Wiki page you created a few more tags
> > that I've seen us use from time to time.
> >
> >
> > On Fri, Mar 7, 2014 at 12:37 PM, Mike Tutkowski <
> > mike.tutkow...@solidfire.com> wrote:
> >
> >> Great! Thanks, Daan
> >>
> >> I also agree that it would be useful info to have in commit messages.
> >>
> >>
> >> On Fri, Mar 7, 2014 at 12:14 PM, Daan Hoogland  >wrote:
> >>
> >>> I created
> >>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/mail+tags+to+
> >>> use+to+help+each+other
> >>> below the path
> >>> Apache Cloudstack / Home / Community / Getting Help
> >>>
> >>>
> >>> On Fri, Mar 7, 2014 at 8:03 PM, Daan Hoogland
> >>> 
> >>> wrote:
> >>> > I had a quick look. Nothing found but a lot of hits on tags of
> course.
> >>> > I'll try to find a place to create the page and start chapters on
> >>> > Dev and Users
> >>> >
> >>> >
> >>> > On Fri, Mar 7, 2014 at 7:54 PM, Daan Hoogland
> >>> > 
> >>> wrote:
> >>> >> No, but I do know that it might be useful to use them in commit
> >>> >> comments as well. If you so feel inclined you can refer to that
> >>> >> as well
> >>> >>
> >>> >> On Fri, Mar 7, 2014 at 7:41 PM, Mike Tutkowski
> >>> >>  wrote:
> >>> >>> Does anyone know if our e-mail tags are documented on the Wiki?
> >>> >>>
> >>> >>>
> >>> >>> On Fri, Mar 7, 2014 at 11:36 AM, Mike Tutkowski <
> >>> >>> mike.tutkow...@solidfire.com> wrote:
> >>> >>>
> >>>  That sounds good, Daan.
> >>> 
> >>>  Let's use both tags.
> >>> 
> >>>  Thanks!
> >>> 
> >>> 
> >>>  On Fri, Mar 7, 2014 at 9:33 AM, Daan Hoogland <
> >>> daan.hoogl...@gmail.com>wrote:
> >>> 
> >>> > Absolutaly,
> >>> >
> >>> > But I meant for us to use both tags. I checked in a commit
> >>> > (that I didn't give a head up on) for a colleague in which a
> >>> > CloudRuntimeException was removed to be more consistent with
> >>> > the
> >>> rest
> >>> > of the code. It was only effecting th upgrade process in this
> >>> > case
> >>> but
> >>> > still;
> >>> > [BEHAVIORAL-CHANGE] was caused. Of course these heads-up will
> >>> > always be an inter developer courtesy but here is mine (hidden
> >>> > in some one elses thread;)
> >>> >
> >>> > so in short i meant and and not or, Daan
> >>> >
> >>> >
> >>> > On Fri, Mar 7, 2014 at 4:20 PM, Mike Tutkowski
> >>> >  wrote:
> >>> > > I like either tag.
> >>> > >
> >>> > > Since DB changes are the most likely to lead to breaking other
> >>> people's
> >>> > > environments, maybe we should go with that one:
> >>> > >
> >>> > > [DB-CHANGE]
> >>> > >
> >>> > > Ideally we'd provide the branch, commit SHA, and a manual way
> >>> around
> >>> > it, if
> >>> > > there is something simple (like in my case yesterday, simply
> >>> deleting
> >>> > and
> >>> > > re-creating two views). If there's no easy way around it, then
> >>> don't
> >>> > bother
> >>> > > providing that.
> >>> > >
> >>> > > Sound reasonable?
> >>> > >
> >>> > >
> >>> > > On Fri, Mar 7, 2014 at 2:12 AM, Daan Hoogland <
> >>> daan.hoogl...@gmail.com
> >>> > >wrote:
> >>> > >
> >>> > >> Thanks for the heads up Mike,
> >>> > >>
> >>> > >> As discussed in your thread [1]. You are eating your own
> dogfood
> >>> here.
> >>> > >> I was checking in a minor change to the upgrade handling
> >>> yesterday and
> >>> > >> decided not to bother everyone with it. evil me. In that
> thread
> >>> we
> >>> > >> didn't dicide on a tag, yet.
> >>> > >>
> >>> > >> I would suggest
> >>> > >> [DB-CHANGE] and
> >>> > >> [BEHAVIORAL-CHANGE]
> >>> > >>
> >>> > >> [1] http://markmail.org/message/r7wv36o356nolq7f
> >>> > >>
> >>> > >> On Thu, Mar 6, 2014 at 9:05 PM, Mike Tutkowski
> >>> > >>  wrote:
> >>> > >> >

system vm disk space issue in ACS 4.3

[Anirban Chakraborty]

Hi All,

I am seeing system vm disk has no space left after running for few days. 
Cloudstack UI shows the agent in v-2-VM in alert state, while agent state of 
s-1-VM shows blank (hyphen in the UI).
Both the system vms are running and ssh-able from the host. The log in s-1-Vm 
shows following errors:

root@s-1-VM:~# grep 'Exception' /var/log/cloud/*.*
/var/log/cloud/cloud.out.2:java.io.IOException: No space left on device
/var/log/cloud/cloud.out.2:java.io.IOException: No space left on device

whereas logs in v-1-VM shows
/var/log/cloud/cloud.out.3:java.io.IOException: No space left on device
/var/log/cloud/cloud.out.3:java.io.IOException: No space left on device
/var/log/cloud/cloud.out.3:07:18:00,547  INFO CSExceptionErrorCode:87 - Could 
not find exception: com.cloud.exception.AgentControlChannelException in error 
code list for exceptions
/var/log/cloud/cloud.out.3:com.cloud.exception.AgentControlChannelException: 
Unable to post agent control request as link is not available

Looks like cloud agent is filling up the log, which is leading to the disk full 
state.

Is this a known issue? Thanks.

Anirban

RE: system vm disk space issue in ACS 4.3

[Rajesh Battala]

AFAIK, log roation is enabled in the systemvm.
Can you check whether the logs are getting zipped .?

-Original Message-
From: Anirban Chakraborty [mailto:abc...@juniper.net] 
Sent: Saturday, March 8, 2014 12:46 PM
To: dev@cloudstack.apache.org
Subject: system vm disk space issue in ACS 4.3

Hi All,

I am seeing system vm disk has no space left after running for few days. 
Cloudstack UI shows the agent in v-2-VM in alert state, while agent state of 
s-1-VM shows blank (hyphen in the UI).
Both the system vms are running and ssh-able from the host. The log in s-1-Vm 
shows following errors:

root@s-1-VM:~# grep 'Exception' /var/log/cloud/*.*
/var/log/cloud/cloud.out.2:java.io.IOException: No space left on device
/var/log/cloud/cloud.out.2:java.io.IOException: No space left on device

whereas logs in v-1-VM shows
/var/log/cloud/cloud.out.3:java.io.IOException: No space left on device
/var/log/cloud/cloud.out.3:java.io.IOException: No space left on device
/var/log/cloud/cloud.out.3:07:18:00,547  INFO CSExceptionErrorCode:87 - Could 
not find exception: com.cloud.exception.AgentControlChannelException in error 
code list for exceptions
/var/log/cloud/cloud.out.3:com.cloud.exception.AgentControlChannelException: 
Unable to post agent control request as link is not available

Looks like cloud agent is filling up the log, which is leading to the disk full 
state.

Is this a known issue? Thanks.

Anirban