Re: failing mvn -P deps in CS 4.0.1

[Ajimangun lintang mas]

when building with command "mvn -P developer clean install" , building
apache cloudstack marvin failure



2013/4/21 Ajimangun lintang mas 

> i've stopped tomcat and jetty server was starting succesfully but when i
> write the localhost:8080/client URL on browser showed :
> HTTP ERROR: 503
>
> Problem accessing /client/. Reason:
>
> SERVICE_UNAVAILABLE
>
> --
> *Powered by Jetty://
>
> *
> this's still error?
> **
>
>
> 2013/4/21 Manikanta Kattamuri 
>
>> Seems like tomcat or some other server is using the default jetty launch
>> port.
>> Try stopping tomcat if present and run "mvn -pl :cloud-client-ui
>> jetty:run"
>>
>>
>> Mani
>>
>>
>> On Sat, Apr 20, 2013 at 10:23 PM, Ajimangun lintang mas <
>> ajimangu...@gmail.com> wrote:
>>
>> > i've passed building CS, but when i want to start management server with
>> > command "mvn -pl :cloud-client-ui jetty:run" hes occured issue like
>> this :
>> >
>> > 2013-04-20 23:16:38.171:WARN::failed
>> SelectChannelConnector@0.0.0.0:8080:
>> > java.net.BindException: Address already in use
>> > 2013-04-20 23:16:38.171:WARN::failed Server@5f00fa88:
>> > java.net.BindException: Address already in use
>> > [INFO] Jetty server exiting.
>> > [INFO]
>> > 
>> > [INFO] BUILD FAILURE
>> > [INFO]
>> > 
>> > [INFO] Total time: 33.183s
>> > [INFO] Finished at: Sat Apr 20 23:16:38 WIT 2013
>> > [INFO] Final Memory: 55M/131M
>> > [INFO]
>> > 
>> > [ERROR] Failed to execute goal
>> > org.mortbay.jetty:maven-jetty-plugin:6.1.26:run (default-cli) on project
>> > cloud-client-ui: Failure: Address already in use -> [Help 1]
>> > [ERROR]
>> > [ERROR] To see the full stack trace of the errors, re-run Maven with
>> the -e
>> > switch.
>> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> > [ERROR]
>> > [ERROR] For more information about the errors and possible solutions,
>> > please read the following articles:
>> > [ERROR] [Help 1]
>> > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>> > 2013-04-20 23:16:38.560:INFO::Shutdown hook executing
>> > 2013-04-20 23:16:38.560:INFO::Stopped
>> SelectChannelConnector@0.0.0.0:8080
>> > 2013-04-20 23:16:39.061:INFO:/client:Closing Spring root
>> > WebApplicationContext
>> > 2013-04-20 23:16:39.062:INFO:/client:Shutting down log4j
>> > 2013-04-20 23:16:39.166:INFO::Shutdown hook complete
>> >
>> > there are something incorrect with my configuration?
>> >
>> >
>> >
>> > 2013/4/19 Ajimangun lintang mas 
>> >
>> > > okay... thanks for your suggestion. i'll try it and post the
>> conclusion
>> > > later
>> > >
>> > >
>> > >
>> > > 2013/4/19 Chip Childers 
>> > >
>> > >> On Fri, Apr 19, 2013 at 09:47:58PM +0700, Ajimangun lintang mas
>> wrote:
>> > >> > how about your internet connectivity? with proxy or vpn too or not?
>> > >>
>> > >> Sorry, but I never access the internet via proxy or vpn.  You'll
>> have to
>> > >> look for help on general maven functionality when through a proxy.
>>  This
>> > >> is definitely something local to you.
>> > >>
>> > >> -chip
>> > >>
>> > >
>> > >
>> >
>>
>
>

Re: Review Request: CLOUDSTACK-713 Limit Resources to domain/accounts

[ASF Subversion and Git Services]

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


Commit 2f67dae711ec2cd084229d8fd5366a72a832c060 in branch refs/heads/master 
from Radhika PC 
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2f67dae ]

CLOUDSTACK-713


- ASF Subversion and Git Services


On Feb. 8, 2013, 11:25 a.m., Sanjay Tripathi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/9110/
> ---
> 
> (Updated Feb. 8, 2013, 11:25 a.m.)
> 
> 
> Review request for cloudstack, Devdeep Singh, Nitin Mehta, Prasanna 
> Santhanam, Chiradeep Vittal, and Min Chen.
> 
> 
> Description
> ---
> 
> CLOUDSTACK-713: Limit Resources to domain/accounts (CPU and Memory)
> 
> Addition of two new resource types i.e. CPU and RAM in the existing pool 
> of
> resource types.
> Added some methods to set the limits on these resources using 
> updateResource
> API command and to get a count using updateResourceCount. Also added 
> calls in
> Virtual machine life cycle to check these limits and to 
> increment/decrement 
> resource count
> 
> Resource Name  :: Resource type number
> CPU   8
> Memory9
> 
> 
> This addresses bug CLOUDSTACK-713.
> 
> 
> Diffs
> -
> 
>   api/src/com/cloud/configuration/Resource.java 7f551d6 
>   
> api/src/org/apache/cloudstack/api/command/user/resource/UpdateResourceCountCmd.java
>  91728ee 
>   
> api/src/org/apache/cloudstack/api/command/user/resource/UpdateResourceLimitCmd.java
>  33f2574 
>   api/src/org/apache/cloudstack/api/response/AccountResponse.java 0277d5b 
>   api/src/org/apache/cloudstack/api/response/ResourceCountResponse.java 
> 9d4f6c5 
>   api/src/org/apache/cloudstack/api/response/ResourceLimitResponse.java 
> beead24 
>   server/src/com/cloud/api/query/dao/AccountJoinDaoImpl.java 22b807c 
>   server/src/com/cloud/api/query/vo/AccountJoinVO.java 6d37f4d 
>   server/src/com/cloud/baremetal/BareMetalVmManagerImpl.java 8e447bc 
>   server/src/com/cloud/configuration/Config.java cbd5b01 
>   server/src/com/cloud/resourcelimit/ResourceLimitManagerImpl.java 7419690 
>   server/src/com/cloud/vm/UserVmManagerImpl.java 7dd726c 
>   server/test/com/cloud/resourcelimit/ResourceLimitManagerImplTest.java 
> PRE-CREATION 
>   server/test/com/cloud/vpc/MockResourceLimitManagerImpl.java 690aed6 
>   setup/db/create-schema-view.sql f68a6ca 
>   setup/db/db/schema-40to410.sql d771a15 
> 
> Diff: https://reviews.apache.org/r/9110/diff/
> 
> 
> Testing
> ---
> 
> Manually tested on my local CloudStack setup.
> Tested deployVirtualMachine API command with/without exceeded limits.
> Also tested APIs like: assignVirtualMachine, recoverVirtualMachine, 
> destroyVirtualMachine commands and checked the corresponding 
> increment/decrement in the resource count in database.
> Added unit tests in the patch.
> 
> 
> Thanks,
> 
> Sanjay Tripathi
> 
>

RE: [VOTE][ACS402] Apache CloudStack 4.0.2 (Third Round)

[Hugo Trippaers]

+1 (binding)

Tested (round 2 vote):
* Clean installation on clean Xen Hypervisors
* Upgrade from 4.0.1 to 4.0.2 with clean database
* Upgrade from 4.0.1 to 4.0.2 with copy of a production database
* Nicira L2 Features (QA NVP 001-006 and NVP 101-106)

Retested (with nonoss) :
* Clean installation on clean Xen Hypervisors
* Upgrade from 4.0.1 to 4.0.2 with clean database

General test procedure:
  Setup zone (with XenServer)
  CreateNetworkOffering
  CreateNetwork
  2x CreateInstance
  Ping A from B
  Ping internet from B


Cheers,

Hugo

> -Original Message-
> From: Joe Brockmeier [mailto:j...@zonker.net]
> Sent: zaterdag 20 april 2013 17:50
> To: dev@cloudstack.apache.org
> Subject: [VOTE][ACS402] Apache CloudStack 4.0.2 (Third Round)
> 
> Hi all,
> 
> I've created a 4.0.2 release, and am asking for you to test the artifacts and
> *after* testing, please submit a vote.
> 
> Suggested testing procedure here:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+
> test+procedure
> 
> (Please don't just +1 a release without any testing!)
> 
> The following artifacts up for a vote:
> 
> Git Branch and Commit SH:
> https://git-wip-
> us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.0
> Commit: 48e7eadb85bd033b642cbc83b0698d4175a183fb
> 
> List of changes:
> https://git-wip-
> us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=CHANGES;hb=4.0
> 
> Source release (checksums and signatures are available at the same
> location):
> http://people.apache.org/~jzb/cloudstack/dist/releases/4.0.2/
> 
> PGP release keys (signed using A0207CD4):
> http://www.apache.org/dist/incubator/cloudstack/KEYS
> 
> Vote will be open for 72 hours.
> 
> NOTE: The only changes between this and the last voting round are to the
> version numbers in the three pom.xml files that aren't automatically changed
> to 4.0.2. The nonoss build breaks if the versions aren't correct, so that is 
> fixed
> now.
> 
> If you are trying to build nonoss RPMs, the default cloud.spec won't work. So
> if you want to build nonoss RPMs for 4.0.2, grab this spec file and cp it to
> cloud.spec under your cloudstack source directory:
> 
> http://people.apache.org/~jzb/cloudstack/dist/releases/4.0.2/nonoss.cloud.
> spec
> 
> For sanity in tallying the vote, can PMC members please be sure to indicate
> "(binding)" with their vote?
> 
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
> 
> Best,
> 
> jzb
> --
> Joe Brockmeier
> j...@zonker.net
> Twitter: @jzb
> http://www.dissociatedpress.net/

RE: ReviewRequest: Storage XenMotion Test Plan

[Devdeep Singh]

Hi,

Some review comments on the test plan.

1. The listHostsForMigration and listStoragePoolsForMigration apis have been 
renamed to findHostsForMigration and findStoragePoolsForMigration. The updated 
FS has these details. This was done to address the review comments shared here 
[1].
2. Test case 7 (SXM_VM_migrate_sameSR). For migrating a vm without its volumes 
the existing migrateVirtualMachine api has to be used. If migrateVmWithVolume 
is called to migrate a vm and it doesn't require storage motion, the api will 
report an error.
3. Test case 15 (SXM_VM_operations_while_migration). When a vm is migrating 
other operations like stopping the vm etc. shouldn't be allowed on it.
4. Test case 16 (SXM_VM_migrate_src_dest_diff_offerings). Can you clarify what 
do you mean by different offerings on the destination?
5. Test case 17 (SXM_VM_migrate_dest_SR_not_available). Can you elaborate more 
on this scenario?
6. Test case 20 (SXM_VM_migrate_dest_xs6.0.2_host_listHostsForMigration). Just 
FYI/clarification, the findHostsForMigration shouldn't return a 6.0.2 xenserver 
host to be suitable for storage motion. If migrateVmWithVolume is called giving 
a 6.0.2 host as destination, the api should report an error saying the 
destination is unsuitable for storage motion.
7. Suggestion, instead of using the term resource pool in the test cases, 
should we use the term cluster as it is more relevant to cloudstack.

Some additional test cases to consider. These add more details to what test 
cases 10, 11, 12 and 13 should test.
findHostsForMigration api.
1. A vm is created with an offering which uses host tags and it gets deployed 
on a host with an appropriate tag. Hosts that are available for migration are 
listed using the api. Only the hosts that have an appropriate (matching) tag 
get listed as suitable.
2. The above test case can be extended to verify that if a vm is created using 
an offering that doesn't have any tags, only the hosts that have not been 
tagged should be listed as suitable.
3. When hosts are listed for migration, if migration to a hosts requires moving 
the volumes of a vm; the requiresstoragemotion flag in the response should be 
true.
4. Create a vm and attach a disk to it created using a disk offering that 
requires local storage. A host that doesn't have storage pool of type local 
attached to it, shouldn't be listed.

migrateVirtualMachineWithVolume api.
1. If only the vmid and destination are passed as parameters, appropriate pools 
are picked up for each volume of the vm. If there isn't an appropriate pool 
available migration fails and it is reported and logged. Examples of why an 
appropriate pool isn't available, the tags on the disk offering with which a 
volume is created doesn't match the storage pools available on the destination 
host. A volume may have been created with shared or local disk offering and 
such a storage pool isn't available on the destination host.
2. Adding to the above test case, each volume should be placed on a storage 
pool with which the tags and type (shared/local) match.
3. 'migrateto' option parameter (volume to pool mapping) is passed. If any of 
the storage pools aren't available on the destination host, a failure is 
reported and logged.
4. 'migrateto' option parameter (volume to pool mapping) is passed. If the tags 
on the destination storage pool do not match the disk offering with which a 
volume is created; migration is allowed.
5. 'migrateto' option parameter (volume to pool mapping) is passed. If the type 
(shared/local) of the destination storage pool do not match the disk offering 
with which a volume is created; migration fails and is reported and logged.
6. Verify when migration of vm with its volumes is taking place, the vm and the 
volumes being migrated are placed in migrating state.
7. If any of volumes of the vm that has to be migrated is not in ready state; 
e.g,. snapshot in progress; migration isn't initiated and reported.
8. Take a snapshot of a volume of a vm. Migrate the vm along with its volumes. 
Try taking a snapshot of the volume again. It should be successful.

findStorgePoolsForMigration api.
1. If a volume is created using a disk offering requiring a local storage, the 
api should return an empty set. A volume on local storage cannot be migrated 
while the vm continues to run on the same host.
2. If a volume has been created using a disk offering requiring certain tags on 
the volume, the storage pools that do not have the right tags are reported as 
unsuitable. A storage pool that has the right tags is reported as suitable. The 
same applies to a volume created with a disk offering with no tags.

migrateVolume api.
1. migration of a volume to a storage pool with which the tags do not match is 
allowed.
2. migration of a volume to a storage pool with which the type (shared/local) 
do not match is not allowed and is reported and logged.
3. Take snapshots of a volume. Migrate the volume to another storage pool. Try 
taking s

[GSOC] Update and registration as mentor

[Sebastien Goasguen]

Hi Folks,

Students applications should start trickling in. Application period will end 
May 3rd.

All interested mentors need to register and request ack from the CloudStack 
PMC, see:
http://community.apache.org/gsoc.html

Note that anyone is welcome to pick up mentorship for the projects I entered.
It is also not too late to enter a project in JIRA with gsoc2013 as label.

All students should check the wiki page:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Student+Projects

Then start emailing this list (with the label [GSOC] on the subject line) to 
talk about your ideas.

-Sebastien

[DOC] Review Documentation on Limiting Resource Usage

[Radhika Puthiyetath]

Hi,

I have attached a draft version at 
https://cwiki.apache.org/confluence/pages/viewpageattachments.action?pageId=30746627.

Please provide your technical review comments.

Thanks
-Radhika

Review Request: Add uuid to AddIpToVmNicCmd nicsecondary ip resonpose

[Jayapal Reddy]

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

Review request for cloudstack, Abhinandan Prateek and Murali Reddy.


Description
---

added the secondary ip id entry uuid to response.


This addresses bug CLOUDSTACK-1741.


Diffs
-

  api/src/com/cloud/network/NetworkService.java 5a6054d 
  api/src/org/apache/cloudstack/api/ResponseGenerator.java c0dd57e 
  api/src/org/apache/cloudstack/api/command/user/vm/AddIpToVmNicCmd.java 
df6b399 
  api/test/org/apache/cloudstack/api/command/test/AddIpToVmNicTest.java 106589d 
  server/src/com/cloud/api/ApiResponseHelper.java 7629e5e 
  server/src/com/cloud/network/NetworkServiceImpl.java 12c6068 
  server/test/com/cloud/network/MockNetworkManagerImpl.java 6a0263e 
  server/test/com/cloud/vpc/MockNetworkManagerImpl.java bfcccf5 

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


Testing
---

1. Acquired secondary ip to the nic.
2. Deleted it from the UI. Deletion is successful. 
Earlier deleting the acquired ip failed when doing it after acquire without 
navigating the pages. 


Thanks,

Jayapal Reddy

RE: [DISCUSS] - Deletion of Users within the Admin account

[Pranav Saxena]

Hi Chip ,

This issue has been fixed in asf/master at both the UI and API layers 
(CLOUDSTACK-1941) . Now , if you think that we should support the same 
functionality in 4.1 as well , then myself and Alena can back-port our fixes to 
4.1 from master. 

Thanks,
Pranav

-Original Message-
From: Alena Prokharchyk 
Sent: Tuesday, April 09, 2013 11:12 PM
To: dev@cloudstack.apache.org
Cc: Pranav Saxena
Subject: Re: [DISCUSS] - Deletion of Users within the Admin account

Chip, 

1) "System" user is always identified by the cloud.user DB id=1 (hardcoded in 
User.java interface). This user is never exposed via API, you can't remove it - 
the checks are already in place for it.

2) For users of "admin" account, currently there is no direct way to tell if 
the user was added by the system, or using API call. We can't rely on name 
"admin" as it's not reserved name and renaming is also allowed.

I think for upgrade we can rely on the cloud.user db id - expect it to be 
"system_user_db_id + 1" as we know that 2 users come with the default 
cloudStack install.


-Alena.



On 4/9/13 10:02 AM, "Chip Childers"  wrote:

>On Tue, Apr 09, 2013 at 09:56:37AM -0700, Alena Prokharchyk wrote:
>> We should allow to delete any CS users except for ones that came as a 
>>part  of cloudStack installation ("system" and "admin" users). The 
>>users you've  created using API, should be allowed to be removed no 
>>matter of their  types.
>
>+1 to this in general terms.  Not sure about requiring a change like
>this for 4.1.0 though.
>
>> 
>> The right way to distinguish between system generated users, and 
>> users created using APIs would be introducing the flag in the cloud.users DB.
>
>Do you have any thoughts on how we would correctly identify these 
>account in existing installs?
>
>

RE: [DOCS] "Submitting Feedback and Getting Help" in Release Notes?

[Radhika Puthiyetath]

Hi Joe/David/Jessica

FYI

Today when I checked in couple of files for limit resource usage, Release Notes 
build failed. The files I checked in are nothing to do with the Release Notes.

I am trying to fix the build errors, and found that no feedback.xml file is 
available in the repo. So I checked in one to Common_Content/.

Waiting for the build notification.

Thanks
-Radhika

-Original Message-
From: Joe Brockmeier [mailto:j...@zonker.net] 
Sent: Friday, April 05, 2013 1:33 AM
To: dev@cloudstack.apache.org
Subject: [DOCS] "Submitting Feedback and Getting Help" in Release Notes?

Hey all,

So working on the Release Notes, I notice that our first section is on 
"Submitting Feedback and Getting Help." It *looks* like this has carried over a 
tradition from Cloud.com/Citrix docs. Looking at the Release Notes from 
CloudStack 2.2.14, it has a "contacting support" section.

So my questions:

1) Does it make sense to have this in the release notes rather than, say, the 
install guide?

2) Should we have this in each guide, or...? 

Maybe it should just live on a documentation landing page with links to the 
other guides?

Thoughts, comments, suggestions?

Best,

jzb
--
Joe Brockmeier
j...@zonker.net
Twitter: @jzb
http://www.dissociatedpress.net/

RE: qa tests for nicira code in 4.1

[Daan Hoogland]

I updated the page you pasted for me to conclude the bureaucratic part. Hope it 
satisfied the apache/cloudstack way. Is it there a formal timeline between 
resolved and closed status for tickets to observe?  (otherwise 2092 can be 
closed)

-Original Message-
From: Sudha Ponnaganti [mailto:sudha.ponnaga...@citrix.com] 
Sent: vrijdag 19 april 2013 17:54
To: dev@cloudstack.apache.org
Subject: RE: qa tests for nicira code in 4.1

If you do additional tests or update any results, you can edit that page and 
update it. Otherwise I just copied your email,

If you don't mind, can you add a note to the ticket on the testing done and 
close them. Thanks

-Original Message-
From: Daan Hoogland [mailto:dhoogl...@schubergphilis.com] 
Sent: Friday, April 19, 2013 7:27 AM
To: dev@cloudstack.apache.org
Subject: RE: qa tests for nicira code in 4.1

Hy Sudha

Both tickets can be closed.

I am not sure what to do with the page you created for me. Do you want me to 
copy the table below, with the fail changed to pass, in a new child page there?

Regards,
Daan Hoogland

-Original Message-
From: Sudha Ponnaganti [mailto:sudha.ponnaga...@citrix.com] 
Sent: donderdag 18 april 2013 22:17
To: dev@cloudstack.apache.org
Subject: RE: qa tests for nicira code in 4.1

Thanks Daan for posting test results !

I have created a place holder for you to update test results [1] - You can 
update it at your convenience. 
Does this execution cover both of these stories for Nicira [2], [3]. If it 
covers both of these stories, may be these can be closed. Looks like doc is 
also outstanding as per the JIRA status. 

[1] 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.1+Test+Execution
[2] https://issues.apache.org/jira/browse/CLOUDSTACK-726
[3] https://issues.apache.org/jira/browse/CLOUDSTACK-727



Thanks
/Sudha

-Original Message-
From: Daan Hoogland [mailto:dhoogl...@schubergphilis.com] 
Sent: Thursday, April 18, 2013 12:38 PM
To: dev@cloudstack.apache.org
Subject: qa tests for nicira code in 4.1

LS,

At Schuberg Philis we did some tests on the 4.1 code for the tests in the 
following table
Test Case ID  Test Description Results
   Infrastructure
NVP-001 Create NVP Element pass
NVP-002 Disable NVP Elementpass
NVP-003 Enable NVP Element pass
NVP-004 Delete NVP Element  pass
NVP-005 Create NVP Device   pass
NVP-006 Delete NVP Devicepass
   L2 Functions
NVP-101 Create Logical Switchpass
NVP-102 Create Logical Portpass
NVP-103 Check Connection Pass
NVP-104 Check Connection Pass
NVP-105 Delete Logical SwitchPass
NVP-106 Delete Logical Port Pass
   L3 Functions
NVP-201 Create Logical RouterPass
NVP-202 Create Source Nat rule  Pass
NVP-203 Create Static Nat rulePass
NVP-204 Create Port FW rule   Pass
NVP-205 Check Source Nat rule  Pass
NVP-206 Check Static Nat rule Pass
NVP-207 Check Port FW rule   Pass
NVP-208 Delete Source Nat rule  Pass
NVP-209 Delete Static Nat rule Fail
NVP-210 Delete Port FW rule   Pass
NVP-211 Delete Logical RouterPass

The tests where partly done aith scripts but these are not yet complete and the 
remainder of functionality was done by hand.
For the failed test, NVP-209 a ticket was created, 'CLOUDSTACK-2092'. The 
problem in this case was that deleting the static rule did not result in the 
deletion of the ip adres from the logical router.

Kind regards,
Daan Hoogland

Error when acquiring new ip for an instance

[Isaac Chiang]

Hi all:
When I tried to acquire a new ip for an instance from UI, I got
following error message from server:

com.cloud.utils.exception.CloudRuntimeException: callHostPlugin failed for
cmd: network_rules_vmSecondaryIp with args vmSecIp: 192.168.
56.168, vmMac: 06:dd:30:00:00:6c, action: -A, vmName: i-2-3-VM,  due to
UNKNOWN_XENAPI_PLUGIN_FUNCTIONnetwork_rules_vmSecondaryIp
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.callHostPlugin(CitrixResourceBase.java:3971)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:7621)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:604)
at
com.cloud.hypervisor.xen.resource.XcpOssResource.executeRequest(XcpOssResource.java:137)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)

No matter the error message from server, I still can get a IP for the
instance. But I cannot ping to the acquired IP.

My env for the case is master code with DevCloud. Is there any detailed
steps or limitations I missed? Any help will be appreciated, thanks

Regards

Isaac

Re: [VOTE][ACS402] Apache CloudStack 4.0.2 (Third Round)

[Sebastien Goasguen]

+1 (binding)

Followed my screencast at:
http://www.youtube.com/watch?v=vvgIkF1e1QE

-sebastien

On Apr 22, 2013, at 4:08 AM, Hugo Trippaers  
wrote:

> +1 (binding)
> 
> Tested (round 2 vote):
> * Clean installation on clean Xen Hypervisors
> * Upgrade from 4.0.1 to 4.0.2 with clean database
> * Upgrade from 4.0.1 to 4.0.2 with copy of a production database
> * Nicira L2 Features (QA NVP 001-006 and NVP 101-106)
> 
> Retested (with nonoss) :
> * Clean installation on clean Xen Hypervisors
> * Upgrade from 4.0.1 to 4.0.2 with clean database
> 
> General test procedure:
>  Setup zone (with XenServer)
>  CreateNetworkOffering
>  CreateNetwork
>  2x CreateInstance
>  Ping A from B
>  Ping internet from B
> 
> 
> Cheers,
> 
> Hugo
> 
>> -Original Message-
>> From: Joe Brockmeier [mailto:j...@zonker.net]
>> Sent: zaterdag 20 april 2013 17:50
>> To: dev@cloudstack.apache.org
>> Subject: [VOTE][ACS402] Apache CloudStack 4.0.2 (Third Round)
>> 
>> Hi all,
>> 
>> I've created a 4.0.2 release, and am asking for you to test the artifacts and
>> *after* testing, please submit a vote.
>> 
>> Suggested testing procedure here:
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+
>> test+procedure
>> 
>> (Please don't just +1 a release without any testing!)
>> 
>> The following artifacts up for a vote:
>> 
>> Git Branch and Commit SH:
>> https://git-wip-
>> us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.0
>> Commit: 48e7eadb85bd033b642cbc83b0698d4175a183fb
>> 
>> List of changes:
>> https://git-wip-
>> us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=CHANGES;hb=4.0
>> 
>> Source release (checksums and signatures are available at the same
>> location):
>> http://people.apache.org/~jzb/cloudstack/dist/releases/4.0.2/
>> 
>> PGP release keys (signed using A0207CD4):
>> http://www.apache.org/dist/incubator/cloudstack/KEYS
>> 
>> Vote will be open for 72 hours.
>> 
>> NOTE: The only changes between this and the last voting round are to the
>> version numbers in the three pom.xml files that aren't automatically changed
>> to 4.0.2. The nonoss build breaks if the versions aren't correct, so that is 
>> fixed
>> now.
>> 
>> If you are trying to build nonoss RPMs, the default cloud.spec won't work. So
>> if you want to build nonoss RPMs for 4.0.2, grab this spec file and cp it to
>> cloud.spec under your cloudstack source directory:
>> 
>> http://people.apache.org/~jzb/cloudstack/dist/releases/4.0.2/nonoss.cloud.
>> spec
>> 
>> For sanity in tallying the vote, can PMC members please be sure to indicate
>> "(binding)" with their vote?
>> 
>> [ ] +1  approve
>> [ ] +0  no opinion
>> [ ] -1  disapprove (and reason why)
>> 
>> Best,
>> 
>> jzb
>> --
>> Joe Brockmeier
>> j...@zonker.net
>> Twitter: @jzb
>> http://www.dissociatedpress.net/

RE: Add/Remove Network for VM : VMware Support

[Sateesh Chodapuneedi]

Hi Saksham,

In case of remove network, we need add support to unplug VM from virtual 
network over dvSwitch. Created Jira ticket [1] for the same. Please include 
this in FS.

[1] CLOUDSTACK-2059 - Support remove network over VMware deployments with 
dvSwitch

Regards,
Sateesh

> -Original Message-
> From: Saksham Srivastava [mailto:saksham.srivast...@citrix.com]
> Sent: 17 April 2013 13:55
> To: dev@cloudstack.apache.org
> Subject: Re: Add/Remove Network for VM : VMware Support
> 
> FS is available at :
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Add+Remove+Netw
> orks+to+VMs+%28Enhanced%29
> 
> Thanks,
> Saksham
> 
> On Monday 15 April 2013 11:11 PM, Saksham Srivastava wrote:
> > Following the discussion on bug:
> https://issues.apache.org/jira/browse/CLOUDSTACK-645 , there needs to be
> some work done for enhancing  VMware support for the feature Add/Remove
> Network on VM.
> >
> > I will be updating the FS soon and will send out for review.
> >
> > Thanks,
> > Saksham
> >

haproxy on VMWare systemVM template

[Abhinandan Prateek]

The haproxy and port map services are not installed on VMWare system VM
template. Is the path used to create the templates different for different
Hypervisor templates ? I was under the assumption that the services
installed on all the system VM templates meant for different hypervisors
should be same ?

-abhi

RE: The IPaddr parameter for vmcreate API

[Pranav Saxena]

Hey Jerry,

Custom ip allocation failure leads to vm deploy failure. Happens in
following cases:

* If ipAddress doesn't exist in the network.
* If requested ip address exists in the network, but already allocated.
* If network model doesn't support custom ip allocation (see list of
cases below), the runtime exception "Does not support custom ip
allocation at this time"  is being thrown.


Custom ip allocation is SUPORTED FOR - 

* Guest Virtual Network
* Direct network in Advanced zone


NOT SUPPORTED - 

* ExternalFirewall setup case. The reason for not supporting: the
original ip can be changed automatically by ExternalGuestNetworkGuru
after the vm is stopped/started.
* Basic zone - as we have 1 Global Network, but separate ip ranges per
each Pod, so the decision about which ip address to take happens after
Allocators figure out the destination Pod.
If you specify the ip address of Pod2, and allocators will pick up Pod1
- the vm creation will fail.

So you can figure out which case might explain your problem to the best extent 
possible.

Thanks,
Pranav
-Original Message-
From: Jerry Jiang [mailto:jerry.ji...@tyxtech.com] 
Sent: Monday, April 22, 2013 3:40 PM
To: us...@cloudstack.apache.org
Subject: 答复: The IPaddr parameter for vmcreate API

Anyone has reponsed to the issue, thanks in advance.

 

jerry

 

发件人: Jerry Jiang [mailto:jerry.ji...@tyxtech.com]
发送时间: 2013年4月18日 星期四 10:29
收件人: 'us...@cloudstack.apache.org'
主题: The IPaddr parameter for vmcreate API

 

Hello all,

 

I am using cloudstack API to create a VM instance. The IP address as one of 
parameters is provided to API

However, I found it didn’t work well, The IP address of creating VM is not what 
I provided for API.

Eg, using IP1 as the parameter, the vm operational IP addr is IP2

 

Why does this issue happen?

 

Thanks

Jerry

Review Request: fix the sting formatting error in cloudConnection.py

[SrikanteswaraRao Talluri]

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

Review request for cloudstack and Prasanna Santhanam.


Description
---

fix the sting formatting error in cloudConnection.py

error seen:

Traceback (most recent call last):
  File "/usr/local/bin/nosetests-2.7", line 9, in 
load_entry_point('nose==1.2.1', 'console_scripts', 'nosetests-2.7')()
  File 
"/usr/local/lib/python2.7/site-packages/nose-1.2.1-py2.7.egg/nose/core.py", 
line 118, in __init__
**extra_args)
  File "/usr/local/lib/python2.7/unittest/main.py", line 94, in __init__
self.parseArgs(argv)
  File 
"/usr/local/lib/python2.7/site-packages/nose-1.2.1-py2.7.egg/nose/core.py", 
line 135, in parseArgs
self.config.configure(argv, doc=self.usage())
  File 
"/usr/local/lib/python2.7/site-packages/nose-1.2.1-py2.7.egg/nose/config.py", 
line 338, in configure
self.plugins.configure(options, self)
  File 
"/usr/local/lib/python2.7/site-packages/nose-1.2.1-py2.7.egg/nose/plugins/manager.py",
 line 284, in configure
cfg(options, config)
  File 
"/usr/local/lib/python2.7/site-packages/nose-1.2.1-py2.7.egg/nose/plugins/manager.py",
 line 99, in __call__
return self.call(*arg, **kw)
  File 
"/usr/local/lib/python2.7/site-packages/nose-1.2.1-py2.7.egg/nose/plugins/manager.py",
 line 167, in simple
result = meth(*arg, **kw)
  File 
"/usr/local/lib/python2.7/site-packages/marvin_nose-0.1.0-py2.7.egg/marvinPlugin.py",
 line 42, in configure
deploy.loadCfg() if options.load else deploy.deploy()
  File "/usr/local/lib/python2.7/site-packages/marvin/deployDataCenter.py", 
line 452, in deploy
self.loadCfg()
  File "/usr/local/lib/python2.7/site-packages/marvin/deployDataCenter.py", 
line 409, in loadCfg
apiKey, securityKey = self.registerApiKey()
  File "/usr/local/lib/python2.7/site-packages/marvin/deployDataCenter.py", 
line 349, in registerApiKey
listuserRes = self.testClient.getApiClient().listUsers(listuser)
  File 
"/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
 line 436, in listUsers
response = self.connection.marvin_request(command, data=postdata, 
response_type=response)
  File "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py", 
line 212, in marvin_request
cmdname, auth=False, payload=payload, data=data)
  File "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py", 
line 141, in request
(self.baseurl, c))
TypeError: not all arguments converted during string formatting 


This addresses bug CLOUDSTACK-2135.


Diffs
-

  tools/marvin/marvin/cloudstackConnection.py 14b12e7 

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


Testing
---

tested


Thanks,

SrikanteswaraRao Talluri

Review Request: updated the listnics response for non-root user

[Jayapal Reddy]

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

Review request for cloudstack, Abhinandan Prateek and Murali Reddy.


Description
---

Updated listnics response for normal user


This addresses bug CLOUDSTACK-1573.


Diffs
-

  server/src/com/cloud/api/ApiResponseHelper.java a7d6165 

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


Testing
---

Tested with admin and normal user


Thanks,

Jayapal Reddy

Re: Review Request: fix the string formatting error in cloudConnection.py

[SrikanteswaraRao Talluri]

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

(Updated April 22, 2013, 11:21 a.m.)


Review request for cloudstack and Prasanna Santhanam.


Summary (updated)
-

fix the string formatting error in cloudConnection.py


Description (updated)
---

fix the string formatting error in cloudConnection.py

error seen:

Traceback (most recent call last):
  File "/usr/local/bin/nosetests-2.7", line 9, in 
load_entry_point('nose==1.2.1', 'console_scripts', 'nosetests-2.7')()
  File 
"/usr/local/lib/python2.7/site-packages/nose-1.2.1-py2.7.egg/nose/core.py", 
line 118, in __init__
**extra_args)
  File "/usr/local/lib/python2.7/unittest/main.py", line 94, in __init__
self.parseArgs(argv)
  File 
"/usr/local/lib/python2.7/site-packages/nose-1.2.1-py2.7.egg/nose/core.py", 
line 135, in parseArgs
self.config.configure(argv, doc=self.usage())
  File 
"/usr/local/lib/python2.7/site-packages/nose-1.2.1-py2.7.egg/nose/config.py", 
line 338, in configure
self.plugins.configure(options, self)
  File 
"/usr/local/lib/python2.7/site-packages/nose-1.2.1-py2.7.egg/nose/plugins/manager.py",
 line 284, in configure
cfg(options, config)
  File 
"/usr/local/lib/python2.7/site-packages/nose-1.2.1-py2.7.egg/nose/plugins/manager.py",
 line 99, in __call__
return self.call(*arg, **kw)
  File 
"/usr/local/lib/python2.7/site-packages/nose-1.2.1-py2.7.egg/nose/plugins/manager.py",
 line 167, in simple
result = meth(*arg, **kw)
  File 
"/usr/local/lib/python2.7/site-packages/marvin_nose-0.1.0-py2.7.egg/marvinPlugin.py",
 line 42, in configure
deploy.loadCfg() if options.load else deploy.deploy()
  File "/usr/local/lib/python2.7/site-packages/marvin/deployDataCenter.py", 
line 452, in deploy
self.loadCfg()
  File "/usr/local/lib/python2.7/site-packages/marvin/deployDataCenter.py", 
line 409, in loadCfg
apiKey, securityKey = self.registerApiKey()
  File "/usr/local/lib/python2.7/site-packages/marvin/deployDataCenter.py", 
line 349, in registerApiKey
listuserRes = self.testClient.getApiClient().listUsers(listuser)
  File 
"/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
 line 436, in listUsers
response = self.connection.marvin_request(command, data=postdata, 
response_type=response)
  File "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py", 
line 212, in marvin_request
cmdname, auth=False, payload=payload, data=data)
  File "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py", 
line 141, in request
(self.baseurl, c))
TypeError: not all arguments converted during string formatting 


This addresses bug CLOUDSTACK-2135.


Diffs
-

  tools/marvin/marvin/cloudstackConnection.py 14b12e7 

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


Testing
---

tested


Thanks,

SrikanteswaraRao Talluri

[Discuss] - Domain admin not having the flexibility to create sub-domains/sub-child domains/accounts

[Pranav Saxena]

Hi,

Currently only the ROOT-admin has the power to create any 
domains/sub-domains/sub-child domains for himself or the domain-admin . But 
there are certain situations ( like updating resource limit for a sub-child 
domain under a domain admin ) for which the ROOT-admin has to create a 
sub-child domain for a domain admin to allow him to update the resource limits 
for that particular sub-child domain.

With this in mind , why hasn't the domain -admin been given the privilege of 
creating sub-child domains himself ? Are there any concerns/threats because of 
which the current architecture doesn't serve this purpose ?

Also , a domain-admin cannot create an account on his own using an API as well 
( UI can be overlooked for now) . He has to go through the ROOT-admin to have 
this functionality enabled . So doesn't that conclude that domain-admin is 
almost a USELESS guy with *No powers*  . To be able to navigate from step 1 - > 
step  2 , you have to go through step 3 which seems to be unconvincing at times 
.

Could someone explain about why such a functionality is not supported in the 
current architecture ? Please let me know in case I am missing something here.

Thanks,
Pranav

RE: [DIscuss]Storage image store plugin framework refactoring

[Sanjeev Neelarapu]

Hi,

I have prepared RIAK CS object store in our lab environment and planning to use 
it for object store feature testing . 
As per my understanding RIAK CS supports S3 APIs. So let me know whether I can 
use it as an alternative to s3 based object store.

Thanks,
Sanjeev

-Original Message-
From: prasanna [mailto:srivatsav.prasa...@gmail.com] On Behalf Of Prasanna 
Santhanam
Sent: Wednesday, April 10, 2013 12:42 PM
To: dev@cloudstack.apache.org
Subject: Re: [DIscuss]Storage image store plugin framework refactoring

On Tue, Apr 09, 2013 at 09:19:11AM -0700, Min Chen wrote:
> Not yet at this moment. But we are planning to provide a sample plugin 
> implementation for this effort. If you are looking at object_store 
> branch, you will see a plugin called 
> "cloud-plugin-storage-image-sample", which will be the placeholder for a 
> sample image store implementation.
> 

Hmmm - more frameworks and no reference implementation? :(

I'm keeping an eye on the branch and was hoping there'd be an implementation of 
an objectstore because I'm looking to span this solution across some qa labs. 
RiakCS, Swift are all opensource now.

--
Prasanna.,

Re: [ACS41] RC Blocker issue. Help Needed!

[Chip Childers]

Yup - The script I used to update versions was incomplete.  Fixed and
will attempt the process again now.

Thanks Mice!

On Sun, Apr 21, 2013 at 11:34 PM, Mice Xia  wrote:
> chip,
>
> in tools/apidoc/pom.xml
> -
> ../../client/target/cloud-client-ui-4.1.0-SNAPSHOT/WEB-INF/
> +
> ../../client/target/cloud-client-ui-4.1.1-SNAPSHOT/WEB-INF/
>
> -mice
>
>
> 2013/4/22 Chip Childers 
>
>> I was about to release the RC for voting, when I hit an error building
>> from the 4.1 branch via the following command:
>>
>> mvn -P developer,systemvm clean install
>>
>> Does anyone know what's going wrong here?
>>
>> Snipped output below:
>>
>>
>> [INFO]
>> 
>> [INFO] Building Apache CloudStack apidoc Tools 4.1.0
>> [INFO]
>> 
>> [INFO]
>> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ cloud-apidoc ---
>> [INFO]
>> [INFO] --- maven-remote-resources-plugin:1.3:process (default) @
>> cloud-apidoc ---
>> [INFO]
>> [INFO] --- exec-maven-plugin:1.2.1:exec (compile) @ cloud-apidoc ---
>> + set -u
>> +
>> TARGETJARDIR=../../client/target/cloud-client-ui-4.1.0-SNAPSHOT/WEB-INF//lib
>> + shift
>> + DEPSDIR=../../client/target/cloud-client-ui-4.1.0-SNAPSHOT/WEB-INF//lib
>> + shift
>> + DISTDIR=./target
>> + shift
>> ++ canonical_readlink ./build-apidoc.sh
>> +++ dirname ./build-apidoc.sh
>> ++ cd .
>> +++ basename ./build-apidoc.sh
>> ++ __filename=build-apidoc.sh
>> ++ '[' -h build-apidoc.sh ']'
>> +++ pwd -P
>> ++ echo /private/tmp/cloudstack/apache-cloudstack-4.1.0-src/tools/apidoc
>> + thisdir=/private/tmp/cloudstack/apache-cloudstack-4.1.0-src/tools/apidoc
>> + PATHSEP=:
>> + [[ darwin11.3.0 == \c\y\g\w\i\n ]]
>> + CP=:/
>> + for file in '$TARGETJARDIR/*.jar'
>> +
>> CP=':/:../../client/target/cloud-client-ui-4.1.0-SNAPSHOT/WEB-INF//lib/*.jar'
>> + for file in '$DEPSDIR/*.jar'
>> +
>> CP=':/:../../client/target/cloud-client-ui-4.1.0-SNAPSHOT/WEB-INF//lib/*.jar:../../client/target/cloud-client-ui-4.1.0-SNAPSHOT/WEB-INF//lib/*.jar'
>> + java -cp
>> ':/:../../client/target/cloud-client-ui-4.1.0-SNAPSHOT/WEB-INF//lib/*.jar:../../client/target/cloud-client-ui-4.1.0-SNAPSHOT/WEB-INF//lib/*.jar'
>> com.cloud.api.doc.ApiXmlDocWriter -d ./target -f
>> ../../client/target/cloud-client-ui-4.1.0-SNAPSHOT/WEB-INF//classes/commands.properties
>> Exception in thread "main" java.lang.NoClassDefFoundError:
>> com/cloud/api/doc/ApiXmlDocWriter
>> Caused by: java.lang.ClassNotFoundException:
>> com.cloud.api.doc.ApiXmlDocWriter
>> at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
>> at java.security.AccessController.doPrivileged(Native Method)
>> at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
>> at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
>> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
>> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>> + '[' 1 -ne 0 ']'
>> + exit 1
>>
>>

Re: [VOTE][ACS402] Apache CloudStack 4.0.2 (Third Round)

[Joe Brockmeier]

On Mon, Apr 22, 2013, at 03:08 AM, Hugo Trippaers wrote:
> +1 (binding)

Thank you Hugo! 

Best,

jzb
-- 
Joe Brockmeier
j...@zonker.net
Twitter: @jzb
http://www.dissociatedpress.net/

Re: [VOTE][ACS402] Apache CloudStack 4.0.2 (Third Round)

[Joe Brockmeier]

On Mon, Apr 22, 2013, at 04:56 AM, Sebastien Goasguen wrote:
> +1 (binding)
> 
> Followed my screencast at:
> http://www.youtube.com/watch?v=vvgIkF1e1QE

Thanks, Sebastien!

Best,

jzb
-- 
Joe Brockmeier
j...@zonker.net
Twitter: @jzb
http://www.dissociatedpress.net/

Re: failing mvn -P deps in CS 4.0.1

[Ajimangun lintang mas]

sorry for my mistakes, last post i used cloudstack 4.2.0 from git. now i am
using cloudstack 4.0.1 and succesfully for building section. but when i
started management server, the result like this :

[INFO] Reactor Summary:
[INFO]
[INFO] Apache CloudStack . SUCCESS [2.100s]
[INFO] Apache CloudStack Utils ... SUCCESS [0.518s]
[INFO] Apache CloudStack API . SUCCESS [0.127s]
[INFO] Apache XenSource XAPI . SUCCESS [0.058s]
[INFO] Apache CloudStack Core  SUCCESS [0.169s]
[INFO] Apache CloudStack Agents .. SUCCESS [0.313s]
[INFO] Apache CloudStack SystemVM Patches  SUCCESS [0.184s]
[INFO] Apache CloudStack Console Proxy ... SUCCESS [0.188s]
[INFO] Apache CloudStack Server .. SUCCESS [0.164s]
[INFO] Apache CloudStack Usage Server  SUCCESS [0.086s]
[INFO] Apache CloudStack Plugin POM .. SUCCESS [0.046s]
[INFO] Apache CloudStack Plugin - User Concentrated Pod Deployment Planner
SUCCESS [0.054s]
[INFO] Apache CloudStack Plugin - User Dispersing Deployment Planner
SUCCESS [0.051s]
[INFO] Apache CloudStack Plugin - Host Allocator Random .. SUCCESS [0.047s]
[INFO] Apache CloudStack Plugin - Hypervisor OracleVM  SUCCESS [0.051s]
[INFO] Apache CloudStack Plugin - Open vSwitch ... SUCCESS [0.041s]
[INFO] Apache CloudStack Plugin - Hypervisor Xen . SUCCESS [0.119s]
[INFO] Apache CloudStack Plugin - Hypervisor KVM . SUCCESS [0.399s]
[INFO] Apache CloudStack Plugin - Network Elastic Load Balancer  SUCCESS
[0.075s]
[INFO] Apache CloudStack Plugin - Network Nicira NVP . SUCCESS [0.057s]
[INFO] Apache CloudStack Plugin - Storage Allocator Random  SUCCESS [0.039s]
[INFO] Apache CloudStack Plugin - User Authenticator LDAP  SUCCESS [0.038s]
[INFO] Apache CloudStack Plugin - User Authenticator MD5 . SUCCESS [0.043s]
[INFO] Apache CloudStack Plugin - User Authenticator Plain Text  SUCCESS
[0.025s]
[INFO] Apache CloudStack AWS API Bridge .. SUCCESS [2.431s]
[INFO] Apache CloudStack Test  SUCCESS [0.155s]
[INFO]

[INFO] BUILD SUCCESS
[INFO]

[INFO] Total time: 8.628s
[INFO] Finished at: Mon Apr 22 20:15:55 WIT 2013
[INFO] Final Memory: 15M/37M
[INFO]

[root@cloudserver apache-cloudstack-4.0.1-incubating-src]# mvn -pl
:cloud-client-ui jetty:run
[INFO] Scanning for projects...
[ERROR] Could not find the selected project in the reactor:
:cloud-client-ui -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MavenExecutionException

i think no cloud-client-ui in cloudstack directory, whereas i've built with
"mvn -P deps" that pulling needed dependencies for management server. any
solution for this? or the configuration's still wrong?


2013/4/22 Ajimangun lintang mas 

> when building with command "mvn -P developer clean install" , building
> apache cloudstack marvin failure
>
>
>
> 2013/4/21 Ajimangun lintang mas 
>
>> i've stopped tomcat and jetty server was starting succesfully but when i
>> write the localhost:8080/client URL on browser showed :
>> HTTP ERROR: 503
>>
>> Problem accessing /client/. Reason:
>>
>> SERVICE_UNAVAILABLE
>>
>> --
>> *Powered by Jetty://
>>
>> *
>> this's still error?
>> **
>>
>>
>> 2013/4/21 Manikanta Kattamuri 
>>
>>> Seems like tomcat or some other server is using the default jetty launch
>>> port.
>>> Try stopping tomcat if present and run "mvn -pl :cloud-client-ui
>>> jetty:run"
>>>
>>>
>>> Mani
>>>
>>>
>>> On Sat, Apr 20, 2013 at 10:23 PM, Ajimangun lintang mas <
>>> ajimangu...@gmail.com> wrote:
>>>
>>> > i've passed building CS, but when i want to start management server
>>> with
>>> > command "mvn -pl :cloud-client-ui jetty:run" hes occured issue like
>>> this :
>>> >
>>> > 2013-04-20 23:16:38.171:WARN::failed
>>> SelectChannelConnector@0.0.0.0:8080:
>>> > java.net.BindException: Address already in use
>>> > 2013-04-20 23:16:38.171:WARN::failed Server@5f00fa88:
>>> > java.net.BindException: Address already in use
>>> > [INFO] Jetty server exiting.
>>> > [INFO]
>>> >
>>> 
>>> > [INFO] BUILD FAILURE
>>> > [INFO]
>>> >
>>> 
>>> > [INFO] Total time: 33.183s
>>> > [INFO] Finished at: Sat Apr 20 23:

Re: Could use a little DevCloud/Python help

[Prasanna Santhanam]

On Sun, Apr 21, 2013 at 12:24:40AM +0530, Rohit Yadav wrote:
> On Sat, Apr 20, 2013 at 11:13 PM, David Nalley  wrote:
> 
> > On Thu, Apr 18, 2013 at 6:45 PM, Ron Young  wrote:
> > > Your message dated: Thu, 18 Apr 2013 16:30:56 -0600
> > > 
> > >
> > > Hi:
> > >
> > > I ran across this same problem this morning...
> > >
> > > I stumbled on the solution:   pip install requests
> > >
> > > -ron
> >
> >
> > Sounds like a bug (lack of proper dependencies). Can one of you file this?
> >
> 
> I think Prasanna already followed this one? Prasanna? One way to solve this
> is to put the deps in setup.py and publish snapshots (perhaps daily) on a
> pypi channel, this way a user/developer upgrades/installs which gets 'em
> any new deps.

That's right. It is fixed in marvin and the dependency has been added.
Even if you publish the snapshots there's that extra step of manually
updating marvin with a $pip install --upgrade.

Alternatively, if and when marvin does change you can simply run the
marvin.sync target in mvn as explained [1] and it will update marvin
on your system with the latest dependencies

[1] http://s.apache.org/5Iv (cf. Sync latest APIs)

-- 
Prasanna.,


Powered by BigRock.com

Re: [DOCS] "Submitting Feedback and Getting Help" in Release Notes?

[Joe Brockmeier]

On Mon, Apr 22, 2013, at 04:34 AM, Radhika Puthiyetath wrote:
> Hi Joe/David/Jessica
> 
> FYI
> 
> Today when I checked in couple of files for limit resource usage, Release
> Notes build failed. The files I checked in are nothing to do with the
> Release Notes.
> 
> I am trying to fix the build errors, and found that no feedback.xml file
> is available in the repo. So I checked in one to Common_Content/.

What platform are you building your stuff on?

I changed the branding package recently to include the Feedback.xml
stuff, and if you're building on Linux you need to re-install the RPM
with the updates. 

Best,

jzb
-- 
Joe Brockmeier
j...@zonker.net
Twitter: @jzb
http://www.dissociatedpress.net/
Best,

jzb
-- 
Joe Brockmeier
j...@zonker.net
Twitter: @jzb
http://www.dissociatedpress.net/

RE: [DOCS] "Submitting Feedback and Getting Help" in Release Notes?

[Radhika Puthiyetath]

Hi Joe,

I was talking about the Release Notes build on my Windows  machine. When I 
checked in the files for admin guide, a build is automatically triggered for 
install, admin, and Release Notes.

Install and RN gave IDREF issues for the files that I have not touched, which I 
tried to fix.

When I ran publican build locally, it gave me the same IDREF error so I had to 
add a feedback.xml file !

-Original Message-
From: Joe Brockmeier [mailto:j...@zonker.net] 
Sent: Monday, April 22, 2013 7:21 PM
To: dev@cloudstack.apache.org
Subject: Re: [DOCS] "Submitting Feedback and Getting Help" in Release Notes?

On Mon, Apr 22, 2013, at 04:34 AM, Radhika Puthiyetath wrote:
> Hi Joe/David/Jessica
> 
> FYI
> 
> Today when I checked in couple of files for limit resource usage, 
> Release Notes build failed. The files I checked in are nothing to do 
> with the Release Notes.
> 
> I am trying to fix the build errors, and found that no feedback.xml 
> file is available in the repo. So I checked in one to Common_Content/.

What platform are you building your stuff on?

I changed the branding package recently to include the Feedback.xml stuff, and 
if you're building on Linux you need to re-install the RPM with the updates. 

Best,

jzb
--
Joe Brockmeier
j...@zonker.net
Twitter: @jzb
http://www.dissociatedpress.net/
Best,

jzb
--
Joe Brockmeier
j...@zonker.net
Twitter: @jzb
http://www.dissociatedpress.net/

Re: Review Request: fix the string formatting error in cloudConnection.py

[Prasanna Santhanam]

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

Ship it!


- Prasanna Santhanam


On April 22, 2013, 11:21 a.m., SrikanteswaraRao Talluri wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/10702/
> ---
> 
> (Updated April 22, 2013, 11:21 a.m.)
> 
> 
> Review request for cloudstack and Prasanna Santhanam.
> 
> 
> Description
> ---
> 
> fix the string formatting error in cloudConnection.py
> 
> error seen:
> 
> Traceback (most recent call last):
>   File "/usr/local/bin/nosetests-2.7", line 9, in 
> load_entry_point('nose==1.2.1', 'console_scripts', 'nosetests-2.7')()
>   File 
> "/usr/local/lib/python2.7/site-packages/nose-1.2.1-py2.7.egg/nose/core.py", 
> line 118, in __init__
> **extra_args)
>   File "/usr/local/lib/python2.7/unittest/main.py", line 94, in __init__
> self.parseArgs(argv)
>   File 
> "/usr/local/lib/python2.7/site-packages/nose-1.2.1-py2.7.egg/nose/core.py", 
> line 135, in parseArgs
> self.config.configure(argv, doc=self.usage())
>   File 
> "/usr/local/lib/python2.7/site-packages/nose-1.2.1-py2.7.egg/nose/config.py", 
> line 338, in configure
> self.plugins.configure(options, self)
>   File 
> "/usr/local/lib/python2.7/site-packages/nose-1.2.1-py2.7.egg/nose/plugins/manager.py",
>  line 284, in configure
> cfg(options, config)
>   File 
> "/usr/local/lib/python2.7/site-packages/nose-1.2.1-py2.7.egg/nose/plugins/manager.py",
>  line 99, in __call__
> return self.call(*arg, **kw)
>   File 
> "/usr/local/lib/python2.7/site-packages/nose-1.2.1-py2.7.egg/nose/plugins/manager.py",
>  line 167, in simple
> result = meth(*arg, **kw)
>   File 
> "/usr/local/lib/python2.7/site-packages/marvin_nose-0.1.0-py2.7.egg/marvinPlugin.py",
>  line 42, in configure
> deploy.loadCfg() if options.load else deploy.deploy()
>   File "/usr/local/lib/python2.7/site-packages/marvin/deployDataCenter.py", 
> line 452, in deploy
> self.loadCfg()
>   File "/usr/local/lib/python2.7/site-packages/marvin/deployDataCenter.py", 
> line 409, in loadCfg
> apiKey, securityKey = self.registerApiKey()
>   File "/usr/local/lib/python2.7/site-packages/marvin/deployDataCenter.py", 
> line 349, in registerApiKey
> listuserRes = self.testClient.getApiClient().listUsers(listuser)
>   File 
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
>  line 436, in listUsers
> response = self.connection.marvin_request(command, data=postdata, 
> response_type=response)
>   File 
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py", line 
> 212, in marvin_request
> cmdname, auth=False, payload=payload, data=data)
>   File 
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py", line 
> 141, in request
> (self.baseurl, c))
> TypeError: not all arguments converted during string formatting 
> 
> 
> This addresses bug CLOUDSTACK-2135.
> 
> 
> Diffs
> -
> 
>   tools/marvin/marvin/cloudstackConnection.py 14b12e7 
> 
> Diff: https://reviews.apache.org/r/10702/diff/
> 
> 
> Testing
> ---
> 
> tested
> 
> 
> Thanks,
> 
> SrikanteswaraRao Talluri
> 
>

Re: Review Request: fix the string formatting error in cloudConnection.py

[Prasanna Santhanam]

> On April 22, 2013, 2:19 p.m., Prasanna Santhanam wrote:
> >

9572f576483796beb85c7aeb5e0ce3925aee9e42


- Prasanna


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


On April 22, 2013, 11:21 a.m., SrikanteswaraRao Talluri wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/10702/
> ---
> 
> (Updated April 22, 2013, 11:21 a.m.)
> 
> 
> Review request for cloudstack and Prasanna Santhanam.
> 
> 
> Description
> ---
> 
> fix the string formatting error in cloudConnection.py
> 
> error seen:
> 
> Traceback (most recent call last):
>   File "/usr/local/bin/nosetests-2.7", line 9, in 
> load_entry_point('nose==1.2.1', 'console_scripts', 'nosetests-2.7')()
>   File 
> "/usr/local/lib/python2.7/site-packages/nose-1.2.1-py2.7.egg/nose/core.py", 
> line 118, in __init__
> **extra_args)
>   File "/usr/local/lib/python2.7/unittest/main.py", line 94, in __init__
> self.parseArgs(argv)
>   File 
> "/usr/local/lib/python2.7/site-packages/nose-1.2.1-py2.7.egg/nose/core.py", 
> line 135, in parseArgs
> self.config.configure(argv, doc=self.usage())
>   File 
> "/usr/local/lib/python2.7/site-packages/nose-1.2.1-py2.7.egg/nose/config.py", 
> line 338, in configure
> self.plugins.configure(options, self)
>   File 
> "/usr/local/lib/python2.7/site-packages/nose-1.2.1-py2.7.egg/nose/plugins/manager.py",
>  line 284, in configure
> cfg(options, config)
>   File 
> "/usr/local/lib/python2.7/site-packages/nose-1.2.1-py2.7.egg/nose/plugins/manager.py",
>  line 99, in __call__
> return self.call(*arg, **kw)
>   File 
> "/usr/local/lib/python2.7/site-packages/nose-1.2.1-py2.7.egg/nose/plugins/manager.py",
>  line 167, in simple
> result = meth(*arg, **kw)
>   File 
> "/usr/local/lib/python2.7/site-packages/marvin_nose-0.1.0-py2.7.egg/marvinPlugin.py",
>  line 42, in configure
> deploy.loadCfg() if options.load else deploy.deploy()
>   File "/usr/local/lib/python2.7/site-packages/marvin/deployDataCenter.py", 
> line 452, in deploy
> self.loadCfg()
>   File "/usr/local/lib/python2.7/site-packages/marvin/deployDataCenter.py", 
> line 409, in loadCfg
> apiKey, securityKey = self.registerApiKey()
>   File "/usr/local/lib/python2.7/site-packages/marvin/deployDataCenter.py", 
> line 349, in registerApiKey
> listuserRes = self.testClient.getApiClient().listUsers(listuser)
>   File 
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
>  line 436, in listUsers
> response = self.connection.marvin_request(command, data=postdata, 
> response_type=response)
>   File 
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py", line 
> 212, in marvin_request
> cmdname, auth=False, payload=payload, data=data)
>   File 
> "/usr/local/lib/python2.7/site-packages/marvin/cloudstackConnection.py", line 
> 141, in request
> (self.baseurl, c))
> TypeError: not all arguments converted during string formatting 
> 
> 
> This addresses bug CLOUDSTACK-2135.
> 
> 
> Diffs
> -
> 
>   tools/marvin/marvin/cloudstackConnection.py 14b12e7 
> 
> Diff: https://reviews.apache.org/r/10702/diff/
> 
> 
> Testing
> ---
> 
> tested
> 
> 
> Thanks,
> 
> SrikanteswaraRao Talluri
> 
>

Re: Review Request: Cloudstack-701 Support for non contiguous vlan ranges.

[Prasanna Santhanam]

On Tue, Apr 16, 2013 at 02:53:43PM +, bharat kumar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/10238/
> ---
> 
> (Updated April 16, 2013, 2:53 p.m.)
> 
> 
> Review request for cloudstack and Abhinandan Prateek.
> 
> 
> Description
> ---
> 
> Cloudstack-701: Support for non contiguous vlan ranges.
> 
> 
> Diffs (updated)
> -
> 
>   test/integration/smoke/test_non_contigiousvlan.py PRE-CREATION 
Thanks for taking the time to write a marvin test. But please ensure
you've run it against the simulator or an environment the test is
suitable for. Also pay attention to the existing examples in other
areas - there's some good libraries included in Marvin to simplify
test case writing.

In your case I had to fix up the test to run as it had SyntaxErrors
in it.

-- 
Prasanna.,


Powered by BigRock.com

Re: [DOCS] "Submitting Feedback and Getting Help" in Release Notes?

[Joe Brockmeier]

On Mon, Apr 22, 2013, at 09:14 AM, Radhika Puthiyetath wrote:
> I was talking about the Release Notes build on my Windows  machine. When
> I checked in the files for admin guide, a build is automatically
> triggered for install, admin, and Release Notes.

I knew you meant local machine. There's the files we usually edit, and
then the Publican branding files that we usually don't but are
automatically pulled in under the system common content. 

On Linux, these are installed with the publican-cloudstack package. I
don't know how you install it on Windows, unfortunately. How did you
install the branding files initially? 

Best,

jzb
-- 
Joe Brockmeier
j...@zonker.net
Twitter: @jzb
http://www.dissociatedpress.net/

Re: [DOCS][TRANSLATIONS] Upate

[Milamber]

Le 17/04/2013 07:26, Sebastien Goasguen a ecrit :

On Apr 16, 2013, at 11:10 AM, Milamber  wrote:



Le 16/04/2013 13:41, Gavin Lee a ecrit :

Yes, Traditional Chinese moving very quickly.
Hopefully, the other languages can have more contributors.

For the UI part, I saw the characters are not recognizable (browser
encoding setting: auto detect&   Unicode UTF-8):
ja: http://snag.gy/AVsbU.jpg
zh_CN: http://snag.gy/MxbBS.jpg

This screenshots shows some characters with a incorrect encoding (try to 
display a char as a ISO-8859-1 (or japanese charset) but the encoding is a 
UTF-8, I think)

With Sebgoa, we have correct all UI ressource file to have only one encoding 
charset in this files (ASCII with unicode). The transifex data isn't up-to-date.

Sebgoa, I think we must upload the last version of this (all) resources files 
(except FR already done) from branch 4.1 to transifex.
The last version of resources files is ASCII with unicode for *all chars* in 
each file, and now transifex keep the unicode char (check with FR download for 
use)


Mistake: transifex don't support uploaded unicode chars.


The way the original workflow was:
-Upload new versions of the resources file in english
-Translators create a new language in transifex.
-Download new language resources file
-Fix encoding


For the fix encoding step, we can use this (unix and JDK) commands for 
each language:


CODELANG=it_IT
FILE_TRANSIFEX=for_use_CloudStack_UI_41xmessageproperties_${CODELANG}.properties
FILE_RES=messages_${CODELANG}.properties

# Convert to ascii with unicode (native2ascii is a JDK tool)
native2ascii ${FILE_TRANSIFEX} /tmp/${FILE_RES}.ascii-with-unicode

# sort key, add a double-backslash before the quote char ( ' ==> \\' )
grep -v "^#" /tmp/${FILE_RES}.ascii-with-unicode | sort -f | uniq | sed 
"s/'/\'/g" > 
/tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote


# Define Apache Licence Header (one long line)
AL2_STRING="# Licensed to the Apache Software Foundation (ASF) under 
one\n# or more contributor license agreements.  See the NOTICE file\n# 
distributed with this work for additional information\n# regarding 
copyright ownership.  The ASF licenses this file\n# to you under the 
Apache License, Version 2.0 (the\n# \"License\"); you may not use this 
file except in compliance\n# with the License.  You may obtain a copy of 
the License at\n#\n#   http://www.apache.org/licenses/LICENSE-2.0\n#\n# 
Unless required by applicable law or agreed to in writing,\n# software 
distributed under the License is distributed on an\n# \"AS IS\" BASIS, 
WITHOUT WARRANTIES OR CONDITIONS OF ANY\n# KIND, either express or 
implied.  See the License for the\n# specific language governing 
permissions and limitations\n# under the License."


# Re-introduce the AL2 header
echo -e "$AL2_STRING" | cat - 
/tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote > 
./FOR_REPO_${FILE_RES}





So I never uploaded the language specific resource file to transifex. Won't we 
have a problem that they won't stay in sync with the en-US resource file, if it 
gets changed ?


On upload, Transifex seems only get the matching key with source language.



In any case I uploaded the ja-JP resource file and the result on transifex is 
less than optimal, check the unreviewed strings, there is a mix of encoding.


We needs to revert the native to ascii convert.
We can use this steps for each language before uploading on transifex :

CODELANG=ja
FILE_RES=messages_${CODELANG}.properties

# Revert convert
native2ascii -reverse ${FILE_RES} /tmp/${FILE_RES}.native1

# Remove double backslashes before quote
sed "s/\\\'/'/g" /tmp/${FILE_RES}.native1 > ${FILE_RES}.native


I've tested this commandes for download/upload with French language, and 
just for download with ko_KR, it_IT, ca, ja, pt_BR.



I can make one shell script to automate this, and put in a tools dir in 
CS git repo.


Milamber









Milamber





The other languages are ok.


On Tue, Apr 16, 2013 at 8:25 PM, Sebastien Goasguenwrote:


Hi,

There has been some terrific progress on the translations.

The easiest way to share it is to check the Transifex dashboard, below are
some screenshots:

The runbook:
http://awesomescreenshot.com/0bd163zldd

The UI:
http://awesomescreenshot.com/089163zva2

The entire docs set:
http://awesomescreenshot.com/01c163zq63

Since 4.1 is not out yet, there is time to finish those last 3% on the UI
translations.

Keep getting the word out, forward to friends and let's all make
CloudStack a truly worldwide project.

Cheers,

-Sebastien

[VOTE] Apache Cloudstack 4.1.0

[Chip Childers]

Hi All,

I've created a 4.1.0 release, with the following artifacts up for a
vote:

Git Branch and Commit SH:
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.1
Commit: b7abc3ca1e5f646722ed9cf78b93849c6c47e3d0

List of changes:
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=CHANGES;hb=4.1

Source release (checksums and signatures are available at the same
location):
https://dist.apache.org/repos/dist/dev/cloudstack/4.1.0/

PGP release keys (signed using A99A5D58):
https://dist.apache.org/repos/dist/release/cloudstack/KEYS

Testing instructions are here:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+procedure

Vote will be open for 72 hours.

For sanity in tallying the vote, can PMC members please be sure to
indicate "(binding)" with their vote?

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

Re: [VOTE][ACS402] Apache CloudStack 4.0.2 (Third Round)

[Marcus Sorensen]

+1 (binding) - tested in devcloud-kvm, deployed advanced zone, template,
VPC, two tiers, two instances, checked connectivity, added data volumes,
removed data volumes, destroyed instances.


On Mon, Apr 22, 2013 at 7:27 AM, Joe Brockmeier  wrote:

> On Mon, Apr 22, 2013, at 04:56 AM, Sebastien Goasguen wrote:
> > +1 (binding)
> >
> > Followed my screencast at:
> > http://www.youtube.com/watch?v=vvgIkF1e1QE
>
> Thanks, Sebastien!
>
> Best,
>
> jzb
> --
> Joe Brockmeier
> j...@zonker.net
> Twitter: @jzb
> http://www.dissociatedpress.net/
>

New PMC Member: Prasanna Santhanam

[Chip Childers]

Hi folks

The Project Management Committee (PMC) for Apache CloudStack
has asked Prasanna Santhanam to become a member of the PMC and 
we are pleased to announce that he has accepted.

Please join me in congratulating Prasanna!

Regards,

--Chip
on behalf of the CloudStack PMC

Re: New PMC Member: Prasanna Santhanam

[Nitin Mehta]

Congrats PrasannaŠgreat work man keep it up !!!

On 22/04/13 9:21 PM, "Chip Childers"  wrote:

>Hi folks
>
>The Project Management Committee (PMC) for Apache CloudStack
>has asked Prasanna Santhanam to become a member of the PMC and
>we are pleased to announce that he has accepted.
>
>Please join me in congratulating Prasanna!
>
>Regards,
>
>--Chip
>on behalf of the CloudStack PMC

RE: New PMC Member: Prasanna Santhanam

[Koushik Das]

Congrats Prasanna!

> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Monday, April 22, 2013 9:21 PM
> To: dev@cloudstack.apache.org
> Subject: New PMC Member: Prasanna Santhanam
> 
> Hi folks
> 
> The Project Management Committee (PMC) for Apache CloudStack has
> asked Prasanna Santhanam to become a member of the PMC and we are
> pleased to announce that he has accepted.
> 
> Please join me in congratulating Prasanna!
> 
> Regards,
> 
> --Chip
> on behalf of the CloudStack PMC

Re: [DOCS][TRANSLATIONS] Upate

[Sebastien Goasguen]

Milamber, I made you a manager of the transifex project so you can help fixing 
those issues.

-sebastien

On Apr 22, 2013, at 11:10 AM, Milamber  wrote:

> 
> 
> Le 17/04/2013 07:26, Sebastien Goasguen a ecrit :
>> On Apr 16, 2013, at 11:10 AM, Milamber  wrote:
>> 
>>> 
>>> Le 16/04/2013 13:41, Gavin Lee a ecrit :
 Yes, Traditional Chinese moving very quickly.
 Hopefully, the other languages can have more contributors.
 
 For the UI part, I saw the characters are not recognizable (browser
 encoding setting: auto detect&   Unicode UTF-8):
 ja: http://snag.gy/AVsbU.jpg
 zh_CN: http://snag.gy/MxbBS.jpg
>>> This screenshots shows some characters with a incorrect encoding (try to 
>>> display a char as a ISO-8859-1 (or japanese charset) but the encoding is a 
>>> UTF-8, I think)
>>> 
>>> With Sebgoa, we have correct all UI ressource file to have only one 
>>> encoding charset in this files (ASCII with unicode). The transifex data 
>>> isn't up-to-date.
>>> 
>>> Sebgoa, I think we must upload the last version of this (all) resources 
>>> files (except FR already done) from branch 4.1 to transifex.
>>> The last version of resources files is ASCII with unicode for *all chars* 
>>> in each file, and now transifex keep the unicode char (check with FR 
>>> download for use)
> 
> Mistake: transifex don't support uploaded unicode chars.
> 
>> The way the original workflow was:
>> -Upload new versions of the resources file in english
>> -Translators create a new language in transifex.
>> -Download new language resources file
>> -Fix encoding
> 
> For the fix encoding step, we can use this (unix and JDK) commands for each 
> language:
> 
> CODELANG=it_IT
> FILE_TRANSIFEX=for_use_CloudStack_UI_41xmessageproperties_${CODELANG}.properties
> FILE_RES=messages_${CODELANG}.properties
> 
> # Convert to ascii with unicode (native2ascii is a JDK tool)
> native2ascii ${FILE_TRANSIFEX} /tmp/${FILE_RES}.ascii-with-unicode
> 
> # sort key, add a double-backslash before the quote char ( ' ==> \\' )
> grep -v "^#" /tmp/${FILE_RES}.ascii-with-unicode | sort -f | uniq | sed 
> "s/'/\'/g" > /tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote
> 
> # Define Apache Licence Header (one long line)
> AL2_STRING="# Licensed to the Apache Software Foundation (ASF) under one\n# 
> or more contributor license agreements.  See the NOTICE file\n# distributed 
> with this work for additional information\n# regarding copyright ownership.  
> The ASF licenses this file\n# to you under the Apache License, Version 2.0 
> (the\n# \"License\"); you may not use this file except in compliance\n# with 
> the License.  You may obtain a copy of the License at\n#\n#   
> http://www.apache.org/licenses/LICENSE-2.0\n#\n# Unless required by 
> applicable law or agreed to in writing,\n# software distributed under the 
> License is distributed on an\n# \"AS IS\" BASIS, WITHOUT WARRANTIES OR 
> CONDITIONS OF ANY\n# KIND, either express or implied.  See the License for 
> the\n# specific language governing permissions and limitations\n# under the 
> License."
> 
> # Re-introduce the AL2 header
> echo -e "$AL2_STRING" | cat - 
> /tmp/${FILE_RES}.ascii-with-unicode_doublebackslashquote > 
> ./FOR_REPO_${FILE_RES}
> 
> 
>> 
>> So I never uploaded the language specific resource file to transifex. Won't 
>> we have a problem that they won't stay in sync with the en-US resource file, 
>> if it gets changed ?
> 
> On upload, Transifex seems only get the matching key with source language.
> 
>> 
>> In any case I uploaded the ja-JP resource file and the result on transifex 
>> is less than optimal, check the unreviewed strings, there is a mix of 
>> encoding.
> 
> We needs to revert the native to ascii convert.
> We can use this steps for each language before uploading on transifex :
> 
> CODELANG=ja
> FILE_RES=messages_${CODELANG}.properties
> 
> # Revert convert
> native2ascii -reverse ${FILE_RES} /tmp/${FILE_RES}.native1
> 
> # Remove double backslashes before quote
> sed "s/\\\'/'/g" /tmp/${FILE_RES}.native1 > ${FILE_RES}.native
> 
> 
> I've tested this commandes for download/upload with French language, and just 
> for download with ko_KR, it_IT, ca, ja, pt_BR.
> 
> 
> I can make one shell script to automate this, and put in a tools dir in CS 
> git repo.
> 
> Milamber
> 
> 
> 
> 
> 
>> 
>> 
>>> Milamber
>>> 
>>> 
>>> 
>>> 
 The other languages are ok.
 
 
 On Tue, Apr 16, 2013 at 8:25 PM, Sebastien Goasguenwrote:
 
> Hi,
> 
> There has been some terrific progress on the translations.
> 
> The easiest way to share it is to check the Transifex dashboard, below are
> some screenshots:
> 
> The runbook:
> http://awesomescreenshot.com/0bd163zldd
> 
> The UI:
> http://awesomescreenshot.com/089163zva2
> 
> The entire docs set:
> http://awesomescreenshot.com/01c163zq63
> 
> Since 4.1 is not out yet, there is time to finish those last 3% on the UI
>>

RE: New PMC Member: Prasanna Santhanam

[Sateesh Chodapuneedi]

> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: 22 April 2013 21:21
> To: dev@cloudstack.apache.org
> Subject: New PMC Member: Prasanna Santhanam
> 
> Hi folks
> 
> The Project Management Committee (PMC) for Apache CloudStack has asked
> Prasanna Santhanam to become a member of the PMC and we are pleased
> to announce that he has accepted.
> 
> Please join me in congratulating Prasanna!

Hearty Congrats Prasanna :)
Well deserved!

Regards,
Sateesh

Re: New PMC Member: Prasanna Santhanam

[Joe Brockmeier]

On Mon, Apr 22, 2013, at 10:51 AM, Chip Childers wrote:
> Please join me in congratulating Prasanna!

Congratulations, Prasanna! 

Best,

jzb
-- 
Joe Brockmeier
j...@zonker.net
Twitter: @jzb
http://www.dissociatedpress.net/

RE: New PMC Member: Prasanna Santhanam

[Radhika Puthiyetath]

Congratz Prasanna...

-Original Message-
From: Chip Childers [mailto:chip.child...@sungard.com] 
Sent: Monday, April 22, 2013 9:21 PM
To: dev@cloudstack.apache.org
Subject: New PMC Member: Prasanna Santhanam

Hi folks

The Project Management Committee (PMC) for Apache CloudStack has asked Prasanna 
Santhanam to become a member of the PMC and we are pleased to announce that he 
has accepted.

Please join me in congratulating Prasanna!

Regards,

--Chip
on behalf of the CloudStack PMC

RE: [DOCS] "Submitting Feedback and Getting Help" in Release Notes?

[Radhika Puthiyetath]

Looks like I have to reinstall the branding files. I simply followed the steps 
in the Publican User Guide...the branding files are grabbed from Jessica.

-Original Message-
From: Joe Brockmeier [mailto:j...@zonker.net] 
Sent: Monday, April 22, 2013 8:09 PM
To: dev@cloudstack.apache.org
Subject: Re: [DOCS] "Submitting Feedback and Getting Help" in Release Notes?

On Mon, Apr 22, 2013, at 09:14 AM, Radhika Puthiyetath wrote:
> I was talking about the Release Notes build on my Windows  machine. 
> When I checked in the files for admin guide, a build is automatically 
> triggered for install, admin, and Release Notes.

I knew you meant local machine. There's the files we usually edit, and then the 
Publican branding files that we usually don't but are automatically pulled in 
under the system common content. 

On Linux, these are installed with the publican-cloudstack package. I don't 
know how you install it on Windows, unfortunately. How did you install the 
branding files initially? 

Best,

jzb
--
Joe Brockmeier
j...@zonker.net
Twitter: @jzb
http://www.dissociatedpress.net/

Re: New PMC Member: Prasanna Santhanam

[Min Chen]

Congratulations, Prasanna.

-min

On 4/22/13 8:51 AM, "Chip Childers"  wrote:

>Hi folks
>
>The Project Management Committee (PMC) for Apache CloudStack
>has asked Prasanna Santhanam to become a member of the PMC and
>we are pleased to announce that he has accepted.
>
>Please join me in congratulating Prasanna!
>
>Regards,
>
>--Chip
>on behalf of the CloudStack PMC

RE: New PMC Member: Prasanna Santhanam

[Musayev, Ilya]

Congrats Prasanna!

> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Monday, April 22, 2013 11:51 AM
> To: dev@cloudstack.apache.org
> Subject: New PMC Member: Prasanna Santhanam
> 
> Hi folks
> 
> The Project Management Committee (PMC) for Apache CloudStack has
> asked Prasanna Santhanam to become a member of the PMC and we are
> pleased to announce that he has accepted.
> 
> Please join me in congratulating Prasanna!
> 
> Regards,
> 
> --Chip
> on behalf of the CloudStack PMC

RE: [VOTE] Apache Cloudstack 4.1.0

[Musayev, Ilya]

+ 1 (binding)

> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Monday, April 22, 2013 11:38 AM
> To: dev@cloudstack.apache.org
> Subject: [VOTE] Apache Cloudstack 4.1.0
> 
> Hi All,
> 
> I've created a 4.1.0 release, with the following artifacts up for a
> vote:
> 
> Git Branch and Commit SH:
> https://git-wip-
> us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.1
> Commit: b7abc3ca1e5f646722ed9cf78b93849c6c47e3d0
> 
> List of changes:
> https://git-wip-
> us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=CHANGES;hb=4.1
> 
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.1.0/
> 
> PGP release keys (signed using A99A5D58):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> 
> Testing instructions are here:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+pr
> ocedure
> 
> Vote will be open for 72 hours.
> 
> For sanity in tallying the vote, can PMC members please be sure to indicate
> "(binding)" with their vote?
> 
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)

Re: [DOCS] "Submitting Feedback and Getting Help" in Release Notes?

[David Nalley]

The branding files are in git /docs/publican-cloudstack

On Mon, Apr 22, 2013 at 12:13 PM, Radhika Puthiyetath
 wrote:
> Looks like I have to reinstall the branding files. I simply followed the 
> steps in the Publican User Guide...the branding files are grabbed from 
> Jessica.
>
> -Original Message-
> From: Joe Brockmeier [mailto:j...@zonker.net]
> Sent: Monday, April 22, 2013 8:09 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [DOCS] "Submitting Feedback and Getting Help" in Release Notes?
>
> On Mon, Apr 22, 2013, at 09:14 AM, Radhika Puthiyetath wrote:
>> I was talking about the Release Notes build on my Windows  machine.
>> When I checked in the files for admin guide, a build is automatically
>> triggered for install, admin, and Release Notes.
>
> I knew you meant local machine. There's the files we usually edit, and then 
> the Publican branding files that we usually don't but are automatically 
> pulled in under the system common content.
>
> On Linux, these are installed with the publican-cloudstack package. I don't 
> know how you install it on Windows, unfortunately. How did you install the 
> branding files initially?
>
> Best,
>
> jzb
> --
> Joe Brockmeier
> j...@zonker.net
> Twitter: @jzb
> http://www.dissociatedpress.net/

Re: New PMC Member: Prasanna Santhanam

[Sebastien Goasguen]

Well done Prasanna,

On Apr 22, 2013, at 12:28 PM, "Musayev, Ilya"  wrote:

> Congrats Prasanna!
> 
>> -Original Message-
>> From: Chip Childers [mailto:chip.child...@sungard.com]
>> Sent: Monday, April 22, 2013 11:51 AM
>> To: dev@cloudstack.apache.org
>> Subject: New PMC Member: Prasanna Santhanam
>> 
>> Hi folks
>> 
>> The Project Management Committee (PMC) for Apache CloudStack has
>> asked Prasanna Santhanam to become a member of the PMC and we are
>> pleased to announce that he has accepted.
>> 
>> Please join me in congratulating Prasanna!
>> 
>> Regards,
>> 
>> --Chip
>> on behalf of the CloudStack PMC
> 
> 

RE: New PMC Member: Prasanna Santhanam

[Kelcey Damage (BT)]

Congrats!


>-Original Message-
>From: Sebastien Goasguen [mailto:run...@gmail.com]
>Sent: Monday, April 22, 2013 9:51 AM
>To: dev@cloudstack.apache.org
>Subject: Re: New PMC Member: Prasanna Santhanam
>
>Well done Prasanna,
>
>On Apr 22, 2013, at 12:28 PM, "Musayev, Ilya" 
>wrote:
>
>> Congrats Prasanna!
>>
>>> -Original Message-
>>> From: Chip Childers [mailto:chip.child...@sungard.com]
>>> Sent: Monday, April 22, 2013 11:51 AM
>>> To: dev@cloudstack.apache.org
>>> Subject: New PMC Member: Prasanna Santhanam
>>>
>>> Hi folks
>>>
>>> The Project Management Committee (PMC) for Apache CloudStack has
>>> asked Prasanna Santhanam to become a member of the PMC and we are
>>> pleased to announce that he has accepted.
>>>
>>> Please join me in congratulating Prasanna!
>>>
>>> Regards,
>>>
>>> --Chip
>>> on behalf of the CloudStack PMC
>>
>>

Re: [DIscuss]Storage image store plugin framework refactoring

[Min Chen]

Yes. You should be able to use it to test S3 object store.

THanks
-min

On 4/22/13 4:53 AM, "Sanjeev Neelarapu" 
wrote:

>Hi,
>
>I have prepared RIAK CS object store in our lab environment and planning
>to use it for object store feature testing .
>As per my understanding RIAK CS supports S3 APIs. So let me know whether
>I can use it as an alternative to s3 based object store.
>
>Thanks,
>Sanjeev
>
>-Original Message-
>From: prasanna [mailto:srivatsav.prasa...@gmail.com] On Behalf Of
>Prasanna Santhanam
>Sent: Wednesday, April 10, 2013 12:42 PM
>To: dev@cloudstack.apache.org
>Subject: Re: [DIscuss]Storage image store plugin framework refactoring
>
>On Tue, Apr 09, 2013 at 09:19:11AM -0700, Min Chen wrote:
>> Not yet at this moment. But we are planning to provide a sample plugin
>> implementation for this effort. If you are looking at object_store
>> branch, you will see a plugin called
>> "cloud-plugin-storage-image-sample", which will be the placeholder for
>>a sample image store implementation.
>> 
>
>Hmmm - more frameworks and no reference implementation? :(
>
>I'm keeping an eye on the branch and was hoping there'd be an
>implementation of an objectstore because I'm looking to span this
>solution across some qa labs. RiakCS, Swift are all opensource now.
>
>--
>Prasanna.,

Re: [DIscuss]Storage image store plugin framework refactoring

[Min Chen]

See my comments inline.

-min

On 4/16/13 11:41 PM, "Sanjeev Neelarapu" 
wrote:

>Hi,
>
>Few more review comments:
>1.In a fresh installed environment will SSVM continue to be there? If yes
>will it be auto launched or admin should launch it?
[Min] ssvm will still be there and auto-launched as before.
>2.How do we seed system vm templates in case of object storage?
[Min] We will trigger system vm template download while adding an S3
object storage into cloudstack. The download is happening through MS host.
>3.Is there any difference in seeding system vm templates with NFS storage
>compared to what we do as of today?
[Min] We are not planning to change system vm templates seeding with NFS
storage at this point, still assume that you have pre-seeded system vm
template on NFS.
>4.In upgraded environment, can we have both NFS and object storage? If
>not what is the procedure to migrate from nfs to object storage ?
[Min] In our FS, we have made an assumption that "you can add multiple
image stores from the same provider, but we prevent you from adding
multiple image
stores from different providers." This implied that we cannot have both
NFS and S3 co-existing for this release. You raised a very good point,
honestly I don't have an answer at this point. Edison, any thoughts on
this?
>
>Thanks,
>Sanjeev
>
>-Original Message-
>From: Min Chen [mailto:min.c...@citrix.com]
>Sent: Wednesday, April 10, 2013 3:23 AM
>To: dev@cloudstack.apache.org
>Subject: Re: [DIscuss]Storage image store plugin framework refactoring
>
>Hi Sangeetha, 
>
>   See my answers inline.
>
>   Thanks
>   -min
>
>On 4/9/13 2:48 PM, "Sangeetha Hariharan" 
>wrote:
>
>>Can image stores from different providers (NFS,SWIFT,S3) coexist in the
>>same deployment ?
>>Is the scope for NFS always Zone-wide and SWIFT and S3 region-wide?
>[Min] Currently this is our assumption: you can add multiple image stores
>from the same provider, but we prevent you from adding multiple image
>stores from different providers. For NFS image store providers, it is
>always zone-wide. And For S3/Swift, it is always region-wide.
>>
>>There is an api for "enableImageStoreCmd" . Can multiple image stores
>>be enabled at the same time?
>>I don't see any api for disabling image store? What does it mean to
>>disable an already enabled image store? Will all the resources like
>>templates, iso and snapshot residing in this image store not be
>>available to the users anymore?
>[Min] On second thought, we decide to drop this api. addImageStore api
>will automatically make the image store added active to be consistent
>with current secondary storage behavior.
>> 
>>
>>deleteImageStoreCmd - Will we allow for deletion of an image store when
>>it has resources like  templates, iso and snapshots residing in it?
>[Min] Deletion of an image store will check if it has resources like
>template, snapshots, and volumes. If there are resources residing in it,
>we will throw error.
>>
>>-Thanks
>>Sangeetha
>>
>>-Original Message-
>>From: Edison Su [mailto:edison...@citrix.com]
>>Sent: Tuesday, April 09, 2013 2:01 PM
>>To: dev@cloudstack.apache.org
>>Subject: RE: [DIscuss]Storage image store plugin framework refactoring
>>
>>
>>
>>> -Original Message-
>>> From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com]
>>> Sent: Monday, April 08, 2013 11:33 PM
>>> To: dev@cloudstack.apache.org
>>> Subject: Re: [DIscuss]Storage image store plugin framework
>>> refactoring
>>> 
>>> We can't deprecate APIs unless we are changing to 5.0 AFAIK the next
>>> release in plan is 4.2
>>For back compatibility, these APIs:
>>addSecondaryStorageCmd,addS3Cmd,addSwiftCmd,listS3Cmd,listSwiftCmd, can
>>still be wired to new code, so this APIs will still work, but we can
>>mark them as deprecated in the API document.
>>
>>> 
>>> How does an upgrade from 4.0/4.1 to 4.2 work with this proposal?
>>> - what happens to existing SSVMs?
>>> - if there are multiple SSVMs?
>>> - current cache-like deployments for S3 and Swift
>>
>>The existing deployment model will still work.
>>There are following combinations currently supported by CloudStack:
>>1. Only NFS as secondary storage. In the new framework, it's NFS as a
>>backup storage.
>>2. NFS + swift/S3. In the new framework, it's swift/s3 as backup
>>storage, while, NFS as cache storage.
>>So the upgrade code from pre-4.2 to 4.2 needs to handle above cases,
>>migrate DB properly.
>>
>>> 
>>> The SSVM code also does duty for VMWare deployments to aid in data
>>> movement.
>>
>>
>>The existing SSVM will still work, it will be renamed to transportation
>>VM in the code(maybe on the UI, it still be called SSVM). The main
>>functionality of these VMs are to help transfer data from one place to
>>another.  As you said, Vmware deployment needs these VMs(as Vmware
>>can't directly download template into primary storage), and old NFS
>>based secondary storage deployment model needs them(data copy when cross
>>zone).
>>
>>
>>> How does this change?
>>>

RE: New PMC Member: Prasanna Santhanam

[Srikanteswararao Talluri]

Congrats Prasanna!

~Talluri

> -Original Message-
> From: Kelcey Damage (BT) [mailto:kel...@backbonetechnology.com]
> Sent: Monday, April 22, 2013 10:35 PM
> To: dev@cloudstack.apache.org
> Subject: RE: New PMC Member: Prasanna Santhanam
> 
> Congrats!
> 
> 
> >-Original Message-
> >From: Sebastien Goasguen [mailto:run...@gmail.com]
> >Sent: Monday, April 22, 2013 9:51 AM
> >To: dev@cloudstack.apache.org
> >Subject: Re: New PMC Member: Prasanna Santhanam
> >
> >Well done Prasanna,
> >
> >On Apr 22, 2013, at 12:28 PM, "Musayev, Ilya" 
> >wrote:
> >
> >> Congrats Prasanna!
> >>
> >>> -Original Message-
> >>> From: Chip Childers [mailto:chip.child...@sungard.com]
> >>> Sent: Monday, April 22, 2013 11:51 AM
> >>> To: dev@cloudstack.apache.org
> >>> Subject: New PMC Member: Prasanna Santhanam
> >>>
> >>> Hi folks
> >>>
> >>> The Project Management Committee (PMC) for Apache CloudStack has
> >>> asked Prasanna Santhanam to become a member of the PMC and we are
> >>> pleased to announce that he has accepted.
> >>>
> >>> Please join me in congratulating Prasanna!
> >>>
> >>> Regards,
> >>>
> >>> --Chip
> >>> on behalf of the CloudStack PMC
> >>
> >>
> 

RE: qa tests for nicira code in 4.1

[Sudha Ponnaganti]

No worries. I have closed the defect and one of the stories (725)  as well.
But waiting for doc to be completed to lose this [1] story

[1] https://issues.apache.org/jira/browse/CLOUDSTACK-726


-Original Message-
From: Daan Hoogland [mailto:dhoogl...@schubergphilis.com] 
Sent: Monday, April 22, 2013 2:46 AM
To: dev@cloudstack.apache.org
Subject: RE: qa tests for nicira code in 4.1

I updated the page you pasted for me to conclude the bureaucratic part. Hope it 
satisfied the apache/cloudstack way. Is it there a formal timeline between 
resolved and closed status for tickets to observe?  (otherwise 2092 can be 
closed)

-Original Message-
From: Sudha Ponnaganti [mailto:sudha.ponnaga...@citrix.com] 
Sent: vrijdag 19 april 2013 17:54
To: dev@cloudstack.apache.org
Subject: RE: qa tests for nicira code in 4.1

If you do additional tests or update any results, you can edit that page and 
update it. Otherwise I just copied your email,

If you don't mind, can you add a note to the ticket on the testing done and 
close them. Thanks

-Original Message-
From: Daan Hoogland [mailto:dhoogl...@schubergphilis.com] 
Sent: Friday, April 19, 2013 7:27 AM
To: dev@cloudstack.apache.org
Subject: RE: qa tests for nicira code in 4.1

Hy Sudha

Both tickets can be closed.

I am not sure what to do with the page you created for me. Do you want me to 
copy the table below, with the fail changed to pass, in a new child page there?

Regards,
Daan Hoogland

-Original Message-
From: Sudha Ponnaganti [mailto:sudha.ponnaga...@citrix.com] 
Sent: donderdag 18 april 2013 22:17
To: dev@cloudstack.apache.org
Subject: RE: qa tests for nicira code in 4.1

Thanks Daan for posting test results !

I have created a place holder for you to update test results [1] - You can 
update it at your convenience. 
Does this execution cover both of these stories for Nicira [2], [3]. If it 
covers both of these stories, may be these can be closed. Looks like doc is 
also outstanding as per the JIRA status. 

[1] 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.1+Test+Execution
[2] https://issues.apache.org/jira/browse/CLOUDSTACK-726
[3] https://issues.apache.org/jira/browse/CLOUDSTACK-727



Thanks
/Sudha

-Original Message-
From: Daan Hoogland [mailto:dhoogl...@schubergphilis.com] 
Sent: Thursday, April 18, 2013 12:38 PM
To: dev@cloudstack.apache.org
Subject: qa tests for nicira code in 4.1

LS,

At Schuberg Philis we did some tests on the 4.1 code for the tests in the 
following table
Test Case ID  Test Description Results
   Infrastructure
NVP-001 Create NVP Element pass
NVP-002 Disable NVP Elementpass
NVP-003 Enable NVP Element pass
NVP-004 Delete NVP Element  pass
NVP-005 Create NVP Device   pass
NVP-006 Delete NVP Devicepass
   L2 Functions
NVP-101 Create Logical Switchpass
NVP-102 Create Logical Portpass
NVP-103 Check Connection Pass
NVP-104 Check Connection Pass
NVP-105 Delete Logical SwitchPass
NVP-106 Delete Logical Port Pass
   L3 Functions
NVP-201 Create Logical RouterPass
NVP-202 Create Source Nat rule  Pass
NVP-203 Create Static Nat rulePass
NVP-204 Create Port FW rule   Pass
NVP-205 Check Source Nat rule  Pass
NVP-206 Check Static Nat rule Pass
NVP-207 Check Port FW rule   Pass
NVP-208 Delete Source Nat rule  Pass
NVP-209 Delete Static Nat rule Fail
NVP-210 Delete Port FW rule   Pass
NVP-211 Delete Logical RouterPass

The tests where partly done aith scripts but these are not yet complete and the 
remainder of functionality was done by hand.
For the failed test, NVP-209 a ticket was created, 'CLOUDSTACK-2092'. The 
problem in this case was that deleting the static rule did not result in the 
deletion of the ip adres from the logical router.

Kind regards,
Daan Hoogland

Re: [Discuss] - Domain admin not having the flexibility to create sub-domains/sub-child domains/accounts

[Chip Childers]

On Mon, Apr 22, 2013 at 11:22:16AM +, Pranav Saxena wrote:
> Hi,
> 
> Currently only the ROOT-admin has the power to create any 
> domains/sub-domains/sub-child domains for himself or the domain-admin . But 
> there are certain situations ( like updating resource limit for a sub-child 
> domain under a domain admin ) for which the ROOT-admin has to create a 
> sub-child domain for a domain admin to allow him to update the resource 
> limits for that particular sub-child domain.
> 
> With this in mind , why hasn't the domain -admin been given the privilege of 
> creating sub-child domains himself ? Are there any concerns/threats because 
> of which the current architecture doesn't serve this purpose ?
> 
> Also , a domain-admin cannot create an account on his own using an API as 
> well ( UI can be overlooked for now) . He has to go through the ROOT-admin to 
> have this functionality enabled . So doesn't that conclude that domain-admin 
> is almost a USELESS guy with *No powers*  . To be able to navigate from step 
> 1 - > step  2 , you have to go through step 3 which seems to be unconvincing 
> at times .
> 
> Could someone explain about why such a functionality is not supported in the 
> current architecture ? Please let me know in case I am missing something here.
> 
> Thanks,
> Pranav

This never made much sense to me.

RE: [DIscuss]Storage image store plugin framework refactoring

[Edison Su]

> -Original Message-
> From: Min Chen
> Sent: Monday, April 22, 2013 10:15 AM
> To: dev@cloudstack.apache.org
> Cc: Edison Su
> Subject: Re: [DIscuss]Storage image store plugin framework refactoring
> 
> See my comments inline.
> 
> -min
> 
> On 4/16/13 11:41 PM, "Sanjeev Neelarapu" 
> wrote:
> 
> >Hi,
> >
> >Few more review comments:
> >1.In a fresh installed environment will SSVM continue to be there? If
> >yes will it be auto launched or admin should launch it?
> [Min] ssvm will still be there and auto-launched as before.
> >2.How do we seed system vm templates in case of object storage?
> [Min] We will trigger system vm template download while adding an S3
> object storage into cloudstack. The download is happening through MS host.
> >3.Is there any difference in seeding system vm templates with NFS
> >storage compared to what we do as of today?
> [Min] We are not planning to change system vm templates seeding with NFS
> storage at this point, still assume that you have pre-seeded system vm
> template on NFS.
> >4.In upgraded environment, can we have both NFS and object storage? If
> >not what is the procedure to migrate from nfs to object storage ?
> [Min] In our FS, we have made an assumption that "you can add multiple
> image stores from the same provider, but we prevent you from adding
> multiple image stores from different providers." This implied that we cannot
> have both NFS and S3 co-existing for this release. You raised a very good
> point, honestly I don't have an answer at this point. Edison, any thoughts on
> this?

The possible migration solution is that, treat existing NFS secondary storage 
as cache storage, then sync all the templates/snapshots on NFS to S3/swift 
object storage.

> >
> >Thanks,
> >Sanjeev
> >
> >-Original Message-
> >From: Min Chen [mailto:min.c...@citrix.com]
> >Sent: Wednesday, April 10, 2013 3:23 AM
> >To: dev@cloudstack.apache.org
> >Subject: Re: [DIscuss]Storage image store plugin framework refactoring
> >
> >Hi Sangeetha,
> >
> > See my answers inline.
> >
> > Thanks
> > -min
> >
> >On 4/9/13 2:48 PM, "Sangeetha Hariharan"
> >
> >wrote:
> >
> >>Can image stores from different providers (NFS,SWIFT,S3) coexist in
> >>the same deployment ?
> >>Is the scope for NFS always Zone-wide and SWIFT and S3 region-wide?
> >[Min] Currently this is our assumption: you can add multiple image
> >stores from the same provider, but we prevent you from adding multiple
> >image stores from different providers. For NFS image store providers,
> >it is always zone-wide. And For S3/Swift, it is always region-wide.
> >>
> >>There is an api for "enableImageStoreCmd" . Can multiple image stores
> >>be enabled at the same time?
> >>I don't see any api for disabling image store? What does it mean to
> >>disable an already enabled image store? Will all the resources like
> >>templates, iso and snapshot residing in this image store not be
> >>available to the users anymore?
> >[Min] On second thought, we decide to drop this api. addImageStore api
> >will automatically make the image store added active to be consistent
> >with current secondary storage behavior.
> >>
> >>
> >>deleteImageStoreCmd - Will we allow for deletion of an image store
> >>when it has resources like  templates, iso and snapshots residing in it?
> >[Min] Deletion of an image store will check if it has resources like
> >template, snapshots, and volumes. If there are resources residing in
> >it, we will throw error.
> >>
> >>-Thanks
> >>Sangeetha
> >>
> >>-Original Message-
> >>From: Edison Su [mailto:edison...@citrix.com]
> >>Sent: Tuesday, April 09, 2013 2:01 PM
> >>To: dev@cloudstack.apache.org
> >>Subject: RE: [DIscuss]Storage image store plugin framework refactoring
> >>
> >>
> >>
> >>> -Original Message-
> >>> From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com]
> >>> Sent: Monday, April 08, 2013 11:33 PM
> >>> To: dev@cloudstack.apache.org
> >>> Subject: Re: [DIscuss]Storage image store plugin framework
> >>> refactoring
> >>>
> >>> We can't deprecate APIs unless we are changing to 5.0 AFAIK the next
> >>> release in plan is 4.2
> >>For back compatibility, these APIs:
> >>addSecondaryStorageCmd,addS3Cmd,addSwiftCmd,listS3Cmd,listSwiftCm
> d,
> >>can still be wired to new code, so this APIs will still work, but we
> >>can mark them as deprecated in the API document.
> >>
> >>>
> >>> How does an upgrade from 4.0/4.1 to 4.2 work with this proposal?
> >>> - what happens to existing SSVMs?
> >>> - if there are multiple SSVMs?
> >>> - current cache-like deployments for S3 and Swift
> >>
> >>The existing deployment model will still work.
> >>There are following combinations currently supported by CloudStack:
> >>1. Only NFS as secondary storage. In the new framework, it's NFS as a
> >>backup storage.
> >>2. NFS + swift/S3. In the new framework, it's swift/s3 as backup
> >>storage, while, NFS as cache storage.
> >>So the upgrade code from pre-4.2 to 4.2 needs to handle abov

RE: New PMC Member: Prasanna Santhanam

[Prachi Damle]

Congratulations Prasanna!

-Original Message-
From: Srikanteswararao Talluri [mailto:srikanteswararao.tall...@citrix.com] 
Sent: Monday, April 22, 2013 10:27 AM
To: dev@cloudstack.apache.org
Subject: RE: New PMC Member: Prasanna Santhanam

Congrats Prasanna!

~Talluri

> -Original Message-
> From: Kelcey Damage (BT) [mailto:kel...@backbonetechnology.com]
> Sent: Monday, April 22, 2013 10:35 PM
> To: dev@cloudstack.apache.org
> Subject: RE: New PMC Member: Prasanna Santhanam
> 
> Congrats!
> 
> 
> >-Original Message-
> >From: Sebastien Goasguen [mailto:run...@gmail.com]
> >Sent: Monday, April 22, 2013 9:51 AM
> >To: dev@cloudstack.apache.org
> >Subject: Re: New PMC Member: Prasanna Santhanam
> >
> >Well done Prasanna,
> >
> >On Apr 22, 2013, at 12:28 PM, "Musayev, Ilya" 
> >wrote:
> >
> >> Congrats Prasanna!
> >>
> >>> -Original Message-
> >>> From: Chip Childers [mailto:chip.child...@sungard.com]
> >>> Sent: Monday, April 22, 2013 11:51 AM
> >>> To: dev@cloudstack.apache.org
> >>> Subject: New PMC Member: Prasanna Santhanam
> >>>
> >>> Hi folks
> >>>
> >>> The Project Management Committee (PMC) for Apache CloudStack has 
> >>> asked Prasanna Santhanam to become a member of the PMC and we are 
> >>> pleased to announce that he has accepted.
> >>>
> >>> Please join me in congratulating Prasanna!
> >>>
> >>> Regards,
> >>>
> >>> --Chip
> >>> on behalf of the CloudStack PMC
> >>
> >>
> 

RE: New PMC Member: Prasanna Santhanam

[Edison Su]

Congrats!

> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Monday, April 22, 2013 8:51 AM
> To: dev@cloudstack.apache.org
> Subject: New PMC Member: Prasanna Santhanam
> 
> Hi folks
> 
> The Project Management Committee (PMC) for Apache CloudStack has
> asked Prasanna Santhanam to become a member of the PMC and we are
> pleased to announce that he has accepted.
> 
> Please join me in congratulating Prasanna!
> 
> Regards,
> 
> --Chip
> on behalf of the CloudStack PMC

Re: [Discuss] - Domain admin not having the flexibility to create sub-domains/sub-child domains/accounts

[Alena Prokharchyk]

On 4/22/13 10:47 AM, "Chip Childers"  wrote:

>On Mon, Apr 22, 2013 at 11:22:16AM +, Pranav Saxena wrote:
>> Hi,
>> 
>> Currently only the ROOT-admin has the power to create any
>>domains/sub-domains/sub-child domains for himself or the domain-admin .
>>But there are certain situations ( like updating resource limit for a
>>sub-child domain under a domain admin ) for which the ROOT-admin has to
>>create a sub-child domain for a domain admin to allow him to update the
>>resource limits for that particular sub-child domain.
>> 
>> With this in mind , why hasn't the domain -admin been given the
>>privilege of creating sub-child domains himself ? Are there any
>>concerns/threats because of which the current architecture doesn't serve
>>this purpose ?
>> 
>> Also , a domain-admin cannot create an account on his own using an API
>>as well ( UI can be overlooked for now) . He has to go through the
>>ROOT-admin to have this functionality enabled . So doesn't that conclude
>>that domain-admin is almost a USELESS guy with *No powers*  . To be able
>>to navigate from step 1 - > step  2 , you have to go through step 3
>>which seems to be unconvincing at times .
>> 
>> Could someone explain about why such a functionality is not supported
>>in the current architecture ? Please let me know in case I am missing
>>something here.
>> 
>> Thanks,
>> Pranav
>
>This never made much sense to me.
>


I remember seeing a feature request for this functionality somewhere on CS
Jira, you might try to locate it and check the status/targeted release.

Re: New PMC Member: Prasanna Santhanam

[Alena Prokharchyk]

Prasanna, well deserved! Congratulations!

On 4/22/13 8:51 AM, "Chip Childers"  wrote:

>Hi folks
>
>The Project Management Committee (PMC) for Apache CloudStack
>has asked Prasanna Santhanam to become a member of the PMC and
>we are pleased to announce that he has accepted.
>
>Please join me in congratulating Prasanna!
>
>Regards,
>
>--Chip
>on behalf of the CloudStack PMC
>

Re: New PMC Member: Prasanna Santhanam

[Ahmad Emneina]

Excellent news. Congrats Mr. Santhanam.


On Mon, Apr 22, 2013 at 11:06 AM, Alena Prokharchyk <
alena.prokharc...@citrix.com> wrote:

> Prasanna, well deserved! Congratulations!
>
> On 4/22/13 8:51 AM, "Chip Childers"  wrote:
>
> >Hi folks
> >
> >The Project Management Committee (PMC) for Apache CloudStack
> >has asked Prasanna Santhanam to become a member of the PMC and
> >we are pleased to announce that he has accepted.
> >
> >Please join me in congratulating Prasanna!
> >
> >Regards,
> >
> >--Chip
> >on behalf of the CloudStack PMC
> >
>
>
>

RE: New PMC Member: Prasanna Santhanam

[Animesh Chaturvedi]

Congratulations Prasanna

> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Monday, April 22, 2013 8:51 AM
> To: dev@cloudstack.apache.org
> Subject: New PMC Member: Prasanna Santhanam
> 
> Hi folks
> 
> The Project Management Committee (PMC) for Apache CloudStack has asked
> Prasanna Santhanam to become a member of the PMC and we are pleased to
> announce that he has accepted.
> 
> Please join me in congratulating Prasanna!
> 
> Regards,
> 
> --Chip
> on behalf of the CloudStack PMC

Re: New PMC Member: Prasanna Santhanam

[Wei ZHOU]

Congratulations!


2013/4/22 Ahmad Emneina 

> Excellent news. Congrats Mr. Santhanam.
>
>
> On Mon, Apr 22, 2013 at 11:06 AM, Alena Prokharchyk <
> alena.prokharc...@citrix.com> wrote:
>
> > Prasanna, well deserved! Congratulations!
> >
> > On 4/22/13 8:51 AM, "Chip Childers"  wrote:
> >
> > >Hi folks
> > >
> > >The Project Management Committee (PMC) for Apache CloudStack
> > >has asked Prasanna Santhanam to become a member of the PMC and
> > >we are pleased to announce that he has accepted.
> > >
> > >Please join me in congratulating Prasanna!
> > >
> > >Regards,
> > >
> > >--Chip
> > >on behalf of the CloudStack PMC
> > >
> >
> >
> >
>

RE: [DISCUSS] - Deletion of Users within the Admin account

[Pranav Saxena]

Hi Chip ,

This issue has been fixed in asf/master at both the UI and API layers 
(CLOUDSTACK-1941) . Now , if you think that we should support the same 
functionality in 4.1 as well , then myself and Alena can back-port our fixes to 
4.1 from master. 

Thanks,
Pranav

-Original Message-
From: Alena Prokharchyk
Sent: Tuesday, April 09, 2013 11:12 PM
To: dev@cloudstack.apache.org
Cc: Pranav Saxena
Subject: Re: [DISCUSS] - Deletion of Users within the Admin account

Chip, 

1) "System" user is always identified by the cloud.user DB id=1 (hardcoded in 
User.java interface). This user is never exposed via API, you can't remove it - 
the checks are already in place for it.

2) For users of "admin" account, currently there is no direct way to tell if 
the user was added by the system, or using API call. We can't rely on name 
"admin" as it's not reserved name and renaming is also allowed.

I think for upgrade we can rely on the cloud.user db id - expect it to be 
"system_user_db_id + 1" as we know that 2 users come with the default 
cloudStack install.


-Alena.



On 4/9/13 10:02 AM, "Chip Childers"  wrote:

>On Tue, Apr 09, 2013 at 09:56:37AM -0700, Alena Prokharchyk wrote:
>> We should allow to delete any CS users except for ones that came as a 
>>part  of cloudStack installation ("system" and "admin" users). The 
>>users you've  created using API, should be allowed to be removed no 
>>matter of their  types.
>
>+1 to this in general terms.  Not sure about requiring a change like
>this for 4.1.0 though.
>
>> 
>> The right way to distinguish between system generated users, and 
>> users created using APIs would be introducing the flag in the cloud.users DB.
>
>Do you have any thoughts on how we would correctly identify these 
>account in existing installs?
>
>

Re: [DISCUSS] - Deletion of Users within the Admin account

[Chip Childers]

On Mon, Apr 22, 2013 at 07:02:41PM +, Pranav Saxena wrote:
> Hi Chip ,
> 
> This issue has been fixed in asf/master at both the UI and API layers 
> (CLOUDSTACK-1941) . Now , if you think that we should support the same 
> functionality in 4.1 as well , then myself and Alena can back-port our fixes 
> to 4.1 from master. 

I already cut an RC for 4.1.0.  Do you think it makes sense to port it
over for 4.1.1 (or depending on when it makes it into the branch and how
the current RC voting goes, it could end up in 4.1.0)?

I wouldn't object, but I don't think we should re-spin an RC specifically for
it.

> 
> Thanks,
> Pranav
> 
> -Original Message-
> From: Alena Prokharchyk
> Sent: Tuesday, April 09, 2013 11:12 PM
> To: dev@cloudstack.apache.org
> Cc: Pranav Saxena
> Subject: Re: [DISCUSS] - Deletion of Users within the Admin account
> 
> Chip, 
> 
> 1) "System" user is always identified by the cloud.user DB id=1 (hardcoded in 
> User.java interface). This user is never exposed via API, you can't remove it 
> - the checks are already in place for it.
> 
> 2) For users of "admin" account, currently there is no direct way to tell if 
> the user was added by the system, or using API call. We can't rely on name 
> "admin" as it's not reserved name and renaming is also allowed.
> 
> I think for upgrade we can rely on the cloud.user db id - expect it to be 
> "system_user_db_id + 1" as we know that 2 users come with the default 
> cloudStack install.
> 
> 
> -Alena.
> 
> 
> 
> On 4/9/13 10:02 AM, "Chip Childers"  wrote:
> 
> >On Tue, Apr 09, 2013 at 09:56:37AM -0700, Alena Prokharchyk wrote:
> >> We should allow to delete any CS users except for ones that came as a 
> >>part  of cloudStack installation ("system" and "admin" users). The 
> >>users you've  created using API, should be allowed to be removed no 
> >>matter of their  types.
> >
> >+1 to this in general terms.  Not sure about requiring a change like
> >this for 4.1.0 though.
> >
> >> 
> >> The right way to distinguish between system generated users, and 
> >> users created using APIs would be introducing the flag in the cloud.users 
> >> DB.
> >
> >Do you have any thoughts on how we would correctly identify these 
> >account in existing installs?
> >
> >
> 
> 
> 

RE: [DISCUSS] - Deletion of Users within the Admin account

[Pranav Saxena]

If we don't , then the only trade-off is the deletion of the users accounts 
won't be possible :) . IMHO , we should be allowing  that .

I'll leave it upto you to take a final go at it . 

-Original Message-
From: Chip Childers [mailto:chip.child...@sungard.com] 
Sent: Tuesday, April 23, 2013 12:43 AM
To: dev@cloudstack.apache.org
Cc: Alena Prokharchyk
Subject: Re: [DISCUSS] - Deletion of Users within the Admin account

On Mon, Apr 22, 2013 at 07:02:41PM +, Pranav Saxena wrote:
> Hi Chip ,
> 
> This issue has been fixed in asf/master at both the UI and API layers 
> (CLOUDSTACK-1941) . Now , if you think that we should support the same 
> functionality in 4.1 as well , then myself and Alena can back-port our fixes 
> to 4.1 from master. 

I already cut an RC for 4.1.0.  Do you think it makes sense to port it over for 
4.1.1 (or depending on when it makes it into the branch and how the current RC 
voting goes, it could end up in 4.1.0)?

I wouldn't object, but I don't think we should re-spin an RC specifically for 
it.

> 
> Thanks,
> Pranav
> 
> -Original Message-
> From: Alena Prokharchyk
> Sent: Tuesday, April 09, 2013 11:12 PM
> To: dev@cloudstack.apache.org
> Cc: Pranav Saxena
> Subject: Re: [DISCUSS] - Deletion of Users within the Admin account
> 
> Chip,
> 
> 1) "System" user is always identified by the cloud.user DB id=1 (hardcoded in 
> User.java interface). This user is never exposed via API, you can't remove it 
> - the checks are already in place for it.
> 
> 2) For users of "admin" account, currently there is no direct way to tell if 
> the user was added by the system, or using API call. We can't rely on name 
> "admin" as it's not reserved name and renaming is also allowed.
> 
> I think for upgrade we can rely on the cloud.user db id - expect it to be 
> "system_user_db_id + 1" as we know that 2 users come with the default 
> cloudStack install.
> 
> 
> -Alena.
> 
> 
> 
> On 4/9/13 10:02 AM, "Chip Childers"  wrote:
> 
> >On Tue, Apr 09, 2013 at 09:56:37AM -0700, Alena Prokharchyk wrote:
> >> We should allow to delete any CS users except for ones that came as 
> >>a part  of cloudStack installation ("system" and "admin" users). The 
> >>users you've  created using API, should be allowed to be removed no 
> >>matter of their  types.
> >
> >+1 to this in general terms.  Not sure about requiring a change like
> >this for 4.1.0 though.
> >
> >> 
> >> The right way to distinguish between system generated users, and 
> >> users created using APIs would be introducing the flag in the cloud.users 
> >> DB.
> >
> >Do you have any thoughts on how we would correctly identify these 
> >account in existing installs?
> >
> >
> 
> 
> 

Re: [DISCUSS] - Deletion of Users within the Admin account

[Chip Childers]

On Mon, Apr 22, 2013 at 07:25:53PM +, Pranav Saxena wrote:
> If we don't , then the only trade-off is the deletion of the users accounts 
> won't be possible :) . IMHO , we should be allowing  that .
> 
> I'll leave it upto you to take a final go at it . 

Tell you what...  why don't you go ahead and back port it.  If it
happens to get into 4.1.0, then great.  Otherwise it'll be in 4.1.1.

logstash

[Sebastien Goasguen]

Is anyone using log stash to look at CloudStack logs ?

I am looking for CS specific filters.

-sebastien

Re: Problem creating primary storage

[Will Stevens]

I just ran into this after pulling master.

I have everything compiling and I can deploy the db and then startup CS
using jetty.  I reverted my Xen server host back to my 'clean' snapshot and
try to do deploy server (using devcloud) and I get this...

Will

---

WARN  [cloud.storage.StorageManagerImpl] (618638248@qtp-1771350202-4:)
Unable to setup the local storage pool for Host[-1-Routing]
java.lang.NullPointerException
at
com.cloud.storage.StorageManagerImpl.createLocalStorage(StorageManagerImpl.java:715)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:319)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at
org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80)
at
com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:41)
at sun.reflect.GeneratedMethodAccessor36.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621)
at
org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610)
at
org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)
at $Proxy127.createLocalStorage(Unknown Source)
at
com.cloud.storage.LocalStoragePoolListener.processConnect(LocalStoragePoolListener.java:86)
at
com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(AgentManagerImpl.java:611)
at
com.cloud.agent.manager.AgentManagerImpl.handleDirectConnectAgent(AgentManagerImpl.java:1504)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:319)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at
org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80)
at
com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:47)
at sun.reflect.GeneratedMethodAccessor36.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621)
at
org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610)
at
org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)
at $Proxy124.handleDirectConnectAgent(Unknown Source)
at
com.cloud.resource.ResourceManagerImpl.createHostAndAgentDeferred(ResourceManagerImpl.java:2074)
at
com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:862)
at
com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:629)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Me

Re: [ASFCS42] Proposed schedule for our next release

[Joe Brockmeier]

On Thu, Apr 11, 2013, at 04:50 PM, Animesh Chaturvedi wrote:
> Based on the community discussions of having 4 month cadence I am
> proposing the following schedule:

We seem to have gone off the rails into a 4-month vs. 6-month
discussion. It's been a week since the original schedule discussion
started and we're in the VOTE for 4.1.0, so it might be good if we get
this discussion wrapped up. 

I'm +1 on the schedule Animesh proposed initially. If we're going to
talk about a six-month cycle seriously, we should probably have a new
thread that makes it clear to anyone skimming the dev@ mailing list. 

Best,

jzb
-- 
Joe Brockmeier
j...@zonker.net
Twitter: @jzb
http://www.dissociatedpress.net/

Re: Problem creating primary storage

[Will Stevens]

This may be related to the other problem we are seeing.  Mike, can you
verify if you get this same error on server startup as well?

On server startup, I get this error.

INFO  [utils.db.GenericDaoBase] (Timer-2:) Register dao interface in
GenericDaoBase entity-DAO map. com.cloud.user.dao.UserDao
ERROR [cloud.server.StatsCollector] (StatsCollector-3:) Error trying to
retrieve storage stats
java.lang.NullPointerException
at com.cloud.utils.db.SearchCriteria2.create(SearchCriteria2.java:72)
at
com.cloud.storage.secondary.SecondaryStorageManagerImpl.listSecondaryStorageHostsInAllZones(SecondaryStorageManagerImpl.java:1395)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:319)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at
org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80)
at
com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:47)
at sun.reflect.GeneratedMethodAccessor36.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621)
at
org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610)
at
org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at
org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)
at $Proxy250.listSecondaryStorageHostsInAllZones(Unknown Source)
at
com.cloud.server.StatsCollector$StorageCollector.run(StatsCollector.java:279)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
at
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
INFO  [utils.db.GenericDaoBase] (Timer-2:) Cache created: [ name =
UserDaoImpl status = STATUS_ALIVE eternal = false overflowToDisk = false
maxElementsInMemory = 5000 maxElementsOnDisk = 0 memoryStoreEvictionPolicy
= LRU timeToLiveSeconds = 300 timeToIdleSeconds = 300 diskPersistent =
false diskExpiryThreadIntervalSeconds = 120 cacheEventListeners:  hitCount
= 0 memoryStoreHitCount = 0 diskStoreHitCount = 0 missCountNotFound = 0
missCountExpired = 0 ]



On Mon, Apr 22, 2013 at 3:45 PM, Will Stevens  wrote:

> I just ran into this after pulling master.
>
> I have everything compiling and I can deploy the db and then startup CS
> using jetty.  I reverted my Xen server host back to my 'clean' snapshot and
> try to do deploy server (using devcloud) and I get this...
>
> Will
>
> ---
>
> WARN  [cloud.storage.StorageManagerImpl] (618638248@qtp-1771350202-4:)
> Unable to setup the local storage pool for Host[-1-Routing]
> java.lang.NullPointerException
> at
> com.cloud.storage.StorageManagerImpl.createLocalStorage(StorageManagerImpl.java:715)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>  at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>  at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:319)
>  at
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMetho

Re: Problem creating primary storage

[Mike Tutkowski]

Hi Will,

I actually do not see that error, but I updated master most recently some
time last week, so I don't have the super latest.

I think my problem at the time was that I was looking at the wrong CS repo.
 I was looking at the one on GitHub instead of this one:

https://git-wip-us.apache.org/repos/asf/cloudstack.git

The one I was looking at at the time likely had the primary storage problem
and that repo wasn't being updated with the fix that went in later.

Talk to you later!


On Mon, Apr 22, 2013 at 2:09 PM, Will Stevens  wrote:

> This may be related to the other problem we are seeing.  Mike, can you
> verify if you get this same error on server startup as well?
>
> On server startup, I get this error.
>
> INFO  [utils.db.GenericDaoBase] (Timer-2:) Register dao interface in
> GenericDaoBase entity-DAO map. com.cloud.user.dao.UserDao
> ERROR [cloud.server.StatsCollector] (StatsCollector-3:) Error trying to
> retrieve storage stats
> java.lang.NullPointerException
> at com.cloud.utils.db.SearchCriteria2.create(SearchCriteria2.java:72)
> at
>
> com.cloud.storage.secondary.SecondaryStorageManagerImpl.listSecondaryStorageHostsInAllZones(SecondaryStorageManagerImpl.java:1395)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
>
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:319)
> at
>
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at
>
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at
>
> org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80)
> at
>
> com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:47)
> at sun.reflect.GeneratedMethodAccessor36.invoke(Unknown Source)
> at
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
>
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621)
> at
>
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610)
> at
>
> org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65)
> at
>
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at
>
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90)
> at
>
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at
>
> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)
> at $Proxy250.listSecondaryStorageHostsInAllZones(Unknown Source)
> at
>
> com.cloud.server.StatsCollector$StorageCollector.run(StatsCollector.java:279)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
> at
> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
> at
>
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
> at
>
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
> at
>
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
> at
>
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> INFO  [utils.db.GenericDaoBase] (Timer-2:) Cache created: [ name =
> UserDaoImpl status = STATUS_ALIVE eternal = false overflowToDisk = false
> maxElementsInMemory = 5000 maxElementsOnDisk = 0 memoryStoreEvictionPolicy
> = LRU timeToLiveSeconds = 300 timeToIdleSeconds = 300 diskPersistent =
> false diskExpiryThreadIntervalSeconds = 120 cacheEventListeners:  hitCount
> = 0 memoryStoreHitCount = 0 diskStoreHitCount = 0 missCountNotFound = 0
> missCountExpired = 0 ]
>
>
>
> On Mon, Apr 22, 2013 at 3:45 PM, Will Stevens 
> wrote:
>
> > I just ran into this after pulling master.
> >
> > I have everything compiling and I can deploy the db and then startup CS
> > using jetty.  I reverted my Xen server host back to my 'clean' snapshot
> and
> > try to do deploy server (using devcloud) and I get this...
> >
> > Will
> >
> > ---
> >
> > WARN  [cloud.storage.StorageManagerImpl] (618638248@qtp-1771350202-4:)
> > Unable to setup the local sto

RE: [ASFCS42] Proposed schedule for our next release

[Animesh Chaturvedi]

Joe thanks for bringing this up and noting that the subject may not have got 
everyone's attention. I will start a separate thread on 4 month v/s 6 month

Animesh

> -Original Message-
> From: Joe Brockmeier [mailto:j...@zonker.net]
> Sent: Monday, April 22, 2013 12:49 PM
> To: dev@cloudstack.apache.org; cloudstack-...@incubator.apache.org
> Subject: Re: [ASFCS42] Proposed schedule for our next release
> 
> On Thu, Apr 11, 2013, at 04:50 PM, Animesh Chaturvedi wrote:
> > Based on the community discussions of having 4 month cadence I am
> > proposing the following schedule:
> 
> We seem to have gone off the rails into a 4-month vs. 6-month discussion. It's
> been a week since the original schedule discussion started and we're in the
> VOTE for 4.1.0, so it might be good if we get this discussion wrapped up.
> 
> I'm +1 on the schedule Animesh proposed initially. If we're going to talk 
> about a
> six-month cycle seriously, we should probably have a new thread that makes it
> clear to anyone skimming the dev@ mailing list.
> 
> Best,
> 
> jzb
> --
> Joe Brockmeier
> j...@zonker.net
> Twitter: @jzb
> http://www.dissociatedpress.net/

Converting Devcloud KVM Image to raw image format

[Navina Ramesh]

Hi,

We are trying to deploy the KVM image for devcloud on one of our cloud systems. 
It does not accept qcow2 disk formats. Hence, I tried converting to a raw image 
format using "qemu-img convert -O raw devcloud.qcow2 devcloud.raw". However, 
the raw image does not boot and fails at finding the dom0 disk image by UUID 
(Please see the attached image).

What is the correct way for this kind of image conversion? 

Thanks!
Navina

Re: [DISCUSS] - Deletion of Users within the Admin account

[Alena Prokharchyk]

On 4/22/13 12:29 PM, "Chip Childers"  wrote:

>On Mon, Apr 22, 2013 at 07:25:53PM +, Pranav Saxena wrote:
>> If we don't , then the only trade-off is the deletion of the users
>>accounts won't be possible :) . IMHO , we should be allowing  that .
>> 
>> I'll leave it upto you to take a final go at it .
>
>Tell you what...  why don't you go ahead and back port it.  If it
>happens to get into 4.1.0, then great.  Otherwise it'll be in 4.1.1.
>

Chip, the fix includes the DB upgrade - adding the "default" field to
user/account DB tables. I've already made changes to 4.1-4.2 upgrade path
on master. If we backport the fix to 4.1 branch, where the db upgrade
steps should go? As we don't know yet whether it becomes 4.1.1 or 4.1.0
yet.

-Alena.

Re: [DISCUSS] - Deletion of Users within the Admin account

[Chip Childers]

On Mon, Apr 22, 2013 at 01:33:32PM -0700, Alena Prokharchyk wrote:
> On 4/22/13 12:29 PM, "Chip Childers"  wrote:
> 
> >On Mon, Apr 22, 2013 at 07:25:53PM +, Pranav Saxena wrote:
> >> If we don't , then the only trade-off is the deletion of the users
> >>accounts won't be possible :) . IMHO , we should be allowing  that .
> >> 
> >> I'll leave it upto you to take a final go at it .
> >
> >Tell you what...  why don't you go ahead and back port it.  If it
> >happens to get into 4.1.0, then great.  Otherwise it'll be in 4.1.1.
> >
> 
> Chip, the fix includes the DB upgrade - adding the "default" field to
> user/account DB tables. I've already made changes to 4.1-4.2 upgrade path
> on master. If we backport the fix to 4.1 branch, where the db upgrade
> steps should go? As we don't know yet whether it becomes 4.1.1 or 4.1.0
> yet.
> 
> -Alena.
> 
> 

Hmmm...  well we have been trying to *not* do schema changes for bug-fix
releases.

If things worked this way for 4.0.x, I don't see any reason to jump on
pushing this into 4.1.x ATM.  Perhaps we just leave it in master then.

Others?

Re: [DISCUSS] - Deletion of Users within the Admin account

[Alena Prokharchyk]

On 4/22/13 1:36 PM, "Chip Childers"  wrote:

>On Mon, Apr 22, 2013 at 01:33:32PM -0700, Alena Prokharchyk wrote:
>> On 4/22/13 12:29 PM, "Chip Childers"  wrote:
>> 
>> >On Mon, Apr 22, 2013 at 07:25:53PM +, Pranav Saxena wrote:
>> >> If we don't , then the only trade-off is the deletion of the users
>> >>accounts won't be possible :) . IMHO , we should be allowing  that .
>> >> 
>> >> I'll leave it upto you to take a final go at it .
>> >
>> >Tell you what...  why don't you go ahead and back port it.  If it
>> >happens to get into 4.1.0, then great.  Otherwise it'll be in 4.1.1.
>> >
>> 
>> Chip, the fix includes the DB upgrade - adding the "default" field to
>> user/account DB tables. I've already made changes to 4.1-4.2 upgrade
>>path
>> on master. If we backport the fix to 4.1 branch, where the db upgrade
>> steps should go? As we don't know yet whether it becomes 4.1.1 or 4.1.0
>> yet.
>> 
>> -Alena.
>> 
>> 
>
>Hmmm...  well we have been trying to *not* do schema changes for bug-fix
>releases.
>
>If things worked this way for 4.0.x, I don't see any reason to jump on
>pushing this into 4.1.x ATM.  Perhaps we just leave it in master then.
>
>Others?
>


+1. Especially when it includes DB changes.

Re: [ACS41] RC Blocker issue. Help Needed!

[Marcus Sorensen]

Why is the HEAD of 4.1 branch now on 4.1.1?  Don't we need a stable 4.1.0
completed first, before we break 4.1? I ran into several issues today with
this, and then finally now there's not a database upgrade from 4.1.0 to
4.1.1-SNAPSHOT.


On Mon, Apr 22, 2013 at 6:54 AM, Chip Childers wrote:

> Yup - The script I used to update versions was incomplete.  Fixed and
> will attempt the process again now.
>
> Thanks Mice!
>
> On Sun, Apr 21, 2013 at 11:34 PM, Mice Xia  wrote:
> > chip,
> >
> > in tools/apidoc/pom.xml
> > -
> >
> ../../client/target/cloud-client-ui-4.1.0-SNAPSHOT/WEB-INF/
> > +
> >
> ../../client/target/cloud-client-ui-4.1.1-SNAPSHOT/WEB-INF/
> >
> > -mice
> >
> >
> > 2013/4/22 Chip Childers 
> >
> >> I was about to release the RC for voting, when I hit an error building
> >> from the 4.1 branch via the following command:
> >>
> >> mvn -P developer,systemvm clean install
> >>
> >> Does anyone know what's going wrong here?
> >>
> >> Snipped output below:
> >>
> >>
> >> [INFO]
> >> 
> >> [INFO] Building Apache CloudStack apidoc Tools 4.1.0
> >> [INFO]
> >> 
> >> [INFO]
> >> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ cloud-apidoc
> ---
> >> [INFO]
> >> [INFO] --- maven-remote-resources-plugin:1.3:process (default) @
> >> cloud-apidoc ---
> >> [INFO]
> >> [INFO] --- exec-maven-plugin:1.2.1:exec (compile) @ cloud-apidoc ---
> >> + set -u
> >> +
> >>
> TARGETJARDIR=../../client/target/cloud-client-ui-4.1.0-SNAPSHOT/WEB-INF//lib
> >> + shift
> >> +
> DEPSDIR=../../client/target/cloud-client-ui-4.1.0-SNAPSHOT/WEB-INF//lib
> >> + shift
> >> + DISTDIR=./target
> >> + shift
> >> ++ canonical_readlink ./build-apidoc.sh
> >> +++ dirname ./build-apidoc.sh
> >> ++ cd .
> >> +++ basename ./build-apidoc.sh
> >> ++ __filename=build-apidoc.sh
> >> ++ '[' -h build-apidoc.sh ']'
> >> +++ pwd -P
> >> ++ echo /private/tmp/cloudstack/apache-cloudstack-4.1.0-src/tools/apidoc
> >> +
> thisdir=/private/tmp/cloudstack/apache-cloudstack-4.1.0-src/tools/apidoc
> >> + PATHSEP=:
> >> + [[ darwin11.3.0 == \c\y\g\w\i\n ]]
> >> + CP=:/
> >> + for file in '$TARGETJARDIR/*.jar'
> >> +
> >>
> CP=':/:../../client/target/cloud-client-ui-4.1.0-SNAPSHOT/WEB-INF//lib/*.jar'
> >> + for file in '$DEPSDIR/*.jar'
> >> +
> >>
> CP=':/:../../client/target/cloud-client-ui-4.1.0-SNAPSHOT/WEB-INF//lib/*.jar:../../client/target/cloud-client-ui-4.1.0-SNAPSHOT/WEB-INF//lib/*.jar'
> >> + java -cp
> >>
> ':/:../../client/target/cloud-client-ui-4.1.0-SNAPSHOT/WEB-INF//lib/*.jar:../../client/target/cloud-client-ui-4.1.0-SNAPSHOT/WEB-INF//lib/*.jar'
> >> com.cloud.api.doc.ApiXmlDocWriter -d ./target -f
> >>
> ../../client/target/cloud-client-ui-4.1.0-SNAPSHOT/WEB-INF//classes/commands.properties
> >> Exception in thread "main" java.lang.NoClassDefFoundError:
> >> com/cloud/api/doc/ApiXmlDocWriter
> >> Caused by: java.lang.ClassNotFoundException:
> >> com.cloud.api.doc.ApiXmlDocWriter
> >> at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
> >> at java.security.AccessController.doPrivileged(Native Method)
> >> at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
> >> at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
> >> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
> >> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> >> + '[' 1 -ne 0 ']'
> >> + exit 1
> >>
> >>
>

RE: [DISCUSS] - Deletion of Users within the Admin account

[Pranav Saxena]

I second that ! we could leave it in master then .

-Original Message-
From: Alena Prokharchyk [mailto:alena.prokharc...@citrix.com] 
Sent: Tuesday, April 23, 2013 2:10 AM
To: Chip Childers
Cc: dev@cloudstack.apache.org
Subject: Re: [DISCUSS] - Deletion of Users within the Admin account

On 4/22/13 1:36 PM, "Chip Childers"  wrote:

>On Mon, Apr 22, 2013 at 01:33:32PM -0700, Alena Prokharchyk wrote:
>> On 4/22/13 12:29 PM, "Chip Childers"  wrote:
>> 
>> >On Mon, Apr 22, 2013 at 07:25:53PM +, Pranav Saxena wrote:
>> >> If we don't , then the only trade-off is the deletion of the users 
>> >>accounts won't be possible :) . IMHO , we should be allowing  that .
>> >> 
>> >> I'll leave it upto you to take a final go at it .
>> >
>> >Tell you what...  why don't you go ahead and back port it.  If it 
>> >happens to get into 4.1.0, then great.  Otherwise it'll be in 4.1.1.
>> >
>> 
>> Chip, the fix includes the DB upgrade - adding the "default" field to  
>>user/account DB tables. I've already made changes to 4.1-4.2 upgrade 
>>path  on master. If we backport the fix to 4.1 branch, where the db 
>>upgrade  steps should go? As we don't know yet whether it becomes 
>>4.1.1 or 4.1.0  yet.
>> 
>> -Alena.
>> 
>> 
>
>Hmmm...  well we have been trying to *not* do schema changes for 
>bug-fix releases.
>
>If things worked this way for 4.0.x, I don't see any reason to jump on 
>pushing this into 4.1.x ATM.  Perhaps we just leave it in master then.
>
>Others?
>


+1. Especially when it includes DB changes.

Re: [ACS41] RC Blocker issue. Help Needed!

[David Nalley]

On Mon, Apr 22, 2013 at 4:50 PM, Marcus Sorensen  wrote:
> Why is the HEAD of 4.1 branch now on 4.1.1?  Don't we need a stable 4.1.0
> completed first, before we break 4.1? I ran into several issues today with
> this, and then finally now there's not a database upgrade from 4.1.0 to
> 4.1.1-SNAPSHOT.
>

This is due to the maven release plugin.
It runs two commits - the first to change all of the version numbers
from 4.1.0-SNAPSHOT to 4.1.0
Then a second commit to increment to the next version number 4.1.1-SNAPSHOT.
It of course has no knowledge of pesky database upgrades or version checking.

--David

Re: [ACS41] RC Blocker issue. Help Needed!

[Chip Childers]

On Mon, Apr 22, 2013 at 02:50:52PM -0600, Marcus Sorensen wrote:
> Why is the HEAD of 4.1 branch now on 4.1.1?  Don't we need a stable 4.1.0
> completed first, before we break 4.1? I ran into several issues today with
> this, and then finally now there's not a database upgrade from 4.1.0 to
> 4.1.1-SNAPSHOT.

I advanced it, but will revert and then re-advance it when the VOTE
closes.  I figured that a history of 4.1.0-SNAPSHOT > 4.1.0 >
4.1.1-SNAPSHOT was the most logical thing to do.

That being said, yes, we need to get the DB upgrade in place I guess.
Should I revert the 4.1.1-SNAPSHOT to 4.1.0-SNAPSHOT?

Re: [ACS41] RC Blocker issue. Help Needed!

[Chip Childers]

On Mon, Apr 22, 2013 at 04:55:11PM -0400, David Nalley wrote:
> On Mon, Apr 22, 2013 at 4:50 PM, Marcus Sorensen  wrote:
> > Why is the HEAD of 4.1 branch now on 4.1.1?  Don't we need a stable 4.1.0
> > completed first, before we break 4.1? I ran into several issues today with
> > this, and then finally now there's not a database upgrade from 4.1.0 to
> > 4.1.1-SNAPSHOT.
> >
> 
> This is due to the maven release plugin.
> It runs two commits - the first to change all of the version numbers
> from 4.1.0-SNAPSHOT to 4.1.0
> Then a second commit to increment to the next version number 4.1.1-SNAPSHOT.
> It of course has no knowledge of pesky database upgrades or version checking.
> 
> --David
> 

Actually the release plugin wasn't working well for me.  I'm using the
version plugin, plus a script that hacks fixes into a couple of POMs
(like the XenServerJava one) that don't play well.

Check the script in tools/build/build_asf.sh or setversion.sh

Re: [ACS41] RC Blocker issue. Help Needed!

[Marcus Sorensen]

So if I understand correctly, when the vote fails it will auto revert so we
can work on the 4.1 branch again? For the moment it's kind of stuck in
limbo, but maybe that's how it's meant to be. I suppose we work on the
branch from the commit where the RC was cut, and then apply any patches
after the revert?


On Mon, Apr 22, 2013 at 2:58 PM, Chip Childers wrote:

> On Mon, Apr 22, 2013 at 02:50:52PM -0600, Marcus Sorensen wrote:
> > Why is the HEAD of 4.1 branch now on 4.1.1?  Don't we need a stable 4.1.0
> > completed first, before we break 4.1? I ran into several issues today
> with
> > this, and then finally now there's not a database upgrade from 4.1.0 to
> > 4.1.1-SNAPSHOT.
>
> I advanced it, but will revert and then re-advance it when the VOTE
> closes.  I figured that a history of 4.1.0-SNAPSHOT > 4.1.0 >
> 4.1.1-SNAPSHOT was the most logical thing to do.
>
> That being said, yes, we need to get the DB upgrade in place I guess.
> Should I revert the 4.1.1-SNAPSHOT to 4.1.0-SNAPSHOT?
>

Re: [ACS41] RC Blocker issue. Help Needed!

[Chip Childers]

On Mon, Apr 22, 2013 at 03:01:30PM -0600, Marcus Sorensen wrote:
> So if I understand correctly, when the vote fails it will auto revert so we
> can work on the 4.1 branch again? For the moment it's kind of stuck in
> limbo, but maybe that's how it's meant to be. I suppose we work on the
> branch from the commit where the RC was cut, and then apply any patches
> after the revert?

Frankly I made a mistake I think, but perhaps it's the right thing
anyway.  Until the VOTE is cancelled or passed, we're sort of stuck.
This isn't a tool thing, as much as it's how I ended up doing things.

Yes, you can work from the commit-sh that I published (keep in mind that
it's set to 4.1.0 with no SNAPSHOT), or the one right before that (which
has the SNAPSHOT).

If we want, I can get it back to 4.1.0-SNAPSHOT easily...

> 
> 
> On Mon, Apr 22, 2013 at 2:58 PM, Chip Childers 
> wrote:
> 
> > On Mon, Apr 22, 2013 at 02:50:52PM -0600, Marcus Sorensen wrote:
> > > Why is the HEAD of 4.1 branch now on 4.1.1?  Don't we need a stable 4.1.0
> > > completed first, before we break 4.1? I ran into several issues today
> > with
> > > this, and then finally now there's not a database upgrade from 4.1.0 to
> > > 4.1.1-SNAPSHOT.
> >
> > I advanced it, but will revert and then re-advance it when the VOTE
> > closes.  I figured that a history of 4.1.0-SNAPSHOT > 4.1.0 >
> > 4.1.1-SNAPSHOT was the most logical thing to do.
> >
> > That being said, yes, we need to get the DB upgrade in place I guess.
> > Should I revert the 4.1.1-SNAPSHOT to 4.1.0-SNAPSHOT?
> >

[MERGE] UI support for VM affinity/anti-affinity groups

[Brian Federle]

Hi all,



I would like to merge the UI support for VM affinity/anti-affinity groups to 
master.



JIRA ticket: https://issues.apache.org/jira/browse/CLOUDSTACK-2074

FS: 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/FS+-+Affinity-Anti-affinity+groups

Branch: ui-vm-affinity

Unit tests: No new unit tests (UI only)



Discussion information: Please see backend discussion @ 
https://issues.apache.org/jira/browse/CLOUDSTACK-739

[Prachi, please add links to any other ML discussions if applicable]



RAT report:
[INFO] Scanning for projects...
[INFO]
[INFO] 
[INFO] Building Apache CloudStack 4.2.0-SNAPSHOT
[INFO] 
[INFO]
[INFO] --- apache-rat-plugin:0.8:check (default-cli) @ cloudstack ---
[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: 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/systemvmtemplate64/*
[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.threshold.js
[INFO] Exclude: ui/lib/jquery-ui/css/jquery-ui.css
[INFO] Exclude: ui/lib/jquery-ui/index.html
[INFO] Exclude: ui/lib/jquery-ui/js/jquery-ui.js
[INFO] Exclude: ui/lib/jquery.cookies.js
[INFO] Exclude: ui/lib/jquery.easing.js
[INFO] Exclude: ui/lib/jquery.js
[INFO] Exclude: ui/lib/jquery.md5.js
[INFO] Exclude: ui/lib/jquery.validate.js
[INFO] Exclude: ui/lib/qunit/qunit.css
[INFO] Exclude: ui/lib/qunit/qunit.js
[INFO] Exclude: ui/lib/reset.css
[INFO] Exclude: ui/lib/require.js
[INFO] Exclude: waf
[INFO] Exclude: patches/systemvm/debian/systemvm.vmx
[INFO] Exclude: patches/systemvm/debian/config/root/.ssh/authorized_keys
[INFO] Exclude: patches/systemvm/debian/config/etc/apache2/httpd.conf
[INFO] Exclude: patches/systemvm/debian/config/etc/apache2/ports.conf
[INFO] Exclude: 
patches/systemvm/debian/config/etc/apache2/sites-available/default
[INFO] Exclude: 
patches/systemvm/debian/config/etc/apache2/sites-available/default-ssl
[INFO] Exclude: patches/systemvm/debian/config/etc/apache2/vhostexample.conf
[INFO] Exclude: patches/systemvm/debian/config/etc/dnsmasq.conf
[INFO] Exclude: patches/systemvm/debian/config/etc/vpcdnsmasq.conf
[INFO] Exclude: patches/systemvm/debian/config/etc/ssh/sshd_config
[INFO] Exclude: patches/systemvm/debian/config/etc/rsyslog.conf
[INFO] Exclude: patches/systemvm/debian/config/etc/logrotate.conf
[INFO] Exclude: patches/systemvm/debian/config/etc/logrotate.d/*
[INFO] Exclude: patches/systemvm/debian/config/etc/sysctl.conf
[INFO] Exclude: 
patches/systemvm/debian/config/root/redundant_router/keepalived.conf.templ
[INFO] Exclude: 
patches/systemvm/d

Re: Problem creating primary storage

[Will Stevens]

Thanks, I was running into the same problem.

Will


On Mon, Apr 22, 2013 at 4:18 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> Hi Will,
>
> I actually do not see that error, but I updated master most recently some
> time last week, so I don't have the super latest.
>
> I think my problem at the time was that I was looking at the wrong CS repo.
>  I was looking at the one on GitHub instead of this one:
>
> https://git-wip-us.apache.org/repos/asf/cloudstack.git
>
> The one I was looking at at the time likely had the primary storage problem
> and that repo wasn't being updated with the fix that went in later.
>
> Talk to you later!
>
>
> On Mon, Apr 22, 2013 at 2:09 PM, Will Stevens 
> wrote:
>
> > This may be related to the other problem we are seeing.  Mike, can you
> > verify if you get this same error on server startup as well?
> >
> > On server startup, I get this error.
> >
> > INFO  [utils.db.GenericDaoBase] (Timer-2:) Register dao interface in
> > GenericDaoBase entity-DAO map. com.cloud.user.dao.UserDao
> > ERROR [cloud.server.StatsCollector] (StatsCollector-3:) Error trying to
> > retrieve storage stats
> > java.lang.NullPointerException
> > at com.cloud.utils.db.SearchCriteria2.create(SearchCriteria2.java:72)
> > at
> >
> >
> com.cloud.storage.secondary.SecondaryStorageManagerImpl.listSecondaryStorageHostsInAllZones(SecondaryStorageManagerImpl.java:1395)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at
> >
> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> > at
> >
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> > at java.lang.reflect.Method.invoke(Method.java:597)
> > at
> >
> >
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:319)
> > at
> >
> >
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> > at
> >
> >
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> > at
> >
> >
> org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80)
> > at
> >
> >
> com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:47)
> > at sun.reflect.GeneratedMethodAccessor36.invoke(Unknown Source)
> > at
> >
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> > at java.lang.reflect.Method.invoke(Method.java:597)
> > at
> >
> >
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621)
> > at
> >
> >
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610)
> > at
> >
> >
> org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65)
> > at
> >
> >
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> > at
> >
> >
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90)
> > at
> >
> >
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> > at
> >
> >
> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)
> > at $Proxy250.listSecondaryStorageHostsInAllZones(Unknown Source)
> > at
> >
> >
> com.cloud.server.StatsCollector$StorageCollector.run(StatsCollector.java:279)
> > at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
> > at
> >
> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
> > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
> > at
> >
> >
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
> > at
> >
> >
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
> > at
> >
> >
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
> > at
> >
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> > at
> >
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> > at java.lang.Thread.run(Thread.java:662)
> > INFO  [utils.db.GenericDaoBase] (Timer-2:) Cache created: [ name =
> > UserDaoImpl status = STATUS_ALIVE eternal = false overflowToDisk = false
> > maxElementsInMemory = 5000 maxElementsOnDisk = 0
> memoryStoreEvictionPolicy
> > = LRU timeToLiveSeconds = 300 timeToIdleSeconds = 300 diskPersistent =
> > false diskExpiryThreadIntervalSeconds = 120 cacheEventListeners:
>  hitCount
> > = 0 memoryStoreHitCount = 0 diskStoreHitCount = 0 missCountNotFound = 0
> > missCountExpired = 0 ]
> >
> >
> >
> > On Mon, Apr 22, 2013 at 3:45 PM, Will Stevens 
>

Re: [ACS41] RC Blocker issue. Help Needed!

[Marcus Sorensen]

The DB version is set to 4.1.0 on my dev systems, so I think somehow the
SNAPSHOT was added to the db version only when we hit 4.1.1.

I think it makes sense to roll back to your 4.1.0 if/when possible, that
way if we need work on the RC we can without rolling forward and back each
time the vote fails. Then increment to 4.1.1 only when we have passing
artifacts.


On Mon, Apr 22, 2013 at 3:04 PM, Chip Childers wrote:

> On Mon, Apr 22, 2013 at 03:01:30PM -0600, Marcus Sorensen wrote:
> > So if I understand correctly, when the vote fails it will auto revert so
> we
> > can work on the 4.1 branch again? For the moment it's kind of stuck in
> > limbo, but maybe that's how it's meant to be. I suppose we work on the
> > branch from the commit where the RC was cut, and then apply any patches
> > after the revert?
>
> Frankly I made a mistake I think, but perhaps it's the right thing
> anyway.  Until the VOTE is cancelled or passed, we're sort of stuck.
> This isn't a tool thing, as much as it's how I ended up doing things.
>
> Yes, you can work from the commit-sh that I published (keep in mind that
> it's set to 4.1.0 with no SNAPSHOT), or the one right before that (which
> has the SNAPSHOT).
>
> If we want, I can get it back to 4.1.0-SNAPSHOT easily...
>
> >
> >
> > On Mon, Apr 22, 2013 at 2:58 PM, Chip Childers <
> chip.child...@sungard.com>wrote:
> >
> > > On Mon, Apr 22, 2013 at 02:50:52PM -0600, Marcus Sorensen wrote:
> > > > Why is the HEAD of 4.1 branch now on 4.1.1?  Don't we need a stable
> 4.1.0
> > > > completed first, before we break 4.1? I ran into several issues today
> > > with
> > > > this, and then finally now there's not a database upgrade from 4.1.0
> to
> > > > 4.1.1-SNAPSHOT.
> > >
> > > I advanced it, but will revert and then re-advance it when the VOTE
> > > closes.  I figured that a history of 4.1.0-SNAPSHOT > 4.1.0 >
> > > 4.1.1-SNAPSHOT was the most logical thing to do.
> > >
> > > That being said, yes, we need to get the DB upgrade in place I guess.
> > > Should I revert the 4.1.1-SNAPSHOT to 4.1.0-SNAPSHOT?
> > >
>

[DISCUSS] ACS Release 4 month v/s 6 month

[Animesh Chaturvedi]

Folks

We started discussing 4 month v/s 6 month release cycle in a another thread 
[1]. Since the subject of that thread was different, community may not have 
participated in this important discussion fully. I am  are bringing this 
discussion to its own thread. Here is the summary so far please refer to [1] 
for more details.

Summary of discussion:
- Animesh pointed out the technical debt that we have accumulated so far needs 
extra time to resolve
- David, Chip favor shorter release cycle of 4 month and keeping master always 
stable and in good quality and enhancing automation as a solution to reduce QA 
manual effort. A focused defect fixing activity may be needed to reduce 
technical debt
- Will brought up several points in the discussion: He called out heavy 
dependence on manual QA for a release and pointed out that manual QA may not be 
always available to match up ACS release schedule. Release overhead for 4 month 
release is still high and suggest that moving to 6 month will save on release 
overhead and that  time can be used for strengthening automation.
 - Joe agrees partly in release overhead being significant for major release

If I missed out  any important point please feel free to bring into the thread.

There were some other discussion in [1] on release planning conference and 
chip's clarification on time based v/s feature based releases but we will not 
discuss those in this thread. Community has agreed to time-based release 
already.

[1] http://markmail.org/thread/6suq2fhltdvgvcxd 

Re: CS 4.0.1 | KVM | CentOS 6.3

[Chiradeep Vittal]

The msid is generated from the mac address: the first mac address found while 
doing 'ifconfig –a'. If this listing changes on every reboot and you have 3 
nics then you might end up with 3 management servers

From: Ahmad Emneina mailto:aemne...@gmail.com>>
Date: Thursday, April 18, 2013 9:40 PM
To: "dev@cloudstack.apache.org" 
mailto:dev@cloudstack.apache.org>>
Cc: Chiradeep Vittal 
mailto:chiradeep.vit...@citrix.com>>, 
"dev@cloudstack.apache.org" 
mailto:dev@cloudstack.apache.org>>
Subject: Re: CS 4.0.1 | KVM | CentOS 6.3

I'd make a backup of the db, and delete the entries where the MS is down. 
Hopefully that'll clear up your logs.

Ahmad

On Apr 18, 2013, at 7:59 PM, Maurice Lawler 
mailto:maurice.law...@me.com>> wrote:

I'm 100% sure it's user error! As always *grin*  Of course I removed my IP 
address / hostname.

- Maurice

The output is:

mysql> SELECT * FROM mshost\G;
*** 1. row ***
  id: 1
msid: 219948120943996
   runid: 1366256187370
name: myhostname.domain.com
   state: Down
 version: 4.0.1.20130201075054
  service_ip: myipaddress
service_port: 9090
 last_update: 2013-04-19 01:49:19
 removed: NULL
 alert_count: 0
*** 2. row ***
  id: 2
msid: 279278805451357
   runid: 1366250623758
name: myhostname.domain.com
   state: Down
 version: 4.0.1.20130201075054
  service_ip: myipaddress
service_port: 9090
 last_update: 2013-04-18 03:32:29
 removed: NULL
 alert_count: 0
*** 3. row ***
  id: 3
msid: 279278805450862
   runid: 1366337908232
name: myhostname.domain.com
   state: Up
 version: 4.0.1.20130201075054
  service_ip: myipaddress
service_port: 9090
 last_update: 2013-04-19 02:57:12
 removed: NULL
 alert_count: 0
3 rows in set (0.00 sec)



On Apr 18, 2013, at 02:11 PM, Chiradeep Vittal 
mailto:chiradeep.vit...@citrix.com>> wrote:

Maurice, it appears to be something specific to the sequence of actions
you took or your environment.

Developers and QA kill and restart their management servers dozens of
times a day and have (AFAIK) never seen this issue.

What are the entries in the mshost table?


On 4/17/13 11:20 PM, "Maurice Lawler" 
mailto:maurice.law...@me.com>> wrote:

>Thank you. How would I correct this and why would the table state
>something other then what I have setup, what would have caused that?
>
>
>On Apr 18, 2013, at 12:27 AM, Chiradeep Vittal
>mailto:chiradeep.vit...@citrix.com>> wrote:
>
>> That's probably not what the mshost table thinks?
>>
>> On 4/17/13 11:00 AM, "Maurice Lawler" 
>> mailto:maurice.law...@me.com>> wrote:
>>
>>> No. I have ONE server running.
>>>
>>> One MS - One Install of CS - One of everything. All on the same IP
>>> address.
>>>
>>>
>>> On Apr 17, 2013, at 12:05 PM, Chiradeep Vittal
>>> mailto:chiradeep.vit...@citrix.com>> wrote:
>>>
 You probably have another MS connecting to the same database?

 On 4/17/13 9:49 AM, "Maurice Lawler" 
 mailto:maurice.law...@me.com>> wrote:

> No the management IP hasn't changed. My question is why when
>restarting
> Cloud Management the issue is cleared up. Then almost an hour later,
>it
> starts in again; how do I correct this issue?
>
>
> On Apr 17, 2013, at 12:23 AM, Chiradeep Vittal
> mailto:chiradeep.vit...@citrix.com>> wrote:
>
>> Did the management server ip change? It somehow thinks there's 2
>> management servers.
>>
>> On 4/16/13 7:00 PM, "Maurice Lawler" 
>> mailto:maurice.law...@me.com>> wrote:
>>
>>> Greetings,
>>>
>>> I am having this FLOOD my log. I will have you know, this is ONE
>>> server
>>> ONE HOST. KVM | CentOS 6.3 | Cloudstack 4.0.1
>>>
>>> I have found restarting cloud management solves the issue for
>>>awhile,
>>> then it starts again.
>>>
>>> Please advise.
>>>
>>> - Maurice
>>>
>>>  Eror Log 
>>>
>>> 2013-04-16 20:58:38,993 DEBUG
>>> [cloud.consoleproxy.ConsoleProxyManagerImpl] (consoleproxy-1:null)
>>> Zone 1
>>> is ready to launch console proxy
>>> 2013-04-16 20:58:39,137 DEBUG [cloud.cluster.ClusterManagerImpl]
>>> (Cluster-Heartbeat-1:null) Detected management node left, id:1,
>>> nodeIP:MYIPADDRESSHERE
>>> 2013-04-16 20:58:39,137 INFO [cloud.cluster.ClusterManagerImpl]
>>> (Cluster-Heartbeat-1:null) Trying to connect to MYIPADDRESSHERE
>>> 2013-04-16 20:58:39,138 INFO [cloud.cluster.ClusterManagerImpl]
>>> (Cluster-Heartbeat-1:null) Management node 1 is detected inactive
>>>by
>>> timestamp but is pingable
>>> 2013-04-16 20:58:39,264 DEBUG
>>> [network.router.VirtualNe

Re: [ACS41] RC Blocker issue. Help Needed!

[Chip Childers]

On Mon, Apr 22, 2013 at 03:10:11PM -0600, Marcus Sorensen wrote:
> The DB version is set to 4.1.0 on my dev systems, so I think somehow the
> SNAPSHOT was added to the db version only when we hit 4.1.1.
> 
> I think it makes sense to roll back to your 4.1.0 if/when possible, that
> way if we need work on the RC we can without rolling forward and back each
> time the vote fails. Then increment to 4.1.1 only when we have passing
> artifacts.

Reverted the commits to be 4.1.0-SNAPSHOT for HEAD of the 4.1 branch.

Verified revert via:

find ./ -name "pom.xml" | xargs grep 4.1.1

also verified with mvn clean install

-chip

Re: PVlan branch created

[Sheng Yang]

Some update:

I just pushed another improved version of ovs policies for pvlan. This time
we won't need to tell if the VM is in the same host as dhcp server or not.
Much more elegant(and less code!) than last time.

--Sheng


On Sun, Apr 21, 2013 at 4:32 PM, Sheng Yang  wrote:

> Hi,
>
> I've pushed the early stage code for private vlan support to the repo.
>
> The FS is at:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/PVLAN+for+isolation+within+a+VLAN
>
> The effort are on simulation PVLAN(isolated secondary vlan) using openflow
> on OVS. But I have to admit it's really less than ideal, especially the "vm
> in the dhcp host" script.
>
> Ideally, when we want to setup pvlan, we need just tell that enable it for
> a VM or enable it for DHCP server. But after spending all the effort try to
> find a way on ovs(supported openflow 1.0), I realize we need higher version
> of openflow support, which I explained in FS. Currently we need to also
> tell VM on the same host with DHCP server, apart from other VMs, and
> programming different rules. It's unusual for CloudStack, and result in
> some hack code as well.
>
> The current code can start/stop VM and DHCP server, but haven't got
> migration work done.
>
> If you're interesting, please take a look at the branch.
>
> --Sheng
>
>
>

[ACS41][BUG] CS does honor use of Storage IP space- Advanced Network w/vSphere 5.x

[Musayev, Ilya]

Deploy ACS too many times and notice an issue, while I have allocated an IP 
range for Storage VMs, the IPs are still being used from Public Network, and my 
storage IP space is unclaimed.

I'm using ACS 4.1 Advanced Network with vSphere 5.0.

Would anyone else please confirm they see a similar problem in their CS setups 
with VMWare? This probably affects ACS4.0 as well.

Looked in the logs and see no abnormalities.

CS picked 2 IP addressed from Public Networks I've defined for Storage VM. This 
is a wrong behavior in my opinion.

Thanks
ilya

RE: [ACS41][BUG] CS does honor use of Storage IP space- Advanced Network w/vSphere 5.x

[Musayev, Ilya]

Also, I don't believe this is VMWare related, perhaps it affects KVM/XEN 
implementations as well. 

> -Original Message-
> From: Musayev, Ilya [mailto:imusa...@webmd.net]
> Sent: Monday, April 22, 2013 6:26 PM
> To: dev@cloudstack.apache.org
> Subject: [ACS41][BUG] CS does honor use of Storage IP space- Advanced
> Network w/vSphere 5.x
> 
> Deploy ACS too many times and notice an issue, while I have allocated an IP
> range for Storage VMs, the IPs are still being used from Public Network, and
> my storage IP space is unclaimed.
> 
> I'm using ACS 4.1 Advanced Network with vSphere 5.0.
> 
> Would anyone else please confirm they see a similar problem in their CS
> setups with VMWare? This probably affects ACS4.0 as well.
> 
> Looked in the logs and see no abnormalities.
> 
> CS picked 2 IP addressed from Public Networks I've defined for Storage VM.
> This is a wrong behavior in my opinion.
> 
> Thanks
> ilya

Re: ebtables

[Maurice Lawler]

<<< text/html; CHARSET=US-ASCII: Unrecognized >>>

Review Request: fix RPM version on non-SNAPSHOT releases

[Marcus Sorensen]

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

Review request for cloudstack and Chip Childers.


Description
---

When trying to make RPMs from the current 4.1, I ran into this because the 
"-SNAPSHOT" has been removed:

[marcus@buildcloud centos63]$ ./package.sh 
error: Macro %_ver has empty body
error: Macro %_ver has empty body
error: File 
/home/marcus/code/cloudstack/dist/rpmbuild/SOURCES/cloudstack-%{_ver}.tgz: No 
such file or directory


Diffs
-

  packaging/centos63/package.sh d9d5b1c 

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


Testing
---

Built RPMs successfully


Thanks,

Marcus Sorensen

[ACS41][Patch Request]

[Marcus Sorensen]

https://reviews.apache.org/r/10714/

RPMs don't build via package.sh when '-SNAPSHOT' is removed from version

Re: [ACS41][Patch Request]

[Chip Childers]

On Mon, Apr 22, 2013 at 04:53:35PM -0600, Marcus Sorensen wrote:
> https://reviews.apache.org/r/10714/
> 
> RPMs don't build via package.sh when '-SNAPSHOT' is removed from version

OK - Cancelling the vote then.

Re: ebtables (More Information)

[Maurice Lawler]

<<< text/html; CHARSET=US-ASCII: Unrecognized >>>

RE: [DISCUSS] ACS Release 4 month v/s 6 month

[Animesh Chaturvedi]

> -Original Message-
> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> Sent: Monday, April 22, 2013 2:20 PM
> To: cloudstack-...@incubator.apache.org
> Subject: [DISCUSS] ACS Release 4 month v/s 6 month
> 
> Folks
> 
> We started discussing 4 month v/s 6 month release cycle in a another thread
> [1]. Since the subject of that thread was different, community may not have
> participated in this important discussion fully. I am  are bringing this 
> discussion
> to its own thread. Here is the summary so far please refer to [1] for more
> details.
> 
> Summary of discussion:
> - Animesh pointed out the technical debt that we have accumulated so far
> needs extra time to resolve
> - David, Chip favor shorter release cycle of 4 month and keeping master always
> stable and in good quality and enhancing automation as a solution to reduce
> QA manual effort. A focused defect fixing activity may be needed to reduce
> technical debt
> - Will brought up several points in the discussion: He called out heavy
> dependence on manual QA for a release and pointed out that manual QA may
> not be always available to match up ACS release schedule. Release overhead
> for 4 month release is still high and suggest that moving to 6 month will save
> on release overhead and that  time can be used for strengthening automation.
>  - Joe agrees partly in release overhead being significant for major release
> 
> If I missed out  any important point please feel free to bring into the 
> thread.
> 
> There were some other discussion in [1] on release planning conference and
> chip's clarification on time based v/s feature based releases but we will not
> discuss those in this thread. Community has agreed to time-based release
> already.
> 
> [1] http://markmail.org/thread/6suq2fhltdvgvcxd

[Animesh>] Please provide your input.

[CANCELLED][VOTE] Apache Cloudstack 4.1.0

[Chip Childers]

On Mon, Apr 22, 2013 at 11:37:30AM -0400, Chip Childers wrote:
> Hi All,
> 
> I've created a 4.1.0 release, with the following artifacts up for a
> vote:
> 
> Git Branch and Commit SH:
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.1
> Commit: b7abc3ca1e5f646722ed9cf78b93849c6c47e3d0
> 
> List of changes:
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=CHANGES;hb=4.1
> 
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.1.0/
> 
> PGP release keys (signed using A99A5D58):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> 
> Testing instructions are here:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+procedure
> 
> Vote will be open for 72 hours.
> 
> For sanity in tallying the vote, can PMC members please be sure to
> indicate "(binding)" with their vote?
> 
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)

Officially cancelling this round, due to the RPM build error that Marcus
just pointed out.  He didn't -1 it, but I am on his behalf.

Re: [CANCELLED][VOTE] Apache Cloudstack 4.1.0

[Marcus Sorensen]

-1 :-)


On Mon, Apr 22, 2013 at 5:08 PM, Chip Childers wrote:

> On Mon, Apr 22, 2013 at 11:37:30AM -0400, Chip Childers wrote:
> > Hi All,
> >
> > I've created a 4.1.0 release, with the following artifacts up for a
> > vote:
> >
> > Git Branch and Commit SH:
> >
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.1
> > Commit: b7abc3ca1e5f646722ed9cf78b93849c6c47e3d0
> >
> > List of changes:
> >
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=CHANGES;hb=4.1
> >
> > Source release (checksums and signatures are available at the same
> > location):
> > https://dist.apache.org/repos/dist/dev/cloudstack/4.1.0/
> >
> > PGP release keys (signed using A99A5D58):
> > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> >
> > Testing instructions are here:
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+procedure
> >
> > Vote will be open for 72 hours.
> >
> > For sanity in tallying the vote, can PMC members please be sure to
> > indicate "(binding)" with their vote?
> >
> > [ ] +1  approve
> > [ ] +0  no opinion
> > [ ] -1  disapprove (and reason why)
>
> Officially cancelling this round, due to the RPM build error that Marcus
> just pointed out.  He didn't -1 it, but I am on his behalf.
>

Re: Review Request: fix RPM version on non-SNAPSHOT releases

[Chip Childers]

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

Ship it!


Ship It!

- Chip Childers


On April 22, 2013, 10:52 p.m., Marcus Sorensen wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/10714/
> ---
> 
> (Updated April 22, 2013, 10:52 p.m.)
> 
> 
> Review request for cloudstack and Chip Childers.
> 
> 
> Description
> ---
> 
> When trying to make RPMs from the current 4.1, I ran into this because the 
> "-SNAPSHOT" has been removed:
> 
> [marcus@buildcloud centos63]$ ./package.sh 
> error: Macro %_ver has empty body
> error: Macro %_ver has empty body
> error: File 
> /home/marcus/code/cloudstack/dist/rpmbuild/SOURCES/cloudstack-%{_ver}.tgz: No 
> such file or directory
> 
> 
> Diffs
> -
> 
>   packaging/centos63/package.sh d9d5b1c 
> 
> Diff: https://reviews.apache.org/r/10714/diff/
> 
> 
> Testing
> ---
> 
> Built RPMs successfully
> 
> 
> Thanks,
> 
> Marcus Sorensen
> 
>