RE: [Doc] Developer Guide API Section for Review

[Sanjeev Neelarapu]

Hi Radhika,

New APIs introduced in 4.2 due to Object Storage feature:

addImageStore
createSecondaryStagingStore
listImageStores
listSecondaryStagingStores

>From 4.2 onwards we will be using only above APIs to create and list any 
>secondary storage. 
We will not be supporting addS3 and listS3 APIs from 4.2 onwards.

addImageStore -- For adding all types of secondary storage providers 
(S3/Swift/NFS)
createSecondaryStagingStore -- For adding staging secondary storage in each zone
listImageStores --list all secondary storages (S3/Swift/NFS)
listSecondaryStagingStores -- list all staging secondary storages

Edison/Min can provide more info on these APIs.

Thanks,
Sanjeev

-Original Message-
From: Harikrishna Patnala [mailto:harikrishna.patn...@citrix.com] 
Sent: Friday, August 16, 2013 12:02 PM
To: 
Cc: us...@cloudstack.apache.org
Subject: Re: [Doc] Developer Guide API Section for Review

Hi Radhika,

Thank you for the doc.
Some changes are required,

1) updateCluster: The following request parameters are added: 
cpuovercommitratio, ramovercommitratio
- These parameters are removed from the updateCluster API. Please remove from 
the doc as well.
  - Same doc entry exists in Page 24 and 29. please remove from both pages
2) addCluster:
- cpuovercommitratio, ramovercommitratio parameters are removed from the API, 
need to remove from the doc also

3) scaleSystemVm: Scales the service offering for a systemVM, console proxy, or 
secondary storage. The system VM
   must be in Stopped state for this command to take effect.
- System vm need not be in stopped state. works for both stopped vm and running 
vm.
4) restoreVirtualMachine:
- please add this line. " The parameter templateId can be an ISO id in case of 
restore vm deployed using ISO"

Please make these changes.

Thankyou
-Harikrishna


On 05-Aug-2013, at 11:44 AM, Radhika Puthiyetath 
mailto:radhika.puthiyet...@citrix.com>> wrote:

Hi,

Developer Guide API section is ready for review. The doc is attached at 
https://issues.apache.org/jira/browse/CLOUDSTACK-3546

Please see section4.1. What's New in the API for 4.2,  and provide your 
feedback.

Also, please let me know other than the API changes what you think what should 
be covered in the What's New Section.

Regards
-Radhika

Re: Review Request 13680: CLOUDSTACK-3927, CLOUDSTACK-3928 Fix to add/remove NS devices in setupClass/tearDownClass

[venkata swamy babu budumuru]

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



test/integration/component/test_netscaler_lb.py


Since you have multiple test suites trying to add the same netscaler 
device, it will be good to keep this whole creation stuff in try block so that 
even if something fails then you will have your tearDown called.

something like I mentioned here :

try:

add_netscaler()
NetworkOffering.create()
ServiceOffering.create()

except:

call tearDownClass()

If we do it in the above way then if something goes wrong in network 
offering creation then our except block will still call the tearDown for 
removing netscaler device so that your rest of test suites will not fail during 
netscaler device addition.



tools/marvin/marvin/integration/lib/common.py


IMO, we don't have to go for an additional library call for add_netscaler 
rather we can rely just on Netscaler.add in base.py. few reasons for saying 
this is as mentioned below.

1. Usually the automation environment is prepared out of a .cfg file where 
we can add the following to make a provider configured and enabled by default 
using something like below

"providers": [

 { "broadcastdomainrange": "ZONE",

"name": "Netscaler"
 }
]





- venkata swamy babu  budumuru


On Aug. 20, 2013, 6:18 a.m., Sowmya Krishnan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/13680/
> ---
> 
> (Updated Aug. 20, 2013, 6:18 a.m.)
> 
> 
> Review request for cloudstack, venkata swamy babu  budumuru and Prasanna 
> Santhanam.
> 
> 
> Bugs: CLOUDSTACK-3927 and CLOUDSTACK-3928
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Fix to add NS device in setupClass and remove in tearDown
> Added a common method to perform these in common.add_netscaler()
> Also fixes few account object issues in netscaler_configs.
> 
> Patch will help in keeping each test suite independent. Otherwise we cannot 
> identify which NS an LB rule will be deployed in if there's more than one NS 
> device.
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_netscaler_configs.py bcea254 
>   test/integration/component/test_netscaler_lb.py 3942f94 
>   test/integration/component/test_netscaler_lb_algo.py 477bd69 
>   test/integration/component/test_netscaler_lb_sticky.py 1edfd7b 
>   tools/marvin/marvin/integration/lib/common.py 4f5acef 
> 
> Diff: https://reviews.apache.org/r/13680/diff/
> 
> 
> Testing
> ---
> 
> Tested locallly
> 
> 
> Thanks,
> 
> Sowmya Krishnan
> 
>

Re: Review Request 13680: CLOUDSTACK-3927, CLOUDSTACK-3928 Fix to add/remove NS devices in setupClass/tearDownClass

[Prasanna Santhanam]

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

(Updated Aug. 20, 2013, 6:18 a.m.)


Review request for cloudstack, venkata swamy babu  budumuru and Prasanna 
Santhanam.


Bugs: CLOUDSTACK-3927 and CLOUDSTACK-3928


Repository: cloudstack-git


Description
---

Fix to add NS device in setupClass and remove in tearDown
Added a common method to perform these in common.add_netscaler()
Also fixes few account object issues in netscaler_configs.

Patch will help in keeping each test suite independent. Otherwise we cannot 
identify which NS an LB rule will be deployed in if there's more than one NS 
device.


Diffs
-

  test/integration/component/test_netscaler_configs.py bcea254 
  test/integration/component/test_netscaler_lb.py 3942f94 
  test/integration/component/test_netscaler_lb_algo.py 477bd69 
  test/integration/component/test_netscaler_lb_sticky.py 1edfd7b 
  tools/marvin/marvin/integration/lib/common.py 4f5acef 

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


Testing
---

Tested locallly


Thanks,

Sowmya Krishnan

Re: Review Request 13633: CLOUDSTACK-3927, CLOUDSTACK-3928 Fix to add/remove NS devices in setupClass/tearDownClass

[Prasanna Santhanam]

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


discarded for https://reviews.apache.org/r/13680/

- Prasanna Santhanam


On Aug. 18, 2013, 7:30 a.m., Sowmya Krishnan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/13633/
> ---
> 
> (Updated Aug. 18, 2013, 7:30 a.m.)
> 
> 
> Review request for cloudstack and Prasanna Santhanam.
> 
> 
> Bugs: CLOUDSTACK-3927 and CLOUDSTACK-3928
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Fix to add NS device in setupClass and remove in tearDown
> Added a common method to perform these in common.add_netscaler()
> Also fixes few account object issues in netscaler_configs.
> 
> 
> Diffs
> -
> 
> 
> Diff: https://reviews.apache.org/r/13633/diff/
> 
> 
> Testing
> ---
> 
> Tested scripts locally.
> 
> 
> File Attachments
> 
> 
> Patch
>   
> https://reviews.apache.org/media/uploaded/files/2013/08/18/0001-CLOUDSTACK-3927-CLOUDSTACK-3928-Fix-NS-scripts-to-ad_1.patch
> 
> 
> Thanks,
> 
> Sowmya Krishnan
> 
>

Review Request 13680: CLOUDSTACK-3927, CLOUDSTACK-3928 Fix to add/remove NS devices in setupClass/tearDownClass

[Sowmya Krishnan]

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

Review request for cloudstack, venkata swamy babu  budumuru and Prasanna 
Santhanam.


Bugs: CLOUDSTACK-3927 and CLOUDSTACK-3928


Repository: cloudstack-git


Description
---

Fix to add NS device in setupClass and remove in tearDown
Added a common method to perform these in common.add_netscaler()
Also fixes few account object issues in netscaler_configs.

Patch will help in keeping each test suite independent. Otherwise we cannot 
identify which NS an LB rule will be deployed in if there's more than one NS 
device.


Diffs
-

  test/integration/component/test_netscaler_configs.py bcea254 
  test/integration/component/test_netscaler_lb.py 3942f94 
  test/integration/component/test_netscaler_lb_algo.py 477bd69 
  test/integration/component/test_netscaler_lb_sticky.py 1edfd7b 
  tools/marvin/marvin/integration/lib/common.py 4f5acef 

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


Testing
---

Tested locallly


Thanks,

Sowmya Krishnan

Re: CloudStack 4.2 Quality Question

[Mike Tutkowski]

Hi Animesh,

Thanks for the detailed response!

First off, I want to make sure it doesn't seem like I don't appreciate your
efforts in keeping track of issues over the course of a release as I
certainly do. :)

I was just a bit startled this week to see so many fixes going in at the
"last minute" (like 150 in the past week). Perhaps RC builds are simply
treated differently in the open source community than in a commercial
product (or perhaps it's because our dev cycle is so short). I'm still
getting accustomed to the environment here. I know we don't have as much
time between releases as many of the products I've worked on in the past.
For example, at HP, the test team literally worked the release over for
months before a RC was built (and critical and blocker bugs were minimal at
that point). We also only churned out a release or two a year.

So, anyways, I am totally fine with observing how the process works here
and just throwing out comments here and there when I think it makes sense
to. Some of them may make sense; others may not (and some of them we might
already be doing).

I think our efforts at improving our automated regression test suite are
great. Once we have really good test coverage, then numerous "last minute"
changes like this are not such a big deal.

But certainly, I know you're working hard on our defect tracking, so I
definitely didn't mean to imply otherwise. :)

Thanks!


On Mon, Aug 19, 2013 at 10:28 PM, Animesh Chaturvedi <
animesh.chaturv...@citrix.com> wrote:

> Mike
>
> The originally planned RC date was for 8/19. Striving for a specific date
> brings urgency and also helps keep time-based release. We are on a short
> time based release cycle of 4 months and had agreed to a three week RC
> after code freeze. If the releases ends up taking a long time to GA after
> code freeze then we are really not sticking to 4 month cycle. IMO we should
> keep the same urgency to release as we do by keeping strict code freeze and
> feature freeze date. This in no way means we should release untested and
> poor quality release.
>
> You would have noticed that for past two months or so there has been
> vigorous activity on both QA and Dev community members. The number of
> issues created and resolved has come down drastically this week. The
> outstanding blocker and critical count used to be 100+ a month back and
> since then it has consistently come down to a single digit number today
> showing the trend down towards stability.  These are the open product
> blocker and critical issues at this time
>
>
> | Assignee   | Key: Summary
>
> |
> | Kelven Yang| CLOUDSTACK-3237 :  [vmware][SM] Migrate volume
> is failing when there are snapshots for that volume
> |
> | Wei Zhou   | CLOUDSTACK-4405 :  (Upgrade) Migrate failed
> between existing hosts and new hosts
> |
> | Vijayendra Bhamidipati | CLOUDSTACK-3010 :  [VMWare]
> [SharedNetworkWithServices] router VM deployment fails with error "Message:
> Invalid configuration for device '2'." |
> | Wido den Hollander | CLOUDSTACK-4249 :  [KVM]ceph:showing wrong
> template size 755.64 TB(template created from snapshot)
> |
> | Sateesh Chodapuneedi   | CLOUDSTACK-4362 :  VM's are failing to start
> after its DATA volume is migrated to second zone wide primary storage
>   |
>
>
> As for tracking the way downwards I have setup many trending widgets in
> Release Dashboard with 20+ filters which I have been actively monitoring
> and reporting to the community. I would also like to point out in this
> release significant and conscious effort has been put in to put automation
> in place which improves confidence. IMO we should roll forward with the RC
> candidate as it brings better engagement with more user testing and
> feedback. It is ok if we have to re-spins as this helps bring release to
> closure sooner.
>
> Once we decide to do an RC I would lock down 4.2 branch to ensure that we
> do not make any destabilizing changes and cherry-pick necessary fixes as
> was done for 4.1. I apologize for delayed response and I understand that
> this thread should be driven to consensus so I will not cut an RC today and
> wait for what community decides.
>
> There are few more logistics that I would like to discuss on how we should
> proceed after RC. I will start a different thread on that once there is
> community consensus on RC.
>
> Thanks
> Animesh
>
>
>
>
>
> > -Original Message-
> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> > Sent: Monday, August 19, 2013 4:14 PM
> > To: dev@cloudstack.apache.org
> > Subject: Re: CloudStack 4.2 Quality Question
> >
> > Also, just to clarify a bit, what I'm mainly wondering about is if we
> > can find a way to make sure our defects are not only trending downward
> > once we get to a certain point in the release, but also approaching zero
> > well in advance of a

RE: CloudStack 4.2 Quality Question

[Animesh Chaturvedi]

Mike

The originally planned RC date was for 8/19. Striving for a specific date 
brings urgency and also helps keep time-based release. We are on a short time 
based release cycle of 4 months and had agreed to a three week RC after code 
freeze. If the releases ends up taking a long time to GA after code freeze then 
we are really not sticking to 4 month cycle. IMO we should keep the same 
urgency to release as we do by keeping strict code freeze and feature freeze 
date. This in no way means we should release untested and poor quality release.

You would have noticed that for past two months or so there has been vigorous 
activity on both QA and Dev community members. The number of issues created and 
resolved has come down drastically this week. The outstanding blocker and 
critical count used to be 100+ a month back and since then it has consistently 
come down to a single digit number today showing the trend down towards 
stability.  These are the open product blocker and critical issues at this time


| Assignee   | Key: Summary 

  |
| Kelven Yang| CLOUDSTACK-3237 :  [vmware][SM] Migrate volume is 
failing when there are snapshots for that volume
 |
| Wei Zhou   | CLOUDSTACK-4405 :  (Upgrade) Migrate failed between 
existing hosts and new hosts
   |
| Vijayendra Bhamidipati | CLOUDSTACK-3010 :  [VMWare] 
[SharedNetworkWithServices] router VM deployment fails with error "Message: 
Invalid configuration for device '2'." |
| Wido den Hollander | CLOUDSTACK-4249 :  [KVM]ceph:showing wrong template 
size 755.64 TB(template created from snapshot)  
   |
| Sateesh Chodapuneedi   | CLOUDSTACK-4362 :  VM's are failing to start after 
its DATA volume is migrated to second zone wide primary storage 
|


As for tracking the way downwards I have setup many trending widgets in Release 
Dashboard with 20+ filters which I have been actively monitoring and reporting 
to the community. I would also like to point out in this release significant 
and conscious effort has been put in to put automation in place which improves 
confidence. IMO we should roll forward with the RC candidate as it brings 
better engagement with more user testing and feedback. It is ok if we have to 
re-spins as this helps bring release to closure sooner. 

Once we decide to do an RC I would lock down 4.2 branch to ensure that we do 
not make any destabilizing changes and cherry-pick necessary fixes as was done 
for 4.1. I apologize for delayed response and I understand that this thread 
should be driven to consensus so I will not cut an RC today and wait for what 
community decides. 

There are few more logistics that I would like to discuss on how we should 
proceed after RC. I will start a different thread on that once there is 
community consensus on RC.

Thanks
Animesh




 
> -Original Message-
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: Monday, August 19, 2013 4:14 PM
> To: dev@cloudstack.apache.org
> Subject: Re: CloudStack 4.2 Quality Question
> 
> Also, just to clarify a bit, what I'm mainly wondering about is if we
> can find a way to make sure our defects are not only trending downward
> once we get to a certain point in the release, but also approaching zero
> well in advance of a RC build.
> 
> I know Animesh sends out regular updates and I definitely appreciate
> that he does this. I was just thinking we could come up with a strategy
> to determine well in advance (on the order of weeks) whether or not a RC
> candidate build would actually be stable enough to send out into the
> field.
> The best way I can think to do this is to make sure Critical and Blocker
> tickets are down to zero several weeks in advance of an RC build and
> that we are doing regression testing during that time.
> 
> Thoughts on this?
> 
> 
> On Mon, Aug 19, 2013 at 3:22 PM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
> 
> > What are you thoughts, Animesh, on so many check ins in the final
> > week, though? I'm just not familiar with a release working like that.
> > Just curious to get your take on that. Do you feel we have a
> > sufficient number of automated regression tests in place to catch any
> new issues?
> >
> >
> > On Mon, Aug 19, 2013 at 3:20 PM, Animesh Chaturvedi <
> > animesh.chaturv...@citrix.com> wrote:
> >
> >> If you look at the Release Dashboard daily trend graph of created v/s
> >> resolved you will see that we have tapered off significantly this
> >> week. I have been actively triaging and monitoring issues.
> >>
> >>
> >> > -Original Message-
> >> > From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com]
> >> > Sent: Monday, August 19, 2013 2:15 P

Re: Instance Names

[Marcus Sorensen]

You can edit the display name via API or the UI's edit button, but
that only changes what shows up in the UI, not the name of the host
itself (e.g. when you log in and do 'hostname'). To change the actual
name in the vm_instance table, column 'name'. I'm not entirely sure
what the repercussions of that are.

On Mon, Aug 19, 2013 at 9:36 PM, Todd Pigram  wrote:
> vm_instance
>
> On Monday, August 19, 2013, Maurice Lawler wrote:
>
>> Greetings,
>>
>> I'm hoping someone can point me into the right direction, I have
>> provisioned an instanced; however, I failed to create a name for it. Now in
>> my list of instances, I see the UUID and not a 'custom' name so to speak.
>> I'm sure this can easily be manipulated via the database, however; I am
>> looking through docs etc, unsure where to make changes.
>>
>> Any guidance would be greatly appreciate!
>>
>> - M.

Re: Secondary IP (4.1.1)

[Marcus Sorensen]

Well, it depends on how you edit the security_group.py script, it
certainly wouldn't have to open up everything. You could add a
one-liner in there that would pass the instance name to a separate
script that looked up the vm in a table or database and applied extra
rules (in post_default_network_rules), maybe adding something like:

"ebtables -t nat -I " + vmchain_in  +  "  -p ARP --arp-ip-src " +
secondary_vm_ip + " -j ACCEPT"

etc.

Although, that might not be fun to maintain.  It would probably be
easier to use the libvirt hooks: http://www.libvirt.org/hooks.html  To
call your script whenever a vm starts or stops.  You would accept the
guest name as an argument to your script, and then that script could
look up secondary IPs in a table, from a database or file, adding them
to the ebtables chain of the same guest name.

On Mon, Aug 19, 2013 at 8:03 PM, Maurice Lawler  wrote:
> Greetings,
>
> Does anyone have experience in adding a secondary IP address (by way of 
> altering the ebtables / security script) in basic networking mode (KVM)
>
> I have reviewed the script that is called to setup the ebtables, but if I 
> alter that, I would believe that would open all ports on all my instances. I 
> just simply want the easy ability to add a secondary IP address.
>
> I understand this is a feature coming in 4.2, but I also understand this 
> version is a ways out.
>
> Any assistance would be GREATLY appreciated!
>
> - Maurice

Re: API doc build in 4.2

[Rayees Namathponnan]

Thanks David



On 8/19/13 7:56 PM, "David Nalley"  wrote:

>https://cwiki.apache.org/CLOUDSTACK/how-to-generate-cloudstack-api-documen
>tation.html
>
>--David
>
>On Mon, Aug 19, 2013 at 10:36 PM, Rayees Namathponnan
> wrote:
>> Hi All,
>>
>> Anyone know, how to build API doc build in 4.2 ?
>>
>> I tried with below command, but its failed
>>
>>
>> + mvn -P developer -pl tools/apidoc clean install
>>
>>
>>
>> [INFO] Scanning for projects...
>> [INFO]
>> [INFO] 
>>
>> [INFO] Building Apache CloudStack apidocs 4.2.0-SNAPSHOT
>> [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 ---
>> 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:217)
>> at java.security.AccessController.doPrivileged(Native Method)
>> at java.net.URLClassLoader.findClass(URLClassLoader.java:205)
>> at java.lang.ClassLoader.loadClass(ClassLoader.java:321)
>> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294)
>> at java.lang.ClassLoader.loadClass(ClassLoader.java:266)
>> Could not find the main class: com.cloud.api.doc.ApiXmlDocWriter.
>>Program will exit.
>> [INFO] 
>>
>> [INFO] BUILD FAILURE
>> [INFO] 
>>
>> [INFO] Total time: 10.431s
>> [INFO] Finished at: Mon Aug 19 10:51:46 PDT 2013
>> [INFO] Final Memory: 20M/143M
>> [INFO] 
>>
>> [ERROR] Failed to execute goal
>>org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile) on project
>>cloud-apidoc: Command execution failed. Process exited with an error: 1
>>(Exit value: 1) -> [Help 1]
>>
>>
>> Regards,
>>
>> Rayees

Re: Instance Names

[Todd Pigram]

vm_instance

On Monday, August 19, 2013, Maurice Lawler wrote:

> Greetings,
>
> I'm hoping someone can point me into the right direction, I have
> provisioned an instanced; however, I failed to create a name for it. Now in
> my list of instances, I see the UUID and not a 'custom' name so to speak.
> I'm sure this can easily be manipulated via the database, however; I am
> looking through docs etc, unsure where to make changes.
>
> Any guidance would be greatly appreciate!
>
> - M.

RE: [ACS42] QA Tasks that are not complete

[Sudha Ponnaganti]

Hi All,

With initial cleanup below 11 items are remaining to be addressed. Some have 
owners and seem to be in progress - some still need contribution  ( 5 features 
at the bottom of the list). Pl review features and see if you can pick up 
validation aspect.

CLOUDSTACK-2800  CLOUDSTACK-1963 QA: New mapping model for CloudStack 
zone and Vmware datacenterangeline shen
CLOUDSTACK-2829  CLOUDSTACK-1311 QA Allow specification of different 
VIF drivers per traffic type in KVMDave Cahill
CLOUDSTACK-879CLOUDSTACK-509 QA S3-backed Secondary Storage Feature 
  John Burwell
CLOUDSTACK-946CLOUDSTACK-733 QA - BigSwitch network plugin  
Kanzhe Jiang
CLOUDSTACK-2797  CLOUDSTACK-1585 QA: Test Consistent use of refresh 
ButtonParth Jagirdar
CLOUDSTACK-2841  CLOUDSTACK-1191 QA: Test RBD cloning, backup and 
snapshotting  sadhu suresh
CLOUDSTACK-2267  CLOUDSTACK-2059 QA: Support remove network over VMware 
deployments with dvSwitchSailaja Mada
CLOUDSTACK-2423  CLOUDSTACK-2367 QA - VPC - allow loadbalanced network 
offering on multiple tiers  Unassigned
CLOUDSTACK-917CLOUDSTACK-399 QA - review Document vSphere / ESXi 
patch installation procedure Unassigned
CLOUDSTACK-915CLOUDSTACK-337 QA - Create SELinux policy for KVM 
agentUnassigned
CLOUDSTACK-912CLOUDSTACK-240 QA Create-Tag feature is not available 
for VPN Customer Gateway Unassigned

Thanks
/sudha

From: Sudha Ponnaganti
Sent: Monday, August 19, 2013 4:08 PM
To: dev@cloudstack.apache.org
Subject: [ACS42] QA Tasks that are not complete

Feature owners/Community members,

Can you pl review these tasks and update them.  If anyone is interested any of 
these features, can you pl review changes and see if these tasks can be closed.
At the moment looks like JIRA is down. I will update once it is backup

CLOUDSTACK-946CLOUDSTACK-733 QA - BigSwitch network plugin  
Kanzhe
CLOUDSTACK-2797  CLOUDSTACK-1585 QA: Test Consistent use of refresh 
ButtonUnassigned
CLOUDSTACK-2423  CLOUDSTACK-2367 QA - VPC - allow loadbalanced network 
offering on multiple tiers  Unassigned
CLOUDSTACK-1466  CLOUDSTACK-713 [QA Automation] Limit Resources on 
domains/accounts   Unassigned
CLOUDSTACK-917CLOUDSTACK-399 QA - review Document vSphere / ESXi 
patch installation procedure Unassigned
CLOUDSTACK-908CLOUDSTACK-921 [QA] Test VPC new 8-tunnel VPN 
capabilityUnassigned
CLOUDSTACK-912CLOUDSTACK-240 QA Create-Tag feature is not avialable 
for VPN Customer Gateway Unassigned
CLOUDSTACK-915CLOUDSTACK-337 QA - Create SELinux policy for KVM 
agentUnassigned
CLOUDSTACK-949CLOUDSTACK-921 QA - nTier Apps 2.0 blacllist of 
routes Unassigned
CLOUDSTACK-1000  CLOUDSTACK-999 QA - Plugin to provide Hyper V support  
  Unassigned
CLOUDSTACK-2829  CLOUDSTACK-1311 QA Allow specification of different 
VIF drivers per traffic type in KVMUnassigned
CLOUDSTACK-950CLOUDSTACK-921 QA - Ntier Apps 2.0 use same public IP 
for static NAT, PF and LB in VPCUnassigned
CLOUDSTACK-2415  CLOUDSTACK-2163 QA Automation : Add ability in CS for 
admin to have better control over first class objects   Unassigned

Thanks
/sudha

From: Sudha Ponnaganti
Sent: Wednesday, August 14, 2013 1:01 PM
To: dev@cloudstack.apache.org
Subject: [ACS42] QA Tasks that are not complete
Importance: High

Feature owners / Community members - can you review the following QA subtasks 
and see if you can provide some validation report so these can be closed.
Even if you are not developer of the features, you may have used it so pl 
provide such type of validation report as well if you happen to have one.
Some may have been pushed to next release, in such case the fix version can be 
set to "Future", if you have such information, pl update the task directly or 
send me mail with details and I can update it

CLOUDSTACK-946CLOUDSTACK-733 QA - BigSwitch network plugin  
Unassigned
CLOUDSTACK-2797  CLOUDSTACK-1585 QA: Test Consistent use of refresh 
ButtonUnassigned
CLOUDSTACK-2423  CLOUDSTACK-2367 QA - VPC - allow loadbalanced network 
offering on multiple tiers  Unassigned
CLOUDSTACK-1466  CLOUDSTACK-713 [QA Automation] Limit Resources on 
domains/accounts   Unassigned
CLOUDSTACK-917CLOUDSTACK-399 QA - review Document vSphere / ESXi 
patch installation procedure Unassigned
CLOUDSTACK-908CLOUDSTACK-921 [QA] Test VPC new 8-tunnel VPN 
capabilityUnassigned
CLOUDSTACK-912CLOUDSTACK-240 QA Create-Tag feature is not avialable 
for VPN Customer Gateway Unassigned
CLOUDSTACK-915CLOUDSTACK-337 

Instance Names

[Maurice Lawler]

Greetings,

I'm hoping someone can point me into the right direction, I have provisioned an 
instanced; however, I failed to create a name for it. Now in my list of 
instances, I see the UUID and not a 'custom' name so to speak. I'm sure this 
can easily be manipulated via the database, however; I am looking through docs 
etc, unsure where to make changes.

Any guidance would be greatly appreciate!

- M.

Re: API doc build in 4.2

[David Nalley]

https://cwiki.apache.org/CLOUDSTACK/how-to-generate-cloudstack-api-documentation.html

--David

On Mon, Aug 19, 2013 at 10:36 PM, Rayees Namathponnan
 wrote:
> Hi All,
>
> Anyone know, how to build API doc build in 4.2 ?
>
> I tried with below command, but its failed
>
>
> + mvn -P developer -pl tools/apidoc clean install
>
>
>
> [INFO] Scanning for projects...
> [INFO]
> [INFO] 
> 
> [INFO] Building Apache CloudStack apidocs 4.2.0-SNAPSHOT
> [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 ---
> 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:217)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:205)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:321)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:266)
> Could not find the main class: com.cloud.api.doc.ApiXmlDocWriter. Program 
> will exit.
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 10.431s
> [INFO] Finished at: Mon Aug 19 10:51:46 PDT 2013
> [INFO] Final Memory: 20M/143M
> [INFO] 
> 
> [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec 
> (compile) on project cloud-apidoc: Command execution failed. Process exited 
> with an error: 1 (Exit value: 1) -> [Help 1]
>
>
> Regards,
>
> Rayees

Re: Agent State missing or Disconnected for SSVM

[Mike Tutkowski]

These are some of the print outs I'm seeing in the console (I'm not sure
what the msg about i-3-6-VM means either because it shows up just fine in
the GUI and looks like it's running fine in vSphere Client):

INFO  [cloud.secstorage.PremiumSecondaryStorageManagerImpl] (secstorage-1:)
No running secondary storage vms found in datacenter id=1, starting one
INFO  [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:) No
stopped secondary storage vm is available, need to allocate a new secondary
storage vm
INFO  [vmware.mo.HostMO] (DirectAgent-36:172.16.140.4) VM i-3-6-VM not
found in host cache
INFO  [storage.endpoint.DefaultEndPointSelector] (StatsCollector-3:) No
running ssvm is found, so command will be sent to LocalHostEndPoint
INFO  [vmware.mo.HostMO] (DirectAgent-56:172.16.140.4) VM i-3-6-VM not
found in host cache
INFO  [storage.endpoint.DefaultEndPointSelector] (StatsCollector-2:) No
running ssvm is found, so command will be sent to LocalHostEndPoint
INFO  [vmware.mo.HostMO] (DirectAgent-4:172.16.140.4) VM i-3-6-VM not found
in host cache
INFO  [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:)
Secondary storage vm s-8-VM is started
INFO  [cloud.secstorage.PremiumSecondaryStorageManagerImpl] (secstorage-1:)
Primary secondary storage is not even started, wait until next turn
INFO  [storage.endpoint.DefaultEndPointSelector] (StatsCollector-2:) No
running ssvm is found, so command will be sent to LocalHostEndPoint
INFO  [vmware.mo.HostMO] (DirectAgent-9:172.16.140.4) VM i-3-6-VM not found
in host cache
INFO  [storage.endpoint.DefaultEndPointSelector] (StatsCollector-1:) No
running ssvm is found, so command will be sent to LocalHostEndPoint
INFO  [vmware.mo.HostMO] (DirectAgent-74:172.16.140.4) VM i-3-6-VM not
found in host cache

WARN  [storage.resource.LocalNfsSecondaryStorageResource]
(pool-2-thread-1:) Unable to mount 172.16.140.5:/export/secondary due to
INFO  [storage.endpoint.DefaultEndPointSelector] (StatsCollector-2:) No
running ssvm is found, so command will be sent to LocalHostEndPoint
INFO  [vmware.mo.HostMO] (DirectAgent-36:172.16.140.4) VM i-3-6-VM not
found in host cache
INFO  [storage.endpoint.DefaultEndPointSelector] (StatsCollector-2:) No
running ssvm is found, so command will be sent to LocalHostEndPoint
INFO  [vmware.mo.HostMO] (DirectAgent-75:172.16.140.4) VM i-3-6-VM not
found in host cache
INFO  [storage.endpoint.DefaultEndPointSelector] (StatsCollector-1:) No
running ssvm is found, so command will be sent to LocalHostEndPoint
INFO  [vmware.mo.HostMO] (DirectAgent-54:172.16.140.4) VM i-3-6-VM not
found in host cache
INFO  [storage.endpoint.DefaultEndPointSelector] (StatsCollector-3:) No
running ssvm is found, so command will be sent to LocalHostEndPoint
INFO  [vmware.mo.HostMO] (DirectAgent-81:172.16.140.4) VM i-3-6-VM not
found in host cache
INFO  [storage.endpoint.DefaultEndPointSelector] (StatsCollector-3:) No
running ssvm is found, so command will be sent to LocalHostEndPoint
INFO  [vmware.mo.HostMO] (DirectAgent-27:172.16.140.4) VM i-3-6-VM not
found in host cache
INFO  [storage.endpoint.DefaultEndPointSelector] (StatsCollector-1:) No
running ssvm is found, so command will be sent to LocalHostEndPoint


On Mon, Aug 19, 2013 at 8:35 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> Hi,
>
> Can anyone tell me why SSVM would show up with a missing (a dash shown) or
> a Disconnected Agent State?
>
> I'm running in 4.2 (updated this morning). I figured I would try
> destroying SSVM and seeing what happened. Instead of being in the
> Disconnected State, its state is now missing (just a dash is shown).
>
> Does anyone know what this happens? In this state, I'm not able to upload
> an ISO, which is how I noticed the problem.
>
> Thanks!
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the 
> cloud
> *™*
>



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

API doc build in 4.2

[Rayees Namathponnan]

Hi All,

Anyone know, how to build API doc build in 4.2 ?

I tried with below command, but its failed


+ mvn -P developer -pl tools/apidoc clean install



[INFO] Scanning for projects...
[INFO]
[INFO] 
[INFO] Building Apache CloudStack apidocs 4.2.0-SNAPSHOT
[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 ---
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:217)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:205)
at java.lang.ClassLoader.loadClass(ClassLoader.java:321)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294)
at java.lang.ClassLoader.loadClass(ClassLoader.java:266)
Could not find the main class: com.cloud.api.doc.ApiXmlDocWriter. Program will 
exit.
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 10.431s
[INFO] Finished at: Mon Aug 19 10:51:46 PDT 2013
[INFO] Final Memory: 20M/143M
[INFO] 
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec 
(compile) on project cloud-apidoc: Command execution failed. Process exited 
with an error: 1 (Exit value: 1) -> [Help 1]


Regards,

Rayees

Agent State missing or Disconnected for SSVM

[Mike Tutkowski]

Hi,

Can anyone tell me why SSVM would show up with a missing (a dash shown) or
a Disconnected Agent State?

I'm running in 4.2 (updated this morning). I figured I would try destroying
SSVM and seeing what happened. Instead of being in the Disconnected State,
its state is now missing (just a dash is shown).

Does anyone know what this happens? In this state, I'm not able to upload
an ISO, which is how I noticed the problem.

Thanks!

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

Secondary IP (4.1.1)

[Maurice Lawler]

Greetings, 

Does anyone have experience in adding a secondary IP address (by way of 
altering the ebtables / security script) in basic networking mode (KVM)

I have reviewed the script that is called to setup the ebtables, but if I alter 
that, I would believe that would open all ports on all my instances. I just 
simply want the easy ability to add a secondary IP address. 

I understand this is a feature coming in 4.2, but I also understand this 
version is a ways out.

Any assistance would be GREATLY appreciated! 

- Maurice

4.2 S3 storage question

[Thomas O'Dowd]

For S3 secondary storage, I'm wondering exactly what types of objects we
are storing in S3:

1. templates - working.
2. snapshots - working.
3. vmsnapshots - not working (at least I don't see these going to s3)
4. volumes - n/a
5. other?

How do files on the secondary storage staging area get cleaned up
currently?

Tom.
-- 
Cloudian KK - http://www.cloudian.com/get-started.html
Fancy 100TB of full featured S3 Storage?
Checkout the Cloudian® Community Edition!

Re: [ANNOUNCE] New Committer: Toshiaki Hatano

[Go Chiba]

Congrats Hatano-san!


On Tue, Aug 20, 2013 at 7:56 AM, Marcus Sorensen wrote:

> The Project Management Committee (PMC) for Apache CloudStack
> has asked Toshiaki Hatano to become a committer and we are pleased
> to announce that he has accepted.
>
> Being a committer enables easier contribution to the
> project since there is no need to go via the patch
> submission process. This should enable better productivity.
>
> Please join us in congratulating Toshiaki!
>



-- 
千葉 豪  Go Chiba
E-mail:go.ch...@gmail.com

Re: [ANNOUNCE] New Committer: Toshiaki Hatano

[Dave Cahill]

Congratulations Toshiaki!


On Tue, Aug 20, 2013 at 7:56 AM, Marcus Sorensen wrote:

> The Project Management Committee (PMC) for Apache CloudStack
> has asked Toshiaki Hatano to become a committer and we are pleased
> to announce that he has accepted.
>
> Being a committer enables easier contribution to the
> project since there is no need to go via the patch
> submission process. This should enable better productivity.
>
> Please join us in congratulating Toshiaki!
>

Re: CloudStack 4.2 Quality Question

[Mike Tutkowski]

Also, just to clarify a bit, what I'm mainly wondering about is if we can
find a way to make sure our defects are not only trending downward once we
get to a certain point in the release, but also approaching zero well in
advance of a RC build.

I know Animesh sends out regular updates and I definitely appreciate that
he does this. I was just thinking we could come up with a strategy to
determine well in advance (on the order of weeks) whether or not a RC
candidate build would actually be stable enough to send out into the field.
The best way I can think to do this is to make sure Critical and Blocker
tickets are down to zero several weeks in advance of an RC build and that
we are doing regression testing during that time.

Thoughts on this?


On Mon, Aug 19, 2013 at 3:22 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> What are you thoughts, Animesh, on so many check ins in the final week,
> though? I'm just not familiar with a release working like that. Just
> curious to get your take on that. Do you feel we have a sufficient number
> of automated regression tests in place to catch any new issues?
>
>
> On Mon, Aug 19, 2013 at 3:20 PM, Animesh Chaturvedi <
> animesh.chaturv...@citrix.com> wrote:
>
>> If you look at the Release Dashboard daily trend graph of created v/s
>> resolved you will see that we have tapered off significantly this week. I
>> have been actively triaging and monitoring issues.
>>
>>
>> > -Original Message-
>> > From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com]
>> > Sent: Monday, August 19, 2013 2:15 PM
>> > To: dev@cloudstack.apache.org
>> > Subject: Re: CloudStack 4.2 Quality Question
>> >
>> > You can always look at the release dashboard
>> >
>> https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=123209
>> > 42
>> >
>> > This is exactly what has been happening
>> >
>> > Animesh has been sending this out fairly regularly.
>> >
>> >
>> > On 8/19/13 2:01 PM, "Mike Tutkowski" 
>> > wrote:
>> >
>> > >I think we need some kind of process in place to monitor the number of
>> > >critical and blocker defects over the course of the release and make
>> > >sure they're tapering off as we approach a RC build.
>> > >
>> > >My main comment about this release (this is the first CS release that
>> > >I've participated in) is that I've never seen 150 bugs get fixed in the
>> > >final week.
>> > >
>> > >At any of the commercial companies I've worked at over the past 15
>> > >years (SolidFire, HP, LeftHand Networks, Agilent Technologies,
>> > >Accenture), checking in more than a small handful of defects at the
>> > "last minute"
>> > >would
>> > >not be likely to happen. If we would absolutely need to do this, the
>> > >release would have to be pushed out so that we could regression test it
>> > >properly.
>> > >
>> > >The main point is that we cannot compromise CloudStack's quality just
>> > >to meet a release deadline. I'm guessing people agree with that.
>> > >
>> > >
>> > >On Mon, Aug 19, 2013 at 2:49 PM, Mike Tutkowski <
>> > >mike.tutkow...@solidfire.com> wrote:
>> > >
>> > >> "it is" meaning "premature"
>> > >>
>> > >>
>> > >> On Mon, Aug 19, 2013 at 2:49 PM, Mike Tutkowski <
>> > >> mike.tutkow...@solidfire.com> wrote:
>> > >>
>> > >>> I still believe it is, but the VMware "problem" was my fault - I
>> > >>>must not  have had nonoss on b/c it works now. :)
>> > >>>
>> > >>>
>> > >>> On Mon, Aug 19, 2013 at 2:44 PM, Chip Childers
>> >  > >>> > wrote:
>> > >>>
>> >  On Mon, Aug 19, 2013 at 02:33:33PM -0600, Mike Tutkowski wrote:
>> >  > Looks like we have serious issues as of today in 4.2 (I've
>> >  > noticed
>> >  > DevCloud2 not working and VMware support is broken) (aside from
>> > plenty
>> >  of
>> >  > blocker defects still to be completed).
>> >  >
>> >  > When do we start talking about how the 4.2 RC build is not going
>> >  > to
>> >  happen
>> >  > until the codebase calms down a bit? I have serious doubts that
>> >  > 4.2
>> > is
>> >  > ready this week.
>> >  >
>> >  > Thoughts?
>> > 
>> >  Agreed - It seems that this first RC might be a bit premature.
>> > 
>> > >>>
>> > >>>
>> > >>>
>> > >>> --
>> > >>> *Mike Tutkowski*
>> > >>>  *Senior CloudStack Developer, SolidFire Inc.*
>> > >>> e: mike.tutkow...@solidfire.com
>> > >>> o: 303.746.7302
>> > >>> Advancing the way the world uses the
>> > >>>cloud
>> > >>> * *
>> > >>>
>> > >>
>> > >>
>> > >>
>> > >> --
>> > >> *Mike Tutkowski*
>> > >> *Senior CloudStack Developer, SolidFire Inc.*
>> > >> e: mike.tutkow...@solidfire.com
>> > >> o: 303.746.7302
>> > >> Advancing the way the world uses the
>> > >>cloud
>> > >> * *
>> > >>
>> > >
>> > >
>> > >
>> > >--
>> > >*Mike Tutkowski*
>> > >*Senior CloudStack Developer, SolidFire Inc.*
>> > >e: mike.tutkow...@solidfire.com
>> > >o: 303.746.7302
>> > >Advancing the 

[ACS42] QA Subtasks that need to be resolved

[Sudha Ponnaganti]

Thanks all who have worked on these features. All but 2 are closed and 
following up on the 2 that are left over.

Thanks
/sudha

From: Sudha Ponnaganti
Sent: Wednesday, August 14, 2013 12:56 PM
To: dev@cloudstack.apache.org
Subject: [ACS42] QA Subtasks that need to be resolved

Hi All,

Following QA Tasks are not closed and require your attention. Can you review 
the list and see if these can be resolved/closed.

-  For some of these parent story might have been pushed to next 
release, in such case set fixed version as "Future"

Thanks
/Sudha


CLOUDSTACK-903CLOUDSTACK-40 QA - New Image based provisioning 
method for Baremetal   angeline shen
CLOUDSTACK-2800  CLOUDSTACK-1963 QA: New mapping model for CloudStack 
zone and Vmware datacenterangeline shen
CLOUDSTACK-2749  CLOUDSTACK-996 QA: Write test plan and execute 
Testplan for midonet network integrationDave Cahill
CLOUDSTACK-879CLOUDSTACK-509 QA S3-backed Secondary Storage Feature 
  John Burwell
CLOUDSTACK-2841  CLOUDSTACK-1191 QA: Test RBD cloning, backup and 
snapshotting  sadhu suresh
CLOUDSTACK-954CLOUDSTACK-788 QA - support multiple VLANs for KVM HV 
   sadhu suresh
CLOUDSTACK-2267  CLOUDSTACK-2059 QA: Support remove network over VMware 
deployments with dvSwitchSailaja Mada
CLOUDSTACK-943CLOUDSTACK-714 QA - S3 based secondary storage
 Sanjeev N
CLOUDSTACK-886CLOUDSTACK-629 QA new storage subsystem   Sanjeev N

[ACS42] QA Tasks that are not complete

[Sudha Ponnaganti]

Feature owners/Community members,

Can you pl review these tasks and update them.  If anyone is interested any of 
these features, can you pl review changes and see if these tasks can be closed.
At the moment looks like JIRA is down. I will update once it is backup

CLOUDSTACK-946CLOUDSTACK-733 QA - BigSwitch network plugin  
Kanzhe
CLOUDSTACK-2797  CLOUDSTACK-1585 QA: Test Consistent use of refresh 
ButtonUnassigned
CLOUDSTACK-2423  CLOUDSTACK-2367 QA - VPC - allow loadbalanced network 
offering on multiple tiers  Unassigned
CLOUDSTACK-1466  CLOUDSTACK-713 [QA Automation] Limit Resources on 
domains/accounts   Unassigned
CLOUDSTACK-917CLOUDSTACK-399 QA - review Document vSphere / ESXi 
patch installation procedure Unassigned
CLOUDSTACK-908CLOUDSTACK-921 [QA] Test VPC new 8-tunnel VPN 
capabilityUnassigned
CLOUDSTACK-912CLOUDSTACK-240 QA Create-Tag feature is not avialable 
for VPN Customer Gateway Unassigned
CLOUDSTACK-915CLOUDSTACK-337 QA - Create SELinux policy for KVM 
agentUnassigned
CLOUDSTACK-949CLOUDSTACK-921 QA - nTier Apps 2.0 blacllist of 
routes Unassigned
CLOUDSTACK-1000  CLOUDSTACK-999 QA - Plugin to provide Hyper V support  
  Unassigned
CLOUDSTACK-2829  CLOUDSTACK-1311 QA Allow specification of different 
VIF drivers per traffic type in KVMUnassigned
CLOUDSTACK-950CLOUDSTACK-921 QA - Ntier Apps 2.0 use same public IP 
for static NAT, PF and LB in VPCUnassigned
CLOUDSTACK-2415  CLOUDSTACK-2163 QA Automation : Add ability in CS for 
admin to have better control over first class objects   Unassigned

Thanks
/sudha

From: Sudha Ponnaganti
Sent: Wednesday, August 14, 2013 1:01 PM
To: dev@cloudstack.apache.org
Subject: [ACS42] QA Tasks that are not complete
Importance: High

Feature owners / Community members - can you review the following QA subtasks 
and see if you can provide some validation report so these can be closed.
Even if you are not developer of the features, you may have used it so pl 
provide such type of validation report as well if you happen to have one.
Some may have been pushed to next release, in such case the fix version can be 
set to "Future", if you have such information, pl update the task directly or 
send me mail with details and I can update it

CLOUDSTACK-946CLOUDSTACK-733 QA - BigSwitch network plugin  
Unassigned
CLOUDSTACK-2797  CLOUDSTACK-1585 QA: Test Consistent use of refresh 
ButtonUnassigned
CLOUDSTACK-2423  CLOUDSTACK-2367 QA - VPC - allow loadbalanced network 
offering on multiple tiers  Unassigned
CLOUDSTACK-1466  CLOUDSTACK-713 [QA Automation] Limit Resources on 
domains/accounts   Unassigned
CLOUDSTACK-917CLOUDSTACK-399 QA - review Document vSphere / ESXi 
patch installation procedure Unassigned
CLOUDSTACK-908CLOUDSTACK-921 [QA] Test VPC new 8-tunnel VPN 
capabilityUnassigned
CLOUDSTACK-912CLOUDSTACK-240 QA Create-Tag feature is not avialable 
for VPN Customer Gateway Unassigned
CLOUDSTACK-915CLOUDSTACK-337 QA - Create SELinux policy for KVM 
agentUnassigned
CLOUDSTACK-949CLOUDSTACK-921 QA - nTier Apps 2.0 blacllist of 
routes Unassigned
CLOUDSTACK-1000  CLOUDSTACK-999 QA - Plugin to provide Hyper V support  
  Unassigned
CLOUDSTACK-2829  CLOUDSTACK-1311 QA Allow specification of different 
VIF drivers per traffic type in KVMUnassigned
CLOUDSTACK-950CLOUDSTACK-921 QA - Ntier Apps 2.0 use same public IP 
for static NAT, PF and LB in VPCUnassigned
CLOUDSTACK-2415  CLOUDSTACK-2163 QA Automation : Add ability in CS for 
admin to have better control over first class objects   Unassigned

Re: Review Request 12364: Follow up fix for CLOUDSTACK-2777

[ASF Subversion and Git Services]

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


Commit a71f41401ba5c04f213f170e76856723655a9204 in branch refs/heads/4.1 from 
Prachi Damle
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a71f414 ]

Followup fix for CLOUDSTACK-2777, crypto.properties and xes.keystore moved to 
AWSAPI installation location and changed permission to 666

Conflicts:

packaging/centos63/cloud.spec


- ASF Subversion and Git Services


On July 9, 2013, 3:20 p.m., Rayees Namathponnan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/12364/
> ---
> 
> (Updated July 9, 2013, 3:20 p.m.)
> 
> 
> Review request for cloudstack, Likitha Shetty and Prachi Damle.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Followup fix for CLOUDSTACK-2777, crypto.properties and xes.keystore moved to 
> AWSAPI installation location and changed permission  to 666
> 
> 
> Diffs
> -
> 
>   packaging/centos63/cloud.spec f7eb629 
> 
> Diff: https://reviews.apache.org/r/12364/diff/
> 
> 
> Testing
> ---
> 
> Tested 
> 
> 
> Thanks,
> 
> Rayees Namathponnan
> 
>

Re: Review Request 12364: Follow up fix for CLOUDSTACK-2777

[ASF Subversion and Git Services]

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


Commit bc43784e013dd761f6b0ffad015584ac2f0bb750 in branch refs/heads/4.1 from 
Likitha Shetty
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=bc43784 ]

CLOUDSTACK-2777. Apache build should create jar file cloud-ec2.aar and package 
it under webapps7080/awsapi/WEB-INF/services


- ASF Subversion and Git Services


On July 9, 2013, 3:20 p.m., Rayees Namathponnan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/12364/
> ---
> 
> (Updated July 9, 2013, 3:20 p.m.)
> 
> 
> Review request for cloudstack, Likitha Shetty and Prachi Damle.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Followup fix for CLOUDSTACK-2777, crypto.properties and xes.keystore moved to 
> AWSAPI installation location and changed permission  to 666
> 
> 
> Diffs
> -
> 
>   packaging/centos63/cloud.spec f7eb629 
> 
> Diff: https://reviews.apache.org/r/12364/diff/
> 
> 
> Testing
> ---
> 
> Tested 
> 
> 
> Thanks,
> 
> Rayees Namathponnan
> 
>

[ANNOUNCE] New Committer: Toshiaki Hatano

[Marcus Sorensen]

The Project Management Committee (PMC) for Apache CloudStack
has asked Toshiaki Hatano to become a committer and we are pleased
to announce that he has accepted.

Being a committer enables easier contribution to the
project since there is no need to go via the patch
submission process. This should enable better productivity.

Please join us in congratulating Toshiaki!

Re: [DISCUSS] Adding RAT checks to the default build

[Chiradeep Vittal]

I think developers will anyway try to optimize their build time.
This cannot be helped.
The danger of course is that they 'git push' before running the full build.

On 8/19/13 11:39 AM, "Chip Childers"  wrote:

>Hey all,
>
>Apache RAT 0.10 has been released, improving the speed for a RAT check
>quite a bit.  I've gone ahead and changed the builds.a.o jobs to use
>version 0.10.
>
>I'd like to propose that we add the plugin to our default build, now
>that it's faster.  You can see the speed by running:
>
>mvn --projects='org.apache.cloudstack:cloudstack'
>org.apache.rat:apache-rat-plugin:0.10:check
>
>And can compare with 0.8 using:
>
>mvn --projects='org.apache.cloudstack:cloudstack'
>org.apache.rat:apache-rat-plugin:0.8:check
>
>
>This would help us ensure that we don't have licensing issues lingering
>out on CI servers with little attention.
>
>-chip

Re: Review Request 13664: Fix for rhel 5 upgrade failure defect CLOUDSTACK-4370

[ASF Subversion and Git Services]

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


Commit c09bbd316c1e2648fe0a07fffb81befc6bb93d31 in branch refs/heads/master 
from rayeesn
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c09bbd3 ]

CLOUDSTACK-4370 - Upgrade failing due to depenency with cloudstack-agent, 
changed remove dependency from cloud-agent to cloud-common


- ASF Subversion and Git Services


On Aug. 19, 2013, 9:19 p.m., Rayees Namathponnan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/13664/
> ---
> 
> (Updated Aug. 19, 2013, 9:19 p.m.)
> 
> 
> Review request for cloudstack and Frank Zhang.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> CLOUDSTACK-4370 - Upgrade failing due to depenency with cloudstack-agent, 
> changed remove dependency from cloud-agent to cloud-common
> 
> Also updated wrong message printing on installation console, to updated 
> server.xml 
> 
> 
> Diffs
> -
> 
>   packaging/centos63/cloud.spec 8cc6b48 
> 
> Diff: https://reviews.apache.org/r/13664/diff/
> 
> 
> Testing
> ---
> 
> Tested 
> 
> 
> Thanks,
> 
> Rayees Namathponnan
> 
>

Re: Review Request 13664: Fix for rhel 5 upgrade failure defect CLOUDSTACK-4370

[Frank Zhang]

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

Ship it!


Ship It!

- Frank Zhang


On Aug. 19, 2013, 9:19 p.m., Rayees Namathponnan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/13664/
> ---
> 
> (Updated Aug. 19, 2013, 9:19 p.m.)
> 
> 
> Review request for cloudstack and Frank Zhang.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> CLOUDSTACK-4370 - Upgrade failing due to depenency with cloudstack-agent, 
> changed remove dependency from cloud-agent to cloud-common
> 
> Also updated wrong message printing on installation console, to updated 
> server.xml 
> 
> 
> Diffs
> -
> 
>   packaging/centos63/cloud.spec 8cc6b48 
> 
> Diff: https://reviews.apache.org/r/13664/diff/
> 
> 
> Testing
> ---
> 
> Tested 
> 
> 
> Thanks,
> 
> Rayees Namathponnan
> 
>

Re: Review Request 13664: Fix for rhel 5 upgrade failure defect CLOUDSTACK-4370

[ASF Subversion and Git Services]

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


Commit 12f36b8dbbfd0f24ca35280215bbd6e797e985d1 in branch refs/heads/4.2 from 
rayeesn
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=12f36b8 ]

CLOUDSTACK-4370 - Upgrade failing due to depenency with cloudstack-agent, 
changed remove dependency from cloud-agent to cloud-common


- ASF Subversion and Git Services


On Aug. 19, 2013, 9:19 p.m., Rayees Namathponnan wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/13664/
> ---
> 
> (Updated Aug. 19, 2013, 9:19 p.m.)
> 
> 
> Review request for cloudstack and Frank Zhang.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> CLOUDSTACK-4370 - Upgrade failing due to depenency with cloudstack-agent, 
> changed remove dependency from cloud-agent to cloud-common
> 
> Also updated wrong message printing on installation console, to updated 
> server.xml 
> 
> 
> Diffs
> -
> 
>   packaging/centos63/cloud.spec 8cc6b48 
> 
> Diff: https://reviews.apache.org/r/13664/diff/
> 
> 
> Testing
> ---
> 
> Tested 
> 
> 
> Thanks,
> 
> Rayees Namathponnan
> 
>

Re: Password requested when starting CS MS

[Mike Tutkowski]

Yeah, I agree, John.

Thanks for the info!


On Mon, Aug 19, 2013 at 3:47 PM, John Burwell  wrote:

> Mike,
>
> CLOUDSTACK-1389 [1] was opened in February regarding this defect.  To me,
> the biggest issue is that, in some scenarios, our daemons may require a tty
> because this script uses sudo.  As a matter of general system etiquette,
> under no circumstances a daemon should never require user input or require
> a tty.
>
> Thanks,
> -John
>
> [1]: https://issues.apache.org/jira/browse/CLOUDSTACK-1389
>
> On Aug 12, 2013, at 2:09 PM, Mike Tutkowski 
> wrote:
>
> Ah, thanks, Pedro
>
>
> On Mon, Aug 12, 2013 at 11:31 AM, Pedro Roque Marques <
> pedro.r.marq...@gmail.com> wrote:
>
> Mike,
> If you create a cloudstack-management package and run
> "cloudstack-setup-management" before  starting the management server you
> can run the MS as user cloud without experiencing these issues...
> It sets up the correct privileges.
>
>  Pedro.
>
> On Aug 12, 2013, at 9:47 AM, Mike Tutkowski wrote:
>
> Yeah, it seems to only happen when I have a fresh install.
>
> I also notice - in this situation - that I get a password prompt in my
> console when trying to upload an ISO for the first time.
>
> Chris - I once wondered about running the CS MS as root, but someone
>
> warned
>
> me not to because it might cover up issues that would otherwise be
>
> exposed
>
> if I weren't running as root. What do you think about that?
>
> Thanks, guys!
>
>
> On Mon, Aug 12, 2013 at 9:54 AM, SuichII, Christopher <
> chris.su...@netapp.com> wrote:
>
> I got around this by running the CS server as root. Would that be an
> option for you, Mike?
>
> On Aug 12, 2013, at 11:19 AM, Daan Hoogland 
> wrote:
>
> does this only happen on a new installation/clean db? Sounds like
> admin account not enabled yet.
>
> Daan
>
> On Tue, Aug 6, 2013 at 7:21 PM, Mike Tutkowski
>  wrote:
>
> -- Forwarded message --
> From: Mike Tutkowski 
> Date: Tue, Aug 6, 2013 at 11:19 AM
> Subject: Password requested when starting CS MS
> To: "dev@cloudstack.apache.org" 
>
>
> Hi,
>
> This happens to me every now and then, but - with the most recent 4.2
>
> code
>
> - I seem to be seeing it again.
>
> When I start up the CS MS, I get a keystore exception and have to hit
>  several times on a Password prompt to get the CS MS to
>
> continue
>
> starting up.
>
> Is this acceptable or am I missing out on some functionality with this
> happening?
>
> Does anyone know why I'm prompted for a password? Even if I enter in
>
> one
>
> (the root password), it still prompts me again for my password. Maybe
> that's not the password it's looking for?
>
> Thanks!
>
> WARN  [cloud.server.ConfigurationServerImpl] (Timer-2:) Would use
>
> fail-safe
>
> keystore to continue.
> java.io.IOException: Fail to generate certificate!: timeout
> at
>
>
>
> com.cloud.server.ConfigurationServerImpl.generateDefaultKeystore(ConfigurationServerImpl.java:496)
>
> at
>
>
>
> com.cloud.server.ConfigurationServerImpl.updateSSLKeystore(ConfigurationServerImpl.java:517)
>
> at
>
>
>
> com.cloud.server.ConfigurationServerImpl.persistDefaultValues(ConfigurationServerImpl.java:289)
>
> at
>
>
>
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
>
> at
>
>
>
> com.cloud.server.ConfigurationServerImpl.configure(ConfigurationServerImpl.java:157)
>
> at
>
>
>
> com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:111)
>
> at
>
> com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:54)
>
> at java.util.TimerThread.mainLoop(Timer.java:512)
> at java.util.TimerThread.run(Timer.java:462)
> INFO  [cloud.server.ConfigurationServerImpl] (Timer-2:) Processing
> updateKeyPairs
> INFO  [cloud.server.ConfigurationServerImpl] (Timer-2:) Keypairs
>
> already in
>
> database, updating local copy
> INFO  [cloud.server.ConfigurationServerImpl] (Timer-2:) Going to
>
> update
>
> systemvm iso with generated keypairs if needed
> Password:
> Password:
> Password:
> Password:
> Password:
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud
> *™*
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud
> *™*
>
>
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud
> *™*
>
>
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud

Re: Password requested when starting CS MS

[John Burwell]

Mike,

CLOUDSTACK-1389 [1] was opened in February regarding this defect.  To me, the 
biggest issue is that, in some scenarios, our daemons may require a tty because 
this script uses sudo.  As a matter of general system etiquette, under no 
circumstances a daemon should never require user input or require a tty.

Thanks,
-John

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

On Aug 12, 2013, at 2:09 PM, Mike Tutkowski  
wrote:

> Ah, thanks, Pedro
> 
> 
> On Mon, Aug 12, 2013 at 11:31 AM, Pedro Roque Marques <
> pedro.r.marq...@gmail.com> wrote:
> 
>> Mike,
>> If you create a cloudstack-management package and run
>> "cloudstack-setup-management" before  starting the management server you
>> can run the MS as user cloud without experiencing these issues...
>> It sets up the correct privileges.
>> 
>>  Pedro.
>> 
>> On Aug 12, 2013, at 9:47 AM, Mike Tutkowski wrote:
>> 
>>> Yeah, it seems to only happen when I have a fresh install.
>>> 
>>> I also notice - in this situation - that I get a password prompt in my
>>> console when trying to upload an ISO for the first time.
>>> 
>>> Chris - I once wondered about running the CS MS as root, but someone
>> warned
>>> me not to because it might cover up issues that would otherwise be
>> exposed
>>> if I weren't running as root. What do you think about that?
>>> 
>>> Thanks, guys!
>>> 
>>> 
>>> On Mon, Aug 12, 2013 at 9:54 AM, SuichII, Christopher <
>>> chris.su...@netapp.com> wrote:
>>> 
 I got around this by running the CS server as root. Would that be an
 option for you, Mike?
 
 On Aug 12, 2013, at 11:19 AM, Daan Hoogland 
 wrote:
 
> does this only happen on a new installation/clean db? Sounds like
> admin account not enabled yet.
> 
> Daan
> 
> On Tue, Aug 6, 2013 at 7:21 PM, Mike Tutkowski
>  wrote:
>> -- Forwarded message --
>> From: Mike Tutkowski 
>> Date: Tue, Aug 6, 2013 at 11:19 AM
>> Subject: Password requested when starting CS MS
>> To: "dev@cloudstack.apache.org" 
>> 
>> 
>> Hi,
>> 
>> This happens to me every now and then, but - with the most recent 4.2
 code
>> - I seem to be seeing it again.
>> 
>> When I start up the CS MS, I get a keystore exception and have to hit
>>  several times on a Password prompt to get the CS MS to
>> continue
>> starting up.
>> 
>> Is this acceptable or am I missing out on some functionality with this
>> happening?
>> 
>> Does anyone know why I'm prompted for a password? Even if I enter in
>> one
>> (the root password), it still prompts me again for my password. Maybe
>> that's not the password it's looking for?
>> 
>> Thanks!
>> 
>> WARN  [cloud.server.ConfigurationServerImpl] (Timer-2:) Would use
 fail-safe
>> keystore to continue.
>> java.io.IOException: Fail to generate certificate!: timeout
>> at
>> 
 
>> com.cloud.server.ConfigurationServerImpl.generateDefaultKeystore(ConfigurationServerImpl.java:496)
>> at
>> 
 
>> com.cloud.server.ConfigurationServerImpl.updateSSLKeystore(ConfigurationServerImpl.java:517)
>> at
>> 
 
>> com.cloud.server.ConfigurationServerImpl.persistDefaultValues(ConfigurationServerImpl.java:289)
>> at
>> 
 
>> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
>> at
>> 
 
>> com.cloud.server.ConfigurationServerImpl.configure(ConfigurationServerImpl.java:157)
>> at
>> 
 
>> com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:111)
>> at
 com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:54)
>> at java.util.TimerThread.mainLoop(Timer.java:512)
>> at java.util.TimerThread.run(Timer.java:462)
>> INFO  [cloud.server.ConfigurationServerImpl] (Timer-2:) Processing
>> updateKeyPairs
>> INFO  [cloud.server.ConfigurationServerImpl] (Timer-2:) Keypairs
 already in
>> database, updating local copy
>> INFO  [cloud.server.ConfigurationServerImpl] (Timer-2:) Going to
>> update
>> systemvm iso with generated keypairs if needed
>> Password:
>> Password:
>> Password:
>> Password:
>> Password:
>> 
>> --
>> *Mike Tutkowski*
>> *Senior CloudStack Developer, SolidFire Inc.*
>> e: mike.tutkow...@solidfire.com
>> o: 303.746.7302
>> Advancing the way the world uses the
>> cloud
>> *™*
>> 
>> 
>> 
>> --
>> *Mike Tutkowski*
>> *Senior CloudStack Developer, SolidFire Inc.*
>> e: mike.tutkow...@solidfire.com
>> o: 303.746.7302
>> Advancing the way the world uses the
>> cloud
>> *™*
 
 
>>> 
>>> 
>>> --
>>> *Mike Tutkowski*
>>> *Senior CloudStack Developer, SolidF

Re: CloudStack 4.2 Quality Question

[Mike Tutkowski]

What are you thoughts, Animesh, on so many check ins in the final week,
though? I'm just not familiar with a release working like that. Just
curious to get your take on that. Do you feel we have a sufficient number
of automated regression tests in place to catch any new issues?


On Mon, Aug 19, 2013 at 3:20 PM, Animesh Chaturvedi <
animesh.chaturv...@citrix.com> wrote:

> If you look at the Release Dashboard daily trend graph of created v/s
> resolved you will see that we have tapered off significantly this week. I
> have been actively triaging and monitoring issues.
>
>
> > -Original Message-
> > From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com]
> > Sent: Monday, August 19, 2013 2:15 PM
> > To: dev@cloudstack.apache.org
> > Subject: Re: CloudStack 4.2 Quality Question
> >
> > You can always look at the release dashboard
> > https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=123209
> > 42
> >
> > This is exactly what has been happening
> >
> > Animesh has been sending this out fairly regularly.
> >
> >
> > On 8/19/13 2:01 PM, "Mike Tutkowski" 
> > wrote:
> >
> > >I think we need some kind of process in place to monitor the number of
> > >critical and blocker defects over the course of the release and make
> > >sure they're tapering off as we approach a RC build.
> > >
> > >My main comment about this release (this is the first CS release that
> > >I've participated in) is that I've never seen 150 bugs get fixed in the
> > >final week.
> > >
> > >At any of the commercial companies I've worked at over the past 15
> > >years (SolidFire, HP, LeftHand Networks, Agilent Technologies,
> > >Accenture), checking in more than a small handful of defects at the
> > "last minute"
> > >would
> > >not be likely to happen. If we would absolutely need to do this, the
> > >release would have to be pushed out so that we could regression test it
> > >properly.
> > >
> > >The main point is that we cannot compromise CloudStack's quality just
> > >to meet a release deadline. I'm guessing people agree with that.
> > >
> > >
> > >On Mon, Aug 19, 2013 at 2:49 PM, Mike Tutkowski <
> > >mike.tutkow...@solidfire.com> wrote:
> > >
> > >> "it is" meaning "premature"
> > >>
> > >>
> > >> On Mon, Aug 19, 2013 at 2:49 PM, Mike Tutkowski <
> > >> mike.tutkow...@solidfire.com> wrote:
> > >>
> > >>> I still believe it is, but the VMware "problem" was my fault - I
> > >>>must not  have had nonoss on b/c it works now. :)
> > >>>
> > >>>
> > >>> On Mon, Aug 19, 2013 at 2:44 PM, Chip Childers
> > >>> > >>> > wrote:
> > >>>
> >  On Mon, Aug 19, 2013 at 02:33:33PM -0600, Mike Tutkowski wrote:
> >  > Looks like we have serious issues as of today in 4.2 (I've
> >  > noticed
> >  > DevCloud2 not working and VMware support is broken) (aside from
> > plenty
> >  of
> >  > blocker defects still to be completed).
> >  >
> >  > When do we start talking about how the 4.2 RC build is not going
> >  > to
> >  happen
> >  > until the codebase calms down a bit? I have serious doubts that
> >  > 4.2
> > is
> >  > ready this week.
> >  >
> >  > Thoughts?
> > 
> >  Agreed - It seems that this first RC might be a bit premature.
> > 
> > >>>
> > >>>
> > >>>
> > >>> --
> > >>> *Mike Tutkowski*
> > >>>  *Senior CloudStack Developer, SolidFire Inc.*
> > >>> e: mike.tutkow...@solidfire.com
> > >>> o: 303.746.7302
> > >>> Advancing the way the world uses the
> > >>>cloud
> > >>> * *
> > >>>
> > >>
> > >>
> > >>
> > >> --
> > >> *Mike Tutkowski*
> > >> *Senior CloudStack Developer, SolidFire Inc.*
> > >> e: mike.tutkow...@solidfire.com
> > >> o: 303.746.7302
> > >> Advancing the way the world uses the
> > >>cloud
> > >> * *
> > >>
> > >
> > >
> > >
> > >--
> > >*Mike Tutkowski*
> > >*Senior CloudStack Developer, SolidFire Inc.*
> > >e: mike.tutkow...@solidfire.com
> > >o: 303.746.7302
> > >Advancing the way the world uses the
> > >cloud
> > >* *
>
>


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

Re: CloudStack 4.2 Quality Question

[Mike Tutkowski]

Yeah, I agree it's been tapering down, but 150 or so in the last week
doesn't really seem like a good place to end before building a RC.


On Mon, Aug 19, 2013 at 3:14 PM, Chiradeep Vittal <
chiradeep.vit...@citrix.com> wrote:

> You can always look at the release dashboard
> https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12320942
>
> This is exactly what has been happening
>
> Animesh has been sending this out fairly regularly.
>
>
> On 8/19/13 2:01 PM, "Mike Tutkowski"  wrote:
>
> >I think we need some kind of process in place to monitor the number of
> >critical and blocker defects over the course of the release and make sure
> >they're tapering off as we approach a RC build.
> >
> >My main comment about this release (this is the first CS release that I've
> >participated in) is that I've never seen 150 bugs get fixed in the final
> >week.
> >
> >At any of the commercial companies I've worked at over the past 15 years
> >(SolidFire, HP, LeftHand Networks, Agilent Technologies, Accenture),
> >checking in more than a small handful of defects at the "last minute"
> >would
> >not be likely to happen. If we would absolutely need to do this, the
> >release would have to be pushed out so that we could regression test it
> >properly.
> >
> >The main point is that we cannot compromise CloudStack's quality just to
> >meet a release deadline. I'm guessing people agree with that.
> >
> >
> >On Mon, Aug 19, 2013 at 2:49 PM, Mike Tutkowski <
> >mike.tutkow...@solidfire.com> wrote:
> >
> >> "it is" meaning "premature"
> >>
> >>
> >> On Mon, Aug 19, 2013 at 2:49 PM, Mike Tutkowski <
> >> mike.tutkow...@solidfire.com> wrote:
> >>
> >>> I still believe it is, but the VMware "problem" was my fault - I must
> >>>not
> >>> have had nonoss on b/c it works now. :)
> >>>
> >>>
> >>> On Mon, Aug 19, 2013 at 2:44 PM, Chip Childers
> >>> >>> > wrote:
> >>>
>  On Mon, Aug 19, 2013 at 02:33:33PM -0600, Mike Tutkowski wrote:
>  > Looks like we have serious issues as of today in 4.2 (I've noticed
>  > DevCloud2 not working and VMware support is broken) (aside from
> plenty
>  of
>  > blocker defects still to be completed).
>  >
>  > When do we start talking about how the 4.2 RC build is not going to
>  happen
>  > until the codebase calms down a bit? I have serious doubts that 4.2
> is
>  > ready this week.
>  >
>  > Thoughts?
> 
>  Agreed - It seems that this first RC might be a bit premature.
> 
> >>>
> >>>
> >>>
> >>> --
> >>> *Mike Tutkowski*
> >>>  *Senior CloudStack Developer, SolidFire Inc.*
> >>> e: mike.tutkow...@solidfire.com
> >>> o: 303.746.7302
> >>> Advancing the way the world uses the
> >>>cloud
> >>> * *
> >>>
> >>
> >>
> >>
> >> --
> >> *Mike Tutkowski*
> >> *Senior CloudStack Developer, SolidFire Inc.*
> >> e: mike.tutkow...@solidfire.com
> >> o: 303.746.7302
> >> Advancing the way the world uses the
> >>cloud
> >> * *
> >>
> >
> >
> >
> >--
> >*Mike Tutkowski*
> >*Senior CloudStack Developer, SolidFire Inc.*
> >e: mike.tutkow...@solidfire.com
> >o: 303.746.7302
> >Advancing the way the world uses the
> >cloud
> >* *
>
>


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

RE: CloudStack 4.2 Quality Question

[Animesh Chaturvedi]

If you look at the Release Dashboard daily trend graph of created v/s resolved 
you will see that we have tapered off significantly this week. I have been 
actively triaging and monitoring issues. 


> -Original Message-
> From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com]
> Sent: Monday, August 19, 2013 2:15 PM
> To: dev@cloudstack.apache.org
> Subject: Re: CloudStack 4.2 Quality Question
> 
> You can always look at the release dashboard
> https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=123209
> 42
> 
> This is exactly what has been happening
> 
> Animesh has been sending this out fairly regularly.
> 
> 
> On 8/19/13 2:01 PM, "Mike Tutkowski" 
> wrote:
> 
> >I think we need some kind of process in place to monitor the number of
> >critical and blocker defects over the course of the release and make
> >sure they're tapering off as we approach a RC build.
> >
> >My main comment about this release (this is the first CS release that
> >I've participated in) is that I've never seen 150 bugs get fixed in the
> >final week.
> >
> >At any of the commercial companies I've worked at over the past 15
> >years (SolidFire, HP, LeftHand Networks, Agilent Technologies,
> >Accenture), checking in more than a small handful of defects at the
> "last minute"
> >would
> >not be likely to happen. If we would absolutely need to do this, the
> >release would have to be pushed out so that we could regression test it
> >properly.
> >
> >The main point is that we cannot compromise CloudStack's quality just
> >to meet a release deadline. I'm guessing people agree with that.
> >
> >
> >On Mon, Aug 19, 2013 at 2:49 PM, Mike Tutkowski <
> >mike.tutkow...@solidfire.com> wrote:
> >
> >> "it is" meaning "premature"
> >>
> >>
> >> On Mon, Aug 19, 2013 at 2:49 PM, Mike Tutkowski <
> >> mike.tutkow...@solidfire.com> wrote:
> >>
> >>> I still believe it is, but the VMware "problem" was my fault - I
> >>>must not  have had nonoss on b/c it works now. :)
> >>>
> >>>
> >>> On Mon, Aug 19, 2013 at 2:44 PM, Chip Childers
> >>> >>> > wrote:
> >>>
>  On Mon, Aug 19, 2013 at 02:33:33PM -0600, Mike Tutkowski wrote:
>  > Looks like we have serious issues as of today in 4.2 (I've
>  > noticed
>  > DevCloud2 not working and VMware support is broken) (aside from
> plenty
>  of
>  > blocker defects still to be completed).
>  >
>  > When do we start talking about how the 4.2 RC build is not going
>  > to
>  happen
>  > until the codebase calms down a bit? I have serious doubts that
>  > 4.2
> is
>  > ready this week.
>  >
>  > Thoughts?
> 
>  Agreed - It seems that this first RC might be a bit premature.
> 
> >>>
> >>>
> >>>
> >>> --
> >>> *Mike Tutkowski*
> >>>  *Senior CloudStack Developer, SolidFire Inc.*
> >>> e: mike.tutkow...@solidfire.com
> >>> o: 303.746.7302
> >>> Advancing the way the world uses the
> >>>cloud
> >>> **
> >>>
> >>
> >>
> >>
> >> --
> >> *Mike Tutkowski*
> >> *Senior CloudStack Developer, SolidFire Inc.*
> >> e: mike.tutkow...@solidfire.com
> >> o: 303.746.7302
> >> Advancing the way the world uses the
> >>cloud
> >> **
> >>
> >
> >
> >
> >--
> >*Mike Tutkowski*
> >*Senior CloudStack Developer, SolidFire Inc.*
> >e: mike.tutkow...@solidfire.com
> >o: 303.746.7302
> >Advancing the way the world uses the
> >cloud
> >**

Review Request 13664: Fix for rhel 5 upgrade failure defect CLOUDSTACK-4370

[Rayees Namathponnan]

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

Review request for cloudstack and Frank Zhang.


Repository: cloudstack-git


Description
---

CLOUDSTACK-4370 - Upgrade failing due to depenency with cloudstack-agent, 
changed remove dependency from cloud-agent to cloud-common

Also updated wrong message printing on installation console, to updated 
server.xml 


Diffs
-

  packaging/centos63/cloud.spec 8cc6b48 

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


Testing
---

Tested 


Thanks,

Rayees Namathponnan

Re: CloudStack 4.2 Quality Question

[Chiradeep Vittal]

You can always look at the release dashboard
https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12320942

This is exactly what has been happening

Animesh has been sending this out fairly regularly.


On 8/19/13 2:01 PM, "Mike Tutkowski"  wrote:

>I think we need some kind of process in place to monitor the number of
>critical and blocker defects over the course of the release and make sure
>they're tapering off as we approach a RC build.
>
>My main comment about this release (this is the first CS release that I've
>participated in) is that I've never seen 150 bugs get fixed in the final
>week.
>
>At any of the commercial companies I've worked at over the past 15 years
>(SolidFire, HP, LeftHand Networks, Agilent Technologies, Accenture),
>checking in more than a small handful of defects at the "last minute"
>would
>not be likely to happen. If we would absolutely need to do this, the
>release would have to be pushed out so that we could regression test it
>properly.
>
>The main point is that we cannot compromise CloudStack's quality just to
>meet a release deadline. I'm guessing people agree with that.
>
>
>On Mon, Aug 19, 2013 at 2:49 PM, Mike Tutkowski <
>mike.tutkow...@solidfire.com> wrote:
>
>> "it is" meaning "premature"
>>
>>
>> On Mon, Aug 19, 2013 at 2:49 PM, Mike Tutkowski <
>> mike.tutkow...@solidfire.com> wrote:
>>
>>> I still believe it is, but the VMware "problem" was my fault - I must
>>>not
>>> have had nonoss on b/c it works now. :)
>>>
>>>
>>> On Mon, Aug 19, 2013 at 2:44 PM, Chip Childers
> > wrote:
>>>
 On Mon, Aug 19, 2013 at 02:33:33PM -0600, Mike Tutkowski wrote:
 > Looks like we have serious issues as of today in 4.2 (I've noticed
 > DevCloud2 not working and VMware support is broken) (aside from
plenty
 of
 > blocker defects still to be completed).
 >
 > When do we start talking about how the 4.2 RC build is not going to
 happen
 > until the codebase calms down a bit? I have serious doubts that 4.2
is
 > ready this week.
 >
 > Thoughts?

 Agreed - It seems that this first RC might be a bit premature.

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

Re: CloudStack 4.2 Quality Question

[Mike Tutkowski]

I think we need some kind of process in place to monitor the number of
critical and blocker defects over the course of the release and make sure
they're tapering off as we approach a RC build.

My main comment about this release (this is the first CS release that I've
participated in) is that I've never seen 150 bugs get fixed in the final
week.

At any of the commercial companies I've worked at over the past 15 years
(SolidFire, HP, LeftHand Networks, Agilent Technologies, Accenture),
checking in more than a small handful of defects at the "last minute" would
not be likely to happen. If we would absolutely need to do this, the
release would have to be pushed out so that we could regression test it
properly.

The main point is that we cannot compromise CloudStack's quality just to
meet a release deadline. I'm guessing people agree with that.


On Mon, Aug 19, 2013 at 2:49 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> "it is" meaning "premature"
>
>
> On Mon, Aug 19, 2013 at 2:49 PM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
>> I still believe it is, but the VMware "problem" was my fault - I must not
>> have had nonoss on b/c it works now. :)
>>
>>
>> On Mon, Aug 19, 2013 at 2:44 PM, Chip Childers > > wrote:
>>
>>> On Mon, Aug 19, 2013 at 02:33:33PM -0600, Mike Tutkowski wrote:
>>> > Looks like we have serious issues as of today in 4.2 (I've noticed
>>> > DevCloud2 not working and VMware support is broken) (aside from plenty
>>> of
>>> > blocker defects still to be completed).
>>> >
>>> > When do we start talking about how the 4.2 RC build is not going to
>>> happen
>>> > until the codebase calms down a bit? I have serious doubts that 4.2 is
>>> > ready this week.
>>> >
>>> > Thoughts?
>>>
>>> Agreed - It seems that this first RC might be a bit premature.
>>>
>>
>>
>>
>> --
>> *Mike Tutkowski*
>>  *Senior CloudStack Developer, SolidFire Inc.*
>> e: mike.tutkow...@solidfire.com
>> o: 303.746.7302
>> Advancing the way the world uses the 
>> cloud
>> *™*
>>
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the 
> cloud
> *™*
>



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

Re: VMware support broken in 4.2

[Mike Tutkowski]

Yeah, Kelven - thanks :)

Just sent an e-mail out about that.


On Mon, Aug 19, 2013 at 2:49 PM, Kelven Yang  wrote:

> It looks like you forgot to turn on nonoss and the API was not included in
> the package because of that.
>
> Kelven
>
> On 8/19/13 1:45 PM, "Mike Tutkowski"  wrote:
>
> >I was just about to. I then recompiled a moment ago and it works. Not sure
> >what I did. Maybe my first compile didn't turn on nonoss.
> >
> >
> >On Mon, Aug 19, 2013 at 2:40 PM, Sudha Ponnaganti <
> >sudha.ponnaga...@citrix.com> wrote:
> >
> >> Last blocker was
> >>https://issues.apache.org/jira/browse/CLOUDSTACK-4403and got resolved
> >>this morning
> >>
> >> Can you pl log a defect for this one?
> >>
> >> -Original Message-
> >> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> >> Sent: Monday, August 19, 2013 1:27 PM
> >> To: dev@cloudstack.apache.org
> >> Subject: VMware support broken in 4.2
> >>
> >> Hi,
> >>
> >> I can't seem to add a VMware datacenter to a zone in the latest from
> >>4.2:
> >>
> >> WARN  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
> >> command: listVmwareDcs
> >> INFO  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
> >> command: listVmwareDcs
> >> WARN  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
> >> command: addVmwareDc
> >> INFO  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
> >> command: addVmwareDc
> >> WARN  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
> >> command: listVmwareDcs
> >> INFO  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
> >> command: listVmwareDcs
> >> WARN  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
> >> command: addVmwareDc
> >> INFO  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
> >> command: addVmwareDc
> >>
> >> Is this a known issue?
> >>
> >> Thanks
> >>
> >> --
> >> *Mike Tutkowski*
> >> *Senior CloudStack Developer, SolidFire Inc.*
> >> e: mike.tutkow...@solidfire.com
> >> o: 303.746.7302
> >> Advancing the way the world uses the
> >> cloud
> >> *(tm)*
> >>
> >
> >
> >
> >--
> >*Mike Tutkowski*
> >*Senior CloudStack Developer, SolidFire Inc.*
> >e: mike.tutkow...@solidfire.com
> >o: 303.746.7302
> >Advancing the way the world uses the
> >cloud
> >* *
>
>


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

Re: CloudStack 4.2 Quality Question

[Mike Tutkowski]

"it is" meaning "premature"


On Mon, Aug 19, 2013 at 2:49 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> I still believe it is, but the VMware "problem" was my fault - I must not
> have had nonoss on b/c it works now. :)
>
>
> On Mon, Aug 19, 2013 at 2:44 PM, Chip Childers 
> wrote:
>
>> On Mon, Aug 19, 2013 at 02:33:33PM -0600, Mike Tutkowski wrote:
>> > Looks like we have serious issues as of today in 4.2 (I've noticed
>> > DevCloud2 not working and VMware support is broken) (aside from plenty
>> of
>> > blocker defects still to be completed).
>> >
>> > When do we start talking about how the 4.2 RC build is not going to
>> happen
>> > until the codebase calms down a bit? I have serious doubts that 4.2 is
>> > ready this week.
>> >
>> > Thoughts?
>>
>> Agreed - It seems that this first RC might be a bit premature.
>>
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the 
> cloud
> *™*
>



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

Re: VMware support broken in 4.2

[Kelven Yang]

It looks like you forgot to turn on nonoss and the API was not included in
the package because of that.

Kelven

On 8/19/13 1:45 PM, "Mike Tutkowski"  wrote:

>I was just about to. I then recompiled a moment ago and it works. Not sure
>what I did. Maybe my first compile didn't turn on nonoss.
>
>
>On Mon, Aug 19, 2013 at 2:40 PM, Sudha Ponnaganti <
>sudha.ponnaga...@citrix.com> wrote:
>
>> Last blocker was
>>https://issues.apache.org/jira/browse/CLOUDSTACK-4403and got resolved
>>this morning
>>
>> Can you pl log a defect for this one?
>>
>> -Original Message-
>> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>> Sent: Monday, August 19, 2013 1:27 PM
>> To: dev@cloudstack.apache.org
>> Subject: VMware support broken in 4.2
>>
>> Hi,
>>
>> I can't seem to add a VMware datacenter to a zone in the latest from
>>4.2:
>>
>> WARN  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
>> command: listVmwareDcs
>> INFO  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
>> command: listVmwareDcs
>> WARN  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
>> command: addVmwareDc
>> INFO  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
>> command: addVmwareDc
>> WARN  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
>> command: listVmwareDcs
>> INFO  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
>> command: listVmwareDcs
>> WARN  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
>> command: addVmwareDc
>> INFO  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
>> command: addVmwareDc
>>
>> Is this a known issue?
>>
>> Thanks
>>
>> --
>> *Mike Tutkowski*
>> *Senior CloudStack Developer, SolidFire Inc.*
>> e: mike.tutkow...@solidfire.com
>> o: 303.746.7302
>> Advancing the way the world uses the
>> cloud
>> *(tm)*
>>
>
>
>
>-- 
>*Mike Tutkowski*
>*Senior CloudStack Developer, SolidFire Inc.*
>e: mike.tutkow...@solidfire.com
>o: 303.746.7302
>Advancing the way the world uses the
>cloud
>**

Re: CloudStack 4.2 Quality Question

[Mike Tutkowski]

I still believe it is, but the VMware "problem" was my fault - I must not
have had nonoss on b/c it works now. :)


On Mon, Aug 19, 2013 at 2:44 PM, Chip Childers wrote:

> On Mon, Aug 19, 2013 at 02:33:33PM -0600, Mike Tutkowski wrote:
> > Looks like we have serious issues as of today in 4.2 (I've noticed
> > DevCloud2 not working and VMware support is broken) (aside from plenty of
> > blocker defects still to be completed).
> >
> > When do we start talking about how the 4.2 RC build is not going to
> happen
> > until the codebase calms down a bit? I have serious doubts that 4.2 is
> > ready this week.
> >
> > Thoughts?
>
> Agreed - It seems that this first RC might be a bit premature.
>



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

Re: CloudStack 4.2 Quality Question

[Chip Childers]

On Mon, Aug 19, 2013 at 02:33:33PM -0600, Mike Tutkowski wrote:
> Looks like we have serious issues as of today in 4.2 (I've noticed
> DevCloud2 not working and VMware support is broken) (aside from plenty of
> blocker defects still to be completed).
> 
> When do we start talking about how the 4.2 RC build is not going to happen
> until the codebase calms down a bit? I have serious doubts that 4.2 is
> ready this week.
> 
> Thoughts?

Agreed - It seems that this first RC might be a bit premature.

Re: VMware support broken in 4.2

[Mike Tutkowski]

I was just about to. I then recompiled a moment ago and it works. Not sure
what I did. Maybe my first compile didn't turn on nonoss.


On Mon, Aug 19, 2013 at 2:40 PM, Sudha Ponnaganti <
sudha.ponnaga...@citrix.com> wrote:

> Last blocker was https://issues.apache.org/jira/browse/CLOUDSTACK-4403and got 
> resolved this morning
>
> Can you pl log a defect for this one?
>
> -Original Message-
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: Monday, August 19, 2013 1:27 PM
> To: dev@cloudstack.apache.org
> Subject: VMware support broken in 4.2
>
> Hi,
>
> I can't seem to add a VMware datacenter to a zone in the latest from 4.2:
>
> WARN  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
> command: listVmwareDcs
> INFO  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
> command: listVmwareDcs
> WARN  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
> command: addVmwareDc
> INFO  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
> command: addVmwareDc
> WARN  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
> command: listVmwareDcs
> INFO  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
> command: listVmwareDcs
> WARN  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
> command: addVmwareDc
> INFO  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
> command: addVmwareDc
>
> Is this a known issue?
>
> Thanks
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud
> *(tm)*
>



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

Fwd: Call for Participation: Gluster Community Days

[John Mark Walker]

This is to invite you to participate in upcoming Gluster Community Day events. 
We would love to have more content on Apache CloudStack storage interfaces 
and/or deploying CloudStack with GlusterFS. 

If you have ideas for topics, please send them to cfp (at) gluster.org.

Thanks!
John Mark Walker
Gluster Community Leader


- Forwarded Message -
From: "John Mark Walker" 
To: annou...@gluster.org
Sent: Monday, August 19, 2013 4:36:54 PM
Subject: [Gluster-users] Call for Participation: Gluster Community Days

If you saw this blog post - 
http://www.gluster.org/2013/08/gluster-world-tour-coming-to-a-city-near-you/ - 
then you know we are planning several upcoming Gluster Community Days:


August 27 – San Francisco – Rackspace has generously agreed to host this 
Community Day
 - http://www.meetup.com/GlusterFS-Silicon-Valley/events/124722542/

September 4 – Stockholm, Sweden – Our first event in the nordic region!
 - http://red.ht/11JazeE

September 10 – London, England – Continuing the Northern road show
 - http://www.meetup.com/Gluster/London-GB/986272/

September 19 – New Orleans, Louisiana – Co-located with LinuxCon/CloudOpen 
North America
 - http://events.linuxfoundation.org/events/linuxcon-north-america/

October 24 – Edinburgh, Scotland – Co-located with LinuxCon/CloudOpen Europe
 - http://events.linuxfoundation.org/events/linuxcon-europe

...with more on the way later this year and next year.

This email is to invite you to participate, either by attending or perhaps 
speaking. Most of the agendas for these community days have been filled, but 
there are still some speaking slots available. If you wish us to consider your 
inclusion in the community day agendas, please send a brief note to cfp (at) 
gluster.org, enclosing a title for your proposed talk, brief description of its 
contents, and a brief bio that includes your past speaking appearances. 

Look forward to seeing you there!

-John Mark

___
Announce mailing list
annou...@gluster.org
http://supercolony.gluster.org/mailman/listinfo/announce
___
Gluster-users mailing list
gluster-us...@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-users

RE: VMware support broken in 4.2

[Sudha Ponnaganti]

Last blocker was https://issues.apache.org/jira/browse/CLOUDSTACK-4403 and got 
resolved this morning

Can you pl log a defect for this one?

-Original Message-
From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com] 
Sent: Monday, August 19, 2013 1:27 PM
To: dev@cloudstack.apache.org
Subject: VMware support broken in 4.2

Hi,

I can't seem to add a VMware datacenter to a zone in the latest from 4.2:

WARN  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
command: listVmwareDcs
INFO  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
command: listVmwareDcs
WARN  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
command: addVmwareDc
INFO  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
command: addVmwareDc
WARN  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
command: listVmwareDcs
INFO  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
command: listVmwareDcs
WARN  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
command: addVmwareDc
INFO  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
command: addVmwareDc

Is this a known issue?

Thanks

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

Re: CloudStack 4.2 Quality Question

[Mike Tutkowski]

Looks like we have serious issues as of today in 4.2 (I've noticed
DevCloud2 not working and VMware support is broken) (aside from plenty of
blocker defects still to be completed).

When do we start talking about how the 4.2 RC build is not going to happen
until the codebase calms down a bit? I have serious doubts that 4.2 is
ready this week.

Thoughts?


On Thu, Aug 15, 2013 at 3:39 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> Good idea, Daan.
>
>
> On Thu, Aug 15, 2013 at 2:17 PM, Daan Hoogland wrote:
>
>> Hugo has a local jenkins that runs as code gets checked in at apache,
>> You could have your SolidFire SAN base install be updated by a trigger
>> on commits in the central git at apache's, and then run your
>> regression tests on it.
>>
>> Hope that helps,
>> Daan
>>
>> On Thu, Aug 15, 2013 at 9:58 PM, Mike Tutkowski
>>  wrote:
>> > I plan to write automated system tests, but I don't think there's any
>> way
>> > for me to check them in and get use out of them because they require a
>> > SolidFire SAN. In other words, I guess I will just have to keep them
>> local
>> > (as in just something I run).
>> >
>> > So far, I have manual regression tests I run and have noted two
>> breakages
>> > in my feature as code has been checked in this week.
>> >
>> > This just makes me a bit nervous. :)
>> >
>> >
>> > On Thu, Aug 15, 2013 at 1:49 PM, Daan Hoogland > >wrote:
>> >
>> >> H Mike,
>> >>
>> >> Make sure you write plenty of unit tests for whatever methods you need
>> >> for the features you are implementing. You can not exaggerate for a
>> >> while. Coverage is behind quite a bit and I am not a betting man, so I
>> >> bet there is going to be a 4.2.1.
>> >>
>> >> In short: I share your concern.
>> >> Daan
>> >>
>> >> On Thu, Aug 15, 2013 at 9:28 PM, Sudha Ponnaganti
>> >>  wrote:
>> >> > Mike,
>> >> >
>> >> > I have similar concern as well.
>> >> >
>> >> > We have regression and BVT tests running daily on 4.2 branch locally
>> >> besides manual validation of the defects and impacted areas. Even
>> though we
>> >> would not be able to catch all the issues, several regressions were
>> caught
>> >>  and you can see the defects by using [Automation] in subject line for
>> 4.2.
>> >>  This type of turnaround is quite uncommon for releases but 4.2 has too
>> >> many features and some of the feature implementation has been  done
>> very
>> >> late which is causing high inflow. All fixes should be coming in for
>> >> Critical and blocker defects only at this point.
>> >> >
>> >> > Thanks
>> >> > /Sudha
>> >> >
>> >> > -Original Message-
>> >> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>> >> > Sent: Thursday, August 15, 2013 12:02 PM
>> >> > To: dev@cloudstack.apache.org
>> >> > Subject: CloudStack 4.2 Quality Question
>> >> >
>> >> > Hi everyone,
>> >> >
>> >> > I've only been working on CS for about 8 months now, so I don't have
>> a
>> >> lot of experience with the way releases go.
>> >> >
>> >> > My question is this: I've noticed over 100 commits to 4.2 since
>> Monday
>> >> (one week from a potential release of the product). Is this normal?
>> Unless
>> >> we have a super great suite of automated regression tests, it makes me
>> >> concerned about the potential quality of the product.
>> >> >
>> >> > Any thoughts on this?
>> >> >
>> >> > Thanks!
>> >> >
>> >> > --
>> >> > *Mike Tutkowski*
>> >> > *Senior CloudStack Developer, SolidFire Inc.*
>> >> > e: mike.tutkow...@solidfire.com
>> >> > o: 303.746.7302
>> >> > Advancing the way the world uses the
>> >> > cloud
>> >> > *(tm)*
>> >>
>> >
>> >
>> >
>> > --
>> > *Mike Tutkowski*
>> > *Senior CloudStack Developer, SolidFire Inc.*
>> > e: mike.tutkow...@solidfire.com
>> > o: 303.746.7302
>> > Advancing the way the world uses the
>> > cloud
>> > *™*
>>
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the 
> cloud
> *™*
>



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

VMware support broken in 4.2

[Mike Tutkowski]

Hi,

I can't seem to add a VMware datacenter to a zone in the latest from 4.2:

WARN  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
command: listVmwareDcs
INFO  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
command: listVmwareDcs
WARN  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
command: addVmwareDc
INFO  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
command: addVmwareDc
WARN  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
command: listVmwareDcs
INFO  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
command: listVmwareDcs
WARN  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
command: addVmwareDc
INFO  [cloud.api.ApiServer] (2097719126@qtp-1366270629-15:) Unknown API
command: addVmwareDc

Is this a known issue?

Thanks

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

Re: SSVM problem

[Chiradeep Vittal]

It looks like the scripts/java binaries have not been copied into the SSVM?
See this thread http://markmail.org/thread/niu2qwsdydkuh2fe for how it is
supposed to work (response from Alex)

On 8/19/13 12:32 PM, "SuichII, Christopher"  wrote:

>I am having an issue getting my SSVM up and running. After pulling,
>rebuilding and seeding with the newest system vm template, I was unable
>to register an ISO, so when I logged in to the SSVM to run ssvm-check.sh,
>I found that the script was not present on my ssvm.
>
>So my first question is, was this script removed, or is something wrong
>with the ssvm?
>
>If I copy the script over manually and run, this is what I get:
>
>root@s-1-VM:~# ./ssvm-check.sh
>
>First DNS server is  8.8.8.8
>PING 8.8.8.8 (8.8.8.8): 56 data bytes
>64 bytes from 8.8.8.8: icmp_seq=0 ttl=40 time=26.465 ms
>64 bytes from 8.8.8.8: icmp_seq=1 ttl=40 time=26.172 ms
>--- 8.8.8.8 ping statistics ---
>2 packets transmitted, 2 packets received, 0% packet loss
>round-trip min/avg/max/stddev = 26.172/26.319/26.465/0.147 ms
>Good: Can ping DNS server
>
>Good: DNS resolves download.cloud.com
>
>NFS is currently mounted
>
>Management server is 10.63.172.148. Checking connectivity.
>Good: Can connect to management server port 8250
>
>ERROR: Java process not running.  Try restarting the SSVM.
>
>And yes, I tried restarting the ssvm =)
>
>FWIW, if I run a df, this is the output:
>
>root@s-1-VM:~# df
>Filesystem 1K-blocks   Used
>Available Use% Mounted on
>rootfs282599 120171
> 147836  45% /
>udev   10240  0
>  10240   0% /dev
>tmpfs  25204140
>  25064   1% /run
>/dev/disk/by-uuid/5129b148-8ca5-48fb-9f62-38861be97287282599 120171
> 147836  45% /
>tmpfs   5120  0
>   5120   0% /run/lock
>tmpfs  80300  0
>  80300   0% /run/shm
>/dev/xvda1 29745  17519
>  10690  63% /boot
>/dev/xvda6 53544   4978
>  45802  10% /home
>/dev/xvda8376807  10388
> 346963   3% /opt
>/dev/xvda1048585   4891
>  41186  11% /tmp
>/dev/xvda7623872 623872
>  0 100% /usr
>/dev/xvda9424420 108890
> 293617  28% /var
>
>Should /usr be at 100% usage?
>
>I don't see anything in the management server logs or ssvm that would be
>of any help.
>
>Thanks,
>Chris

SSVM problem

[SuichII, Christopher]

I am having an issue getting my SSVM up and running. After pulling, rebuilding 
and seeding with the newest system vm template, I was unable to register an 
ISO, so when I logged in to the SSVM to run ssvm-check.sh, I found that the 
script was not present on my ssvm.

So my first question is, was this script removed, or is something wrong with 
the ssvm?

If I copy the script over manually and run, this is what I get:

root@s-1-VM:~# ./ssvm-check.sh 

First DNS server is  8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=40 time=26.465 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=40 time=26.172 ms
--- 8.8.8.8 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 26.172/26.319/26.465/0.147 ms
Good: Can ping DNS server

Good: DNS resolves download.cloud.com

NFS is currently mounted

Management server is 10.63.172.148. Checking connectivity.
Good: Can connect to management server port 8250

ERROR: Java process not running.  Try restarting the SSVM.

And yes, I tried restarting the ssvm =)

FWIW, if I run a df, this is the output:

root@s-1-VM:~# df
Filesystem 1K-blocks   Used 
Available Use% Mounted on
rootfs282599 120171
147836  45% /
udev   10240  0 
10240   0% /dev
tmpfs  25204140 
25064   1% /run
/dev/disk/by-uuid/5129b148-8ca5-48fb-9f62-38861be97287282599 120171
147836  45% /
tmpfs   5120  0  
5120   0% /run/lock
tmpfs  80300  0 
80300   0% /run/shm
/dev/xvda1 29745  17519 
10690  63% /boot
/dev/xvda6 53544   4978 
45802  10% /home
/dev/xvda8376807  10388
346963   3% /opt
/dev/xvda1048585   4891 
41186  11% /tmp
/dev/xvda7623872 623872 
0 100% /usr
/dev/xvda9424420 108890
293617  28% /var

Should /usr be at 100% usage?

I don't see anything in the management server logs or ssvm that would be of any 
help.

Thanks,
Chris

DevCloud2 not working with 4.2

[Mike Tutkowski]

Hi everyone,

I've been trying to get DevCloud2 running with the most recent from 4.2,
but keep getting tons of exceptions (some of which are below).

Is this a known issue?

With the 4.2 RC build slated to happen soon, I wasn't expecting any problem
getting 4.2 to run.

Thanks!

com.cloud.utils.exception.CloudRuntimeException: callHostPlugin failed for
cmd: getVhdParent with args snapshotUuid:
9482d1aa-6dc2-413e-80df-0a4610307e50, isISCSI: false, primaryStorageSRUuid:
9f3f9262-3f77-09cc-2df7-0d8475676260,  due to There was a failure
communicating with the plugin.
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.callHostPlugin(CitrixResourceBase.java:4188)
at
com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.getVhdParent(XenServerStorageProcessor.java:823)
at
com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.copyTemplateToPrimaryStorage(XenServerStorageProcessor.java:868)
at
com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:70)
at
com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:49)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:617)
at
com.cloud.hypervisor.xen.resource.XcpOssResource.executeRequest(XcpOssResource.java:143)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:680)
INFO  [storage.volume.VolumeServiceImpl] (consoleproxy-1:) releasing lock
for VMTemplateStoragePool 1
WARN  [utils.db.Merovingian2] (consoleproxy-1:) Was unable to find lock for
the key template_spool_ref1 and thread id 85262930
INFO  [cloud.vm.VirtualMachineManagerImpl] (consoleproxy-1:) Unable to
contact resource.
com.cloud.exception.StorageUnavailableException: Resource [StoragePool:1]
is unreachable: Unable to create Vol[2|vm=2|ROOT]:Catch Exception
com.cloud.utils.exception.CloudRuntimeException for template +  due to
com.cloud.utils.exception.CloudRuntimeException: callHostPlugin failed for
cmd: getVhdParent with args snapshotUuid:
9482d1aa-6dc2-413e-80df-0a4610307e50, isISCSI: false, primaryStorageSRUuid:
9f3f9262-3f77-09cc-2df7-0d8475676260,  due to There was a failure
communicating with the plugin.
at
com.cloud.storage.VolumeManagerImpl.recreateVolume(VolumeManagerImpl.java:2534)
at com.cloud.storage.VolumeManagerImpl.prepare(VolumeManagerImpl.java:2582)
at
com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:886)
at
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:576)
at
com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:569)
at
com.cloud.consoleproxy.ConsoleProxyManagerImpl.startProxy(ConsoleProxyManagerImpl.java:556)
at
com.cloud.consoleproxy.ConsoleProxyManagerImpl.allocCapacity(ConsoleProxyManagerImpl.java:928)
at
com.cloud.consoleproxy.ConsoleProxyManagerImpl.expandPool(ConsoleProxyManagerImpl.java:1672)
at
com.cloud.consoleproxy.ConsoleProxyManagerImpl.expandPool(ConsoleProxyManagerImpl.java:157)
at com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:111)
at com.cloud.vm.SystemVmLoadScanner.access$100(SystemVmLoadScanner.java:33)
at com.cloud.vm.SystemVmLoadScanner$1.reallyRun(SystemVmLoadScanner.java:81)
at com.cloud.vm.SystemVmLoadScanner$1.run(SystemVmLoadScanner.java:72)
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:895)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:680)
INFO  [xen.resource.CitrixResourceBase] (DirectAgent-12:) VM does not exist
on XenServer9d4c9db8-32f7-25c3-0435-eab4bf3adcea
ERROR [network.element.SspElement] (consoleproxy-1:) ReservationContext was
null

Re: Whats involved in adding an extra hypervisor

[Chiradeep Vittal]

On XenServer (from Citrix), there is no JVM, not sure if you can install
it even after the open sourcing.


On 8/19/13 10:38 AM, "Sebastien Goasguen"  wrote:

>
>On Aug 19, 2013, at 1:25 PM, Chiradeep Vittal
> wrote:
>
>> I thought libvirt supports xen as well? Why "modify libvirt calls to
>>talk
>> to xl" ?
>> 
>
>what I meant is that I believe our current Xen support makes use of xapi
>not libvrit.
>
>So I would think we could "copy" the KVM agent and modify the "libvirt
>calls" -not libvrt itself- to use the xl tool.
>
>That said I have not looked at the code for our Xen support.
>
>
>> On 8/19/13 6:40 AM, "Sebastien Goasguen"  wrote:
>> 
>>> Kind of on that same vein:
>>> 
>>> Anyone interested in modifying the KVM agent to support "pure" Xen
>>> without xapi.
>>> 
>>> I think it might be possible to just use the kvm agent and modify the
>>> libvirt calls to talk to xl , that way there would be no need for
>>>xapi...
>>> 
>>> Which if I am not mistaken would give us Xen on ARM support instantly
>>>in
>>> CloudStack
>>> 
>>> Any takers ? or anyone telling me I got this completely wrong ?
>>> 
>>> -Sebastien
>>> 
>>> On Aug 16, 2013, at 2:42 AM, Likitha Shetty 
>>> wrote:
>>> 
 Ian, with AWS it¹s the other way around. The package allows us to spin
 up VMs in CS using AWS EC2 API's.
 
 -Likitha
 
> -Original Message-
> From: Ian Duffy [mailto:i...@ianduffy.ie]
> Sent: Friday, August 16, 2013 12:07 PM
> To: CloudStack Dev
> Subject: Re: Whats involved in adding an extra hypervisor
> 
> Hi Donal and Chiradeep,
> 
> Thanks for your comments. It was an interesting read.
> 
> I might be missing something here but I will ask anyways. If I
> understand
> correctly, at current with awsapi we are able to submit our aws api
> credentials
> to Cloudstack and spin up VMs on aws correct? Is there a reason the
> communication with aws could not be provided like a standard
> hypervisor? what
> is the reasoning behind keeping it as an almost separate package?
> 
> The reason I'm asking is because I'm wanting to do something
> Cloudstack based
> for a college project next year. However there is a hard 1 month
> deadline. I was
> interested to see could a base(or something of demoable quality) for
> supporting
> Google Compute Engine be completed in such a short deadline.
> 
> On 15 August 2013 09:29, Donal Lafferty 
> wrote:
>> Definitely possible to add new Hypervisor types, if that's what
>> you're asking.
>> 
>> How easy it is depends on how much existing CloudStack
>>infrastructure
>> you
> can exploit.  Let me out line the task with the help of some planning
> questions:
>> 
>> 1. What will be your agent model?  Will you talk directly to the
>> hypervisor
> (direct connect agent), or will you install a remote agent on the
> hypervisor
> (connected agent).  This comes down to whether the hypervisor exposes
> a high
> level API remotely.
>> 
>> 2. What will be your secondary storage model?  Secondary storage
>> provides
> low IOPS storage accessible to all hypervisors in the zone.  Thus, we
> store the
> templates in secondary storage.  IIRC, CloudStack supports NFS, S3
>and
> Swift.
> Does one of these options suit your data centre, or do you need to
> expand the
> list?  Will your agent be able to download disk images in secondary
> storage to
> the hypervisor?
>> 
>> 3. What will be your primary storage model?  Typically, primary
>> storage is
> high IOPS storage specific to a hypervisor or cluster of hypervisors.
> The easiest
> to setup is local storage, which can be a hard disk or storage you
> mount
> manually on the hypervisor.  Alternatively, you may want to automate
> mounting
> storage on the hypervisor.
>> 
>> 4.  What will be your system VM model?  System VMs offload the
>> following
> functionality from the management server:  VM console access,
> networking
> services, and secondary storage (upload) service.  You could skip
> system VMs
> and run these services in the management server's host using
> QuickCloud.  You
> could run system VMs on an existing hypervisor type, or you could add
> a new
> system VM type for your hypervisor.  Keep in mind that QuickCloud
> can't run
> your networking services.  Also, if you want to create a new system
>VM
> type, you
> have to come up with VM image.
>> 
>> The tricky bits:
>> 
>> 5. What language will your agent use?  A direct connect agent sits
>>in
>> the
> CloudStack process, so it is written in Java.  Alternatively, there
>is
> infrastructure
> for a Java-based remote agent, which handles all your communications.
> If you
> need a non-Java remote agen

[DISCUSS] Adding RAT checks to the default build

[Chip Childers]

Hey all,

Apache RAT 0.10 has been released, improving the speed for a RAT check
quite a bit.  I've gone ahead and changed the builds.a.o jobs to use
version 0.10.

I'd like to propose that we add the plugin to our default build, now
that it's faster.  You can see the speed by running:

mvn --projects='org.apache.cloudstack:cloudstack'
org.apache.rat:apache-rat-plugin:0.10:check

And can compare with 0.8 using:

mvn --projects='org.apache.cloudstack:cloudstack'
org.apache.rat:apache-rat-plugin:0.8:check


This would help us ensure that we don't have licensing issues lingering
out on CI servers with little attention.

-chip

Re: [DOC] cloudstack.apache.org Search

[Marty Sweet]

Ah forgot that!  Thanks!


On Mon, Aug 19, 2013 at 6:39 PM, Sebastien Goasguen wrote:

>
> On Aug 19, 2013, at 1:24 PM, Marty Sweet  wrote:
>
> > Hi Sebastien,
> >
> > It still seems to be 'searching' localhost for me.
> >
>
> did you clean your cache ?
>
>
> > Thanks,
> > Marty
> >
> >
> > On Mon, Aug 19, 2013 at 2:26 PM, Sebastien Goasguen  >wrote:
> >
> >>
> >> On Aug 18, 2013, at 2:22 PM, Marty Sweet  wrote:
> >>
> >>> Hi Guys,
> >>>
> >>> Not sure if your aware but the doc search feature is broken on
> >>> http://cloudstack.apache.org/docs/en-US/
> >>>
> >>> The search feature takes users to the following URL (searched
> templates):
> >>>
> >>
> https://www.google.com/search?q=templates&sitesearch=http%3A%2F%2Flocalhost%2F
> >>>
> >>> The domain is being specified as localhost, it should be
> >>> http://cloudstack.apache.org/docs
> >>>
> >>
> https://www.google.com/search?q=templates&sitesearch=http%3A%2F%2Flocalhost%2F#bav=on.2,or.r_cp.r_qf.&fp=fd636efafc1f2c54&q=templates+site:http%3A%2F%2Fcloudstack.apache.org%2Fdocs&safe=off
> >>>
> >>> I think many new users find this frustrating when trying to look
> through
> >>> documentation.
> >>>
> >>> Regards,
> >>> Marty
> >>
> >> Marty, thanks for reporting this.
> >>
> >> I fixed it (at least in english). Can you check that it works for you
> now ?
> >>
> >> The docs are built automatically with publican, we will have to keep an
> >> eye out for 4.2 to make sure this does not get broken.
> >>
> >> -Sebastien
>
>

Re: Review Request 13643: Unplug the nic when there are no ips set on the interface

[anthony xu]

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

Ship it!


Ship It!

- anthony xu


On Aug. 19, 2013, 10:58 a.m., Jayapal Reddy wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/13643/
> ---
> 
> (Updated Aug. 19, 2013, 10:58 a.m.)
> 
> 
> Review request for cloudstack, anthony xu, Abhinandan Prateek, and Murali 
> Reddy.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Unplugging the public nic on the VR when there are no ips set on the 
> interface.
> This issue of not reusing the public nic is present in the xen and mvm.
> 
> For vmware the nic got reused.
> 
> 
> Diffs
> -
> 
>   
> core/src/com/cloud/agent/resource/virtualnetwork/VirtualRoutingResource.java 
> 1fb86e0 
>   patches/systemvm/debian/config/opt/cloud/bin/ipassoc.sh ae2d7e4 
>   
> plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtComputingResource.java
>  9104504 
>   
> plugins/hypervisors/xen/src/com/cloud/hypervisor/xen/resource/CitrixResourceBase.java
>  338e741 
> 
> Diff: https://reviews.apache.org/r/13643/diff/
> 
> 
> Testing
> ---
> 
> Tested in xen and kvm.
> 
> 
> Thanks,
> 
> Jayapal Reddy
> 
>

Re: Whats involved in adding an extra hypervisor

[Sebastien Goasguen]

On Aug 19, 2013, at 1:25 PM, Chiradeep Vittal  
wrote:

> I thought libvirt supports xen as well? Why "modify libvirt calls to talk
> to xl" ?
> 

what I meant is that I believe our current Xen support makes use of xapi not 
libvrit.

So I would think we could "copy" the KVM agent and modify the "libvirt calls" 
-not libvrt itself- to use the xl tool.

That said I have not looked at the code for our Xen support.


> On 8/19/13 6:40 AM, "Sebastien Goasguen"  wrote:
> 
>> Kind of on that same vein:
>> 
>> Anyone interested in modifying the KVM agent to support "pure" Xen
>> without xapi.
>> 
>> I think it might be possible to just use the kvm agent and modify the
>> libvirt calls to talk to xl , that way there would be no need for xapi...
>> 
>> Which if I am not mistaken would give us Xen on ARM support instantly in
>> CloudStack
>> 
>> Any takers ? or anyone telling me I got this completely wrong ?
>> 
>> -Sebastien
>> 
>> On Aug 16, 2013, at 2:42 AM, Likitha Shetty 
>> wrote:
>> 
>>> Ian, with AWS it¹s the other way around. The package allows us to spin
>>> up VMs in CS using AWS EC2 API's.
>>> 
>>> -Likitha
>>> 
 -Original Message-
 From: Ian Duffy [mailto:i...@ianduffy.ie]
 Sent: Friday, August 16, 2013 12:07 PM
 To: CloudStack Dev
 Subject: Re: Whats involved in adding an extra hypervisor
 
 Hi Donal and Chiradeep,
 
 Thanks for your comments. It was an interesting read.
 
 I might be missing something here but I will ask anyways. If I
 understand
 correctly, at current with awsapi we are able to submit our aws api
 credentials
 to Cloudstack and spin up VMs on aws correct? Is there a reason the
 communication with aws could not be provided like a standard
 hypervisor? what
 is the reasoning behind keeping it as an almost separate package?
 
 The reason I'm asking is because I'm wanting to do something
 Cloudstack based
 for a college project next year. However there is a hard 1 month
 deadline. I was
 interested to see could a base(or something of demoable quality) for
 supporting
 Google Compute Engine be completed in such a short deadline.
 
 On 15 August 2013 09:29, Donal Lafferty 
 wrote:
> Definitely possible to add new Hypervisor types, if that's what
> you're asking.
> 
> How easy it is depends on how much existing CloudStack infrastructure
> you
 can exploit.  Let me out line the task with the help of some planning
 questions:
> 
> 1. What will be your agent model?  Will you talk directly to the
> hypervisor
 (direct connect agent), or will you install a remote agent on the
 hypervisor
 (connected agent).  This comes down to whether the hypervisor exposes
 a high
 level API remotely.
> 
> 2. What will be your secondary storage model?  Secondary storage
> provides
 low IOPS storage accessible to all hypervisors in the zone.  Thus, we
 store the
 templates in secondary storage.  IIRC, CloudStack supports NFS, S3 and
 Swift.
 Does one of these options suit your data centre, or do you need to
 expand the
 list?  Will your agent be able to download disk images in secondary
 storage to
 the hypervisor?
> 
> 3. What will be your primary storage model?  Typically, primary
> storage is
 high IOPS storage specific to a hypervisor or cluster of hypervisors.
 The easiest
 to setup is local storage, which can be a hard disk or storage you
 mount
 manually on the hypervisor.  Alternatively, you may want to automate
 mounting
 storage on the hypervisor.
> 
> 4.  What will be your system VM model?  System VMs offload the
> following
 functionality from the management server:  VM console access,
 networking
 services, and secondary storage (upload) service.  You could skip
 system VMs
 and run these services in the management server's host using
 QuickCloud.  You
 could run system VMs on an existing hypervisor type, or you could add
 a new
 system VM type for your hypervisor.  Keep in mind that QuickCloud
 can't run
 your networking services.  Also, if you want to create a new system VM
 type, you
 have to come up with VM image.
> 
> The tricky bits:
> 
> 5. What language will your agent use?  A direct connect agent sits in
> the
 CloudStack process, so it is written in Java.  Alternatively, there is
 infrastructure
 for a Java-based remote agent, which handles all your communications.
 If you
 need a non-Java remote agent, you are better off sending the kernel
 commands
 over HTTP, which looks more like an RPC mechanism than REST.
> 
> 6. How will you know what instructions to implement?  You can look at
> an
 existing ServerResource class for a hypervisor to know what command
 types
 there are.  The relevan

Re: [DOC] cloudstack.apache.org Search

[Sebastien Goasguen]

On Aug 19, 2013, at 1:24 PM, Marty Sweet  wrote:

> Hi Sebastien,
> 
> It still seems to be 'searching' localhost for me.
> 

did you clean your cache ?


> Thanks,
> Marty
> 
> 
> On Mon, Aug 19, 2013 at 2:26 PM, Sebastien Goasguen wrote:
> 
>> 
>> On Aug 18, 2013, at 2:22 PM, Marty Sweet  wrote:
>> 
>>> Hi Guys,
>>> 
>>> Not sure if your aware but the doc search feature is broken on
>>> http://cloudstack.apache.org/docs/en-US/
>>> 
>>> The search feature takes users to the following URL (searched templates):
>>> 
>> https://www.google.com/search?q=templates&sitesearch=http%3A%2F%2Flocalhost%2F
>>> 
>>> The domain is being specified as localhost, it should be
>>> http://cloudstack.apache.org/docs
>>> 
>> https://www.google.com/search?q=templates&sitesearch=http%3A%2F%2Flocalhost%2F#bav=on.2,or.r_cp.r_qf.&fp=fd636efafc1f2c54&q=templates+site:http%3A%2F%2Fcloudstack.apache.org%2Fdocs&safe=off
>>> 
>>> I think many new users find this frustrating when trying to look through
>>> documentation.
>>> 
>>> Regards,
>>> Marty
>> 
>> Marty, thanks for reporting this.
>> 
>> I fixed it (at least in english). Can you check that it works for you now ?
>> 
>> The docs are built automatically with publican, we will have to keep an
>> eye out for 4.2 to make sure this does not get broken.
>> 
>> -Sebastien

Re: Whats involved in adding an extra hypervisor

[Chiradeep Vittal]

I thought libvirt supports xen as well? Why "modify libvirt calls to talk
to xl" ?

On 8/19/13 6:40 AM, "Sebastien Goasguen"  wrote:

>Kind of on that same vein:
>
>Anyone interested in modifying the KVM agent to support "pure" Xen
>without xapi.
>
>I think it might be possible to just use the kvm agent and modify the
>libvirt calls to talk to xl , that way there would be no need for xapi...
>
>Which if I am not mistaken would give us Xen on ARM support instantly in
>CloudStack
>
>Any takers ? or anyone telling me I got this completely wrong ?
>
>-Sebastien
>
>On Aug 16, 2013, at 2:42 AM, Likitha Shetty 
>wrote:
>
>> Ian, with AWS it¹s the other way around. The package allows us to spin
>>up VMs in CS using AWS EC2 API's.
>> 
>> -Likitha
>> 
>>> -Original Message-
>>> From: Ian Duffy [mailto:i...@ianduffy.ie]
>>> Sent: Friday, August 16, 2013 12:07 PM
>>> To: CloudStack Dev
>>> Subject: Re: Whats involved in adding an extra hypervisor
>>> 
>>> Hi Donal and Chiradeep,
>>> 
>>> Thanks for your comments. It was an interesting read.
>>> 
>>> I might be missing something here but I will ask anyways. If I
>>>understand
>>> correctly, at current with awsapi we are able to submit our aws api
>>>credentials
>>> to Cloudstack and spin up VMs on aws correct? Is there a reason the
>>> communication with aws could not be provided like a standard
>>>hypervisor? what
>>> is the reasoning behind keeping it as an almost separate package?
>>> 
>>> The reason I'm asking is because I'm wanting to do something
>>>Cloudstack based
>>> for a college project next year. However there is a hard 1 month
>>>deadline. I was
>>> interested to see could a base(or something of demoable quality) for
>>>supporting
>>> Google Compute Engine be completed in such a short deadline.
>>> 
>>> On 15 August 2013 09:29, Donal Lafferty 
>>>wrote:
 Definitely possible to add new Hypervisor types, if that's what
you're asking.
 
 How easy it is depends on how much existing CloudStack infrastructure
you
>>> can exploit.  Let me out line the task with the help of some planning
>>>questions:
 
 1. What will be your agent model?  Will you talk directly to the
hypervisor
>>> (direct connect agent), or will you install a remote agent on the
>>>hypervisor
>>> (connected agent).  This comes down to whether the hypervisor exposes
>>>a high
>>> level API remotely.
 
 2. What will be your secondary storage model?  Secondary storage
provides
>>> low IOPS storage accessible to all hypervisors in the zone.  Thus, we
>>>store the
>>> templates in secondary storage.  IIRC, CloudStack supports NFS, S3 and
>>>Swift.
>>> Does one of these options suit your data centre, or do you need to
>>>expand the
>>> list?  Will your agent be able to download disk images in secondary
>>>storage to
>>> the hypervisor?
 
 3. What will be your primary storage model?  Typically, primary
storage is
>>> high IOPS storage specific to a hypervisor or cluster of hypervisors.
>>>The easiest
>>> to setup is local storage, which can be a hard disk or storage you
>>>mount
>>> manually on the hypervisor.  Alternatively, you may want to automate
>>>mounting
>>> storage on the hypervisor.
 
 4.  What will be your system VM model?  System VMs offload the
following
>>> functionality from the management server:  VM console access,
>>>networking
>>> services, and secondary storage (upload) service.  You could skip
>>>system VMs
>>> and run these services in the management server's host using
>>>QuickCloud.  You
>>> could run system VMs on an existing hypervisor type, or you could add
>>>a new
>>> system VM type for your hypervisor.  Keep in mind that QuickCloud
>>>can't run
>>> your networking services.  Also, if you want to create a new system VM
>>>type, you
>>> have to come up with VM image.
 
 The tricky bits:
 
 5. What language will your agent use?  A direct connect agent sits in
the
>>> CloudStack process, so it is written in Java.  Alternatively, there is
>>>infrastructure
>>> for a Java-based remote agent, which handles all your communications.
>>>If you
>>> need a non-Java remote agent, you are better off sending the kernel
>>>commands
>>> over HTTP, which looks more like an RPC mechanism than REST.
 
 6. How will you know what instructions to implement?  You can look at
an
>>> existing ServerResource class for a hypervisor to know what command
>>>types
>>> there are.  The relevant pieces of data in each command can be found
>>>out from
>>> existing hypervisor implementations.  Alternatively, you can look at
>>>test logs,
>>> which contain the data from each command.  Eventually you'll want to
>>>try your
>>> plugin with CloudStack itself.
 
 Chiradeep's comments relate to #6 above.
 
 
> -Original Message-
> From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com]
> Sent: 15 August 2013 02:51
> To: dev@cloudstack.apache.org
> Subject: Re: 

Re: [DOC] cloudstack.apache.org Search

[Marty Sweet]

Hi Sebastien,

It still seems to be 'searching' localhost for me.

Thanks,
Marty


On Mon, Aug 19, 2013 at 2:26 PM, Sebastien Goasguen wrote:

>
> On Aug 18, 2013, at 2:22 PM, Marty Sweet  wrote:
>
> > Hi Guys,
> >
> > Not sure if your aware but the doc search feature is broken on
> > http://cloudstack.apache.org/docs/en-US/
> >
> > The search feature takes users to the following URL (searched templates):
> >
> https://www.google.com/search?q=templates&sitesearch=http%3A%2F%2Flocalhost%2F
> >
> > The domain is being specified as localhost, it should be
> > http://cloudstack.apache.org/docs
> >
> https://www.google.com/search?q=templates&sitesearch=http%3A%2F%2Flocalhost%2F#bav=on.2,or.r_cp.r_qf.&fp=fd636efafc1f2c54&q=templates+site:http%3A%2F%2Fcloudstack.apache.org%2Fdocs&safe=off
> >
> > I think many new users find this frustrating when trying to look through
> > documentation.
> >
> > Regards,
> > Marty
>
> Marty, thanks for reporting this.
>
> I fixed it (at least in english). Can you check that it works for you now ?
>
> The docs are built automatically with publican, we will have to keep an
> eye out for 4.2 to make sure this does not get broken.
>
> -Sebastien

RE: [Doc] nTier App is Ready for Review

[Radhika Puthiyetath]

Thanks Rajesh, Kishan, and Sowmya. I shall share the final docs once I finish 
fixing them.

-Original Message-
From: Rajesh Battala [mailto:rajesh.batt...@citrix.com] 
Sent: Monday, August 19, 2013 7:30 PM
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org; Chandan 
Purushothama; Kishan Kavala
Subject: RE: [Doc] nTier App is Ready for Review

I had gone through the doc. 
Whatever Sowmya had listed, apart from that looks good to me.

Thanks
Rajesh Battala

-Original Message-
From: Sowmya Krishnan [mailto:sowmya.krish...@citrix.com]
Sent: Monday, August 19, 2013 4:43 PM
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org; Chandan 
Purushothama; Kishan Kavala
Subject: RE: [Doc] nTier App is Ready for Review

Thanks Radhika.
Minor corrections under: 15.27.11.1.2. Creating a Network Offering for External 
LB

1. Please edit " To have internal LB support on VPC," to "To have external LB 
support on VPC,"
2. Under "Supported Services", choose Load Balancer Provider as Netscaler or 
VpcVirtualRouter 3. Load Balancer Type should be Public LB 4. LB Isolation 
should be Dedicated if Netscaler is being used as the external LB provider

Rest look good. Thanks.

> -Original Message-
> From: Radhika Puthiyetath [mailto:radhika.puthiyet...@citrix.com]
> Sent: Tuesday, August 13, 2013 3:25 PM
> To: us...@cloudstack.apache.org; dev@cloudstack.apache.org; Chandan 
> Purushothama; Kishan Kavala
> Subject: RE: [Doc] nTier App is Ready for Review
> 
> Hi,
> 
> nTier Apps documentation is ready for review. The doc is attached at 
> https://issues.apache.org/jira/browse/CLOUDSTACK-770.
> 
> The sub tasks also have the respective sections mentioned for easy reviewing.
> 
> Regards
> -Radhika
> 

[Responsiveness report] dev 2013w33

[Daan Hoogland]

nothing to report :)

some well known posters didn't get feedback, but no people that are
possibly new to the community, which was why I started reporting in
the first place.

regards,
Daan

[Responsiveness report] users 2013w33

[Daan Hoogland]

I noticed i missed some mails before, so I am getting less selective
what i put in this list. The second included an answer to himself. The
first one is illegible from all my mail readers so i did the base64
decoding by hand, see  at the bottom.

http://markmail.org/message/br52s3flymghcjxh Managing vm networks by
Jonathan Creasy
http://markmail.org/message/bdbca4szqrhmbv6m Production Agent
Disconnect by Marty Sweet


I am trying to figure out a way to always append another ethernet
interface to a vm when it is created.

Lets say a user creates a vm with two selected networks. I want the vm
to come up with three networks, the third being a pre-defined network
in a vlan we use for management. If the user selected one network,
then a second would be added.

Any thoughts?


regards,
Daan

Re: Whats involved in adding an extra hypervisor

[Nguyen Anh Tu]

2013/8/19 Sebastien Goasguen 

> Kind of on that same vein:
>
> Anyone interested in modifying the KVM agent to support "pure" Xen without
> xapi.
>
> I think it might be possible to just use the kvm agent and modify the
> libvirt calls to talk to xl , that way there would be no need for xapi...
>
> Which if I am not mistaken would give us Xen on ARM support instantly in
> CloudStack
>
> Any takers ? or anyone telling me I got this completely wrong ?
>

Xen on ARM or ARM hypervisor, can be supported for mobile devices, sound
like interesting. If we have plan to do it, I'm willing to contribute.
Anything related to Xen makes me excited.

A short demo about Xen on ARM cloud with OpenNebula:
http://www.youtube.com/watch?v=xZP9YKv3P_E

-- 

N.g.U.y.e.N.A.n.H.t.U

RE: Documentation issue in CloudStack 4.1

[Radhika Puthiyetath]

+ Dev list.

+1 

We should have someone to sign off each section before the release.

-Original Message-
From: Ron Wheeler [mailto:rwhee...@artifact-software.com] 
Sent: Monday, August 19, 2013 7:03 PM
To: us...@cloudstack.apache.org
Subject: Re: Documentation issue in CloudStack 4.1

It is too bad that an errata list can not be applied to an existing release in 
the same way that a book publisher issues one against a printed book.

Suggestion:
Docs should be tested in the same way that the code is.

At least try the installation once to see if it still works.
I hope that 4.2 will actually work as described.

Have someone read each section once and sign off on it before the release 
decision is made.

Get rid of the duplication between external documentation wikis and the manuals.
There is not enough manpower to maintain both and having 3 places to look for 
documentation is just confusing.

The wikis are easy to maintain but hard to version.

Ron


On 19/08/2013 5:05 AM, Sebastien Goasguen wrote:
> On Aug 19, 2013, at 4:50 AM, Ryan Lei  wrote:
>
>> More specifically, Ashutosh, did you forget to use baseurl= 
>> http://cloudstack.apt-get.eu/rhel/4.1/ in your yum setting?
>> Ironically, the 4.1.0 Installation Guide still points to 4.0, whose 
>> doc fix can only be applied to the next version 4.1.1.
>>
>> It's sad to me that critical doc mistakes like this will stay in the 
>> 4.1.0 docs "forever", just as the 4.0.2 Release Note would always 
>> have the title 4.0.1-incubating even if there was 4.0.3 (It was fixed 
>> in the 4.0 branch, though [1]). These fixes just can't be backported to docs 
>> already "online."
>> (sigh)
> Well, the error you mention is indeed in the 4.1.0 release docs, but 
> it was fixed in subsequent release 4.1.1
>   
> Everyone should aim to install the latest version: if 4.1.1 is out then try 
> to avoid installing 4.1.0 and don't read the 4.1.0 docs.
>
> But I understand what you are saying and we definitely need everyone to file 
> bugs for docs defects, we need to fix them and improve the docs greatly.
>
> Any help/recommendations much welcome !
>
> -sebastien
>
>
>> [1] https://issues.apache.org/jira/browse/CLOUDSTACK-2204
>>
>> -
>> -- Yu-Heng (Ryan) Lei, Associate Researcher 
>> Chunghwa Telecom Laboratories / Cloud Computing Laboratory 
>> ryan...@cht.com.tw> G0SWYpVkiWo8SsDdf3ZqO9AIuAPTzRnFYCUi-z4YljtI_hyVKkNHfn9F1Bn-vUWJnQ4.&
>> URL=mailto%3aryanlei%40cht.com.tw>
>> or
>> ryanlei750...@gmail.com
>>
>>
>>
>> On Mon, Aug 19, 2013 at 4:33 PM, Sebastien Goasguen wrote:
>>
>>> On Aug 19, 2013, at 4:29 AM, Ryan Lei  wrote:
>>>
 That's weird. My environment has the community RPMs [1] installed 
 (tried both 4.1.0 and 4.1.1), but there DOES exist the
>>> cloudstack-setup-databases
 command, located in /usr/bin.

 $ which cloudstack-setup-databases
 /usr/bin/cloudstack-setup-databases

 As I remember, these cloud-*** commands have all changed their 
 titles to
 cloudstack-*** since version 4.1. So I was confused when I first 
 read
>>> your
 thread concerning 4.1.

 Are you using a RPM-based Linux and the community RPMs, too? I have 
 no
>>> idea
 why you have cloud-setup-databases, instead!

 [1] http://cloudstack.apt-get.eu/rhel/4.1/
>>>
>>> Ryan, I actually agree with you and I remember fixing the doc for this.
>>>
>>> Ashutosh, are you using 4.0 instead of 4.1 ?
>>>

>>> 
>>> ---
 Yu-Heng (Ryan) Lei, Associate Reasearcher Chunghwa Telecom 
 Laboratories / Cloud Computing Laboratory ryan...@cht.com.tw<
>>> https://email.cht.com.tw/owa/redir.aspx?C=-wE1FEC3G0SWYpVkiWo8SsDdf3
>>> ZqO9AIuAPTzRnFYCUi-z4YljtI_hyVKkNHfn9F1Bn-vUWJnQ4.&URL=mailto%3aryan
>>> lei%40cht.com.tw
 or
 ryanlei750...@gmail.com



 On Fri, Jul 12, 2013 at 6:01 PM, Ashutosh Narayan < 
 aashutoshnara...@gmail.com> wrote:

> Hi Folks,
>
> I just came across some command issues in the installation 
> document mentioned on this link -
>
>
>>> http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.1.0/html
>>> /Installation_Guide/management-server-install-flow.html
> Section 4.5.4.1 has *cloudstack-setup-databases* but no such 
> command is found instead *cloud-setup-databases* is present for 
> CloudStack version 4.1. Looks like a documentation issue.
>
> Just wanted the list to know.
>
> Thank you,
> --
> Ashutosh Narayan
>
> http://ashutoshn.wordpress.com/
>
>>>
>


--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102

RE: [Doc] nTier App is Ready for Review

[Rajesh Battala]

I had gone through the doc. 
Whatever Sowmya had listed, apart from that looks good to me.

Thanks
Rajesh Battala

-Original Message-
From: Sowmya Krishnan [mailto:sowmya.krish...@citrix.com] 
Sent: Monday, August 19, 2013 4:43 PM
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org; Chandan 
Purushothama; Kishan Kavala
Subject: RE: [Doc] nTier App is Ready for Review

Thanks Radhika.
Minor corrections under: 15.27.11.1.2. Creating a Network Offering for External 
LB

1. Please edit " To have internal LB support on VPC," to "To have external LB 
support on VPC,"
2. Under "Supported Services", choose Load Balancer Provider as Netscaler or 
VpcVirtualRouter 3. Load Balancer Type should be Public LB 4. LB Isolation 
should be Dedicated if Netscaler is being used as the external LB provider

Rest look good. Thanks.

> -Original Message-
> From: Radhika Puthiyetath [mailto:radhika.puthiyet...@citrix.com]
> Sent: Tuesday, August 13, 2013 3:25 PM
> To: us...@cloudstack.apache.org; dev@cloudstack.apache.org; Chandan 
> Purushothama; Kishan Kavala
> Subject: RE: [Doc] nTier App is Ready for Review
> 
> Hi,
> 
> nTier Apps documentation is ready for review. The doc is attached at 
> https://issues.apache.org/jira/browse/CLOUDSTACK-770.
> 
> The sub tasks also have the respective sections mentioned for easy reviewing.
> 
> Regards
> -Radhika
> 

Re: Whats involved in adding an extra hypervisor

[Sebastien Goasguen]

Kind of on that same vein:

Anyone interested in modifying the KVM agent to support "pure" Xen without xapi.

I think it might be possible to just use the kvm agent and modify the libvirt 
calls to talk to xl , that way there would be no need for xapi...

Which if I am not mistaken would give us Xen on ARM support instantly in 
CloudStack

Any takers ? or anyone telling me I got this completely wrong ?

-Sebastien

On Aug 16, 2013, at 2:42 AM, Likitha Shetty  wrote:

> Ian, with AWS it’s the other way around. The package allows us to spin up VMs 
> in CS using AWS EC2 API's.
> 
> -Likitha
> 
>> -Original Message-
>> From: Ian Duffy [mailto:i...@ianduffy.ie]
>> Sent: Friday, August 16, 2013 12:07 PM
>> To: CloudStack Dev
>> Subject: Re: Whats involved in adding an extra hypervisor
>> 
>> Hi Donal and Chiradeep,
>> 
>> Thanks for your comments. It was an interesting read.
>> 
>> I might be missing something here but I will ask anyways. If I understand
>> correctly, at current with awsapi we are able to submit our aws api 
>> credentials
>> to Cloudstack and spin up VMs on aws correct? Is there a reason the
>> communication with aws could not be provided like a standard hypervisor? what
>> is the reasoning behind keeping it as an almost separate package?
>> 
>> The reason I'm asking is because I'm wanting to do something Cloudstack based
>> for a college project next year. However there is a hard 1 month deadline. I 
>> was
>> interested to see could a base(or something of demoable quality) for 
>> supporting
>> Google Compute Engine be completed in such a short deadline.
>> 
>> On 15 August 2013 09:29, Donal Lafferty  wrote:
>>> Definitely possible to add new Hypervisor types, if that's what you're 
>>> asking.
>>> 
>>> How easy it is depends on how much existing CloudStack infrastructure you
>> can exploit.  Let me out line the task with the help of some planning 
>> questions:
>>> 
>>> 1. What will be your agent model?  Will you talk directly to the hypervisor
>> (direct connect agent), or will you install a remote agent on the hypervisor
>> (connected agent).  This comes down to whether the hypervisor exposes a high
>> level API remotely.
>>> 
>>> 2. What will be your secondary storage model?  Secondary storage provides
>> low IOPS storage accessible to all hypervisors in the zone.  Thus, we store 
>> the
>> templates in secondary storage.  IIRC, CloudStack supports NFS, S3 and Swift.
>> Does one of these options suit your data centre, or do you need to expand the
>> list?  Will your agent be able to download disk images in secondary storage 
>> to
>> the hypervisor?
>>> 
>>> 3. What will be your primary storage model?  Typically, primary storage is
>> high IOPS storage specific to a hypervisor or cluster of hypervisors.  The 
>> easiest
>> to setup is local storage, which can be a hard disk or storage you mount
>> manually on the hypervisor.  Alternatively, you may want to automate mounting
>> storage on the hypervisor.
>>> 
>>> 4.  What will be your system VM model?  System VMs offload the following
>> functionality from the management server:  VM console access, networking
>> services, and secondary storage (upload) service.  You could skip system VMs
>> and run these services in the management server's host using QuickCloud.  You
>> could run system VMs on an existing hypervisor type, or you could add a new
>> system VM type for your hypervisor.  Keep in mind that QuickCloud can't run
>> your networking services.  Also, if you want to create a new system VM type, 
>> you
>> have to come up with VM image.
>>> 
>>> The tricky bits:
>>> 
>>> 5. What language will your agent use?  A direct connect agent sits in the
>> CloudStack process, so it is written in Java.  Alternatively, there is 
>> infrastructure
>> for a Java-based remote agent, which handles all your communications.  If you
>> need a non-Java remote agent, you are better off sending the kernel commands
>> over HTTP, which looks more like an RPC mechanism than REST.
>>> 
>>> 6. How will you know what instructions to implement?  You can look at an
>> existing ServerResource class for a hypervisor to know what command types
>> there are.  The relevant pieces of data in each command can be found out from
>> existing hypervisor implementations.  Alternatively, you can look at test 
>> logs,
>> which contain the data from each command.  Eventually you'll want to try your
>> plugin with CloudStack itself.
>>> 
>>> Chiradeep's comments relate to #6 above.
>>> 
>>> 
 -Original Message-
 From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com]
 Sent: 15 August 2013 02:51
 To: dev@cloudstack.apache.org
 Subject: Re: Whats involved in adding an extra hypervisor
 
 Yes, it is a hypervisor plugin. While the extension method may be
 simple, the impedance mismatch between the CloudStack virtual model
 and the hypervisor API is what causes the most pain.
 E.g., CloudStack will hand a VirtualMachineTO o

Re: [DOC] cloudstack.apache.org Search

[Sebastien Goasguen]

On Aug 18, 2013, at 2:22 PM, Marty Sweet  wrote:

> Hi Guys,
> 
> Not sure if your aware but the doc search feature is broken on
> http://cloudstack.apache.org/docs/en-US/
> 
> The search feature takes users to the following URL (searched templates):
> https://www.google.com/search?q=templates&sitesearch=http%3A%2F%2Flocalhost%2F
> 
> The domain is being specified as localhost, it should be
> http://cloudstack.apache.org/docs
> https://www.google.com/search?q=templates&sitesearch=http%3A%2F%2Flocalhost%2F#bav=on.2,or.r_cp.r_qf.&fp=fd636efafc1f2c54&q=templates+site:http%3A%2F%2Fcloudstack.apache.org%2Fdocs&safe=off
> 
> I think many new users find this frustrating when trying to look through
> documentation.
> 
> Regards,
> Marty

Marty, thanks for reporting this.

I fixed it (at least in english). Can you check that it works for you now ?

The docs are built automatically with publican, we will have to keep an eye out 
for 4.2 to make sure this does not get broken.

-Sebastien

Re: Review Request 13615: [Autoscale] Account deletion doesn't delete all autoscaled LB rules created by the account

[Rajesh Battala]

> On Aug. 17, 2013, 9:03 a.m., Murali Reddy wrote:
> > 4.2 a03c5f5b1bb3e45b5b2a8365b0c09d48778e426a
> > master bb26b854fb89ef71c5183e2c23ef17898d9d

Thanks Murali for reviewing and pushing the patch


- Rajesh


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


On Aug. 16, 2013, 12:39 p.m., Rajesh Battala wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/13615/
> ---
> 
> (Updated Aug. 16, 2013, 12:39 p.m.)
> 
> 
> Review request for cloudstack, Murali Reddy and Ram Ganesh.
> 
> 
> Bugs: CLOUDSTACK-4237
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Issue:
> for an account if there are multiple LB rules and Autoscale Policies, when 
> Account is deleted. All the LBrules, Autoscale polices are not getting delete 
> in Netscaler resource. But in CS db they are getting cleared.
> 
> Root Cause:
> ===
> while processing the LBConfigcmd in NSResource, after processing the first 
> Autoscale cmd, no other rules are getting processed as its returning from 
> loop.
> 
> Fix:
>  
> 
> Fixed the issue to process all the autoscale config rules in the 
> LBConfigCommand.
> 
> 
> Diffs
> -
> 
>   
> plugins/network-elements/netscaler/src/com/cloud/network/resource/NetscalerResource.java
>  4020059 
> 
> Diff: https://reviews.apache.org/r/13615/diff/
> 
> 
> Testing
> ---
> 
> 1. created a testA account and created network with NS as LB provider and 
> Acquired 3 ip's
> 2. on each IP configured multiple Autoscale polices and normal LB rules.
> 3. Verified on NS there are total 4 vservers and 3 services ( 2 autoscale and 
> 2 cloud service)
> 4. deleted one LB rule. LB rule got delete successfully and the same is 
> removed from NS.
> 5. deleted the account, network got deleted as part of it all the rules got 
> revoked and sent to NSResource to execute them. 
> All the servers, lb vservers got remove successfully.
> 
> 
> Thanks,
> 
> Rajesh Battala
> 
>

Re: Review Request 13641: Fix for build failure in 4.2

[Rajesh Battala]

> On Aug. 19, 2013, 1:01 p.m., Devdeep Singh wrote:
> > Committed to 4.2 in 6c593b0b16f37951c0c30b2ad3cff69835085fe2

Thanks for the review and pushing to repo


- Rajesh


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


On Aug. 19, 2013, 6:26 a.m., Rajesh Battala wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/13641/
> ---
> 
> (Updated Aug. 19, 2013, 6:26 a.m.)
> 
> 
> Review request for cloudstack, Devdeep Singh, edison su, and Sateesh 
> Chodapuneedi.
> 
> 
> Bugs: CLOUDSTACK-4391
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> 4.2 build is failing as there is an issue with the Unittest for 
> LibvirtComputingResourceTest with recent commit to LibvirtComputingResouce 
> class.
> 
> 
> Diffs
> -
> 
>   
> plugins/hypervisors/kvm/test/com/cloud/hypervisor/kvm/resource/LibvirtComputingResourceTest.java
>  56d6536 
> 
> Diff: https://reviews.apache.org/r/13641/diff/
> 
> 
> Testing
> ---
> 
> Created a possible fix for the issue 
> Applying the patch, KVM unittess are running successful.
> 
> KVM tests are passing successfully. 
>  
> ---
> T E S T S
> ---
> Running com.cloud.hypervisor.kvm.resource.LibvirtVifDriverTest
> log4j:WARN No appenders could be found for logger 
> (com.cloud.hypervisor.kvm.resource.LibvirtComputingResource).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
> info.
> Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.034 sec
> Running com.cloud.hypervisor.kvm.resource.LibvirtComputingResourceTest
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.058 sec
> Running com.cloud.hypervisor.kvm.resource.LibvirtVMDefTest
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.018 sec
>  
> Results :
>  
> Tests run: 13, Failures: 0, Errors: 0, Skipped: 0
>  
>  
> Thanks
> Rajesh Battala
> 
> 
> Thanks,
> 
> Rajesh Battala
> 
>

Re: Review Request 13641: Fix for build failure in 4.2

[Devdeep Singh]

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

Ship it!


Committed to 4.2 in 6c593b0b16f37951c0c30b2ad3cff69835085fe2

- Devdeep Singh


On Aug. 19, 2013, 6:26 a.m., Rajesh Battala wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/13641/
> ---
> 
> (Updated Aug. 19, 2013, 6:26 a.m.)
> 
> 
> Review request for cloudstack, Devdeep Singh, edison su, and Sateesh 
> Chodapuneedi.
> 
> 
> Bugs: CLOUDSTACK-4391
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> 4.2 build is failing as there is an issue with the Unittest for 
> LibvirtComputingResourceTest with recent commit to LibvirtComputingResouce 
> class.
> 
> 
> Diffs
> -
> 
>   
> plugins/hypervisors/kvm/test/com/cloud/hypervisor/kvm/resource/LibvirtComputingResourceTest.java
>  56d6536 
> 
> Diff: https://reviews.apache.org/r/13641/diff/
> 
> 
> Testing
> ---
> 
> Created a possible fix for the issue 
> Applying the patch, KVM unittess are running successful.
> 
> KVM tests are passing successfully. 
>  
> ---
> T E S T S
> ---
> Running com.cloud.hypervisor.kvm.resource.LibvirtVifDriverTest
> log4j:WARN No appenders could be found for logger 
> (com.cloud.hypervisor.kvm.resource.LibvirtComputingResource).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
> info.
> Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.034 sec
> Running com.cloud.hypervisor.kvm.resource.LibvirtComputingResourceTest
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.058 sec
> Running com.cloud.hypervisor.kvm.resource.LibvirtVMDefTest
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.018 sec
>  
> Results :
>  
> Tests run: 13, Failures: 0, Errors: 0, Skipped: 0
>  
>  
> Thanks
> Rajesh Battala
> 
> 
> Thanks,
> 
> Rajesh Battala
> 
>

Re: Review Request 13642: Cloudstack-4356: Implicit planner - Added check for empty host, Skip if no empty host found

[Gaurav Aradhye]

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

(Updated Aug. 19, 2013, 12:55 p.m.)


Review request for cloudstack, Rayees Namathponnan and Prasanna Santhanam.


Changes
---

Added check for any SSVM or routers running on host, as implicit dedication 
also considers these two too along with user vms while finding an "Empty Host".


Repository: cloudstack-git


Description
---

Issue 4356: Implicit planner
As mentioned in the issue, added check for finding empty host.
Passed zone id of empty host while creating deployment.

If no empty host is found, test case will skip.

However, deployment of VM still fails with implicit dedication even when empty 
host is found. Created Issue 4397 for this.


Diffs (updated)
-

  test/integration/component/test_implicit_planner.py 854b481 

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


Testing
---


Thanks,

Gaurav Aradhye

Re: Review Request 13001: Automation: Adding test cases for CPU limits from Limit Resources.

[Sanjay Tripathi]

> On Aug. 19, 2013, 11:49 a.m., Sanjay Tripathi wrote:
> > test/integration/component/cpu_limits/test_domain_limits.py, line 718
> > 
> >
> > if i am not wrong, the api_client should be api_client_cadmin_2

Can you please close the opened issues once you fix them, also remove the 
trailing white spaces. 


- Sanjay


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


On Aug. 8, 2013, 12:51 p.m., Gaurav Aradhye wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/13001/
> ---
> 
> (Updated Aug. 8, 2013, 12:51 p.m.)
> 
> 
> Review request for cloudstack, Girish Shilamkar, sailaja mada, Sanjay 
> Tripathi, and Prasanna Santhanam.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Adding test cases for CPU limits from Limit Resources.
> Marvin changes have to be picked up from Memory Limits patch 
> (https://reviews.apache.org/r/11626/). Those are not included in this patch.
> 
> 
> Diffs
> -
> 
>   test/integration/component/cpu_limits/test_cpu_limits.py PRE-CREATION 
>   test/integration/component/cpu_limits/test_domain_limits.py PRE-CREATION 
>   test/integration/component/cpu_limits/test_maximum_limits.py PRE-CREATION 
>   test/integration/component/cpu_limits/test_project_limits.py PRE-CREATION 
>   tools/marvin/marvin/integration/lib/base.py b5d086b 
>   tools/marvin/marvin/integration/lib/common.py 4f5acef 
> 
> Diff: https://reviews.apache.org/r/13001/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Gaurav Aradhye
> 
>

Re: Review Request 13001: Automation: Adding test cases for CPU limits from Limit Resources.

[Sanjay Tripathi]

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



test/integration/component/cpu_limits/test_cpu_limits.py


can't we have expected_resource_count which would be the exact expected 
value after the vm_delete operation and as we already knows about the service 
offering, we can easily calculate the expected value.



test/integration/component/cpu_limits/test_cpu_limits.py


As the test title says "reboot_instance" , please use reboot instance API 
instead of stopping and then starting an instance.



test/integration/component/cpu_limits/test_cpu_limits.py


create and use the expected_resource_count and assign the exact expected 
value.



test/integration/component/cpu_limits/test_cpu_limits.py


This seems like a duplicate test as there is already a test which is 
testing this scenario i.e. "test_02_migrate_instance"

Please remove the tests which you think are checking the same scenario more 
than once, as it will minimize the running time for this script.



test/integration/component/cpu_limits/test_domain_limits.py


as the test title says "reboot_instance", please use reboot instance API.



test/integration/component/cpu_limits/test_domain_limits.py


use different limits then what you have set for cadmin_1, it will help in 
checking more test cases.



test/integration/component/cpu_limits/test_domain_limits.py


if i am not wrong, the api_client should be api_client_cadmin_2


- Sanjay Tripathi


On Aug. 8, 2013, 12:51 p.m., Gaurav Aradhye wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/13001/
> ---
> 
> (Updated Aug. 8, 2013, 12:51 p.m.)
> 
> 
> Review request for cloudstack, Girish Shilamkar, sailaja mada, Sanjay 
> Tripathi, and Prasanna Santhanam.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Adding test cases for CPU limits from Limit Resources.
> Marvin changes have to be picked up from Memory Limits patch 
> (https://reviews.apache.org/r/11626/). Those are not included in this patch.
> 
> 
> Diffs
> -
> 
>   test/integration/component/cpu_limits/test_cpu_limits.py PRE-CREATION 
>   test/integration/component/cpu_limits/test_domain_limits.py PRE-CREATION 
>   test/integration/component/cpu_limits/test_maximum_limits.py PRE-CREATION 
>   test/integration/component/cpu_limits/test_project_limits.py PRE-CREATION 
>   tools/marvin/marvin/integration/lib/base.py b5d086b 
>   tools/marvin/marvin/integration/lib/common.py 4f5acef 
> 
> Diff: https://reviews.apache.org/r/13001/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Gaurav Aradhye
> 
>

Re: Ruby dev wanted

[Sebastien Goasguen]

On Aug 19, 2013, at 7:26 AM, Isaac Chiang  wrote:

> Hi Sebastien,
>   Chip's cloudstack_ruby_client is almost ready (waiting for
> second time pull request). I'll spend some time on rOCCi in next few weeks.
> Currently I still can't have the pictures of what exactly the rOCCi is
> doing. I'll try to find myself more use cases. Thanks for the provided
> information.
> 

The best might be to have a look at the OCCI Opennebula documentation:
http://opennebula.org/documentation:rel4.2:occicg

OCCI is a cloud computing standard defined by OGF.  Similar to CIMI but a 
different standard :)

Basically instead of making calls to the CloudStack API, which is not an 
official standard, users could use an OCCI client to manage their cloud (basic 
functionality being to start/stop vms).  This means that CloudStack needs to 
expose a service that answers to OCCI standard requests. With rOCCI we can 
deploy a server side by side with CloudStack mgt server. The OCCI requests 
would get to that server and then be forwarded to the CloudStack mgt API server 
thanks to the driver that you can write :)

It is a similar idea to the AWS interface in CloudStack.

Does that make more sense ?

> Regards
> Isaac
> 
> 
> On Mon, Aug 19, 2013 at 4:19 PM, Sebastien Goasguen wrote:
> 
>> 
>> On Aug 1, 2013, at 6:03 AM, Isaac Chiang  wrote:
>> 
>>> Hi Sebastien,
>>>  I've read the ruby client project by Chips. It's pretty looks like
>>> I'm doing now for _https://github.com/isaacchiang/cloud_ruby. Please
>> have a
>>> look. I believe there are
>>> some code segments that would be helpful to the rOCCI driver. I need more
>>> advice to
>>> the rOCCI project, thanks.
>> 
>> Isaac, thanks for the work on the ruby gem for cloudstack.
>> 
>> rOCCI is a server that implements the OCCI standard.
>> We need to create a CloudStack driver in rOCCI, based on the cloudstack
>> gem from chip.
>> You can git clone rOCCI from github:
>> https://github.com/gwdg/rOCCI-server/tree/master
>> 
>> The drivers of backend are at:
>> https://github.com/gwdg/rOCCI-server/tree/master/lib/occi/backend
>> 
>> Once this is done, we should run it in parallel to a cloudstack instance
>> and send OCCI requests to it, this will in turn send cloudstack api calls.
>> 
>> Happy to chat on IRC if you want,
>> 
>> Cheers,
>> 
>> -Sebastien
>> 
>>> 
>>> Regard
>>> 
>>> Isaac
>>> 
>>> 
>>> On Fri, Jul 26, 2013 at 11:16 PM, Sebastien Goasguen >> wrote:
>>> 
 
 On Jul 25, 2013, at 8:04 PM, Isaac Chiang 
>> wrote:
 
> Hi Sebastien,
>   I'm interested in the rOCCi project. I'd like to join.
> However, I know nothing about the OCCI and will spend some time on it
>> in
> next few days. Please kindly let me know more information about the
> project(status, repo location, e.t.c., thanks :)
> 
> 
 
 Hi Isaac,
 
 Great, that's terrific of you to volunteer, should be fun.
 
 The first thing I think would be to check out Chip'c ruby client:
 https://github.com/chipchilders/cloudstack_ruby_client
 
 Test it and finish it up  (I am sure Chip can chime in).
 
 Then, you would need to look at:
 https://github.com/gwdg/rOCCI
 
 Figure out how to write a driver, there is an example for opennebula and
 ec2 I believe.
 And then go for it :)
 
 Cheers,
 
 -Sebastien
 
> Regards
> 
> Isaac
> 
> 
> Hi folks,
> 
> I committed to do an interoperability workshop in Madrid, Spain in
> september:
> 
 
>> http://www.cloudplugfest.org/cloud-interoperability-week/detailed-program
> 
> All "four sisters" of cloud are represented.
> 
> The main goal is to show that we can talk to CloudStack with OCCI and
 even
> CIMI standards.
> 
> The problem is that currently we cannot :)
> 
> So I am looking for some help from Ruby developers who would be willing
 to
> work on:
> 
> https://github.com/gwdg/rOCCI
> 
> and also on delta cloud (even though the project may have stalled):
> 
> http://deltacloud.apache.org
> 
> A good start might be Chip's ruby client:
> https://github.com/chipchilders/cloudstack_ruby_client
> 
> Help, any takers  ?
> 
> 
> 
> -Sebastien
 
 
>> 
>> 

RE: [Doc] nTier App is Ready for Review

[Kishan Kavala]

Thanks Radhika for the Doc.

Please find my comments below:

15.27.3.6
Add Tier -> ACL List selection is missing in the screenshot. 

15.27.4 and 15.27.4.1
All outgoing traffic is not blocked by default. Behaviour is as follows:
"By default, all incoming traffic to guest networks is blocked. All outgoing 
traffic from guest networks is allowed, once you add an ACL rule for outgoing 
traffic, then only outgoing traffic specified in this ACL rule is allowed, the 
rest is blocked."

15.27.4.4 - Heading should be "Creating tier with custom ACL List"

~kishan

> -Original Message-
> From: Sowmya Krishnan
> Sent: Monday, 19 August 2013 4:43 PM
> To: dev@cloudstack.apache.org; us...@cloudstack.apache.org; Chandan
> Purushothama; Kishan Kavala
> Subject: RE: [Doc] nTier App is Ready for Review
> 
> Thanks Radhika.
> Minor corrections under: 15.27.11.1.2. Creating a Network Offering for
> External LB
> 
> 1. Please edit " To have internal LB support on VPC," to "To have external LB
> support on VPC,"
> 2. Under "Supported Services", choose Load Balancer Provider as Netscaler or
> VpcVirtualRouter 3. Load Balancer Type should be Public LB 4. LB Isolation
> should be Dedicated if Netscaler is being used as the external LB provider
> 
> Rest look good. Thanks.
> 
> > -Original Message-
> > From: Radhika Puthiyetath [mailto:radhika.puthiyet...@citrix.com]
> > Sent: Tuesday, August 13, 2013 3:25 PM
> > To: us...@cloudstack.apache.org; dev@cloudstack.apache.org; Chandan
> > Purushothama; Kishan Kavala
> > Subject: RE: [Doc] nTier App is Ready for Review
> >
> > Hi,
> >
> > nTier Apps documentation is ready for review. The doc is attached at
> > https://issues.apache.org/jira/browse/CLOUDSTACK-770.
> >
> > The sub tasks also have the respective sections mentioned for easy 
> > reviewing.
> >
> > Regards
> > -Radhika
> >

RE: [Doc] nTier App is Ready for Review

[Radhika Puthiyetath]

Thanks Sowmya.

Kishan, could you please sign off because I need developer's sign off for each 
feature.

Let me know if that is not necessary.

Regards
-Radhika

-Original Message-
From: Sowmya Krishnan [mailto:sowmya.krish...@citrix.com] 
Sent: Monday, August 19, 2013 4:43 PM
To: dev@cloudstack.apache.org; us...@cloudstack.apache.org; Chandan 
Purushothama; Kishan Kavala
Subject: RE: [Doc] nTier App is Ready for Review

Thanks Radhika.
Minor corrections under: 15.27.11.1.2. Creating a Network Offering for External 
LB

1. Please edit " To have internal LB support on VPC," to "To have external LB 
support on VPC,"
2. Under "Supported Services", choose Load Balancer Provider as Netscaler or 
VpcVirtualRouter 3. Load Balancer Type should be Public LB 4. LB Isolation 
should be Dedicated if Netscaler is being used as the external LB provider

Rest look good. Thanks.

> -Original Message-
> From: Radhika Puthiyetath [mailto:radhika.puthiyet...@citrix.com]
> Sent: Tuesday, August 13, 2013 3:25 PM
> To: us...@cloudstack.apache.org; dev@cloudstack.apache.org; Chandan 
> Purushothama; Kishan Kavala
> Subject: RE: [Doc] nTier App is Ready for Review
> 
> Hi,
> 
> nTier Apps documentation is ready for review. The doc is attached at 
> https://issues.apache.org/jira/browse/CLOUDSTACK-770.
> 
> The sub tasks also have the respective sections mentioned for easy reviewing.
> 
> Regards
> -Radhika
> 

Re: Ruby dev wanted

[Isaac Chiang]

Hi Sebastien,
   Chip's cloudstack_ruby_client is almost ready (waiting for
second time pull request). I'll spend some time on rOCCi in next few weeks.
Currently I still can't have the pictures of what exactly the rOCCi is
doing. I'll try to find myself more use cases. Thanks for the provided
information.

Regards
Isaac


On Mon, Aug 19, 2013 at 4:19 PM, Sebastien Goasguen wrote:

>
> On Aug 1, 2013, at 6:03 AM, Isaac Chiang  wrote:
>
> > Hi Sebastien,
> >   I've read the ruby client project by Chips. It's pretty looks like
> > I'm doing now for _https://github.com/isaacchiang/cloud_ruby. Please
> have a
> > look. I believe there are
> > some code segments that would be helpful to the rOCCI driver. I need more
> > advice to
> > the rOCCI project, thanks.
>
> Isaac, thanks for the work on the ruby gem for cloudstack.
>
> rOCCI is a server that implements the OCCI standard.
> We need to create a CloudStack driver in rOCCI, based on the cloudstack
> gem from chip.
> You can git clone rOCCI from github:
> https://github.com/gwdg/rOCCI-server/tree/master
>
> The drivers of backend are at:
> https://github.com/gwdg/rOCCI-server/tree/master/lib/occi/backend
>
> Once this is done, we should run it in parallel to a cloudstack instance
> and send OCCI requests to it, this will in turn send cloudstack api calls.
>
> Happy to chat on IRC if you want,
>
> Cheers,
>
> -Sebastien
>
> >
> > Regard
> >
> > Isaac
> >
> >
> > On Fri, Jul 26, 2013 at 11:16 PM, Sebastien Goasguen  >wrote:
> >
> >>
> >> On Jul 25, 2013, at 8:04 PM, Isaac Chiang 
> wrote:
> >>
> >>> Hi Sebastien,
> >>>I'm interested in the rOCCi project. I'd like to join.
> >>> However, I know nothing about the OCCI and will spend some time on it
> in
> >>> next few days. Please kindly let me know more information about the
> >>> project(status, repo location, e.t.c., thanks :)
> >>>
> >>>
> >>
> >> Hi Isaac,
> >>
> >> Great, that's terrific of you to volunteer, should be fun.
> >>
> >> The first thing I think would be to check out Chip'c ruby client:
> >> https://github.com/chipchilders/cloudstack_ruby_client
> >>
> >> Test it and finish it up  (I am sure Chip can chime in).
> >>
> >> Then, you would need to look at:
> >> https://github.com/gwdg/rOCCI
> >>
> >> Figure out how to write a driver, there is an example for opennebula and
> >> ec2 I believe.
> >> And then go for it :)
> >>
> >> Cheers,
> >>
> >> -Sebastien
> >>
> >>> Regards
> >>>
> >>> Isaac
> >>>
> >>>
> >>> Hi folks,
> >>>
> >>> I committed to do an interoperability workshop in Madrid, Spain in
> >>> september:
> >>>
> >>
> http://www.cloudplugfest.org/cloud-interoperability-week/detailed-program
> >>>
> >>> All "four sisters" of cloud are represented.
> >>>
> >>> The main goal is to show that we can talk to CloudStack with OCCI and
> >> even
> >>> CIMI standards.
> >>>
> >>> The problem is that currently we cannot :)
> >>>
> >>> So I am looking for some help from Ruby developers who would be willing
> >> to
> >>> work on:
> >>>
> >>> https://github.com/gwdg/rOCCI
> >>>
> >>> and also on delta cloud (even though the project may have stalled):
> >>>
> >>> http://deltacloud.apache.org
> >>>
> >>> A good start might be Chip's ruby client:
> >>> https://github.com/chipchilders/cloudstack_ruby_client
> >>>
> >>> Help, any takers  ?
> >>>
> >>>
> >>>
> >>> -Sebastien
> >>
> >>
>
>

RE: [Doc] nTier App is Ready for Review

[Sowmya Krishnan]

Thanks Radhika.
Minor corrections under: 15.27.11.1.2. Creating a Network Offering for External 
LB

1. Please edit " To have internal LB support on VPC," to "To have external LB 
support on VPC,"
2. Under "Supported Services", choose Load Balancer Provider as Netscaler or 
VpcVirtualRouter
3. Load Balancer Type should be Public LB
4. LB Isolation should be Dedicated if Netscaler is being used as the external 
LB provider

Rest look good. Thanks.

> -Original Message-
> From: Radhika Puthiyetath [mailto:radhika.puthiyet...@citrix.com]
> Sent: Tuesday, August 13, 2013 3:25 PM
> To: us...@cloudstack.apache.org; dev@cloudstack.apache.org; Chandan
> Purushothama; Kishan Kavala
> Subject: RE: [Doc] nTier App is Ready for Review
> 
> Hi,
> 
> nTier Apps documentation is ready for review. The doc is attached at
> https://issues.apache.org/jira/browse/CLOUDSTACK-770.
> 
> The sub tasks also have the respective sections mentioned for easy reviewing.
> 
> Regards
> -Radhika
> 

Review Request 13644: CLOUDSTACK-4257: [Automation] test_storage_motion test cases failed during with unexpected result in listStoragePool API call

[Saksham Srivastava]

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

Review request for cloudstack, Devdeep Singh and Prasanna Santhanam.


Bugs: CLOUDSTACK-4257


Repository: cloudstack-git


Description
---

Test case 
integration.component.test_storage_motion.TestStorageMotion.test_02_migrate_volume
 failed during api call liststorage pool with unexpected result 
AssertionError: Check list storage pools response for valid list

This happens when there are no suitable pools found for migration.
Added check for empty pool list and then skip the test if no suitable hosts are 
found.


Diffs
-

  test/integration/component/test_storage_motion.py eda77d1 

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


Testing
---

If there is a single pool in the cluster, the test is skipped.
If multiple suitable hosts are found, the test passes.


Thanks,

Saksham Srivastava

Review Request 13643: Unplug the nic when there are no ips set on the interface

[Jayapal Reddy]

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

Review request for cloudstack, anthony xu, Abhinandan Prateek, and Murali Reddy.


Repository: cloudstack-git


Description
---

Unplugging the public nic on the VR when there are no ips set on the interface.
This issue of not reusing the public nic is present in the xen and mvm.

For vmware the nic got reused.


Diffs
-

  core/src/com/cloud/agent/resource/virtualnetwork/VirtualRoutingResource.java 
1fb86e0 
  patches/systemvm/debian/config/opt/cloud/bin/ipassoc.sh ae2d7e4 
  
plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtComputingResource.java
 9104504 
  
plugins/hypervisors/xen/src/com/cloud/hypervisor/xen/resource/CitrixResourceBase.java
 338e741 

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


Testing
---

Tested in xen and kvm.


Thanks,

Jayapal Reddy

Review Request 13642: Cloudstack-4356: Implicit planner - Added check for empty host, Skip if no empty host found

[Gaurav Aradhye]

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

Review request for cloudstack, Rayees Namathponnan and Prasanna Santhanam.


Repository: cloudstack-git


Description
---

Issue 4356: Implicit planner
As mentioned in the issue, added check for finding empty host.
Passed zone id of empty host while creating deployment.

If no empty host is found, test case will skip.

However, deployment of VM still fails with implicit dedication even when empty 
host is found. Created Issue 4397 for this.


Diffs
-

  test/integration/component/test_implicit_planner.py 854b481 

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


Testing
---


Thanks,

Gaurav Aradhye

RE: USAGE problem with SNAPSHOT

[Kishan Kavala]

Antonio,
Usageid in response "658b084e-3e52-4baf-888b-2fd471d9181e" refers to snapshot 
UUID. You can use this to refer the snapshot.

~kishan

From: Antonio Petrocelli [mailto:a.petroce...@netsons.com]
Sent: Monday, 19 August 2013 4:02 PM
To: dev@cloudstack.apache.org
Subject: USAGE problem with SNAPSHOT

Hello,

the 
"listUsageRecords"
 response in case of Snapshot response is:

array(12) {
  ["account"]=>
  string(23) "x...@netsons.com"
  ["accountid"]=>
  string(36) "72e16957-0a22-4739-b353-729da6301837"
  ["domainid"]=>
  string(36) "c1279c33-deb9-464f-8840-3dcd924cfcde"
  ["zoneid"]=>
  string(36) "dd9d48f8-8d9d-45e9-adf3-04d3d17829e5"
  ["description"]=>
  string(30) "Snapshot Id:1 Size:53687091200"
  ["usage"]=>
  float(1)
  ["usagetype"]=>
  int(9)
  ["rawusage"]=>
  string(1) "1"
  ["usageid"]=>
  string(36) "658b084e-3e52-4baf-888b-2fd471d9181e"
  ["size"]=>
  int(53687091200)
  ["startdate"]=>
  string(27) "2013-08-18'T'00:00:00+02:00"
  ["enddate"]=>
  string(27) "2013-08-18'T'00:59:59+02:00"
}

inside field "description" i can found the Snapshot Id:1

Someone know how it can be used to refeer to exact snapshot?

Thanks!

USAGE problem with SNAPSHOT

[Antonio Petrocelli]

Hello,

the "listUsageRecords 
" 
response in case of *Snapshot *response is:


array(12) {
  ["account"]=>
  string(23) "x...@netsons.com"
  ["accountid"]=>
  string(36) "72e16957-0a22-4739-b353-729da6301837"
  ["domainid"]=>
  string(36) "c1279c33-deb9-464f-8840-3dcd924cfcde"
  ["zoneid"]=>
  string(36) "dd9d48f8-8d9d-45e9-adf3-04d3d17829e5"
  ["description"]=>
  string(30) "Snapshot Id:1 Size:53687091200"
  ["usage"]=>
  float(1)
  ["usagetype"]=>
  int(9)
  ["rawusage"]=>
  string(1) "1"
  ["usageid"]=>
  string(36) "658b084e-3e52-4baf-888b-2fd471d9181e"
  ["size"]=>
  int(53687091200)
  ["startdate"]=>
  string(27) "2013-08-18'T'00:00:00+02:00"
  ["enddate"]=>
  string(27) "2013-08-18'T'00:59:59+02:00"
}

inside field "*description*" i can found the Snapshot Id:1

Someone know how it can be used to refeer to exact snapshot?

Thanks!



smime.p7s
Description: Firma crittografica S/MIME

Re: ACS 4.2 planned RC on Monday 8/19 - Push to RC

[Sebastien Goasguen]

On Aug 16, 2013, at 9:37 PM, Animesh Chaturvedi  
wrote:

> 
> 
> Folks our planned RC date is on Monday 8/19 and we have a bunch of blockers 
> and critical to take care of. I hope we can bring them to resolution by 
> Monday morning PST.
> 
> Sebastien I also need help on getting translation taken care of, Jessica and 
> Radhika are planning to wrap up new feature docs soon
> 

Hi, I will try to have a look at it now, I was off-line for a while. Copying a 
few translations folks to get some help.

-sebastien

> Here is the list of open blocker and critical:
> 
> 
> | Key | Summary   
>| Assignee 
>| 
> | CLOUDSTACK-4378 | [Automation] [Regression] Affinity group test cases 
> failed during VM deployment  | Prachi 
> Damle|
> | CLOUDSTACK-4376 | [Automation] [vmware] Failed to deploy VPC router in 
> parallel deployment scenario| Kelven Yang 
> |
> | CLOUDSTACK-4375 | VM Migration is failing from one cluster to another 
> cluster. | Sateesh 
> Chodapuneedi|
> | CLOUDSTACK-4372 | [XenServer] Commands info which are executed via 
> xenserver are not logged in SMlog   | Devdeep 
> Singh   |
> | CLOUDSTACK-4370 | [packaging]unable to upgrade cp 4.2 build on centos5.5
>| Rayees 
> Namathponnan |   
> | CLOUDSTACK-4368 | UI: findhostsformigration tab is ignoring 
> requiresstoragemotion flag in the response | 
> Jessica Wang|   
> | CLOUDSTACK-4367 | [VMware]Extract volume(local and shared) is failing with 
> NPE | Min Chen
> |   
> | CLOUDSTACK-4363 | [VMware]Migration of data volume is throwing NPE  
>| edison su
>|   
> | CLOUDSTACK-4362 | VM's are failing to start after its DATA volume is 
> migrated to second zone wide primary storage  | Sateesh 
> Chodapuneedi|   
> | CLOUDSTACK-4358 | [Automation] [vmware] Few VM deployment failed with 
> IndexOutOfBoundsException at "VolumeManagerImpl.java:2534"   | Kelven 
> Yang |   
> | CLOUDSTACK-4357 | [Automation] Failed to create snapshot in vmware, failed 
> with SOAP Exception | Kelven Yang 
> |   
> | CLOUDSTACK-4350 | [Performance Testing] Adding hosts take much longer time 
> than baselines  | Koushik Das 
> |   
> | CLOUDSTACK-4325 | [Zone-Wide-PrimaryStorage]
>| edison su
>|   
> | CLOUDSTACK-4300 | [upgrade][2.2.14 to 4.2][KVM] system vms are not coming 
> up after upgrade | edison su  
>  |   
> | CLOUDSTACK-4294 | After upgrade of to 4.2, support old vswitch type in 
> existing clusters   | Sateesh 
> Chodapuneedi|   
> | CLOUDSTACK-4253 | [VMWARE] Failed to deploy one of the VM with NPE when 
> tried deploy two VM's at the same time | edison su
>|   
> | CLOUDSTACK-4249 | [KVM]ceph:showing wrong template size 755.64 TB(template 
> created from snapshot)  | Unassigned  
> |   
> | CLOUDSTACK-4237 | [Autoscale] Account deletion doesn't delete all 
> autoscaled LB rules created by the account   | Rajesh 
> Battala  |   
> | CLOUDSTACK-4176 | [XenServer] Nic not unplugged after all IPs are released  
>| Jayapal Reddy
>|   
> | CLOUDSTACK-4139 | [VMWARE][ZWPS] Failed to resize the volumes which are 
> created from snapshot  | Vijayendra 
> Bhamidipati |   
> | CLOUDSTACK-4081 | [DOC]Fresh install of cloud platform failed with 
> dependency errors on centos5.5 OS   | 
> Unassigned  |   
> | CLOUDSTACK-3950 | [UI] Failed to copy ISO between zones 
>| Min Chen 
>  

Re: Review Request 13641: Fix for build failure in 4.2

[Ram Ganesh]

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

Ship it!


Ship It!

- Ram Ganesh


On Aug. 19, 2013, 6:26 a.m., Rajesh Battala wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/13641/
> ---
> 
> (Updated Aug. 19, 2013, 6:26 a.m.)
> 
> 
> Review request for cloudstack, Devdeep Singh, edison su, and Sateesh 
> Chodapuneedi.
> 
> 
> Bugs: CLOUDSTACK-4391
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> 4.2 build is failing as there is an issue with the Unittest for 
> LibvirtComputingResourceTest with recent commit to LibvirtComputingResouce 
> class.
> 
> 
> Diffs
> -
> 
>   
> plugins/hypervisors/kvm/test/com/cloud/hypervisor/kvm/resource/LibvirtComputingResourceTest.java
>  56d6536 
> 
> Diff: https://reviews.apache.org/r/13641/diff/
> 
> 
> Testing
> ---
> 
> Created a possible fix for the issue 
> Applying the patch, KVM unittess are running successful.
> 
> KVM tests are passing successfully. 
>  
> ---
> T E S T S
> ---
> Running com.cloud.hypervisor.kvm.resource.LibvirtVifDriverTest
> log4j:WARN No appenders could be found for logger 
> (com.cloud.hypervisor.kvm.resource.LibvirtComputingResource).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
> info.
> Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.034 sec
> Running com.cloud.hypervisor.kvm.resource.LibvirtComputingResourceTest
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.058 sec
> Running com.cloud.hypervisor.kvm.resource.LibvirtVMDefTest
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.018 sec
>  
> Results :
>  
> Tests run: 13, Failures: 0, Errors: 0, Skipped: 0
>  
>  
> Thanks
> Rajesh Battala
> 
> 
> Thanks,
> 
> Rajesh Battala
> 
>

Re: Ruby dev wanted

[Sebastien Goasguen]

On Aug 1, 2013, at 6:03 AM, Isaac Chiang  wrote:

> Hi Sebastien,
>   I've read the ruby client project by Chips. It's pretty looks like
> I'm doing now for _https://github.com/isaacchiang/cloud_ruby. Please have a
> look. I believe there are
> some code segments that would be helpful to the rOCCI driver. I need more
> advice to
> the rOCCI project, thanks.

Isaac, thanks for the work on the ruby gem for cloudstack.

rOCCI is a server that implements the OCCI standard.
We need to create a CloudStack driver in rOCCI, based on the cloudstack gem 
from chip.
You can git clone rOCCI from github:
https://github.com/gwdg/rOCCI-server/tree/master

The drivers of backend are at:
https://github.com/gwdg/rOCCI-server/tree/master/lib/occi/backend

Once this is done, we should run it in parallel to a cloudstack instance and 
send OCCI requests to it, this will in turn send cloudstack api calls.

Happy to chat on IRC if you want,

Cheers,

-Sebastien

> 
> Regard
> 
> Isaac
> 
> 
> On Fri, Jul 26, 2013 at 11:16 PM, Sebastien Goasguen wrote:
> 
>> 
>> On Jul 25, 2013, at 8:04 PM, Isaac Chiang  wrote:
>> 
>>> Hi Sebastien,
>>>I'm interested in the rOCCi project. I'd like to join.
>>> However, I know nothing about the OCCI and will spend some time on it in
>>> next few days. Please kindly let me know more information about the
>>> project(status, repo location, e.t.c., thanks :)
>>> 
>>> 
>> 
>> Hi Isaac,
>> 
>> Great, that's terrific of you to volunteer, should be fun.
>> 
>> The first thing I think would be to check out Chip'c ruby client:
>> https://github.com/chipchilders/cloudstack_ruby_client
>> 
>> Test it and finish it up  (I am sure Chip can chime in).
>> 
>> Then, you would need to look at:
>> https://github.com/gwdg/rOCCI
>> 
>> Figure out how to write a driver, there is an example for opennebula and
>> ec2 I believe.
>> And then go for it :)
>> 
>> Cheers,
>> 
>> -Sebastien
>> 
>>> Regards
>>> 
>>> Isaac
>>> 
>>> 
>>> Hi folks,
>>> 
>>> I committed to do an interoperability workshop in Madrid, Spain in
>>> september:
>>> 
>> http://www.cloudplugfest.org/cloud-interoperability-week/detailed-program
>>> 
>>> All "four sisters" of cloud are represented.
>>> 
>>> The main goal is to show that we can talk to CloudStack with OCCI and
>> even
>>> CIMI standards.
>>> 
>>> The problem is that currently we cannot :)
>>> 
>>> So I am looking for some help from Ruby developers who would be willing
>> to
>>> work on:
>>> 
>>> https://github.com/gwdg/rOCCI
>>> 
>>> and also on delta cloud (even though the project may have stalled):
>>> 
>>> http://deltacloud.apache.org
>>> 
>>> A good start might be Chip's ruby client:
>>> https://github.com/chipchilders/cloudstack_ruby_client
>>> 
>>> Help, any takers  ?
>>> 
>>> 
>>> 
>>> -Sebastien
>> 
>> 

Re: [ACS42] Issues that need to bre resolved for RC on Monday 8/19

[Wido den Hollander]

On 08/19/2013 07:49 AM, Animesh Chaturvedi wrote:

Here is the latest list of issues that need to be resolved for RC tomorrow. 
Wido can you pick up 4249 related to Ceph?



Yes, I'll do that! I'll pick up 4249



| Assignee | Issues Id: Summary 

 |
| Bharat Kumar | CLOUDSTACK-4132 : current dnsmasq config does not 
allow guest virtual machines(clients) to update its hostnames with a DNS server 
  |
| Jayapal Reddy| CLOUDSTACK-4176 : [XenServer] Nic not unplugged after 
all IPs are released
  |
| Kelven Yang  | CLOUDSTACK-4358 : [Automation] [vmware] Few VM deployment failed 
with IndexOutOfBoundsException at "VolumeManagerImpl.java:2534"|
| Kelven Yang  | CLOUDSTACK-4376 : [Automation] [vmware] Failed to 
deploy VPC router in parallel deployment scenario   
  |
| Kishan Kavala| CLOUDSTACK-4382 : [Automation] Null pointer exception 
observed while creating template and failed to create template  
  |
| Koushik Das  | CLOUDSTACK-3441 : [Load Test] High delays between VM 
being allocated to Pod and network implementation causing delays in VM 
deployment  |
| Koushik Das  | CLOUDSTACK-4350 : [Performance Testing] Adding hosts 
take much longer time than baselines
   |
| Mice Xia | CLOUDSTACK-3234 : [VM_Snapshot] Starting VM fails if 
VM snapshot is created from the VM  
   |
| Rayees Namathponnan  | CLOUDSTACK-4370 : [packaging]unable to upgrade cp 4.2 
build on centos5.5  
  |
| Sateesh Chodapuneedi | CLOUDSTACK-4294 : After upgrade of CloudStack to 4.2, 
support old vswitch type in existing clusters if user changes the vswitch 
backend |
| Sateesh Chodapuneedi | CLOUDSTACK-4362 : VM's are failing to start after its 
DATA volume is migrated to second zone wide primary storage 
  |
| Sateesh Chodapuneedi | CLOUDSTACK-4368 : when source and destination hosts 
are in different cluster UI is not calling properAPI
|
| Sateesh Chodapuneedi | CLOUDSTACK-4375 : VM Migration is failing from one 
cluster to another cluster. 
 |
| Sateesh Chodapuneedi | CLOUDSTACK-4385 : [ZWPS]Across the cluster live 
migration of VM on zone wide primary storage pool fails 
|

| Unassigned   | CLOUDSTACK-4249 : [KVM]ceph:showing wrong template 
size 755.64 TB(template created from snapshot)  
 |

Doc issues:

| shweta agarwal   | CLOUDSTACK-4081 : [DOC]Fresh install of cloud platform 
failed with dependency errors on centos5.5 OS   
 |
| Sudha Ponnaganti | CLOUDSTACK-3765 : [packaging][document] unable to 
upgrade cp 4.2 build on centos5.5   
  |
| Unassigned   | CLOUDSTACK-3138 : Flaws in upgrade documentation from 
3.0.2 -> 4.1.0  
  |


Thanks
Animesh