Re: KVM Tools

[Maurice Lawler]

No, nothing in particular. I just noticed in my pervious ventures with 
Cloudstack / XEN / ESXI that there were some tools you could (or were required 
/ suggested by installation guides) I just did not know if there was anything 
like that. 


On Mar 28, 2013, at 1:49 AM, Marcus Sorensen  wrote:

> The qemu guest agent is installed in the guest, that is...
> On Mar 28, 2013 12:48 AM, "Marcus Sorensen"  wrote:
> 
>> What specifically? A large chunk of the tools for VMware/xen are upgraded
>> drivers, which aren't necessary with Linux and already available for other
>> operating systems. There's also the qemu-guest-agent which can be installed
>> in the host to do things like write files from host to guest, but
>> cloudstack doesn't have any functionality around that. Which features were
>> you hoping for?
>> On Mar 28, 2013 12:43 AM, "Maurice Lawler"  wrote:
>> 
>>> Hello,
>>> 
>>> I've been seeing some idle chatter about possible KVM Guest Tools, like
>>> there are for VMware and Xen Server.
>>> 
>>> Has anything be done about this?
>>> 
>>> 
>>> 

Unable to create a deployment for VM

[Maurice Lawler]

Attempting to create a VM from a template I created (Twice) getting this in my 
logs: 

013-03-28 02:07:17,873 WARN  [cloud.api.ApiDispatcher] (Job-Executor-22:job-77) 
class com.cloud.api.ServerApiException : Unable to create a deployment for 
VM[User|i-2-11-VM]
2013-03-28 02:07:17,873 DEBUG [cloud.async.AsyncJobManagerImpl] 
(Job-Executor-22:job-77) Complete async job-77, jobStatus: 2, resultCode: 530, 
result: com.cloud.api.response.ExceptionResponse@2637df06
2013-03-28 02:07:19,339 DEBUG [cloud.cluster.ClusterManagerImpl] 
(Cluster-Heartbeat-1:null) Detected management node left, id:1, nodeIP:0.0.0.0
2013-03-28 02:07:19,339 INFO  [cloud.cluster.ClusterManagerImpl] 
(Cluster-Heartbeat-1:null) Trying to connect to 0.0.0.0
2013-03-28 02:07:19,340 INFO  [cloud.cluster.ClusterManagerImpl] 
(Cluster-Heartbeat-1:null) Management node 1 is detected inactive by timestamp 
but is pingable
2013-03-28 02:07:20,839 DEBUG [cloud.cluster.ClusterManagerImpl] 
(Cluster-Heartbeat-1:null) Detected management node left, id:1, nodeIP:0.0.0.0
2013-03-28 02:07:20,840 INFO  [cloud.cluster.ClusterManagerImpl] 
(Cluster-Heartbeat-1:null) Trying to connect to 0.0.0.0
2013-03-28 02:07:20,840 INFO  [cloud.cluster.ClusterManagerImpl] 
(Cluster-Heartbeat-1:null) Management node 1 is detected inactive by timestamp 
but is pingable
2013-03-28 02:07:21,183 DEBUG [cloud.server.StatsCollector] 
(StatsCollector-2:null) VmStatsCollector is running...
2013-03-28 02:07:21,219 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
(AgentManager-Handler-9:null) Cleanup succeeded. Details null
2013-03-28 02:07:21,219 DEBUG [agent.transport.Request] (StatsCollector-2:null) 
Seq 1-2359860: Received:  { Ans: , MgmtId: 279278805451068, via: 1, Ver: v1, 
Flags: 10, { GetVmStatsAnswer } }
2013-03-28 02:07:21,219 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
(StatsCollector-2:null) Cleanup succeeded. Details null
2013-03-28 02:07:22,339 DEBUG [cloud.cluster.ClusterManagerImpl] 
(Cluster-Heartbeat-1:null) Detected management node left, id:1, nodeIP:0.0.0.0
2013-03-28 02:07:22,340 INFO  [cloud.cluster.ClusterManagerImpl] 
(Cluster-Heartbeat-1:null) Trying to connect to 0.0.0.0
2013-03-28 02:07:22,340 INFO  [cloud.cluster.ClusterManagerImpl] 
(Cluster-Heartbeat-1:null) Management node 1 is detected inactive by timestamp 
but is pingable
2013-03-28 02:07:22,629 DEBUG [cloud.async.AsyncJobManagerImpl] 
(catalina-exec-1:null) Async job-77 completed
2013-03-28 02:07:23,586 DEBUG [storage.secondary.SecondaryStorageManagerImpl] 
(secstorage-1:null) Zone 1 is ready to launch secondary storage VM
2013-03-28 02:07:23,710 DEBUG [cloud.consoleproxy.ConsoleProxyManagerImpl] 
(consoleproxy-1:null) Zone 1 is ready to launch console proxy
2013-03-28 02:07:23,839 DEBUG [cloud.cluster.ClusterManagerImpl] 
(Cluster-Heartbeat-1:null) Detected management node left, id:1, nodeIP:0.0.0.0
2013-03-28 02:07:23,839 INFO  [cloud.cluster.ClusterManagerImpl] 
(Cluster-Heartbeat-1:null) Trying to connect to 0.0.0.0



Lots of: 2013-03-28 02:07:19,339 INFO  [cloud.cluster.ClusterManagerImpl] 
(Cluster-Heartbeat-1:null) Trying to connect to 0.0.0.0 (of course it's no 
really 0.0.0.0) but yeah, not sure how to solve this.

Any thoughts? 

Re: Unable to create a deployment for VM

[Abhinandan Prateek]

It seems you have a cluster of management servers. It is possible that the
host/agents are owned by the the management server that is inactive:

2013-03-28 02:07:22,340 INFO  [cloud.cluster.ClusterManagerImpl]
(Cluster-Heartbeat-1:null) Management node 1 is *detected inactive* by
timestamp but is pingable


-abhi


On 28/03/13 12:41 PM, "Maurice Lawler"  wrote:

>Attempting to create a VM from a template I created (Twice) getting this
>in my logs: 
>
>013-03-28 02:07:17,873 WARN  [cloud.api.ApiDispatcher]
>(Job-Executor-22:job-77) class com.cloud.api.ServerApiException : Unable
>to create a deployment for VM[User|i-2-11-VM]
>2013-03-28 02:07:17,873 DEBUG [cloud.async.AsyncJobManagerImpl]
>(Job-Executor-22:job-77) Complete async job-77, jobStatus: 2, resultCode:
>530, result: com.cloud.api.response.ExceptionResponse@2637df06
>2013-03-28 02:07:19,339 DEBUG [cloud.cluster.ClusterManagerImpl]
>(Cluster-Heartbeat-1:null) Detected management node left, id:1,
>nodeIP:0.0.0.0
>2013-03-28 02:07:19,339 INFO  [cloud.cluster.ClusterManagerImpl]
>(Cluster-Heartbeat-1:null) Trying to connect to 0.0.0.0
>2013-03-28 02:07:19,340 INFO  [cloud.cluster.ClusterManagerImpl]
>(Cluster-Heartbeat-1:null) Management node 1 is detected inactive by
>timestamp but is pingable
>2013-03-28 02:07:20,839 DEBUG [cloud.cluster.ClusterManagerImpl]
>(Cluster-Heartbeat-1:null) Detected management node left, id:1,
>nodeIP:0.0.0.0
>2013-03-28 02:07:20,840 INFO  [cloud.cluster.ClusterManagerImpl]
>(Cluster-Heartbeat-1:null) Trying to connect to 0.0.0.0
>2013-03-28 02:07:20,840 INFO  [cloud.cluster.ClusterManagerImpl]
>(Cluster-Heartbeat-1:null) Management node 1 is detected inactive by
>timestamp but is pingable
>2013-03-28 02:07:21,183 DEBUG [cloud.server.StatsCollector]
>(StatsCollector-2:null) VmStatsCollector is running...
>2013-03-28 02:07:21,219 DEBUG [cloud.vm.VirtualMachineManagerImpl]
>(AgentManager-Handler-9:null) Cleanup succeeded. Details null
>2013-03-28 02:07:21,219 DEBUG [agent.transport.Request]
>(StatsCollector-2:null) Seq 1-2359860: Received:  { Ans: , MgmtId:
>279278805451068, via: 1, Ver: v1, Flags: 10, { GetVmStatsAnswer } }
>2013-03-28 02:07:21,219 DEBUG [cloud.vm.VirtualMachineManagerImpl]
>(StatsCollector-2:null) Cleanup succeeded. Details null
>2013-03-28 02:07:22,339 DEBUG [cloud.cluster.ClusterManagerImpl]
>(Cluster-Heartbeat-1:null) Detected management node left, id:1,
>nodeIP:0.0.0.0
>2013-03-28 02:07:22,340 INFO  [cloud.cluster.ClusterManagerImpl]
>(Cluster-Heartbeat-1:null) Trying to connect to 0.0.0.0
>2013-03-28 02:07:22,340 INFO  [cloud.cluster.ClusterManagerImpl]
>(Cluster-Heartbeat-1:null) Management node 1 is detected inactive by
>timestamp but is pingable
>2013-03-28 02:07:22,629 DEBUG [cloud.async.AsyncJobManagerImpl]
>(catalina-exec-1:null) Async job-77 completed
>2013-03-28 02:07:23,586 DEBUG
>[storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Zone
>1 is ready to launch secondary storage VM
>2013-03-28 02:07:23,710 DEBUG
>[cloud.consoleproxy.ConsoleProxyManagerImpl] (consoleproxy-1:null) Zone 1
>is ready to launch console proxy
>2013-03-28 02:07:23,839 DEBUG [cloud.cluster.ClusterManagerImpl]
>(Cluster-Heartbeat-1:null) Detected management node left, id:1,
>nodeIP:0.0.0.0
>2013-03-28 02:07:23,839 INFO  [cloud.cluster.ClusterManagerImpl]
>(Cluster-Heartbeat-1:null) Trying to connect to 0.0.0.0
>
>
>
>Lots of: 2013-03-28 02:07:19,339 INFO  [cloud.cluster.ClusterManagerImpl]
>(Cluster-Heartbeat-1:null) Trying to connect to 0.0.0.0 (of course it's
>no really 0.0.0.0) but yeah, not sure how to solve this.
>
>Any thoughts? 

Re: [PROPOSAL][CLOUDSTACK-768] ACL on private gateway

[Abhinandan Prateek]

+1, thanks for proposing and working on this feature.

On 28/03/13 11:32 AM, "Jayapal Reddy Uradi"
 wrote:

>I would like to propose the new feature ACL on private gateway.
>This feature is sub feature of the nTier 2.0 apps.
>
>Currently we do not have way to control the traffic on the private
>gateway.
>Using this feature we can configure the ingress/egress ACL on the private
>gateway.
>
>
>Jira Id:
>https://issues.apache.org/jira/browse/CLOUDSTACK-768
>
>FS:
>https://cwiki.apache.org/confluence/display/CLOUDSTACK/ACLs+on+private+GW
>
>Please provide your comments on the above FS.
>
>Thanks,
>Jayapal
>

Re: Review Request: CLOUDSTACK-1156: Limit Primary and Secondary storage for domain/accounts

[Sanjay Tripathi]

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

(Updated March 28, 2013, 8:36 a.m.)


Review request for cloudstack, Devdeep Singh, Nitin Mehta, Sateesh 
Chodapuneedi, mice xia, and Min Chen.


Changes
---

Resolved conflicts with the latest code.


Description
---

CLOUDSTACK-1156: Limit Primary and Secondary storage for domain/accounts

Addition of two new resource types i.e. Primary and Secondary storage space 
in the existing pool of
resource types.
Added methods to set the limits on these resources using updateResourceLimit
API command and to get a count using updateResourceCount. Also added calls 
in the
Templates, Volumes, Snapshots life cycle to check these limits and to 
increment/decrement the new
resource types

Resource Name  :: Resource type number
Primary Storage   10
Secondary Storage 11

Also added jUnit Tests for the same.


This addresses bug CLOUDSTACK-1156.


Diffs (updated)
-

  api/src/com/cloud/configuration/Resource.java 7614c8a 
  api/src/com/cloud/storage/VolumeApiService.java 8517988 
  
api/src/org/apache/cloudstack/api/command/user/resource/UpdateResourceCountCmd.java
 f6d3a98 
  
api/src/org/apache/cloudstack/api/command/user/resource/UpdateResourceLimitCmd.java
 0039f62 
  api/src/org/apache/cloudstack/api/command/user/volume/ResizeVolumeCmd.java 
955727a 
  api/src/org/apache/cloudstack/api/response/AccountResponse.java 9a98a35 
  api/src/org/apache/cloudstack/api/response/ResourceCountResponse.java a7fbbf2 
  api/src/org/apache/cloudstack/api/response/ResourceLimitResponse.java b444e7a 
  
plugins/hypervisors/baremetal/src/com/cloud/baremetal/manager/BareMetalTemplateAdapter.java
 33725f6 
  server/src/com/cloud/alert/AlertManagerImpl.java a45482f 
  server/src/com/cloud/api/ApiResponseHelper.java f33601f 
  server/src/com/cloud/api/query/dao/AccountJoinDaoImpl.java 898bafc 
  server/src/com/cloud/api/query/vo/AccountJoinVO.java cd7231c 
  server/src/com/cloud/configuration/Config.java 1a57a64 
  server/src/com/cloud/resourcelimit/ResourceLimitManagerImpl.java 23c0796 
  server/src/com/cloud/storage/VolumeManager.java af3cbbf 
  server/src/com/cloud/storage/VolumeManagerImpl.java 737ed0a 
  server/src/com/cloud/storage/dao/SnapshotDao.java 0e378a7 
  server/src/com/cloud/storage/dao/SnapshotDaoImpl.java 825b6d5 
  server/src/com/cloud/storage/dao/VolumeDao.java d7a2667 
  server/src/com/cloud/storage/dao/VolumeDaoImpl.java 40ed875 
  server/src/com/cloud/storage/download/DownloadListener.java d4c20cf 
  server/src/com/cloud/storage/download/DownloadMonitorImpl.java 0bc89e3 
  server/src/com/cloud/storage/snapshot/SnapshotManagerImpl.java bacca01 
  server/src/com/cloud/template/HypervisorTemplateAdapter.java 1426421 
  server/src/com/cloud/template/TemplateManagerImpl.java d843dbc 
  server/src/com/cloud/vm/UserVmManagerImpl.java 82a69bd 
  server/test/com/cloud/resourcelimit/ResourceLimitManagerImplTest.java d311ad3 
  server/test/com/cloud/vpc/MockResourceLimitManagerImpl.java b9fc861 
  setup/db/db/schema-40to410.sql 60ad025 
  setup/db/db/schema-410to420.sql 9eed0a6 
  utils/src/com/cloud/utils/UriUtils.java a8b5ccb 

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


Testing
---

Tested life cycle of templates, volumes, snapshots, vm on my local CloudStack 
setup.


Thanks,

Sanjay Tripathi

[master branch issue ]Problem with SystemVMs and Primary Storage in latest Master

[Pranav Saxena]

Hi ,

There seems to be a problem with the latest master branch code though I did not 
happen to see any exception being thrown.

The system VM's don't come up and the primary storage added as part of the zone 
creation wizard does not show up on the host in the XenCenter UI .

Anyone else happened to see this issue ?

Thanks,
Pranav

RE: [master branch issue ]Problem with SystemVMs and Primary Storage in latest Master

[Suresh Sadhu]

Pranav,

While creating primary ,did you select  scope as zone or cluster.

By default its setting the scope as  zone.it won't work. There is no support 
(zone wide primary storage)t for xen ,at this moment supported hypervisor is 
kvm .

so select the scope as cluster.


Regards
Sadhu


-Original Message-
From: Pranav Saxena [mailto:pranav.sax...@citrix.com] 
Sent: 28 March 2013 14:29
To: dev@cloudstack.apache.org
Subject: [master branch issue ]Problem with SystemVMs and Primary Storage in 
latest Master

Hi ,

There seems to be a problem with the latest master branch code though I did not 
happen to see any exception being thrown.

The system VM's don't come up and the primary storage added as part of the zone 
creation wizard does not show up on the host in the XenCenter UI .

Anyone else happened to see this issue ?

Thanks,
Pranav

Re: Review Request: (CLOUDSTACK-1638) Network plugins won't be notified VM migration.

[Hiroaki Kawai]

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

(Updated March 28, 2013, 9:10 a.m.)


Review request for cloudstack, Hugo Trippaers and Chiradeep Vittal.


Changes
---

Updated a patch fully to make every NetworkGuru and NetworkElement would be 
ready for handling migration.
I did `mvn test` runs. As it is hard to test everything, I'd like to ask people 
for testing in a real deployment... 
For Nicira plugin, I extended the database to track the migration phases.


Description
---

The location of the virtual machine is provided by DeployDestination, which 
will be passed in NetworkGuru#reserve and NetworkElement#prepare. 

During the virtual machine migration, it actually changes DeployDestination and 
it looks like that it will tell that event to network components as it has 
NetworkManager#prepareNicForMigration. The problem is that althogh the 
interface has that method, NetworkManagerImpl does not tell the 
DeployDestination changes to network components. 

So IMHO, we need to add calls of NetworkGuru#reserve and NetworkElement#prepare 
in NetworkManagerImpl#prepareNicForMigration . And then, we also need to add 
calls NetworkGuru#release and NetworkElement#release after the migration, 
otherwise the network resources that plugin reserved will be kept even when the 
vm leaves off.

Created a first minimum patch to show the concept.


This addresses bug CLOUDSTACK-1638.


Diffs (updated)
-

  docs/en-US/plugin-niciranvp-tables.xml 4f81655 
  
plugins/network-elements/nicira-nvp/src/com/cloud/network/NiciraNvpNicMappingVO.java
 0779e69 
  
plugins/network-elements/nicira-nvp/src/com/cloud/network/element/NiciraNvpElement.java
 1fcccdb 
  server/src/com/cloud/network/NetworkManager.java 4124b19 
  server/src/com/cloud/network/NetworkManagerImpl.java a98bdd4 
  server/src/com/cloud/network/guru/ControlNetworkGuru.java 934cd70 
  server/src/com/cloud/network/guru/DirectNetworkGuru.java ee824af 
  server/src/com/cloud/network/guru/DirectPodBasedNetworkGuru.java 354d7ed 
  server/src/com/cloud/network/guru/ExternalGuestNetworkGuru.java 24d24f8 
  server/src/com/cloud/network/guru/GuestNetworkGuru.java cebfb08 
  server/src/com/cloud/network/guru/PodBasedNetworkGuru.java b513325 
  server/src/com/cloud/network/guru/StorageNetworkGuru.java 879d0cd 
  server/src/com/cloud/vm/VirtualMachineManagerImpl.java 9230f4a 
  setup/db/create-schema.sql 5b6dc04 

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


Testing
---


Thanks,

Hiroaki Kawai

Re: KVM Tools

[Kelceydamage@bbits]

What most people seem to associate with guest tools is the ability for greater 
console interactions (drag and drop/shared clipboard), as well as API login 
functions in the API.

I myself have brought these up many times, if your interested in other 
features, the. Please describe in detail.

Thanks.

Sent from my iPhone

On Mar 28, 2013, at 12:01 AM, Maurice Lawler  wrote:

> No, nothing in particular. I just noticed in my pervious ventures with 
> Cloudstack / XEN / ESXI that there were some tools you could (or were 
> required / suggested by installation guides) I just did not know if there was 
> anything like that. 
> 
> 
> On Mar 28, 2013, at 1:49 AM, Marcus Sorensen  wrote:
> 
>> The qemu guest agent is installed in the guest, that is...
>> On Mar 28, 2013 12:48 AM, "Marcus Sorensen"  wrote:
>> 
>>> What specifically? A large chunk of the tools for VMware/xen are upgraded
>>> drivers, which aren't necessary with Linux and already available for other
>>> operating systems. There's also the qemu-guest-agent which can be installed
>>> in the host to do things like write files from host to guest, but
>>> cloudstack doesn't have any functionality around that. Which features were
>>> you hoping for?
>>> On Mar 28, 2013 12:43 AM, "Maurice Lawler"  wrote:
>>> 
 Hello,
 
 I've been seeing some idle chatter about possible KVM Guest Tools, like
 there are for VMware and Xen Server.
 
 Has anything be done about this?
 
 
 
> 

Re: Call for 4.2 and 4.1.1 Release Managers!

[Sebastien Goasguen]

On Mar 27, 2013, at 10:20 PM, Chip Childers  wrote:

> On Wed, Mar 27, 2013 at 01:00:52PM -0400, David Nalley wrote:
>> On Thu, Mar 21, 2013 at 4:09 PM, Musayev, Ilya  wrote:
>>> Chip
>>> 
>>> Would you please collaborate as to what release manager does. An examples 
>>> would be nice.
>>> 
>>> Thanks
>>> ilya
>> 
>> 
>> Hi Ilya:
>> 
>> So the short description is 'cat herder'
>> 
>> The real tasks/duties - assuming a feature release:
>> 
>> Act as the release schedule reminder - effectively driving and
>> enforcing the dates we agreed to earlier in the release cycle.
>> Triage/manage the bugs/new features coming into a feature release,
>> ensuring the severity is set appropriately and drawing attention to
>> things that get ignored/dropped.
>> Calling for votes
>> Creating releases (and signing, and getting them uploaded and mirrored)
>> Acting as change control when we start locking down a branch for
>> release - essentially ensuring that changes after a certain period get
>> some minimum level of review and testing, and that we aren't deviating
>> from that. Chip has called himself the human gerrit because of this.
>> 
>> 
>> The point releases are a bit different - there are no new features,
>> and you really are trying to focus on bugfixes, so point releases
>> should be a bit less work. Experience has shown that most folks aren't
>> as happy to fix bugs as to develop new features. So you become much
>> more of a 'attention seeker' - or perhaps 'attention driver' is a
>> better word. - driving attention to things that need to be fixed. It
>> also means spending copious amounts of time in Jira (as you would in a
>> feature release, but this is even more pervasive) You essentially have
>> to look at bugs reported against newer releases and see if they apply
>> - if patches for them are applicable to your release (e.g. if I fix a
>> bug for 4.2 - does that bug apply to 4.1? Should the fix be in 4.1.1?)
>> etc.
>> 
>> --David
>> 
> 
> So with David's description (thanks BTW, it's been a lng $dayjob
> week for me already), we have one volunteer in Animesh (and Animesh,
> does your offer still stand?).  Anyone else want to take a crack at it?
> 
> -chip

As a last resort, I can do RM duties for 4.1.x but I would be happy to pass it 
to someone else.

-sebastien

Re: [master branch issue ]Problem with SystemVMs and Primary Storage in latest Master

[Nitin Mehta]

Yes, I saw the same issue yesterday evening.

On 28/03/13 2:29 PM, "Pranav Saxena"  wrote:

>Hi ,
>
>There seems to be a problem with the latest master branch code though I
>did not happen to see any exception being thrown.
>
>The system VM's don't come up and the primary storage added as part of
>the zone creation wizard does not show up on the host in the XenCenter UI
>.
>
>Anyone else happened to see this issue ?
>
>Thanks,
>Pranav

Re: Unable to create a deployment for VM

[Nitin Mehta]

Can you grep for job-77 in the logs and see if there are any exceptions ?

On 28/03/13 12:42 PM, "Maurice Lawler"  wrote:

>Attempting to create a VM from a template I created (Twice) getting this
>in my logs: 
>
>013-03-28 02:07:17,873 WARN  [cloud.api.ApiDispatcher]
>(Job-Executor-22:job-77) class com.cloud.api.ServerApiException : Unable
>to create a deployment for VM[User|i-2-11-VM]
>2013-03-28 02:07:17,873 DEBUG [cloud.async.AsyncJobManagerImpl]
>(Job-Executor-22:job-77) Complete async job-77, jobStatus: 2, resultCode:
>530, result: com.cloud.api.response.ExceptionResponse@2637df06
>2013-03-28 02:07:19,339 DEBUG [cloud.cluster.ClusterManagerImpl]
>(Cluster-Heartbeat-1:null) Detected management node left, id:1,
>nodeIP:0.0.0.0
>2013-03-28 02:07:19,339 INFO  [cloud.cluster.ClusterManagerImpl]
>(Cluster-Heartbeat-1:null) Trying to connect to 0.0.0.0
>2013-03-28 02:07:19,340 INFO  [cloud.cluster.ClusterManagerImpl]
>(Cluster-Heartbeat-1:null) Management node 1 is detected inactive by
>timestamp but is pingable
>2013-03-28 02:07:20,839 DEBUG [cloud.cluster.ClusterManagerImpl]
>(Cluster-Heartbeat-1:null) Detected management node left, id:1,
>nodeIP:0.0.0.0
>2013-03-28 02:07:20,840 INFO  [cloud.cluster.ClusterManagerImpl]
>(Cluster-Heartbeat-1:null) Trying to connect to 0.0.0.0
>2013-03-28 02:07:20,840 INFO  [cloud.cluster.ClusterManagerImpl]
>(Cluster-Heartbeat-1:null) Management node 1 is detected inactive by
>timestamp but is pingable
>2013-03-28 02:07:21,183 DEBUG [cloud.server.StatsCollector]
>(StatsCollector-2:null) VmStatsCollector is running...
>2013-03-28 02:07:21,219 DEBUG [cloud.vm.VirtualMachineManagerImpl]
>(AgentManager-Handler-9:null) Cleanup succeeded. Details null
>2013-03-28 02:07:21,219 DEBUG [agent.transport.Request]
>(StatsCollector-2:null) Seq 1-2359860: Received:  { Ans: , MgmtId:
>279278805451068, via: 1, Ver: v1, Flags: 10, { GetVmStatsAnswer } }
>2013-03-28 02:07:21,219 DEBUG [cloud.vm.VirtualMachineManagerImpl]
>(StatsCollector-2:null) Cleanup succeeded. Details null
>2013-03-28 02:07:22,339 DEBUG [cloud.cluster.ClusterManagerImpl]
>(Cluster-Heartbeat-1:null) Detected management node left, id:1,
>nodeIP:0.0.0.0
>2013-03-28 02:07:22,340 INFO  [cloud.cluster.ClusterManagerImpl]
>(Cluster-Heartbeat-1:null) Trying to connect to 0.0.0.0
>2013-03-28 02:07:22,340 INFO  [cloud.cluster.ClusterManagerImpl]
>(Cluster-Heartbeat-1:null) Management node 1 is detected inactive by
>timestamp but is pingable
>2013-03-28 02:07:22,629 DEBUG [cloud.async.AsyncJobManagerImpl]
>(catalina-exec-1:null) Async job-77 completed
>2013-03-28 02:07:23,586 DEBUG
>[storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Zone
>1 is ready to launch secondary storage VM
>2013-03-28 02:07:23,710 DEBUG
>[cloud.consoleproxy.ConsoleProxyManagerImpl] (consoleproxy-1:null) Zone 1
>is ready to launch console proxy
>2013-03-28 02:07:23,839 DEBUG [cloud.cluster.ClusterManagerImpl]
>(Cluster-Heartbeat-1:null) Detected management node left, id:1,
>nodeIP:0.0.0.0
>2013-03-28 02:07:23,839 INFO  [cloud.cluster.ClusterManagerImpl]
>(Cluster-Heartbeat-1:null) Trying to connect to 0.0.0.0
>
>
>
>Lots of: 2013-03-28 02:07:19,339 INFO  [cloud.cluster.ClusterManagerImpl]
>(Cluster-Heartbeat-1:null) Trying to connect to 0.0.0.0 (of course it's
>no really 0.0.0.0) but yeah, not sure how to solve this.
>
>Any thoughts? 

RE: [master branch issue ]Problem with SystemVMs and Primary Storage in latest Master

[Pranav Saxena]

Ok , Suresh was right in pointing that out that we need to select "cluster " 
right now as the scope for primary storage with xenserver as the hypervisor . 
With "Zone-wide" , we see this error . Perhaps I can introduce a check in the 
UI for the scope depending upon the hypervisor type (xen/KVM) since we don't 
support zone-wide primary storage for Xenserver as of now.

My set up is working fine now.

Thanks,
Pranav

-Original Message-
From: Nitin Mehta [mailto:nitin.me...@citrix.com] 
Sent: Thursday, March 28, 2013 3:17 PM
To: dev@cloudstack.apache.org
Cc: Abhinandan Prateek
Subject: Re: [master branch issue ]Problem with SystemVMs and Primary Storage 
in latest Master

Yes, I saw the same issue yesterday evening.

On 28/03/13 2:29 PM, "Pranav Saxena"  wrote:

>Hi ,
>
>There seems to be a problem with the latest master branch code though I 
>did not happen to see any exception being thrown.
>
>The system VM's don't come up and the primary storage added as part of 
>the zone creation wizard does not show up on the host in the XenCenter 
>UI .
>
>Anyone else happened to see this issue ?
>
>Thanks,
>Pranav

RE: Question pertaining to the Support of ACL deny rules

[Kishan Kavala]

Chandan,
  User can assign any number as rule priority. But the number has to be unique 
within the container. Two ACLs in the same container cannot have same priority 
number.
e.g.
ACL1 - number 10
ACL2 - number 40
ACL3 - number 30

In the above example, ACL1 will have the highest priority followed by ACL3 and 
ACL2.

Priority number of the deleted rule can be re-used. Priority number can be 
modified using updateNetworkACL API. 

Same NetworkACLContainer can be assigned to multiple tiers (belonging to two 
different VPCs also) as long as they belong to same account.

Regards,
Kishan


> -Original Message-
> From: Chandan Purushothama
> Sent: Thursday, 28 March 2013 5:19 AM
> To: dev@cloudstack.apache.org; Kishan Kavala
> Subject: RE: Question pertaining to the Support of ACL deny rules
> 
> Kishan,
> 
> Can NetworkACLContainer be used for two network tiers belonging to two
> different VPCs?
> 
> Thank you,
> Chandan.
> 
> -Original Message-
> From: Chandan Purushothama [mailto:chandan.purushoth...@citrix.com]
> Sent: Wednesday, March 27, 2013 4:37 PM
> To: dev@cloudstack.apache.org; Kishan Kavala
> Subject: RE: Question pertaining to the Support of ACL deny rules
> 
> Kishan,
> 
> I referred to your FS at
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Support+ACL+de
> ny+rules . May I know how does a user choose a rule priority number. Do we
> allow two rules with the same priority for any reason?  Can the user re-use
> the priority number of the deleted rule? Can the User shuffle the priorities
> between rules at any time? Can more information pertaining to the rule
> number priority be mentioned in your functional specification,
> 
> Thank you,
> Chandan.
> 
> -Original Message-
> From: Chandan Purushothama [mailto:chandan.purushoth...@citrix.com]
> Sent: Monday, March 04, 2013 10:00 AM
> To: cloudstack-...@incubator.apache.org
> Cc: Kishan Kavala
> Subject: RE: Question pertaining to the Support of ACL deny rules
> 
> May I know how can I use this feature in CloudStack. I mean, What do I need
> to do on CloudStack to specify multiple ACL deny rules?
> 
> Thank you,
> Chandan.
> 
> -Original Message-
> From: Pranav Saxena [mailto:pranav.sax...@citrix.com]
> Sent: Friday, March 01, 2013 9:35 PM
> To: cloudstack-...@incubator.apache.org
> Cc: Kishan Kavala
> Subject: RE: Question pertaining to the Support of ACL deny rules
> 
> This feature is also under development and I believe , Kishan is yet to check
> in his code . After that we'll be adding the UI support for this and then you 
> 'll
> be able to do it from the UI itself.
> 
> Thanks,
> Pranav
> 
> -Original Message-
> From: Chandan Purushothama [mailto:chandan.purushoth...@citrix.com]
> Sent: Saturday, March 02, 2013 8:39 AM
> To: cloudstack-...@incubator.apache.org
> Cc: Kishan Kavala
> Subject: Question pertaining to the Support of ACL deny rules
> 
> I referred to the feature presented at
> https://issues.apache.org/jira/browse/CLOUDSTACK-763  . May I know how
> can I use this feature in CloudStack. I mean, What do I need to do on
> CloudStack to specify multiple ACL deny rules?
> 
> Thank you,
> Chandan.

RE: [master branch issue ]Problem with SystemVMs and Primary Storage in latest Master

[Srikanteswararao Talluri]

We might need to disable scope field for non -KVM zones to avoid such mistakes.

Thanks,
~Talluri

> -Original Message-
> From: Suresh Sadhu [mailto:suresh.sa...@citrix.com]
> Sent: Thursday, March 28, 2013 2:35 PM
> To: dev@cloudstack.apache.org
> Subject: RE: [master branch issue ]Problem with SystemVMs and Primary Storage
> in latest Master
> 
> Pranav,
> 
> While creating primary ,did you select  scope as zone or cluster.
> 
> By default its setting the scope as  zone.it won't work. There is no support 
> (zone
> wide primary storage)t for xen ,at this moment supported hypervisor is kvm .
> 
> so select the scope as cluster.
> 
> 
> Regards
> Sadhu
> 
> 
> -Original Message-
> From: Pranav Saxena [mailto:pranav.sax...@citrix.com]
> Sent: 28 March 2013 14:29
> To: dev@cloudstack.apache.org
> Subject: [master branch issue ]Problem with SystemVMs and Primary Storage in
> latest Master
> 
> Hi ,
> 
> There seems to be a problem with the latest master branch code though I did
> not happen to see any exception being thrown.
> 
> The system VM's don't come up and the primary storage added as part of the
> zone creation wizard does not show up on the host in the XenCenter UI .
> 
> Anyone else happened to see this issue ?
> 
> Thanks,
> Pranav

Re: [DOCS] Can't build Japanese docs

[Sebastien Goasguen]

On Mar 28, 2013, at 1:02 AM, Hiroaki KAWAI  wrote:

> I fixed those on transifex. Please feel free to tell me if you still
> have trouble in building ja-JP docs. :-)

thanks, I pulled all new translations. I am not sure what you did in transifex 
but it did not fix the issue :)

I ended fixing it in remove-vpx.xml , the  tags need to be on a new line…

Feel free to have a look at the runbook in transifex, it needs a little more 
love in Japanese (couple hours of work :) ).

-sebastien


> 
> Thanks
> 
> (2013/03/24 19:28), Sebastien Goasguen wrote:
>> I filed https://issues.apache.org/jira/browse/CLOUDSTACK-1796
>> 
>> I can't publican build japanese docs. I managed to fix chinese and 
>> portuguese.
>> 
>> But I cannot figure out how to edit the problematic string in the .po file 
>> to solve the issue.
>> 
>> Anyone cares to take a look ?
>> 
>> -sebastien
>> 
> 

Re: [master branch issue ]Problem with SystemVMs and Primary Storage in latest Master

[Chip Childers]

On Mar 28, 2013, at 6:00 AM, Pranav Saxena  wrote:

> Ok , Suresh was right in pointing that out that we need to select "cluster " 
> right now as the scope for primary storage with xenserver as the hypervisor .

Sounds like we should actually have the default behavior match the
previous versions, and make cluster the default.


> With "Zone-wide" , we see this error . Perhaps I can introduce a check in the 
> UI for the scope depending upon the hypervisor type (xen/KVM) since we don't 
> support zone-wide primary storage for Xenserver as of now.

+1

>
> My set up is working fine now.
>
> Thanks,
> Pranav
>
> -Original Message-
> From: Nitin Mehta [mailto:nitin.me...@citrix.com]
> Sent: Thursday, March 28, 2013 3:17 PM
> To: dev@cloudstack.apache.org
> Cc: Abhinandan Prateek
> Subject: Re: [master branch issue ]Problem with SystemVMs and Primary Storage 
> in latest Master
>
> Yes, I saw the same issue yesterday evening.
>
> On 28/03/13 2:29 PM, "Pranav Saxena"  wrote:
>
>> Hi ,
>>
>> There seems to be a problem with the latest master branch code though I
>> did not happen to see any exception being thrown.
>>
>> The system VM's don't come up and the primary storage added as part of
>> the zone creation wizard does not show up on the host in the XenCenter
>> UI .
>>
>> Anyone else happened to see this issue ?
>>
>> Thanks,
>> Pranav
>
>

RE: [master branch issue ]Problem with SystemVMs and Primary Storage in latest Master

[Srikanteswararao Talluri]

> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Thursday, March 28, 2013 5:24 PM
> To: 
> Subject: Re: [master branch issue ]Problem with SystemVMs and Primary Storage
> in latest Master
> 
> On Mar 28, 2013, at 6:00 AM, Pranav Saxena 
> wrote:
> 
> > Ok , Suresh was right in pointing that out that we need to select "cluster 
> > " right
> now as the scope for primary storage with xenserver as the hypervisor .
> 
> Sounds like we should actually have the default behavior match the previous
> versions, and make cluster the default.

+1

> 
> 
> > With "Zone-wide" , we see this error . Perhaps I can introduce a check in 
> > the UI
> for the scope depending upon the hypervisor type (xen/KVM) since we don't
> support zone-wide primary storage for Xenserver as of now.
> 
> +1
> 
> >
> > My set up is working fine now.
> >
> > Thanks,
> > Pranav
> >
> > -Original Message-
> > From: Nitin Mehta [mailto:nitin.me...@citrix.com]
> > Sent: Thursday, March 28, 2013 3:17 PM
> > To: dev@cloudstack.apache.org
> > Cc: Abhinandan Prateek
> > Subject: Re: [master branch issue ]Problem with SystemVMs and Primary
> > Storage in latest Master
> >
> > Yes, I saw the same issue yesterday evening.
> >
> > On 28/03/13 2:29 PM, "Pranav Saxena"  wrote:
> >
> >> Hi ,
> >>
> >> There seems to be a problem with the latest master branch code though
> >> I did not happen to see any exception being thrown.
> >>
> >> The system VM's don't come up and the primary storage added as part
> >> of the zone creation wizard does not show up on the host in the
> >> XenCenter UI .
> >>
> >> Anyone else happened to see this issue ?
> >>
> >> Thanks,
> >> Pranav
> >
> >

[DISCUSS][TRANSLATION] commit to master or not ?

[Sebastien Goasguen]

Hi,

I have been pulling all translations (docs and UI) and committing them in 4.1 
branch to make the deadline.

I have not yet committed them to master and now I am wondering if we should.

There would be tons of small files pushed in master.

-Sebastien

Re: VI Java API Question

[Chip Childers]

On Wed, Mar 27, 2013 at 11:54:53PM -0600, Mike Tutkowski wrote:
> Hi,
> 
> I was wondering if anyone could answer this question for me.  I've been
> looking at all sorts of properties of various VI Java Objects to find out
> how to do this and don't see any answers on the web either.

Mike,

Just so that I understand.  Are you using the VIJava [1] SDK (which is
*not* from VMware), or are you using the VMware vSphere Java SDK [2]
(which is). Currently we use the VMware vSphere Java SDK within the
VMware HV plugin.

-chip

[1] http://vijava.sourceforge.net/
[2] http://communities.vmware.com/community/vmtn/developer/forums/java_toolkit

Re: VI Java API Question

[Chip Childers]

On Thu, Mar 28, 2013 at 9:20 AM, Chip Childers
 wrote:
> On Wed, Mar 27, 2013 at 11:54:53PM -0600, Mike Tutkowski wrote:
>> Hi,
>>
>> I was wondering if anyone could answer this question for me.  I've been
>> looking at all sorts of properties of various VI Java Objects to find out
>> how to do this and don't see any answers on the web either.
>
> Mike,
>
> Just so that I understand.  Are you using the VIJava [1] SDK (which is
> *not* from VMware), or are you using the VMware vSphere Java SDK [2]
> (which is). Currently we use the VMware vSphere Java SDK within the
> VMware HV plugin.
>
> -chip
>
> [1] http://vijava.sourceforge.net/
> [2] http://communities.vmware.com/community/vmtn/developer/forums/java_toolkit

Also, you might consider this book:
http://www.amazon.com/gp/product/0137153635?ie=UTF8&tag=doublecloudor-20&linkCode=as2&camp=1789&creative=9325&creativeASIN=0137153635

I found it very useful a couple of years back.

-chip

Re: [ACS4.2] master blockers

[Chip Childers]

Abhinandan,

Why the push on master?  We should probably focus on 4.0.2 and 4.1.0.  I
know that testing is happening against master for some features, but
those are probably best handled in feature-specific threads.  I'm
concerned that this might be diluting everyone's focus on the active
releases.

-chip

On Thu, Mar 28, 2013 at 05:04:37AM +, Abhinandan Prateek wrote:
> Once again a reminder to close the following blockers and criticals in
> master, if you are assigned but cannot figure out the issue please reach
> out.
> 
> >CLOUDSTACK-1687  Mice Xia
> >CLOUDSTACK-1677  Kelven Yang
> >CLOUDSTACK-1774  Rohit Yadav
> >CLOUDSTACK-1721  Prachi Damle
> >CLOUDSTACK-1613  Bharat Kumar
> >CLOUDSTACK-1610  frank zhang
> >CLOUDSTACK-1591  edison su
> >CLOUDSTACK-1732  Sheng Yang
> >CLOUDSTACK-1739  Bharat Kumar
> >CLOUDSTACK-1392  edison su
> >CLOUDSTACK-1404  edison su
> >CLOUDSTACK-1753  Brian Federle
> >CLOUDSTACK-1730  Jessica Wang
> >CLOUDSTACK-1707  Mice Xia
> >CLOUDSTACK-1672  Mice Xia
> >CLOUDSTACK-1513  edison su
> >CLOUDSTACK-1728  Jessica Wang
> >CLOUDSTACK-1619  frank zhang
> >CLOUDSTACK-1618  frank zhang
> >CLOUDSTACK-1607  Nitin Mehta
> >CLOUDSTACK-1635  edison su
> >CLOUDSTACK-1614  frank zhang
> >CLOUDSTACK-1616  Jessica Wang
> >CLOUDSTACK-1639  edison su
> >CLOUDSTACK-1602  edison su
> >CLOUDSTACK-1737  Anthony Xu
> >CLOUDSTACK-1698  Mice Xia
> >CLOUDSTACK-1731  Jessica Wang
> >CLOUDSTACK-1440  frank zhang
> >CLOUDSTACK-1405  edison su
> >CLOUDSTACK-1646  Bharat Kumar
> >CLOUDSTACK-1534  Bharat Kumar
> >
> 
> -abhi
> >
> 
> 

RE: [ACS4.1] blockers

[Kishan Kavala]

I'm looking into CLOUDSTACK-1819. I'll be able to close it by Friday.

> -Original Message-
> From: Abhinandan Prateek [mailto:abhinandan.prat...@citrix.com]
> Sent: Thursday, 28 March 2013 10:28 AM
> To: dev@cloudstack.apache.org
> Cc: cloudstack dev
> Subject: Re: [ACS4.1] blockers
> 
> There is some encouraging movement on 4.1 issues but still we have some of
> the blockers and criticals open:
> 
> 
> CLOUDSTACK-1819   Kishan Kavala
> CLOUDSTACK-1805   Kelven Yang
> CLOUDSTACK-1755   Sheng Yang
> CLOUDSTACK-1664   Murali Reddy
> 
> 
> 
> -abhi
> 
> 
> On 27/03/13 8:03 PM, "Abhinandan Prateek"
> 
> wrote:
> 
> >Text only list of blockers and criticals in 4.1 branch, please treat
> >these with expected urgency:
> >
> >CLOUDSTACK-1819  Kishan Kavala
> >CLOUDSTACK-1811  Kelven Yang
> >CLOUDSTACK-1810  Min Chen
> >CLOUDSTACK-1805  Kelven Yang
> >CLOUDSTACK-1776  Kelven Yang
> >CLOUDSTACK-1755  Sheng Yang
> >CLOUDSTACK-1673  Murali Reddy
> >CLOUDSTACK-1664  Kelven Yang
> >
> >
> >-abhi
> >
> >On 27/03/13 7:46 PM, "Chip Childers"  wrote:
> >
> >>
> >>I'm sorry, but I can't read this email's content particularly well...
> >>Can you please be sure to email in plain text?
> >>
> >>On Wed, Mar 27, 2013 at 11:28:26AM +, Abhinandan Prateek wrote:
> >>> Team,
> >>>   I think the 4.1 RC is not yet made as there are still several
> >>>blockers and criticals, please treat them as high priority.
> >>> T   Key Summary AssigneeReporterP   Status
> >>>Resolution  Created Updated Due
> >>>
> >>> 1819>[Bug] >>>iss
> >>>u
> >>>es.apache.org/jira/browse/CLOUDSTACK-1819>
> >>>CLOUDSTACK-
> 1819 
> >>>
> >>> AWS Regions - Issues seen when trying to move a zone from 1 region
> >>>to another.
> >>> Kishan
> >>>Kavala >>>sha
> >>>n
>    Sangeetha
> Hariharan e=s
> a
> ngeethah> [Critical]  [Open]  OpenUnresolved  27/Mar/13
>   27/Mar/13
> >>>
> >>>
> >>>Actions >>>cti
> >>>o
> >>>nsAndOperations?atl_token=A5KQ-2QAV-T4JA-
> FDED|806c180e1de55e6f3cb672c
> >>>8d7
> >>>1
> >>>d59537d3fcce7|lin>
> >>>
> >>>
> >>> 1812>[Bug] >>>iss
> >>>u
> >>>es.apache.org/jira/browse/CLOUDSTACK-1812>
> >>>CLOUDSTACK-
> 1812 
> >>>
> >>> create physical network fails while creating basic
> >>>zone
> >>> Venkata Siva Vijayendra
> >>>Bhamidipati >>>me=
> >>>v
> >>>ijayendrabvs>  Srikanteswararao
> >>>Talluri >>>all
> >>>u
> >>>ri>   [Blocker]   [Open]  OpenUnresolved  26/Mar/13
> >>>27/Mar/13
> >>>
> >>>
> >>>Actions >>>cti
> >>>o
> >>>nsAndOperations?atl_token=A5KQ-2QAV-T4JA-
> FDED|806c180e1de55e6f3cb672c
> >>>8d7
> >>>1
> >>>d59537d3fcce7|lin>
> >>>
> >>>
> >>> 1811>[Bug] >>>iss
> >>>u
> >>>es.apache.org/jira/browse/CLOUDSTACK-1811>
> >>>CLOUDSTACK-
> 1811 
> >>>
> >>> Upgrade 4.0->4.1 - When upgrade scripts fail , component loading
> >>>continues and management server
> >>>starts.
> >>> Kelven
> >>>Yang v
> >>>eny
> 
> >>>Sangeetha
> >>>Hariharan >>>=sa
> >>>n
> >>>geethah> [Critical]  [Reopened]  ReopenedUnresolved
> >>>26/Mar/13   27/Mar/13
> >>>
> >>>
> >>>Actions >>>cti
> >>>o
> >>>nsAndOperations?atl_token=A5KQ-2QAV-T4JA-
> FDED|806c180e1de55e6f3cb672c
> >>>8d7
> >>>1
> >>>d59537d3fcce7|lin>
> >>>
> >>>
> >>> 1810>[Bug] >>>iss
> >>>u
> >>>es.apache.org/jira/browse/CLOUDSTACK-1810>
> >>>CLOUDSTACK-
> 1810 
> >>>
> >>> listTemplate API with templatefilter=featured|community is not
> >>>returning any
> >>>list
> >>> Min
> >>>Chen nc
> >>>hen
> >>>0
> >>>7> Srikanteswararao
> >>>Talluri >>>all
> >>>u
> 

[DISCUSS][DOCS] Docs as their own repo? Was: [DISCUSS][TRANSLATION] commit to master or not ?

[Chip Childers]

On Thu, Mar 28, 2013 at 08:02:59AM -0400, Sebastien Goasguen wrote:
> Hi,
> 
> I have been pulling all translations (docs and UI) and committing them in 4.1 
> branch to make the deadline.
> 
> I have not yet committed them to master and now I am wondering if we should.
> 
> There would be tons of small files pushed in master.
> 
> -Sebastien

Before we get to this, I have a broader question:  Do we want to move
the docs to their own git repo?  We manage them with different rules,
especially WRT code freeze and whatnot.  This translation question just
adds to the logic to pull the repo apart.

-chip

Re: CS4 AWS S3 support

[Chip Childers]

On Thu, Mar 28, 2013 at 12:27:33PM +, Asmita Vagyani wrote:
> By when do you think Cloudstack 4 will be supporting S3 AWS APIs fully? Which 
> version of Cloudstack?
> And I have raised JIRA defects 
> https://issues.apache.org/jira/browse/CLOUDSTACK-1821
> https://issues.apache.org/jira/browse/CLOUDSTACK-1807
> 
> Can I get some fix for this or work-around.
> 
> 
> Thanks and Regards.
> 
> Asmita 

Asmita,

I've moved this discussion to the dev list.  

BTW - patches are *always* welcome if you want to help make the support
work the way you expect it.

Devs - anyone want to look at the issues above?

-chip

Re: [ACS41] Release Status - Bugs to kill!

[Murali Reddy]

On 27/03/13 9:49 PM, "Chip Childers"  wrote:

>On Wed, Mar 27, 2013 at 03:39:25PM +, Murali Reddy wrote:
>> On 27/03/13 8:04 PM, "Chip Childers"  wrote:
>> 
>> >
>> >Murali Reddy -
>> >  CLOUDSTACK-1673 AWS Regions - Events - User disable event does not
>> >include the UUID of the user that was disabled.
>> >
>> >  Murali, you mentioned that you were working on a fix for this.  You
>> >  happened to note that you would have it by the 20th.  Having any
>>luck?
>> 
>> 
>> Sorry on the delay. Though I have fix ready, I can not fully test it
>> because most of the events are not generated due to bug CLOUDSTACK-1664.
>> Moreover I do not think its critical bug. I have left below comment in
>>the
>> bug and marked as major. I can fix this bug if required only after fix
>>for
>> CLOUDSTACK-1664 is checked-in.
>> 
>> "Do not think its critical issue in the context of Regions. While
>>syncing
>> account/user/domain information across the regions using event bus is
>>just
>> one implementation option. User provisioning system's like portals can
>> directly create account/user/domains across regions with out need of
>>event
>> bus.
>> 
>> Even if one uses event bus, there are other implementation options with
>> which once achieve this. For eg, when User/Account/Domain create event
>> occurs, consumers can query list of account/domain/accounts details in
>>the
>> region which generated the event and figure the details of new object
>> created."
>> 
>
>Thanks for the reply.  Assuming that Kelvin's patch for 1664 is actually
>in the
>set of fixes I already applied to 4.1, does that mean that you can test
>and resolve 1673 now?  I see your point about this not being the only
>implementation model for regions, but it is the one that's being
>included as the reference approach for 4.1.  Not syncing a disable event
>sounds like a potential security hole.
>
>Unless anyone objects, and based on the logic above, I'd still consider
>1673 as a critical fix for 4.1.
>
>-chip
>

Ok, I can fix bug 1673 for 4.1 but I do not see any security issue with
1673. There bug is about the events published on the event bus, does not
have specific information (UUID) on which user/account action is taken.
Did you mean issue reported in 1664 is security issue? There are no events
generated at all by CloudStack for account enable etc.

On 1673, I wasted some time testing this issue on master, looks like
changes for CLOUDSTACK-1664 are not in master yet. I will test with 4.1,
and see if I can close this bug by EOD today.

Re: [ACS41] Release Status - Bugs to kill!

[Chip Childers]

On Thu, Mar 28, 2013 at 01:33:15PM +, Murali Reddy wrote:
> On 27/03/13 9:49 PM, "Chip Childers"  wrote:
> 
> >On Wed, Mar 27, 2013 at 03:39:25PM +, Murali Reddy wrote:
> >> On 27/03/13 8:04 PM, "Chip Childers"  wrote:
> >> 
> >> >
> >> >Murali Reddy -
> >> >  CLOUDSTACK-1673 AWS Regions - Events - User disable event does not
> >> >include the UUID of the user that was disabled.
> >> >
> >> >  Murali, you mentioned that you were working on a fix for this.  You
> >> >  happened to note that you would have it by the 20th.  Having any
> >>luck?
> >> 
> >> 
> >> Sorry on the delay. Though I have fix ready, I can not fully test it
> >> because most of the events are not generated due to bug CLOUDSTACK-1664.
> >> Moreover I do not think its critical bug. I have left below comment in
> >>the
> >> bug and marked as major. I can fix this bug if required only after fix
> >>for
> >> CLOUDSTACK-1664 is checked-in.
> >> 
> >> "Do not think its critical issue in the context of Regions. While
> >>syncing
> >> account/user/domain information across the regions using event bus is
> >>just
> >> one implementation option. User provisioning system's like portals can
> >> directly create account/user/domains across regions with out need of
> >>event
> >> bus.
> >> 
> >> Even if one uses event bus, there are other implementation options with
> >> which once achieve this. For eg, when User/Account/Domain create event
> >> occurs, consumers can query list of account/domain/accounts details in
> >>the
> >> region which generated the event and figure the details of new object
> >> created."
> >> 
> >
> >Thanks for the reply.  Assuming that Kelvin's patch for 1664 is actually
> >in the
> >set of fixes I already applied to 4.1, does that mean that you can test
> >and resolve 1673 now?  I see your point about this not being the only
> >implementation model for regions, but it is the one that's being
> >included as the reference approach for 4.1.  Not syncing a disable event
> >sounds like a potential security hole.
> >
> >Unless anyone objects, and based on the logic above, I'd still consider
> >1673 as a critical fix for 4.1.
> >
> >-chip
> >
> 
> Ok, I can fix bug 1673 for 4.1 but I do not see any security issue with
> 1673. There bug is about the events published on the event bus, does not
> have specific information (UUID) on which user/account action is taken.
> Did you mean issue reported in 1664 is security issue? There are no events
> generated at all by CloudStack for account enable etc.
> 
> On 1673, I wasted some time testing this issue on master, looks like
> changes for CLOUDSTACK-1664 are not in master yet. I will test with 4.1,
> and see if I can close this bug by EOD today.

It's possible that I'm misinterpreting the effect of 1673, specifically
I assumed that it meant that a user/account being disabled in one region
wouldn't propagate to the other region(s).  If that's not the case, then
this may certainly be a nice to have.  I defer to your judgement, but in
either case a fix would be great...  ;-)

-chip

Re: [ACS4.2] master blockers

[Abhinandan Prateek]

I think both the branches are important, yes 4.1 is close to release and
people assigned issues should give priority to 4.1.
There are also many people trying to test there features in master and
unstable master is resulting in wasted cycles.

Having said that I guess people having issues assigned in both the
branches should focus on 4.1 issues first before moving to 4.2 bugs.

-abhi


On 28/03/13 6:53 PM, "Chip Childers"  wrote:

>Abhinandan,
>
>Why the push on master?  We should probably focus on 4.0.2 and 4.1.0.  I
>know that testing is happening against master for some features, but
>those are probably best handled in feature-specific threads.  I'm
>concerned that this might be diluting everyone's focus on the active
>releases.
>
>-chip
>
>On Thu, Mar 28, 2013 at 05:04:37AM +, Abhinandan Prateek wrote:
>> Once again a reminder to close the following blockers and criticals in
>> master, if you are assigned but cannot figure out the issue please reach
>> out.
>> 
>> >CLOUDSTACK-1687 Mice Xia
>> >CLOUDSTACK-1677 Kelven Yang
>> >CLOUDSTACK-1774 Rohit Yadav
>> >CLOUDSTACK-1721 Prachi Damle
>> >CLOUDSTACK-1613 Bharat Kumar
>> >CLOUDSTACK-1610 frank zhang
>> >CLOUDSTACK-1591 edison su
>> >CLOUDSTACK-1732 Sheng Yang
>> >CLOUDSTACK-1739 Bharat Kumar
>> >CLOUDSTACK-1392 edison su
>> >CLOUDSTACK-1404 edison su
>> >CLOUDSTACK-1753 Brian Federle
>> >CLOUDSTACK-1730 Jessica Wang
>> >CLOUDSTACK-1707 Mice Xia
>> >CLOUDSTACK-1672 Mice Xia
>> >CLOUDSTACK-1513 edison su
>> >CLOUDSTACK-1728 Jessica Wang
>> >CLOUDSTACK-1619 frank zhang
>> >CLOUDSTACK-1618 frank zhang
>> >CLOUDSTACK-1607 Nitin Mehta
>> >CLOUDSTACK-1635 edison su
>> >CLOUDSTACK-1614 frank zhang
>> >CLOUDSTACK-1616 Jessica Wang
>> >CLOUDSTACK-1639 edison su
>> >CLOUDSTACK-1602 edison su
>> >CLOUDSTACK-1737 Anthony Xu
>> >CLOUDSTACK-1698 Mice Xia
>> >CLOUDSTACK-1731 Jessica Wang
>> >CLOUDSTACK-1440 frank zhang
>> >CLOUDSTACK-1405 edison su
>> >CLOUDSTACK-1646 Bharat Kumar
>> >CLOUDSTACK-1534 Bharat Kumar
>> >
>> 
>> -abhi
>> >
>> 
>> 

Review Request: Cloudmonkey requester.py change to return clearer errors and implement a logic change for async calls.

[Funs Kessen]

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

Review request for cloudstack and Rohit Yadav.


Description
---

Change to requester.py to make it give back the actual error that was thrown by 
the API (the HTTPError bit). The rest is to catch the correct result code and 
act accordingly on async requests. Initially async requests seemed to work 
because of the sleep that was introduced before the second call and usually the 
api would be able to respond within the sleep, the issue was however that if a 
call would take longer another request would be spawned due to the recursive 
call that was done on monkeyrequest, and so re-curse on itself, a side effect 
of this was that it never gave the output of the result, but rather that of the 
initial response for calls that would take longer. A nice side effect is that 
the script no longer waits the interval for every call it makes.


Diffs
-

  tools/cli/cloudmonkey/requester.py 5c4cd1e 

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


Testing
---

I have two scripts, the first monkey.sh, which creates a complete zone with 
basic networking and waits till the systevms have succesfully booted. The other 
a script called monkey-clean.sh which tears the entire stack down using 
cloudmonkey. So this includes setting up the zone, physical networking, 
networking, pod, cluster, hypervisors, primary and secondary storage.


Thanks,

Funs Kessen

Re: [ACS4.2] master blockers

[Chip Childers]

On Thu, Mar 28, 2013 at 01:44:30PM +, Abhinandan Prateek wrote:
> I think both the branches are important, yes 4.1 is close to release and
> people assigned issues should give priority to 4.1.
> There are also many people trying to test there features in master and
> unstable master is resulting in wasted cycles.
> 
> Having said that I guess people having issues assigned in both the
> branches should focus on 4.1 issues first before moving to 4.2 bugs.

Yes, and it seems to me that discussions around prioritization of bugs
in master should be threaded by *feature* primarily (excepting general
blockers that *break* the build/tests).

Re: Call for 4.2 and 4.1.1 Release Managers!

[Chip Childers]

On Wed, Mar 27, 2013 at 01:00:52PM -0400, David Nalley wrote:
> On Thu, Mar 21, 2013 at 4:09 PM, Musayev, Ilya  wrote:
> > Chip
> >
> > Would you please collaborate as to what release manager does. An examples 
> > would be nice.
> >
> > Thanks
> > ilya
> 
> 
> Hi Ilya:
> 
> So the short description is 'cat herder'
> 
> The real tasks/duties - assuming a feature release:
> 
> Act as the release schedule reminder - effectively driving and
> enforcing the dates we agreed to earlier in the release cycle.
> Triage/manage the bugs/new features coming into a feature release,
> ensuring the severity is set appropriately and drawing attention to
> things that get ignored/dropped.
> Calling for votes
> Creating releases (and signing, and getting them uploaded and mirrored)
> Acting as change control when we start locking down a branch for
> release - essentially ensuring that changes after a certain period get
> some minimum level of review and testing, and that we aren't deviating
> from that. Chip has called himself the human gerrit because of this.
> 
> 
> The point releases are a bit different - there are no new features,
> and you really are trying to focus on bugfixes, so point releases
> should be a bit less work. Experience has shown that most folks aren't
> as happy to fix bugs as to develop new features. So you become much
> more of a 'attention seeker' - or perhaps 'attention driver' is a
> better word. - driving attention to things that need to be fixed. It
> also means spending copious amounts of time in Jira (as you would in a
> feature release, but this is even more pervasive) You essentially have
> to look at bugs reported against newer releases and see if they apply
> - if patches for them are applicable to your release (e.g. if I fix a
> bug for 4.2 - does that bug apply to 4.1? Should the fix be in 4.1.1?)
> etc.
> 
> --David
>

One more follow-up to this...  I'm personally looking to spend more time
actually coding on this (and other related) projects for a bit.  That's
why I've suggested a switch for 4.2.  The other reason is that we need
to foster a group of folks that are willing / capable of RMing a feature
or bug-fix release.  As with other times where we discuss "single point
of failure" in supporting areas of the code, the same applies to
project-level coordination activities like release management!

That being said, I want to be *super clear* that if someone wants to do
this, but is concerned about knowing *what* or *how*, then they should
feel free to volunteer.  I'm *very* willing to help, coach, support,
whatever is needed.  Don't let a feeling of not knowing what to do stop
you from stepping forward!

-chip

Re: VI Java API Question

[Mike Tutkowski]

Hi Chip,

I was actually using the open source one you referred to (1).

I had done some research on this a week or so ago and people were
complaining about (2) and recommending (1).

That book does look useful.  Maybe I'll stop in at the bookstore on my way
into work.

Thanks!


On Thu, Mar 28, 2013 at 7:21 AM, Chip Childers wrote:

> On Thu, Mar 28, 2013 at 9:20 AM, Chip Childers
>  wrote:
> > On Wed, Mar 27, 2013 at 11:54:53PM -0600, Mike Tutkowski wrote:
> >> Hi,
> >>
> >> I was wondering if anyone could answer this question for me.  I've been
> >> looking at all sorts of properties of various VI Java Objects to find
> out
> >> how to do this and don't see any answers on the web either.
> >
> > Mike,
> >
> > Just so that I understand.  Are you using the VIJava [1] SDK (which is
> > *not* from VMware), or are you using the VMware vSphere Java SDK [2]
> > (which is). Currently we use the VMware vSphere Java SDK within the
> > VMware HV plugin.
> >
> > -chip
> >
> > [1] http://vijava.sourceforge.net/
> > [2]
> http://communities.vmware.com/community/vmtn/developer/forums/java_toolkit
>
> Also, you might consider this book:
>
> http://www.amazon.com/gp/product/0137153635?ie=UTF8&tag=doublecloudor-20&linkCode=as2&camp=1789&creative=9325&creativeASIN=0137153635
>
> I found it very useful a couple of years back.
>
> -chip
>



-- 
*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: VI Java API Question

[Chip Childers]

On Thu, Mar 28, 2013 at 08:01:32AM -0600, Mike Tutkowski wrote:
> Hi Chip,
> 
> I was actually using the open source one you referred to (1).
> 
> I had done some research on this a week or so ago and people were
> complaining about (2) and recommending (1).

So I agree that VIJava is a easier to consume library (Steve did a great
job on it), but understand that we're not using it today.  That's not a
blocker, but any patch that includes it as a dependency would need to
account for (and call out) the addition.

> 
> That book does look useful.  Maybe I'll stop in at the bookstore on my way
> into work.
> 
> Thanks!
> 
> 
> On Thu, Mar 28, 2013 at 7:21 AM, Chip Childers 
> wrote:
> 
> > On Thu, Mar 28, 2013 at 9:20 AM, Chip Childers
> >  wrote:
> > > On Wed, Mar 27, 2013 at 11:54:53PM -0600, Mike Tutkowski wrote:
> > >> Hi,
> > >>
> > >> I was wondering if anyone could answer this question for me.  I've been
> > >> looking at all sorts of properties of various VI Java Objects to find
> > out
> > >> how to do this and don't see any answers on the web either.
> > >
> > > Mike,
> > >
> > > Just so that I understand.  Are you using the VIJava [1] SDK (which is
> > > *not* from VMware), or are you using the VMware vSphere Java SDK [2]
> > > (which is). Currently we use the VMware vSphere Java SDK within the
> > > VMware HV plugin.
> > >
> > > -chip
> > >
> > > [1] http://vijava.sourceforge.net/
> > > [2]
> > http://communities.vmware.com/community/vmtn/developer/forums/java_toolkit
> >
> > Also, you might consider this book:
> >
> > http://www.amazon.com/gp/product/0137153635?ie=UTF8&tag=doublecloudor-20&linkCode=as2&camp=1789&creative=9325&creativeASIN=0137153635
> >
> > I found it very useful a couple of years back.
> >
> > -chip
> >
> 
> 
> 
> -- 
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud
> *™*

[MERGE] bvt branch to master

[Prasanna Santhanam]

I'd like to merge the bvt branch into master. The proposal [1] was to
stabilize master by allowing devs to quickly setup CloudStack using
simulated hypervisors and run some basic tests against it.

The bvt branch integrates the testing of cloudstack using marvin and
the simulator hypervisor. Alternately you may use devcloud as well
with the appropriate maven profiles enabled. One can try the
integrated tests today as described in [2]

While this is not to be touted as the magic pill for master stability
I think it is a good first step towards bringing together tests as
part of the build system. I've tested the steps on Linux and OSX.

[1] http://s.apache.org/5Lc
[2] https://cwiki.apache.org/confluence/x/PgvMAQ

Thanks,

-- 
Prasanna.,

Re: [ACS4.2] master blockers

[Abhinandan Prateek]

On 28-Mar-2013, at 7:20 PM, "Chip Childers"  wrote:

> On Thu, Mar 28, 2013 at 01:44:30PM +, Abhinandan Prateek wrote:
>> I think both the branches are important, yes 4.1 is close to release and
>> people assigned issues should give priority to 4.1.
>> There are also many people trying to test there features in master and
>> unstable master is resulting in wasted cycles.
>> 
>> Having said that I guess people having issues assigned in both the
>> branches should focus on 4.1 issues first before moving to 4.2 bugs.
> 
> Yes, and it seems to me that discussions around prioritization of bugs
> in master should be threaded by *feature* primarily (excepting general
> blockers that *break* the build/tests).
> 
Sure, will prioritise the master bugs only if they block some feature 
development or in general break the build/test.

Re: Review Request: Remove duplicate plugin dependency, fixes maven build warning

[Chip Childers]

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

Ship it!


Applied to 4.1:

commit 7678987ca030a711854fb30fa6cc5351f7b612d7
Author: Rohit Yadav 
Date:   Thu Mar 28 11:49:52 2013 +0530

usage: remove duplicate maven plugin dependency in cloud-usage

Signed-off-by: Rohit Yadav 

- Chip Childers


On March 28, 2013, 6:21 a.m., Rohit Yadav wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/10165/
> ---
> 
> (Updated March 28, 2013, 6:21 a.m.)
> 
> 
> Review request for cloudstack and Chip Childers.
> 
> 
> Description
> ---
> 
> Patch remove a duplicate plugin definitions from usage/pom.xml, fixes maven 
> build/run warning.
> 
> 
> Diffs
> -
> 
>   usage/pom.xml bc1d9c8 
> 
> Diff: https://reviews.apache.org/r/10165/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Rohit Yadav
> 
>

Re: [DISCUSS][DOCS] Docs as their own repo? Was: [DISCUSS][TRANSLATION] commit to master or not ?

[Joe Brockmeier]

On Thu, Mar 28, 2013, at 08:28 AM, Chip Childers wrote:
> Before we get to this, I have a broader question:  Do we want to move
> the docs to their own git repo?  We manage them with different rules,
> especially WRT code freeze and whatnot.  This translation question just
> adds to the logic to pull the repo apart.

This came up once before, and initially I was against having a different
repo - but we've tried it for a while, and maybe it makes sense to break
it out. 

Two questions: 

- one, are we still going to bundle docs into the tarball for release?

- two, there was a proposal about using docs as tooltips, how would this
affect that if the two are separate trees?

Best,

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

Re: [ACS4.2] master blockers

[Chip Childers]

On Thu, Mar 28, 2013 at 02:19:06PM +, Abhinandan Prateek wrote:
> On 28-Mar-2013, at 7:20 PM, "Chip Childers"  wrote:
> 
> > On Thu, Mar 28, 2013 at 01:44:30PM +, Abhinandan Prateek wrote:
> >> I think both the branches are important, yes 4.1 is close to release and
> >> people assigned issues should give priority to 4.1.
> >> There are also many people trying to test there features in master and
> >> unstable master is resulting in wasted cycles.
> >> 
> >> Having said that I guess people having issues assigned in both the
> >> branches should focus on 4.1 issues first before moving to 4.2 bugs.
> > 
> > Yes, and it seems to me that discussions around prioritization of bugs
> > in master should be threaded by *feature* primarily (excepting general
> > blockers that *break* the build/tests).
> > 
> Sure, will prioritise the master bugs only if they block some feature 
> development or in general break the build/test.

Sorry, I think you may be missing the point I'm trying to make.  I'm suggesting 
that communication around features is probably best done with the feature 
itself 
being the subject of the thread. If someone is building feature X, and
someone else has volunteered to test feature X, then they should be
coordinating with each other on feature X.

The reason that a release cycle changes this communication to "release
level" focus, is that there is a specific schedule that we're trying to
work towards as a community.

Does that distinction make sense?

Re: [DISCUSS][DOCS] Docs as their own repo? Was: [DISCUSS][TRANSLATION] commit to master or not ?

[Chip Childers]

On Thu, Mar 28, 2013 at 09:27:00AM -0500, Joe Brockmeier wrote:
> On Thu, Mar 28, 2013, at 08:28 AM, Chip Childers wrote:
> > Before we get to this, I have a broader question:  Do we want to move
> > the docs to their own git repo?  We manage them with different rules,
> > especially WRT code freeze and whatnot.  This translation question just
> > adds to the logic to pull the repo apart.
> 
> This came up once before, and initially I was against having a different
> repo - but we've tried it for a while, and maybe it makes sense to break
> it out. 
> 
> Two questions: 
> 
> - one, are we still going to bundle docs into the tarball for release?

I'd propose that they are actually a distinct download / artifact for
the release.  I'd procedurally release them at the same time as the
source artifacts, but I don't think that there's a ton of value in
bundling them with the source.  The build processes are different, and
packaging doesn't pull in the docs anyway.  Really, our docs are being
published to our website as the primary target for distribution right
now anyway...

> 
> - two, there was a proposal about using docs as tooltips, how would this
> affect that if the two are separate trees?

Unsure where that proposal went...  and frankly I'm not sure I agree
with that approach anyway.

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

Re: [DISCUSS][TRANSLATION] commit to master or not ?

[Joe Brockmeier]

On Thu, Mar 28, 2013, at 07:02 AM, Sebastien Goasguen wrote:
> Hi,
> 
> I have been pulling all translations (docs and UI) and committing them in
> 4.1 branch to make the deadline.
> 
> I have not yet committed them to master and now I am wondering if we
> should.

Shouldn't we push the UI bits, at least, so that the translations are
available for anyone testing the UI? 

Best,

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

Re: [DISCUSS][DOCS] Docs as their own repo? Was: [DISCUSS][TRANSLATION] commit to master or not ?

[David Nalley]

On Thu, Mar 28, 2013 at 10:34 AM, Chip Childers
 wrote:
> On Thu, Mar 28, 2013 at 09:27:00AM -0500, Joe Brockmeier wrote:
>> On Thu, Mar 28, 2013, at 08:28 AM, Chip Childers wrote:
>> > Before we get to this, I have a broader question:  Do we want to move
>> > the docs to their own git repo?  We manage them with different rules,
>> > especially WRT code freeze and whatnot.  This translation question just
>> > adds to the logic to pull the repo apart.
>>
>> This came up once before, and initially I was against having a different
>> repo - but we've tried it for a while, and maybe it makes sense to break
>> it out.
>>
>> Two questions:
>>
>> - one, are we still going to bundle docs into the tarball for release?
>
> I'd propose that they are actually a distinct download / artifact for
> the release.  I'd procedurally release them at the same time as the
> source artifacts, but I don't think that there's a ton of value in
> bundling them with the source.  The build processes are different, and
> packaging doesn't pull in the docs anyway.  Really, our docs are being
> published to our website as the primary target for distribution right
> now anyway...
>
>>
>> - two, there was a proposal about using docs as tooltips, how would this
>> affect that if the two are separate trees?
>
> Unsure where that proposal went...  and frankly I'm not sure I agree
> with that approach anyway.
>

That proposal moved forward and the first generation is in 4.1 iirc.
That said it's not in the state originally proposed, and I've been
struggling to get answers on how it is going to be handled in the
future.
If this is a veto from you, lets stop folks from working on it.

--David

Re: [DISCUSS] create a general@ mailing list?

[Chip Childers]

On Mon, Mar 25, 2013 at 06:36:25PM -0400, David Nalley wrote:
> On Wed, Mar 20, 2013 at 11:42 PM, Chip Childers
>  wrote:
> > I've noticed that some of the projects separate discussions between dev
> > and general administrative items via a general@ and a dev@ list.  For
> > example, the last email I sent was about project meta-data.  It's not
> > specifically about developing cloudstack, but about managing our
> > community activities.
> >
> > Does anyone think it makes sense to break that type of discussion out
> > into a general@ list?
> 
> So I unclear on this.
> 
> All committers are expected to be on -dev.
> 
> Now, because administrivia is happening on general@ all committers
> will also need to be on that list. So I don't see a lot of benefit to
> moving that traffic off of  dev@. I also don't see adminitrstrative
> stuff taking up that much bandwidth. I understand marketing being
> separate, though I think we've seen a number of 'missed messages'
> already from that. Dev@ is where contributors 'live' - so metadata
> about the project seems a fit there - or am I missing something?
> 
> --David
>

I didn't have a specific opinion about doing this or not.  I raised it
simply because I saw that other projects do things this way.  Looking 
into it a bit more deeply, it appears that it's largely a function of 
the projects having built themselves up into unbrella projects.  The 
ASF Board flattened things since then, but the lists still exist.

Given that we have a mix of responses to this question (some for it and
some against it), and that the pattern seems to be tied to the unliked
practice of creating umbrella communities, I believe that we should not 
make the change within CloudStack.

-chip

Re: [DISCUSS][DOCS] Docs as their own repo? Was: [DISCUSS][TRANSLATION] commit to master or not ?

[Chip Childers]

On Thu, Mar 28, 2013 at 10:45:41AM -0400, David Nalley wrote:
> On Thu, Mar 28, 2013 at 10:34 AM, Chip Childers
>  wrote:
> > On Thu, Mar 28, 2013 at 09:27:00AM -0500, Joe Brockmeier wrote:
> >> On Thu, Mar 28, 2013, at 08:28 AM, Chip Childers wrote:
> >> > Before we get to this, I have a broader question:  Do we want to move
> >> > the docs to their own git repo?  We manage them with different rules,
> >> > especially WRT code freeze and whatnot.  This translation question just
> >> > adds to the logic to pull the repo apart.
> >>
> >> This came up once before, and initially I was against having a different
> >> repo - but we've tried it for a while, and maybe it makes sense to break
> >> it out.
> >>
> >> Two questions:
> >>
> >> - one, are we still going to bundle docs into the tarball for release?
> >
> > I'd propose that they are actually a distinct download / artifact for
> > the release.  I'd procedurally release them at the same time as the
> > source artifacts, but I don't think that there's a ton of value in
> > bundling them with the source.  The build processes are different, and
> > packaging doesn't pull in the docs anyway.  Really, our docs are being
> > published to our website as the primary target for distribution right
> > now anyway...
> >
> >>
> >> - two, there was a proposal about using docs as tooltips, how would this
> >> affect that if the two are separate trees?
> >
> > Unsure where that proposal went...  and frankly I'm not sure I agree
> > with that approach anyway.
> >
> 
> That proposal moved forward and the first generation is in 4.1 iirc.
> That said it's not in the state originally proposed, and I've been
> struggling to get answers on how it is going to be handled in the
> future.
> If this is a veto from you, lets stop folks from working on it.
> 
> --David
>

Not a veto ATM. Let's take this to a separate thread to discuss.

Re: [MERGE] scaleupvm functionality branch to master

[Nitin Mehta]

I have merged the feature with commit below.

commit 3e4430d811d5e148c4fef1900bdd8dd07a38bdeb
Author: Nitin Mehta 
Date:   Thu Mar 28 16:43:37 2013 +0530

CLOUDSTACK-658 - Scale vm support for Xenserver
Added the framweork so that it can be extended for vmware and kvm as
well.
Added unitests and marvin tests.



On 23/03/13 1:06 AM, "Chip Childers"  wrote:

>On Fri, Mar 22, 2013 at 06:35:02AM +, Nitin Mehta wrote:
>> Alright Chip, I have pushed in the unit tests for CitrixResourceBase and
>> will work with Prasanna to learn writing the marvin tests and will push
>> them shortly as well.
>
>Great!
>
>> Lets please merge the feature as I think the unit tests should be good
>>as
>> first line of defense. I assure you that I will push the marvin tests
>>soon
>> as well.
>
>I'm OK with that, if others are.

Re: [DISCUSS][TRANSLATION] commit to master or not ?

[Chip Childers]

On Thu, Mar 28, 2013 at 09:38:57AM -0500, Joe Brockmeier wrote:
> On Thu, Mar 28, 2013, at 07:02 AM, Sebastien Goasguen wrote:
> > Hi,
> > 
> > I have been pulling all translations (docs and UI) and committing them in
> > 4.1 branch to make the deadline.
> > 
> > I have not yet committed them to master and now I am wondering if we
> > should.
> 
> Shouldn't we push the UI bits, at least, so that the translations are
> available for anyone testing the UI? 

+1, they do belong there.

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

RE: [MERGE] scaleupvm functionality branch to master

[Sudha Ponnaganti]

Thanks Nitin for Marvin Tests. Girish is going to extend the initial set of 
Marvin tests in due course. 
Prashanth - pl do check the test results in subsequent automation runs. 

I have crated Automation task and assigned it to Girish. 

Thanks
/Sudha


-Original Message-
From: Nitin Mehta [mailto:nitin.me...@citrix.com] 
Sent: Thursday, March 28, 2013 8:03 AM
To: dev@cloudstack.apache.org
Subject: Re: [MERGE] scaleupvm functionality branch to master

I have merged the feature with commit below.

commit 3e4430d811d5e148c4fef1900bdd8dd07a38bdeb
Author: Nitin Mehta 
Date:   Thu Mar 28 16:43:37 2013 +0530

CLOUDSTACK-658 - Scale vm support for Xenserver
Added the framweork so that it can be extended for vmware and kvm as well.
Added unitests and marvin tests.



On 23/03/13 1:06 AM, "Chip Childers"  wrote:

>On Fri, Mar 22, 2013 at 06:35:02AM +, Nitin Mehta wrote:
>> Alright Chip, I have pushed in the unit tests for CitrixResourceBase 
>> and will work with Prasanna to learn writing the marvin tests and 
>> will push them shortly as well.
>
>Great!
>
>> Lets please merge the feature as I think the unit tests should be 
>>good as  first line of defense. I assure you that I will push the 
>>marvin tests soon  as well.
>
>I'm OK with that, if others are.

Re: [DISCUSS][TRANSLATION] commit to master or not ?

[Sebastien Goasguen]

On Mar 28, 2013, at 11:20 AM, Chip Childers  wrote:

> On Thu, Mar 28, 2013 at 09:38:57AM -0500, Joe Brockmeier wrote:
>> On Thu, Mar 28, 2013, at 07:02 AM, Sebastien Goasguen wrote:
>>> Hi,
>>> 
>>> I have been pulling all translations (docs and UI) and committing them in
>>> 4.1 branch to make the deadline.
>>> 
>>> I have not yet committed them to master and now I am wondering if we
>>> should.
>> 
>> Shouldn't we push the UI bits, at least, so that the translations are
>> available for anyone testing the UI? 
> 
> +1, they do belong there.

I agree

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

Re: [ACS4.2] master blockers

[Abhinandan Prateek]

On 28/03/13 7:59 PM, "Chip Childers"  wrote:

>On Thu, Mar 28, 2013 at 02:19:06PM +, Abhinandan Prateek wrote:
>> On 28-Mar-2013, at 7:20 PM, "Chip Childers" 
>>wrote:
>> 
>> > On Thu, Mar 28, 2013 at 01:44:30PM +, Abhinandan Prateek wrote:
>> >> I think both the branches are important, yes 4.1 is close to release
>>and
>> >> people assigned issues should give priority to 4.1.
>> >> There are also many people trying to test there features in master
>>and
>> >> unstable master is resulting in wasted cycles.
>> >> 
>> >> Having said that I guess people having issues assigned in both the
>> >> branches should focus on 4.1 issues first before moving to 4.2 bugs.
>> > 
>> > Yes, and it seems to me that discussions around prioritization of bugs
>> > in master should be threaded by *feature* primarily (excepting general
>> > blockers that *break* the build/tests).
>> > 
>> Sure, will prioritise the master bugs only if they block some feature
>>development or in general break the build/test.
>
>Sorry, I think you may be missing the point I'm trying to make.  I'm
>suggesting 
>that communication around features is probably best done with the feature
>itself 
>being the subject of the thread. If someone is building feature X, and
>someone else has volunteered to test feature X, then they should be
>coordinating with each other on feature X.
>
>The reason that a release cycle changes this communication to "release
>level" focus, is that there is a specific schedule that we're trying to
>work towards as a community.
>
>Does that distinction make sense?

Yes, I understand that we are trying to get the current releases out and
the focus should not be diluted.

For any follow up on current features or bugs the communication should be
around features and not around the release as it is still not there in the
release cycle.
 
My intention is to help out people who cannot test the feature due to
existing issues on master if any.
Again I will be taking it slow on master (only focusing on issues that
matter at this point in release cycle) so that appropriate focus is there
on current releases.

Does this sound good or I am still missing something.
 

>

[PROPOSAL][CLOUDSTACK-779] Egress firewall rules for SRX

[Jayapal Reddy Uradi]

I would like to propose the egress firewall rules feature for the external 
firewall device SRX guest network.

Currently egress firewall rules is supported in the VR isolated network. With 
this feature egress firewall rules
is supported in the external device SRX guest networks.

Jira Id:
https://issues.apache.org/jira/browse/CLOUDSTACK-779

FS:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Egress+firewall+rules+feature+support+for+external+device+Juniper+SRX
Please let me know your comments on the above FS.

Thanks,
Jayapal

Re: [ACS4.2] master blockers

[Chip Childers]

On Thu, Mar 28, 2013 at 03:37:15PM +, Abhinandan Prateek wrote:
> 
> 
> On 28/03/13 7:59 PM, "Chip Childers"  wrote:
> 
> >On Thu, Mar 28, 2013 at 02:19:06PM +, Abhinandan Prateek wrote:
> >> On 28-Mar-2013, at 7:20 PM, "Chip Childers" 
> >>wrote:
> >> 
> >> > On Thu, Mar 28, 2013 at 01:44:30PM +, Abhinandan Prateek wrote:
> >> >> I think both the branches are important, yes 4.1 is close to release
> >>and
> >> >> people assigned issues should give priority to 4.1.
> >> >> There are also many people trying to test there features in master
> >>and
> >> >> unstable master is resulting in wasted cycles.
> >> >> 
> >> >> Having said that I guess people having issues assigned in both the
> >> >> branches should focus on 4.1 issues first before moving to 4.2 bugs.
> >> > 
> >> > Yes, and it seems to me that discussions around prioritization of bugs
> >> > in master should be threaded by *feature* primarily (excepting general
> >> > blockers that *break* the build/tests).
> >> > 
> >> Sure, will prioritise the master bugs only if they block some feature
> >>development or in general break the build/test.
> >
> >Sorry, I think you may be missing the point I'm trying to make.  I'm
> >suggesting 
> >that communication around features is probably best done with the feature
> >itself 
> >being the subject of the thread. If someone is building feature X, and
> >someone else has volunteered to test feature X, then they should be
> >coordinating with each other on feature X.
> >
> >The reason that a release cycle changes this communication to "release
> >level" focus, is that there is a specific schedule that we're trying to
> >work towards as a community.
> >
> >Does that distinction make sense?
> 
> Yes, I understand that we are trying to get the current releases out and
> the focus should not be diluted.
> 
> For any follow up on current features or bugs the communication should be
> around features and not around the release as it is still not there in the
> release cycle.
>  
> My intention is to help out people who cannot test the feature due to
> existing issues on master if any.

Good intention!

> Again I will be taking it slow on master (only focusing on issues that
> matter at this point in release cycle) so that appropriate focus is there
> on current releases.
> 
> Does this sound good or I am still missing something.
>  

It does.  Thanks for hearing me out.

Re: Unable to create a deployment for VM

[Maurice Lawler]

It is one sever. Handling it all. CentOS with KVM. that's it. Not sure where to 
go to correct this.



Abhinandan Prateek  wrote:

>It seems you have a cluster of management servers. It is possible that the
>host/agents are owned by the the management server that is inactive:
>
>2013-03-28 02:07:22,340 INFO  [cloud.cluster.ClusterManagerImpl]
>(Cluster-Heartbeat-1:null) Management node 1 is *detected inactive* by
>timestamp but is pingable
>
>
>-abhi
>
>
>On 28/03/13 12:41 PM, "Maurice Lawler"  wrote:
>
>>Attempting to create a VM from a template I created (Twice) getting this
>>in my logs: 
>>
>>013-03-28 02:07:17,873 WARN  [cloud.api.ApiDispatcher]
>>(Job-Executor-22:job-77) class com.cloud.api.ServerApiException : Unable
>>to create a deployment for VM[User|i-2-11-VM]
>>2013-03-28 02:07:17,873 DEBUG [cloud.async.AsyncJobManagerImpl]
>>(Job-Executor-22:job-77) Complete async job-77, jobStatus: 2, resultCode:
>>530, result: com.cloud.api.response.ExceptionResponse@2637df06
>>2013-03-28 02:07:19,339 DEBUG [cloud.cluster.ClusterManagerImpl]
>>(Cluster-Heartbeat-1:null) Detected management node left, id:1,
>>nodeIP:0.0.0.0
>>2013-03-28 02:07:19,339 INFO  [cloud.cluster.ClusterManagerImpl]
>>(Cluster-Heartbeat-1:null) Trying to connect to 0.0.0.0
>>2013-03-28 02:07:19,340 INFO  [cloud.cluster.ClusterManagerImpl]
>>(Cluster-Heartbeat-1:null) Management node 1 is detected inactive by
>>timestamp but is pingable
>>2013-03-28 02:07:20,839 DEBUG [cloud.cluster.ClusterManagerImpl]
>>(Cluster-Heartbeat-1:null) Detected management node left, id:1,
>>nodeIP:0.0.0.0
>>2013-03-28 02:07:20,840 INFO  [cloud.cluster.ClusterManagerImpl]
>>(Cluster-Heartbeat-1:null) Trying to connect to 0.0.0.0
>>2013-03-28 02:07:20,840 INFO  [cloud.cluster.ClusterManagerImpl]
>>(Cluster-Heartbeat-1:null) Management node 1 is detected inactive by
>>timestamp but is pingable
>>2013-03-28 02:07:21,183 DEBUG [cloud.server.StatsCollector]
>>(StatsCollector-2:null) VmStatsCollector is running...
>>2013-03-28 02:07:21,219 DEBUG [cloud.vm.VirtualMachineManagerImpl]
>>(AgentManager-Handler-9:null) Cleanup succeeded. Details null
>>2013-03-28 02:07:21,219 DEBUG [agent.transport.Request]
>>(StatsCollector-2:null) Seq 1-2359860: Received:  { Ans: , MgmtId:
>>279278805451068, via: 1, Ver: v1, Flags: 10, { GetVmStatsAnswer } }
>>2013-03-28 02:07:21,219 DEBUG [cloud.vm.VirtualMachineManagerImpl]
>>(StatsCollector-2:null) Cleanup succeeded. Details null
>>2013-03-28 02:07:22,339 DEBUG [cloud.cluster.ClusterManagerImpl]
>>(Cluster-Heartbeat-1:null) Detected management node left, id:1,
>>nodeIP:0.0.0.0
>>2013-03-28 02:07:22,340 INFO  [cloud.cluster.ClusterManagerImpl]
>>(Cluster-Heartbeat-1:null) Trying to connect to 0.0.0.0
>>2013-03-28 02:07:22,340 INFO  [cloud.cluster.ClusterManagerImpl]
>>(Cluster-Heartbeat-1:null) Management node 1 is detected inactive by
>>timestamp but is pingable
>>2013-03-28 02:07:22,629 DEBUG [cloud.async.AsyncJobManagerImpl]
>>(catalina-exec-1:null) Async job-77 completed
>>2013-03-28 02:07:23,586 DEBUG
>>[storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Zone
>>1 is ready to launch secondary storage VM
>>2013-03-28 02:07:23,710 DEBUG
>>[cloud.consoleproxy.ConsoleProxyManagerImpl] (consoleproxy-1:null) Zone 1
>>is ready to launch console proxy
>>2013-03-28 02:07:23,839 DEBUG [cloud.cluster.ClusterManagerImpl]
>>(Cluster-Heartbeat-1:null) Detected management node left, id:1,
>>nodeIP:0.0.0.0
>>2013-03-28 02:07:23,839 INFO  [cloud.cluster.ClusterManagerImpl]
>>(Cluster-Heartbeat-1:null) Trying to connect to 0.0.0.0
>>
>>
>>
>>Lots of: 2013-03-28 02:07:19,339 INFO  [cloud.cluster.ClusterManagerImpl]
>>(Cluster-Heartbeat-1:null) Trying to connect to 0.0.0.0 (of course it's
>>no really 0.0.0.0) but yeah, not sure how to solve this.
>>
>>Any thoughts? 
>

Re: KVM Tools

[Maurice Lawler]

No, there isn't really anything in particular I was getting at. Was simply 
making sure with my setup I wasn't missing anything 

"Kelceydamage@bbits"  wrote:

>What most people seem to associate with guest tools is the ability for greater 
>console interactions (drag and drop/shared clipboard), as well as API login 
>functions in the API.
>
>I myself have brought these up many times, if your interested in other 
>features, the. Please describe in detail.
>
>Thanks.
>
>Sent from my iPhone
>
>On Mar 28, 2013, at 12:01 AM, Maurice Lawler  wrote:
>
>> No, nothing in particular. I just noticed in my pervious ventures with 
>> Cloudstack / XEN / ESXI that there were some tools you could (or were 
>> required / suggested by installation guides) I just did not know if there 
>> was anything like that. 
>> 
>> 
>> On Mar 28, 2013, at 1:49 AM, Marcus Sorensen  wrote:
>> 
>>> The qemu guest agent is installed in the guest, that is...
>>> On Mar 28, 2013 12:48 AM, "Marcus Sorensen"  wrote:
>>> 
 What specifically? A large chunk of the tools for VMware/xen are upgraded
 drivers, which aren't necessary with Linux and already available for other
 operating systems. There's also the qemu-guest-agent which can be installed
 in the host to do things like write files from host to guest, but
 cloudstack doesn't have any functionality around that. Which features were
 you hoping for?
 On Mar 28, 2013 12:43 AM, "Maurice Lawler"  wrote:
 
> Hello,
> 
> I've been seeing some idle chatter about possible KVM Guest Tools, like
> there are for VMware and Xen Server.
> 
> Has anything be done about this?
> 
> 
> 
>> 

Re: [DISCUSS] create a general@ mailing list?

[Joe Brockmeier]

On Thu, Mar 28, 2013, at 09:57 AM, Chip Childers wrote:
> Given that we have a mix of responses to this question (some for it and
> some against it), and that the pattern seems to be tied to the unliked
> practice of creating umbrella communities, I believe that we should not 
> make the change within CloudStack.

+1 

Maybe someday we'll need one. But we're a long way from that right now.

Best,

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

RE: [ACS41][QA] Has anyone upgraded from 4.0 to 4.1

[Sangeetha Hariharan]

Can we get a confirmation on the approach we want to take?

1. We are going to fix the router for  the case - " if the router has upgraded 
its scripts, and then adjust how we call edithosts.sh" ?
2. Going to suggest a reboot (start and stop) of all the system Vms (SSVM,CPVM 
and routers) as part of Upgrade procedure?

-Thanks
Sangeetha

-Original Message-
From: Marcus Sorensen [mailto:shadow...@gmail.com] 
Sent: Wednesday, March 27, 2013 10:02 PM
To: dev@cloudstack.apache.org
Cc: Sangeetha Hariharan
Subject: Re: [ACS41][QA] Has anyone upgraded from 4.0 to 4.1

Ok, found the issue. The 4.0 script in the system vm that adds DHCP entries 
parses args like this:

# edithosts.sh -- edit the dhcphosts file on the routing domain # $mac : the 
mac address # $ip : the associated ip address # $host : the hostname # $4 : 
default router # $5 : nameserver on default nic # $6 : comma separated static 
routes

mac=$1
ip=$2
host=$3
dflt=$4
dns=$5
routes=$6

And the script in 4.1 parses args like this:

while getopts 'm:4:h:d:n:s:6:u:N' OPTION do
  case $OPTION in
  m)mac="$OPTARG"
;;
  4)ipv4="$OPTARG"
;;
  6)ipv6="$OPTARG"
;;
  u)duid="$OPTARG"
;;
  h)host="$OPTARG"
;;
  d)dflt="$OPTARG"
;;
  n)dns="$OPTARG"
;;
  s)routes="$OPTARG"
;;
  N)nondefault=1
;;
  ?)usage
exit 2
;;
  esac
done

So in 4.0 it's looking at flags as though they're arguments, which is why we 
get garbage in the dhcp file. In the router log we see the results (first line 
is a working one, second line isn't)

Mar 28 04:41:54 r-5-VM cloud: edithosts: update 02:00:2b:58:00:01
10.1.1.6 ff9b5970-d095-4602-aa7d-671e3a7535da to hosts Mar 28 04:48:01 r-5-VM 
cloud: edithosts: update -4 10.1.1.245 -m to hosts

I don't see an easy way around this. We could perhaps detect if the router has 
upgraded its scripts, and then adjust how we call edithosts.sh accordingly. 
Anyone want to take that on? Is this the only issue? I'm assuming people will 
need to reboot their system vms anyway for other features.

On Wed, Mar 27, 2013 at 9:27 PM, Marcus Sorensen  wrote:
> We can look into it, my guess is that an existing script now has new 
> and/or different parameters. Perhaps it could be adjusted to be 
> backward compatible so people can reboot at their leisure. All just guesswork.
>
> On Mar 27, 2013 9:21 PM, "Marcus Sorensen"  wrote:
>>
>> Hard to say. Sometimes functionality/implementation changes even 
>> though the feature is the same.
>>
>> On Mar 27, 2013 9:20 PM, "David Nalley"  wrote:
>>>
>>> On Wed, Mar 27, 2013 at 11:13 PM, Marcus Sorensen 
>>> 
>>> wrote:
>>> > Just to clarify a step further, this should have been the case 
>>> > with 3.x to
>>> > 4.0 as well. We had all of these new vpc scripts that added brand 
>>> > new functionality that needed to go on the virtual routers. The 
>>> > system VM template stayed the same, even though new scripts were 
>>> > added via systemvm.iso.
>>>
>>>
>>> That said, why would new functionality make existing functionality 
>>> stop working in a system VM.
>>>
>>> --David

Re: KVM Tools

[Kelceydamage@bbits]

It's sounds like you have everything you need then :)

Sent from my iPhone

On Mar 28, 2013, at 9:44 AM, Maurice Lawler  wrote:

> No, there isn't really anything in particular I was getting at. Was simply 
> making sure with my setup I wasn't missing anything 
> 
> "Kelceydamage@bbits"  wrote:
> 
>> What most people seem to associate with guest tools is the ability for 
>> greater console interactions (drag and drop/shared clipboard), as well as 
>> API login functions in the API.
>> 
>> I myself have brought these up many times, if your interested in other 
>> features, the. Please describe in detail.
>> 
>> Thanks.
>> 
>> Sent from my iPhone
>> 
>> On Mar 28, 2013, at 12:01 AM, Maurice Lawler  wrote:
>> 
>>> No, nothing in particular. I just noticed in my pervious ventures with 
>>> Cloudstack / XEN / ESXI that there were some tools you could (or were 
>>> required / suggested by installation guides) I just did not know if there 
>>> was anything like that. 
>>> 
>>> 
>>> On Mar 28, 2013, at 1:49 AM, Marcus Sorensen  wrote:
>>> 
 The qemu guest agent is installed in the guest, that is...
 On Mar 28, 2013 12:48 AM, "Marcus Sorensen"  wrote:
 
> What specifically? A large chunk of the tools for VMware/xen are upgraded
> drivers, which aren't necessary with Linux and already available for other
> operating systems. There's also the qemu-guest-agent which can be 
> installed
> in the host to do things like write files from host to guest, but
> cloudstack doesn't have any functionality around that. Which features were
> you hoping for?
> On Mar 28, 2013 12:43 AM, "Maurice Lawler"  wrote:
> 
>> Hello,
>> 
>> I've been seeing some idle chatter about possible KVM Guest Tools, like
>> there are for VMware and Xen Server.
>> 
>> Has anything be done about this?
>> 
>> 
>> 
>>> 

Attaching Volumes to Windows Instance

[Maurice Lawler]

Greetings,

I am utilizing CloudStack-oss-3.0.2-1 on CentOS 6.3 | KVM.


It's running wonderfully, however, I have a Windows Instance I would like to 
attach a 'storage' volume to. However, when I go to add the volume it only 
lists the Linux falvor instances that are running to attach to.

How can I get this secondary volume attached to this Windows Instance. 

PS: I have also powered off the instance and it still did not allow me to add 
it to the windows machine.

Any suggestions, will be greatly appreciate ! 

- Maurice

Re: [DISCUSS] create a general@ mailing list?

[Kelceydamage@bbits]

+1 from me as well. It duplicates or segregates, neither of which seem like a 
positive change.

-kd

Sent from my iPhone

On Mar 28, 2013, at 9:46 AM, Joe Brockmeier  wrote:

> On Thu, Mar 28, 2013, at 09:57 AM, Chip Childers wrote:
>> Given that we have a mix of responses to this question (some for it and
>> some against it), and that the pattern seems to be tied to the unliked
>> practice of creating umbrella communities, I believe that we should not 
>> make the change within CloudStack.
> 
> +1 
> 
> Maybe someday we'll need one. But we're a long way from that right now.
> 
> Best,
> 
> jzb
> -- 
> Joe Brockmeier
> j...@zonker.net
> Twitter: @jzb
> http://www.dissociatedpress.net/

Re: KVM Tools

[Maurice Lawler]

You'd be right! I'm pretty set, just trying to figure out spinning up my VM's 
from templates -- Having issues! :-(

- M.
On Mar 28, 2013, at 11:53 AM, Kelceydamage@bbits  wrote:

> It's sounds like you have everything you need then :)
> 
> Sent from my iPhone
> 
> On Mar 28, 2013, at 9:44 AM, Maurice Lawler  wrote:
> 
>> No, there isn't really anything in particular I was getting at. Was simply 
>> making sure with my setup I wasn't missing anything 
>> 
>> "Kelceydamage@bbits"  wrote:
>> 
>>> What most people seem to associate with guest tools is the ability for 
>>> greater console interactions (drag and drop/shared clipboard), as well as 
>>> API login functions in the API.
>>> 
>>> I myself have brought these up many times, if your interested in other 
>>> features, the. Please describe in detail.
>>> 
>>> Thanks.
>>> 
>>> Sent from my iPhone
>>> 
>>> On Mar 28, 2013, at 12:01 AM, Maurice Lawler  wrote:
>>> 
 No, nothing in particular. I just noticed in my pervious ventures with 
 Cloudstack / XEN / ESXI that there were some tools you could (or were 
 required / suggested by installation guides) I just did not know if there 
 was anything like that. 
 
 
 On Mar 28, 2013, at 1:49 AM, Marcus Sorensen  wrote:
 
> The qemu guest agent is installed in the guest, that is...
> On Mar 28, 2013 12:48 AM, "Marcus Sorensen"  wrote:
> 
>> What specifically? A large chunk of the tools for VMware/xen are upgraded
>> drivers, which aren't necessary with Linux and already available for 
>> other
>> operating systems. There's also the qemu-guest-agent which can be 
>> installed
>> in the host to do things like write files from host to guest, but
>> cloudstack doesn't have any functionality around that. Which features 
>> were
>> you hoping for?
>> On Mar 28, 2013 12:43 AM, "Maurice Lawler"  wrote:
>> 
>>> Hello,
>>> 
>>> I've been seeing some idle chatter about possible KVM Guest Tools, like
>>> there are for VMware and Xen Server.
>>> 
>>> Has anything be done about this?
>>> 
>>> 
>>> 
 

Re: Unable to create a deployment for VM

[Maurice Lawler]

Reviewing the logs, grepping for job 77 I get the following errors: This is 
when spinning up a instance from a template. 



[root@lunder ~]# cat  /var/log/cloud/management/management-server.log |grep  
job-77
2013-03-28 02:07:17,540 DEBUG [cloud.async.AsyncJobManagerImpl] 
(catalina-exec-22:null) submit async job-77, details: AsyncJobVO {id:77, 
userId: 2, accountId: 2, sessionKey: null, instanceType: VirtualMachine, 
instanceId: 11, cmd: com.cloud.api.commands.DeployVMCmd, cmdOriginator: null, 
cmdInfo: 
{"sessionkey":"AX3hqEZ8EpqXTA/AsF3oDek4MIc\u003d","ctxUserId":"2","serviceOfferingId":"97b8d235-7b71-4ca0-8a04-fe90ec9220f0","securitygroupids":"f78f103f-77fb-4fbe-b437-91b656c8427f","zoneId":"28b7e853-1b2c-474c-be2f-4b91466fd4a9","templateId":"c4e7d8f3-d80b-45da-a29f-19687d7494f2","response":"json","id":"11","hypervisor":"KVM","name":"temptest","diskOfferingId":"07148505-9dd2-4f31-9494-bb82c64c7436","_":"1364454437368","ctxAccountId":"2","ctxStartEventId":"429","displayname":"temptest"},
 cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, 
processStatus: 0, resultCode: 0, result: null, initMsid: 279278805451068, 
completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
2013-03-28 02:07:17,540 DEBUG [cloud.async.AsyncJobManagerImpl] 
(Job-Executor-22:job-77) Executing com.cloud.api.commands.DeployVMCmd for job-77
2013-03-28 02:07:17,559 DEBUG [cloud.capacity.CapacityManagerImpl] 
(Job-Executor-22:job-77) VM state transitted from :Stopped to Starting with 
event: StartRequestedvm's original host id: null new host id: null host id 
before state transition: null
2013-03-28 02:07:17,559 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
(Job-Executor-22:job-77) Successfully transitioned to start state for 
VM[User|i-2-11-VM] reservation id = 77d9fc64-54d5-460e-bf85-ce9378bcf1cb
2013-03-28 02:07:17,562 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
(Job-Executor-22:job-77) Trying to deploy VM, vm has dcId: 1 and podId: null
2013-03-28 02:07:17,562 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
(Job-Executor-22:job-77) Deploy avoids pods: null, clusters: null, hosts: null
2013-03-28 02:07:17,563 DEBUG [cloud.deploy.FirstFitPlanner] 
(Job-Executor-22:job-77) DeploymentPlanner allocation algorithm: random
2013-03-28 02:07:17,564 DEBUG [cloud.deploy.FirstFitPlanner] 
(Job-Executor-22:job-77) Trying to allocate a host and storage pools from dc:1, 
pod:null,cluster:null, requested cpu: 500, requested ram: 536870912
2013-03-28 02:07:17,564 DEBUG [cloud.deploy.FirstFitPlanner] 
(Job-Executor-22:job-77) Is ROOT volume READY (pool already allocated)?: No
2013-03-28 02:07:17,564 DEBUG [cloud.deploy.FirstFitPlanner] 
(Job-Executor-22:job-77) Searching all possible resources under this Zone: 1
2013-03-28 02:07:17,565 DEBUG [cloud.deploy.FirstFitPlanner] 
(Job-Executor-22:job-77) Listing clusters in order of aggregate capacity, that 
have (atleast one host with) enough CPU and RAM capacity under this Zone: 1
2013-03-28 02:07:17,566 DEBUG [cloud.deploy.FirstFitPlanner] 
(Job-Executor-22:job-77) CPUOverprovisioningFactor considered: 1.0
2013-03-28 02:07:17,573 DEBUG [cloud.deploy.FirstFitPlanner] 
(Job-Executor-22:job-77) Checking resources in Cluster: 1 under Pod: 1
2013-03-28 02:07:17,573 DEBUG [cloud.deploy.FirstFitPlanner] 
(Job-Executor-22:job-77) Calling HostAllocators to find suitable hosts
2013-03-28 02:07:17,573 DEBUG [allocator.impl.FirstFitAllocator] 
(Job-Executor-22:job-77 FirstFitRoutingAllocator) Looking for hosts in dc: 1  
pod:1  cluster:1
2013-03-28 02:07:17,575 DEBUG [allocator.impl.FirstFitAllocator] 
(Job-Executor-22:job-77 FirstFitRoutingAllocator) FirstFitAllocator has 1 hosts 
to check for allocation: [Host[-1-Routing]]
2013-03-28 02:07:17,577 DEBUG [allocator.impl.FirstFitAllocator] 
(Job-Executor-22:job-77 FirstFitRoutingAllocator) Found 1 hosts for allocation 
after prioritization: [Host[-1-Routing]]
2013-03-28 02:07:17,577 DEBUG [allocator.impl.FirstFitAllocator] 
(Job-Executor-22:job-77 FirstFitRoutingAllocator) Looking for speed=500Mhz, 
Ram=512
2013-03-28 02:07:17,578 DEBUG [cloud.capacity.CapacityManagerImpl] 
(Job-Executor-22:job-77 FirstFitRoutingAllocator) Checking if host: 1 has 
enough capacity for requested CPU: 500 and requested RAM: 536870912 , 
cpuOverprovisioningFactor: 1.0
2013-03-28 02:07:17,581 DEBUG [cloud.capacity.CapacityManagerImpl] 
(Job-Executor-22:job-77 FirstFitRoutingAllocator) Hosts's actual total CPU: 
36256 and CPU after applying overprovisioning: 36256
2013-03-28 02:07:17,581 DEBUG [cloud.capacity.CapacityManagerImpl] 
(Job-Executor-22:job-77 FirstFitRoutingAllocator) Free CPU: 26756 , Requested 
CPU: 500
2013-03-28 02:07:17,581 DEBUG [cloud.capacity.CapacityManagerImpl] 
(Job-Executor-22:job-77 FirstFitRoutingAllocator) Free RAM: 19516366848 , 
Requested RAM: 536870912
2013-03-28 02:07:17,581 DEBUG [cloud.capacity.CapacityManagerImpl] 
(Job-Executor-22:job-77 FirstFitRoutingAllocator) Host has enough CPU and RAM 
available
2013-03-28

Re: [QuickCloud] zero to cloud in less than a minute

[prasanna]

This is a significant step no doubt!

One comment - I think the deployDataCenter.py should move out of the
 phase of the devcloud/pom.xml. When it runs the install
phase which includes the package phase the build will fail with the
following  stack:

https://gist.github.com/vogxn/5264956

In the bvt branch I work around this problem by putting the deploy
into the integration-test phase and into a profile that takes a
property which is the config file of marvin.

On 28 March 2013 05:49, Chiradeep Vittal  wrote:
> This should now be usable for production use as well
> Follow instructions here
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/QuickCloud#QuickClou
> d-howto2
>
> From:  Ahmad Emneina 
> Reply-To:  "aemne...@gmail.com" 
> Date:  Wednesday, March 27, 2013 10:34 AM
> To:  Chiradeep Vittal 
> Cc:  "dev@cloudstack.apache.org" 
> Subject:  Re: [QuickCloud] zero to cloud in less than a minute
>
>
> +1
> so awesome!
>
>
> On Wed, Mar 27, 2013 at 10:17 AM, Chiradeep Vittal
>  wrote:
>
> Yes (actually that's what the instructions say)
>
> On 3/26/13 10:46 PM, "Ahmad Emneina"  wrote:
>
>>would someone be able to fire up all those services (say for a basic zone)
>>on one host?
>>
>>
>>On Tue, Mar 26, 2013 at 10:37 PM, Chiradeep Vittal <
>>chiradeep.vit...@citrix.com> wrote:
>>
>>> Following the discussion [1], we have QuickCloud in a rough-but-ready
>>> state for developers to try out
>>> Instructions  for developers to try it out with DevCloud2 here:
>>>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/QuickCloud
> 
>>>
>>> For now only Mac / Unix developers can use this workflow since NFS
>>>mounts
>>> are required.
>>>
>>> [1] http://markmail.org/thread/ajw7b6arhluqcuv2
>>>
>
>
>
>
>
>
>
>

Re: [ACS4.1] blockers

[Sheng Yang]

Abhi,

As Chip and I said, CLOUDSTACK-1755 is not a release blocker and would
be fixed in 4.2(as issue indicated).

--Sheng

On Wed, Mar 27, 2013 at 9:57 PM, Abhinandan Prateek
 wrote:
> There is some encouraging movement on 4.1 issues but still we have some of
> the blockers and criticals open:
>
>
> CLOUDSTACK-1819 Kishan Kavala
> CLOUDSTACK-1805 Kelven Yang
> CLOUDSTACK-1755 Sheng Yang
> CLOUDSTACK-1664 Murali Reddy
>
>
>
> -abhi
>
>
> On 27/03/13 8:03 PM, "Abhinandan Prateek" 
> wrote:
>
>>Text only list of blockers and criticals in 4.1 branch, please treat these
>>with expected urgency:
>>
>>CLOUDSTACK-1819Kishan Kavala
>>CLOUDSTACK-1811Kelven Yang
>>CLOUDSTACK-1810Min Chen
>>CLOUDSTACK-1805Kelven Yang
>>CLOUDSTACK-1776Kelven Yang
>>CLOUDSTACK-1755Sheng Yang
>>CLOUDSTACK-1673Murali Reddy
>>CLOUDSTACK-1664Kelven Yang
>>
>>
>>-abhi
>>
>>On 27/03/13 7:46 PM, "Chip Childers"  wrote:
>>
>>>
>>>I'm sorry, but I can't read this email's content particularly well...
>>>Can you please be sure to email in plain text?
>>>
>>>On Wed, Mar 27, 2013 at 11:28:26AM +, Abhinandan Prateek wrote:
 Team,
   I think the 4.1 RC is not yet made as there are still several
blockers and criticals, please treat them as high priority.
 T   Key Summary AssigneeReporterP   Status
Resolution  Created Updated Due

[Bug]
CLOUDSTACK-1819

 AWS Regions - Issues seen when trying to move a zone from 1 region to
another.
 Kishan
Kavala   Sangeetha
>Hariharana
>ngeethah> [Critical]  [Open]  OpenUnresolved  27/Mar/13
>  27/Mar/13


Actions


[Bug]
CLOUDSTACK-1812

 create physical network fails while creating basic
zone
 Venkata Siva Vijayendra
Bhamidipati  Srikanteswararao
Talluri   [Blocker]   [Open]  OpenUnresolved  26/Mar/13
27/Mar/13


Actions


[Bug]
CLOUDSTACK-1811

 Upgrade 4.0->4.1 - When upgrade scripts fail , component loading
continues and management server
starts.
 Kelven
Yang
Sangeetha
Hariharan [Critical]  [Reopened]  ReopenedUnresolved
26/Mar/13   27/Mar/13


Actions


[Bug]
CLOUDSTACK-1810

 listTemplate API with templatefilter=featured|community is not
returning any
list
 Min
Chen Srikanteswararao
Talluri   [Blocker]   [Open]  OpenUnresolved  26/Mar/13
26/Mar/13


Actions


[Bug]

Re: [DISCUSS] create a general@ mailing list?

[Noah Slater]

Just a note that the previous two +1 votes are actually -1 votes in the
context of the DISCUSS topic.

I am also ready to cast my -1 vote.


On 28 March 2013 16:56, Kelceydamage@bbits  wrote:

> +1 from me as well. It duplicates or segregates, neither of which seem
> like a positive change.
>
> -kd
>
> Sent from my iPhone
>
> On Mar 28, 2013, at 9:46 AM, Joe Brockmeier  wrote:
>
> > On Thu, Mar 28, 2013, at 09:57 AM, Chip Childers wrote:
> >> Given that we have a mix of responses to this question (some for it and
> >> some against it), and that the pattern seems to be tied to the unliked
> >> practice of creating umbrella communities, I believe that we should not
> >> make the change within CloudStack.
> >
> > +1
> >
> > Maybe someday we'll need one. But we're a long way from that right now.
> >
> > Best,
> >
> > jzb
> > --
> > Joe Brockmeier
> > j...@zonker.net
> > Twitter: @jzb
> > http://www.dissociatedpress.net/
>



-- 
NS

Re: Couple VMWare Issues with 4.1

[Francois Gaudreault]

2 - Public VLAN created on vSwitch0 even if we tell to use vSwitch2.

For some reason, CS creates a tagged port-group on the vSwitch0 for the
public interface of the VR even if we told CS to use vSwitch2. In fact, CS
creates and uses the public port-group on the vSwitch2... So why it creates
an unused port-group on vSwitch0? See attached screenshot.

Preparing NIC device on network cloud.public.142.0.1-vSwitch0 INFO
[vmware.resource.VmwareResource] (DirectAgent-47:yul01vi13.ops.dot)
Prepare NIC device based on NicTO: {"deviceId":4,"networkRateMbps":-
1,"defaultNic":false,"ip":"0.0.0.0","netmask":"255.255.255.255","gateway":"1
0.0.142.1","mac":"02:00:3b:5a:00:02","dns1":"10.0.31.24","dns2":"10.0.31.28",
"broadcastType":"Vlan","type":"Public","broadcastUri":"vlan://142","isolatio
nUri":"vlan://142","isSecurityGroupEnabled":false}
INFO  [vmware.resource.VmwareResource] (DirectAgent-
47:yul01vi13.ops.dot) Prepare network on vSwitch: P[vSwitch0:untagged]
with name prefix: cloud.public INFO  [vmware.mo.HypervisorHostHelper]
(DirectAgent-47:yul01vi13.ops.dot) Network cloud.public.142.0.1-vSwitch0 is
ready on vSwitch vSwitch0 INFO  [vmware.mo.HypervisorHostHelper]
(DirectAgent-47:yul01vi13.ops.dot) Network cloud.public.142.0.1-vSwitch0 is
ready on vSwitch vSwitch0 INFO  [vmware.resource.VmwareResource]
(DirectAgent-47:yul01vi13.ops.dot) Preparing NIC device on network
cloud.public.142.0.1-vSwitch0


This is a bug, if I'm not mistaken I've seen some reference in source code to 
try to use vSwitch0 as default, unless another vSwitch is defined (in your 
case, its vSwitch2).
Specifically, the create-schema.sql file and VmwareManagerImpl.java have hardcoded references of 
vSwitch0 - that technically should be overridden by "vmware traffic label" defined in 
"physical network" settings. Something with a logic there did not go smooth and hence 
additional creation of unused port-group on vSwitch0.

Please file the bug and include the content above.

Bug created under:
https://issues.apache.org/jira/browse/CLOUDSTACK-1835

--
Francois Gaudreault
Architecte de Solution Cloud | Cloud Solutions Architect
fgaudrea...@cloudops.com
514-629-6775
- - -
CloudOps
420 rue Guy
Montréal QC  H3J 1S6
www.cloudops.com
@CloudOps_

Re: [DISCUSS] Palo Alto Integration

[Will Stevens]

I am trying to implement the non-overlapping cidrs right now and I have
some questions.  Does the ExternalGuestNetworkGuru create networks with
non-overlapping cidrs by default?  Or do I need to override it's 'design'
and 'implement' methods to implement non overlapping cidrs?

If I have to write my own methods, I think I understand how to
override ExternalGuestNetworkGuru and then get it to run by adding it to
the components.xml (or nonoss-components.xml) as well as the
componentContext.xml.in.

If I do not have to actually write the logic for the non-overlapping cidrs
(which i am hoping is the case), and the ExternalGuestNetworkGuru actually
implements that logic, how would I get the ExternalGuestNetworkGuru into my
flow without actually overriding the class?  I understand that the
components are loaded through the components.xml stuff, but its not clear
how you specify which NetworkGuru should be used in my specific flow.

I am basically working from this
documentand
the code.  Is there any other resources I should be aware of for
extending the CloudStack networking functionality?

I have a good start on a Resource, ExternalFirewallElement and an
ExternalFirewallService.  I can currently set the Palo Alto as the provider
of Firewall, SourceNat, StaticNat and Port Forwarding services.  I can
currently Add, List, Configure and Delete my Palo Alto provider.

I am getting there, but I still feel like there are gaps in my knowledge
when using the CS networking plugin functionality.

Thanks,

Will


On Mon, Mar 18, 2013 at 2:46 AM, Murali Reddy wrote:

> On 16/03/13 1:46 AM, "Will Stevens"  wrote:
> >
> >1. Restrict the available subnets for each account so two accounts can't
> >create overlapping subnets.
> >To me, this breaks the whole concept of cloud, but for enterprise
> >customers
> >this is not a huge limitation because they usually solve this problem this
> >way.
> >
> >2. Run multiple Palo Alto VM firewalls and associate one VM firewall per
> >account.
> >The management overhead of this is crazy, so this type of implementation
> >would be very hard to work with.
> >
> >Since I do not like either of these approaches, I wanted to see if I could
> >get some feedback on this.  Are there other alternatives that would solve
> >the problem more elegantly that I have not mentioned?  What would be the
> >best way to solve this problem in a 'CloudStack way'?
>
> Unfortunately vendor appliacnces CloudStack support, does not have
> multi-tenancy yet. 'CloudStack way' has been both #1 and #2 to work around
> this.
>
> Please see [1], so 'external guest network' Guru designs the network such
> that no two guest networks in a zone using external network device has
> overlapping Cidr's. You may use 'external guest network' guru or extend it
> ensure automatically generated non-overlapping CIDR's for guest network.
>
> Also CloudStack already supports notion of multiple provider instances per
> physical network. Using which for load balancer devices there is generic
> management piece of code to allocate a dedicated (per tenant) or shared
> load balancer from a pool of admin provisioned load balancers [2]. See if
> this helps if you intend to support pool of firewall VM's.
>
> [1] server/src/com/cloud/network/guru/ExternalGuestNetworkGuru.java
> [2] server/src/com/cloud/network/ExternalLoadBalancerDeviceManagerImpl.java
>
> -Murali
>
>
> >
> >Any feedback on this would be appreciated.
> >
> >Cheers,
> >
> >Will
> >
>
>
>

Re: [ACS41][QA] Has anyone upgraded from 4.0 to 4.1

[Chip Childers]

On Thu, Mar 28, 2013 at 09:51:16AM -0700, Sangeetha Hariharan wrote:
> Can we get a confirmation on the approach we want to take?
> 
> 1. We are going to fix the router for  the case - " if the router has 
> upgraded its scripts, and then adjust how we call edithosts.sh" ?
> 2. Going to suggest a reboot (start and stop) of all the system Vms 
> (SSVM,CPVM and routers) as part of Upgrade procedure?

Option 2 is my preference.  Option 1 requires more testing, etc...

Re: Attaching Volumes to Windows Instance

[Ahmad Emneina]

bumping and adding in the resident kvm gurus.


On Thu, Mar 28, 2013 at 9:56 AM, Maurice Lawler wrote:

> Greetings,
>
> I am utilizing CloudStack-oss-3.0.2-1 on CentOS 6.3 | KVM.
>
>
> It's running wonderfully, however, I have a Windows Instance I would like
> to attach a 'storage' volume to. However, when I go to add the volume it
> only lists the Linux falvor instances that are running to attach to.
>
> How can I get this secondary volume attached to this Windows Instance.
>
> PS: I have also powered off the instance and it still did not allow me to
> add it to the windows machine.
>
> Any suggestions, will be greatly appreciate !
>
> - Maurice

[DISCUSS]VMware Open Source APIs

[Musayev, Ilya]

Stumbled upon Open Source Version of Java API for VSphere on 
vijava.sourceforge.net

Wanted to get the feel of developers if we can consider using these APIs 
instead and make VMWare support as an Open Source build (vs nonoss as of now).

RE: Attaching Volumes to Windows Instance

[Edison Su]

Need to install virtio disk pv driver inside Windows guest VM, otherwise the 
disk will not be shown up.

From: Ahmad Emneina [mailto:aemne...@gmail.com]
Sent: Thursday, March 28, 2013 10:46 AM
To: dev@cloudstack.apache.org; Marcus Sorensen; Edison Su
Subject: Re: Attaching Volumes to Windows Instance

bumping and adding in the resident kvm gurus.

On Thu, Mar 28, 2013 at 9:56 AM, Maurice Lawler 
mailto:maurice.law...@me.com>> wrote:
Greetings,

I am utilizing CloudStack-oss-3.0.2-1 on CentOS 6.3 | KVM.


It's running wonderfully, however, I have a Windows Instance I would like to 
attach a 'storage' volume to. However, when I go to add the volume it only 
lists the Linux falvor instances that are running to attach to.

How can I get this secondary volume attached to this Windows Instance.

PS: I have also powered off the instance and it still did not allow me to add 
it to the windows machine.

Any suggestions, will be greatly appreciate !

- Maurice

Re: Attaching Volumes to Windows Instance

[Maurice Lawler]

But I cannot attach it to the Windows Instance. When I attempt to attach, the 
only things listed in the Attachment list is the linux flavors. So, once I get 
this installed, reboot the device; I will then be able to see the Windows 
Instances in the attachment list? 


On Mar 28, 2013, at 1:03 PM, Edison Su  wrote:

> Need to install virtio disk pv driver inside Windows guest VM, otherwise the 
> disk will not be shown up.
> 
> From: Ahmad Emneina [mailto:aemne...@gmail.com]
> Sent: Thursday, March 28, 2013 10:46 AM
> To: dev@cloudstack.apache.org; Marcus Sorensen; Edison Su
> Subject: Re: Attaching Volumes to Windows Instance
> 
> bumping and adding in the resident kvm gurus.
> 
> On Thu, Mar 28, 2013 at 9:56 AM, Maurice Lawler 
> mailto:maurice.law...@me.com>> wrote:
> Greetings,
> 
> I am utilizing CloudStack-oss-3.0.2-1 on CentOS 6.3 | KVM.
> 
> 
> It's running wonderfully, however, I have a Windows Instance I would like to 
> attach a 'storage' volume to. However, when I go to add the volume it only 
> lists the Linux falvor instances that are running to attach to.
> 
> How can I get this secondary volume attached to this Windows Instance.
> 
> PS: I have also powered off the instance and it still did not allow me to add 
> it to the windows machine.
> 
> Any suggestions, will be greatly appreciate !
> 
> - Maurice
> 

Re: [DISCUSS]VMware Open Source APIs

[David Nalley]

On Thu, Mar 28, 2013 at 2:00 PM, Musayev, Ilya  wrote:
> Stumbled upon Open Source Version of Java API for VSphere on 
> vijava.sourceforge.net
>
> Wanted to get the feel of developers if we can consider using these APIs 
> instead and make VMWare support as an Open Source build (vs nonoss as of now).


Personally I think that since an open source option exists we have a
compelling reason to try and adopt it provided there are no adverse
effects. The ASF exists to build open source, freely-available,
software for the public good.

--David

Re: [DISCUSS]VMware Open Source APIs

[Ahmad Emneina]

i agree, if there is feature parity between the sdk's we should use the
opensource one.


On Thu, Mar 28, 2013 at 11:07 AM, David Nalley  wrote:

> On Thu, Mar 28, 2013 at 2:00 PM, Musayev, Ilya  wrote:
> > Stumbled upon Open Source Version of Java API for VSphere on
> vijava.sourceforge.net
> >
> > Wanted to get the feel of developers if we can consider using these APIs
> instead and make VMWare support as an Open Source build (vs nonoss as of
> now).
>
>
> Personally I think that since an open source option exists we have a
> compelling reason to try and adopt it provided there are no adverse
> effects. The ASF exists to build open source, freely-available,
> software for the public good.
>
> --David
>

Re: [ACS41][QA] Has anyone upgraded from 4.0 to 4.1

[Marcus Sorensen]

I'm also not confident that option 1 really fixes anything. The user has to
reboot their system VMS eventually, and even if we fix this one thing to
help them get by until they do, what other lingering issues will arise?
On Mar 28, 2013 11:38 AM, "Chip Childers"  wrote:

> On Thu, Mar 28, 2013 at 09:51:16AM -0700, Sangeetha Hariharan wrote:
> > Can we get a confirmation on the approach we want to take?
> >
> > 1. We are going to fix the router for  the case - " if the router has
> upgraded its scripts, and then adjust how we call edithosts.sh" ?
> > 2. Going to suggest a reboot (start and stop) of all the system Vms
> (SSVM,CPVM and routers) as part of Upgrade procedure?
>
> Option 2 is my preference.  Option 1 requires more testing, etc...
>

RE: [ACS41][QA] Has anyone upgraded from 4.0 to 4.1

[Sangeetha Hariharan]

Then we can go with the option of reboot (start and stop) of all the system Vms 
(SSVM,CPVM and routers) as part of Upgrade procedure ?

-Thanks 
Sangeetha

-Original Message-
From: Marcus Sorensen [mailto:shadow...@gmail.com] 
Sent: Thursday, March 28, 2013 11:21 AM
To: Chip Childers
Cc: dev@cloudstack.apache.org
Subject: Re: [ACS41][QA] Has anyone upgraded from 4.0 to 4.1

I'm also not confident that option 1 really fixes anything. The user has to 
reboot their system VMS eventually, and even if we fix this one thing to help 
them get by until they do, what other lingering issues will arise?
On Mar 28, 2013 11:38 AM, "Chip Childers"  wrote:

> On Thu, Mar 28, 2013 at 09:51:16AM -0700, Sangeetha Hariharan wrote:
> > Can we get a confirmation on the approach we want to take?
> >
> > 1. We are going to fix the router for  the case - " if the router 
> > has
> upgraded its scripts, and then adjust how we call edithosts.sh" ?
> > 2. Going to suggest a reboot (start and stop) of all the system Vms
> (SSVM,CPVM and routers) as part of Upgrade procedure?
>
> Option 2 is my preference.  Option 1 requires more testing, etc...
>

Re: Unable to create a deployment for VM

[Maurice Lawler]

> Reviewing the logs, grepping for job 77 I get the following errors: This is 
> when spinning up a instance from a template. 
> 
> 
> 
> [root@lunder ~]# cat  /var/log/cloud/management/management-server.log |grep  
> job-77
> 2013-03-28 02:07:17,540 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (catalina-exec-22:null) submit async job-77, details: AsyncJobVO {id:77, 
> userId: 2, accountId: 2, sessionKey: null, instanceType: VirtualMachine, 
> instanceId: 11, cmd: com.cloud.api.commands.DeployVMCmd, cmdOriginator: null, 
> cmdInfo: 
> {"sessionkey":"AX3hqEZ8EpqXTA/AsF3oDek4MIc\u003d","ctxUserId":"2","serviceOfferingId":"97b8d235-7b71-4ca0-8a04-fe90ec9220f0","securitygroupids":"f78f103f-77fb-4fbe-b437-91b656c8427f","zoneId":"28b7e853-1b2c-474c-be2f-4b91466fd4a9","templateId":"c4e7d8f3-d80b-45da-a29f-19687d7494f2","response":"json","id":"11","hypervisor":"KVM","name":"temptest","diskOfferingId":"07148505-9dd2-4f31-9494-bb82c64c7436","_":"1364454437368","ctxAccountId":"2","ctxStartEventId":"429","displayname":"temptest"},
>  cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0, 
> processStatus: 0, resultCode: 0, result: null, initMsid: 279278805451068, 
> completeMsid: null, lastUpdated: null, lastPolled: null, created: null}
> 2013-03-28 02:07:17,540 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (Job-Executor-22:job-77) Executing com.cloud.api.commands.DeployVMCmd for 
> job-77
> 2013-03-28 02:07:17,559 DEBUG [cloud.capacity.CapacityManagerImpl] 
> (Job-Executor-22:job-77) VM state transitted from :Stopped to Starting with 
> event: StartRequestedvm's original host id: null new host id: null host id 
> before state transition: null
> 2013-03-28 02:07:17,559 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
> (Job-Executor-22:job-77) Successfully transitioned to start state for 
> VM[User|i-2-11-VM] reservation id = 77d9fc64-54d5-460e-bf85-ce9378bcf1cb
> 2013-03-28 02:07:17,562 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
> (Job-Executor-22:job-77) Trying to deploy VM, vm has dcId: 1 and podId: null
> 2013-03-28 02:07:17,562 DEBUG [cloud.vm.VirtualMachineManagerImpl] 
> (Job-Executor-22:job-77) Deploy avoids pods: null, clusters: null, hosts: null
> 2013-03-28 02:07:17,563 DEBUG [cloud.deploy.FirstFitPlanner] 
> (Job-Executor-22:job-77) DeploymentPlanner allocation algorithm: random
> 2013-03-28 02:07:17,564 DEBUG [cloud.deploy.FirstFitPlanner] 
> (Job-Executor-22:job-77) Trying to allocate a host and storage pools from 
> dc:1, pod:null,cluster:null, requested cpu: 500, requested ram: 536870912
> 2013-03-28 02:07:17,564 DEBUG [cloud.deploy.FirstFitPlanner] 
> (Job-Executor-22:job-77) Is ROOT volume READY (pool already allocated)?: No
> 2013-03-28 02:07:17,564 DEBUG [cloud.deploy.FirstFitPlanner] 
> (Job-Executor-22:job-77) Searching all possible resources under this Zone: 1
> 2013-03-28 02:07:17,565 DEBUG [cloud.deploy.FirstFitPlanner] 
> (Job-Executor-22:job-77) Listing clusters in order of aggregate capacity, 
> that have (atleast one host with) enough CPU and RAM capacity under this 
> Zone: 1
> 2013-03-28 02:07:17,566 DEBUG [cloud.deploy.FirstFitPlanner] 
> (Job-Executor-22:job-77) CPUOverprovisioningFactor considered: 1.0
> 2013-03-28 02:07:17,573 DEBUG [cloud.deploy.FirstFitPlanner] 
> (Job-Executor-22:job-77) Checking resources in Cluster: 1 under Pod: 1
> 2013-03-28 02:07:17,573 DEBUG [cloud.deploy.FirstFitPlanner] 
> (Job-Executor-22:job-77) Calling HostAllocators to find suitable hosts
> 2013-03-28 02:07:17,573 DEBUG [allocator.impl.FirstFitAllocator] 
> (Job-Executor-22:job-77 FirstFitRoutingAllocator) Looking for hosts in dc: 1  
> pod:1  cluster:1
> 2013-03-28 02:07:17,575 DEBUG [allocator.impl.FirstFitAllocator] 
> (Job-Executor-22:job-77 FirstFitRoutingAllocator) FirstFitAllocator has 1 
> hosts to check for allocation: [Host[-1-Routing]]
> 2013-03-28 02:07:17,577 DEBUG [allocator.impl.FirstFitAllocator] 
> (Job-Executor-22:job-77 FirstFitRoutingAllocator) Found 1 hosts for 
> allocation after prioritization: [Host[-1-Routing]]
> 2013-03-28 02:07:17,577 DEBUG [allocator.impl.FirstFitAllocator] 
> (Job-Executor-22:job-77 FirstFitRoutingAllocator) Looking for speed=500Mhz, 
> Ram=512
> 2013-03-28 02:07:17,578 DEBUG [cloud.capacity.CapacityManagerImpl] 
> (Job-Executor-22:job-77 FirstFitRoutingAllocator) Checking if host: 1 has 
> enough capacity for requested CPU: 500 and requested RAM: 536870912 , 
> cpuOverprovisioningFactor: 1.0
> 2013-03-28 02:07:17,581 DEBUG [cloud.capacity.CapacityManagerImpl] 
> (Job-Executor-22:job-77 FirstFitRoutingAllocator) Hosts's actual total CPU: 
> 36256 and CPU after applying overprovisioning: 36256
> 2013-03-28 02:07:17,581 DEBUG [cloud.capacity.CapacityManagerImpl] 
> (Job-Executor-22:job-77 FirstFitRoutingAllocator) Free CPU: 26756 , Requested 
> CPU: 500
> 2013-03-28 02:07:17,581 DEBUG [cloud.capacity.CapacityManagerImpl] 
> (Job-Executor-22:job-77 FirstFitRoutingAllocator) Free RAM: 19516366848 , 
> Requested RAM: 536870912
> 2013-03-28 02

New Committer: Ilya Musayev

[Chip Childers]

The Project Management Committee (PMC) for Apache CloudStack
has asked Ilya Musayev to become a committer and we are pleased to 
announce that they have accepted.

Being a committer allows many contributors to contribute more
autonomously. For developers, it makes it easier to submit changes and
eliminates the need to have contributions reviewed via the patch
submission process. Whether contributions are development-related or
otherwise, it is a recognition of a contributor's participation in the
project and commitment to the project and the Apache Way.

Please join me in congratulating Ilya!

--Chip Childers
on behalf of the CloudStack PMC

RE: New Committer: Ilya Musayev

[Pranav Saxena]

Congrats Ilya . Welcome :)

Regards,
Pranav

-Original Message-
From: Chip Childers [mailto:chip.child...@sungard.com] 
Sent: Friday, March 29, 2013 12:06 AM
To: dev@cloudstack.apache.org
Subject: New Committer: Ilya Musayev

The Project Management Committee (PMC) for Apache CloudStack has asked Ilya 
Musayev to become a committer and we are pleased to announce that they have 
accepted.

Being a committer allows many contributors to contribute more autonomously. For 
developers, it makes it easier to submit changes and eliminates the need to 
have contributions reviewed via the patch submission process. Whether 
contributions are development-related or otherwise, it is a recognition of a 
contributor's participation in the project and commitment to the project and 
the Apache Way.

Please join me in congratulating Ilya!

--Chip Childers
on behalf of the CloudStack PMC

Re: New Committer: Ilya Musayev

[Ahmad Emneina]

brilliant news, congrats Ilya!


On Thu, Mar 28, 2013 at 11:40 AM, Pranav Saxena wrote:

> Congrats Ilya . Welcome :)
>
> Regards,
> Pranav
>
> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Friday, March 29, 2013 12:06 AM
> To: dev@cloudstack.apache.org
> Subject: New Committer: Ilya Musayev
>
> The Project Management Committee (PMC) for Apache CloudStack has asked
> Ilya Musayev to become a committer and we are pleased to announce that they
> have accepted.
>
> Being a committer allows many contributors to contribute more
> autonomously. For developers, it makes it easier to submit changes and
> eliminates the need to have contributions reviewed via the patch submission
> process. Whether contributions are development-related or otherwise, it is
> a recognition of a contributor's participation in the project and
> commitment to the project and the Apache Way.
>
> Please join me in congratulating Ilya!
>
> --Chip Childers
> on behalf of the CloudStack PMC
>

RE: New Committer: Ilya Musayev

[Kelcey Damage (BT)]

It's about time :)

Congrats!

-kd


>-Original Message-
>From: Chip Childers [mailto:chip.child...@sungard.com]
>Sent: Thursday, March 28, 2013 11:36 AM
>To: dev@cloudstack.apache.org
>Subject: New Committer: Ilya Musayev
>
>The Project Management Committee (PMC) for Apache CloudStack has asked
>Ilya Musayev to become a committer and we are pleased to announce that
>they have accepted.
>
>Being a committer allows many contributors to contribute more autonomously.
>For developers, it makes it easier to submit changes and eliminates the
need to
>have contributions reviewed via the patch submission process. Whether
>contributions are development-related or otherwise, it is a recognition of
a
>contributor's participation in the project and commitment to the project
and
>the Apache Way.
>
>Please join me in congratulating Ilya!
>
>--Chip Childers
>on behalf of the CloudStack PMC

RE: [master branch issue ]Problem with SystemVMs and Primary Storage in latest Master

[Edison Su]

> -Original Message-
> From: Srikanteswararao Talluri [mailto:srikanteswararao.tall...@citrix.com]
> Sent: Thursday, March 28, 2013 5:02 AM
> To: dev@cloudstack.apache.org
> Subject: RE: [master branch issue ]Problem with SystemVMs and Primary
> Storage in latest Master
> 
> 
> 
> > -Original Message-
> > From: Chip Childers [mailto:chip.child...@sungard.com]
> > Sent: Thursday, March 28, 2013 5:24 PM
> > To: 
> > Subject: Re: [master branch issue ]Problem with SystemVMs and Primary
> > Storage in latest Master
> >
> > On Mar 28, 2013, at 6:00 AM, Pranav Saxena 
> > wrote:
> >
> > > Ok , Suresh was right in pointing that out that we need to select
> > > "cluster " right
> > now as the scope for primary storage with xenserver as the hypervisor .
> >
> > Sounds like we should actually have the default behavior match the
> > previous versions, and make cluster the default.
> 
> +1

+1, The UI should use "cluster" wide storage as the default, that's the default 
behavior of createstoragepool API: if no scope is specified, it implies 
"cluster" scope.

> 
> >
> >
> > > With "Zone-wide" , we see this error . Perhaps I can introduce a
> > > check in the UI
> > for the scope depending upon the hypervisor type (xen/KVM) since we
> > don't support zone-wide primary storage for Xenserver as of now.
> >
> > +1
> >
> > >
> > > My set up is working fine now.
> > >
> > > Thanks,
> > > Pranav
> > >
> > > -Original Message-
> > > From: Nitin Mehta [mailto:nitin.me...@citrix.com]
> > > Sent: Thursday, March 28, 2013 3:17 PM
> > > To: dev@cloudstack.apache.org
> > > Cc: Abhinandan Prateek
> > > Subject: Re: [master branch issue ]Problem with SystemVMs and
> > > Primary Storage in latest Master
> > >
> > > Yes, I saw the same issue yesterday evening.
> > >
> > > On 28/03/13 2:29 PM, "Pranav Saxena" 
> wrote:
> > >
> > >> Hi ,
> > >>
> > >> There seems to be a problem with the latest master branch code
> > >> though I did not happen to see any exception being thrown.
> > >>
> > >> The system VM's don't come up and the primary storage added as part
> > >> of the zone creation wizard does not show up on the host in the
> > >> XenCenter UI .
> > >>
> > >> Anyone else happened to see this issue ?
> > >>
> > >> Thanks,
> > >> Pranav
> > >
> > >

Re: [MERGE] bvt branch to master

[Chip Childers]

On Thu, Mar 28, 2013 at 07:36:58PM +0530, Prasanna Santhanam wrote:
> I'd like to merge the bvt branch into master. The proposal [1] was to
> stabilize master by allowing devs to quickly setup CloudStack using
> simulated hypervisors and run some basic tests against it.
> 
> The bvt branch integrates the testing of cloudstack using marvin and
> the simulator hypervisor. Alternately you may use devcloud as well
> with the appropriate maven profiles enabled. One can try the
> integrated tests today as described in [2]
> 
> While this is not to be touted as the magic pill for master stability
> I think it is a good first step towards bringing together tests as
> part of the build system. I've tested the steps on Linux and OSX.
> 
> [1] http://s.apache.org/5Lc
> [2] https://cwiki.apache.org/confluence/x/PgvMAQ
> 
> Thanks,
> 
> -- 
> Prasanna.,
>

+1 - this looks good to me!

Re: Jetty Failing on latest master due to class UCS manager not Found

[Chiradeep Vittal]

For optional dependencies, JSR330 injection requires using setter
injection.
You should write

@Inject void setGslbProvider(GslbProvider provider) {
  this._gslbProvider = provider;
}



On 3/27/13 8:36 PM, "Murali Reddy"  wrote:

>On 28/03/13 9:00 AM, "Rajesh Battala"  wrote:
>
>>Jetty is failing to start on latest master building oss.
>>Am on the latest master, building oss and starting jetty is failing with
>>below error. 
>>
>>Error creating bean with name 'globalLoadBalancingRulesServiceImpl':
>>Injection of autowired dependencies failed; nested exception is
>>org.springframewor
>>  k.beans.factory.BeanCreationException: Could not autowire field:
>>protected org.apache.cloudstack.region.
>>   gslb.GslbServiceProvider
>>org.apache.cloudstack.region.gslb.GlobalLoadBalancingRulesServiceImpl._gs
>>l
>>bProv  ider;
>>nested exception is
>>org.springframework.beans.factory.NoSuchBeanDefinitionException: No
>>matching b  ean
>>of type [org.apache.cloudstack.region.gslb.GslbServiceProvider] found for
>>dependency: expected at le
>>  ast 1 bean which qualifies as autowire candidate for this
>>dependency. Dependency annotations: {@javax.in
>>  ject.Inject()}
>>at 
>>org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostP
>>r
>>ocessor.postProcess
>>   PropertyValues(AutowiredAnnotationBeanPostProcessor.java:287)
>>at org.springframe
>
>Please pull latest master, I pushed a fix.
>

Re: [ACS41][QA] Has anyone upgraded from 4.0 to 4.1

[Chip Childers]

On Thu, Mar 28, 2013 at 11:28:33AM -0700, Sangeetha Hariharan wrote:
> Then we can go with the option of reboot (start and stop) of all the system 
> Vms (SSVM,CPVM and routers) as part of Upgrade procedure ?

Sounds like it.  Care to add a note to the release notes wiki page to
this effect?

> 
> -Thanks 
> Sangeetha
> 
> -Original Message-
> From: Marcus Sorensen [mailto:shadow...@gmail.com] 
> Sent: Thursday, March 28, 2013 11:21 AM
> To: Chip Childers
> Cc: dev@cloudstack.apache.org
> Subject: Re: [ACS41][QA] Has anyone upgraded from 4.0 to 4.1
> 
> I'm also not confident that option 1 really fixes anything. The user has to 
> reboot their system VMS eventually, and even if we fix this one thing to help 
> them get by until they do, what other lingering issues will arise?
> On Mar 28, 2013 11:38 AM, "Chip Childers"  wrote:
> 
> > On Thu, Mar 28, 2013 at 09:51:16AM -0700, Sangeetha Hariharan wrote:
> > > Can we get a confirmation on the approach we want to take?
> > >
> > > 1. We are going to fix the router for  the case - " if the router 
> > > has
> > upgraded its scripts, and then adjust how we call edithosts.sh" ?
> > > 2. Going to suggest a reboot (start and stop) of all the system Vms
> > (SSVM,CPVM and routers) as part of Upgrade procedure?
> >
> > Option 2 is my preference.  Option 1 requires more testing, etc...
> >
> 

RE: Storage Subsystem 2.0 plugin docs

[Vladimir Popovski]

Hi Mike,



Say hi to John from me. He is an amazing guy and most likely I will meet
him during the OS summit.



We don’t have any hypervisor-specific code for manipulating with storage
objects. There was no such a need for the OpenStack drives. Inside of our
systems, we usually provide a direct access to the HW (PCI Passthrough) for
our VMs and they skip the HV level all together (and access network-related
storage resources “directly”).



I hope we will not need to invent it for the CS driver/plugin.



Regarding datastores per volume – I hope there will be no limitations in
terms of number of datastores per server and per cluster/zone. Potentially,
this approach will create thousands/millions of datastores and we must be
ready for it.



Regards,

-Vladimir





*From:* Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
*Sent:* Wednesday, March 27, 2013 1:18 PM
*To:* Vladimir Popovski
*Cc:* Edison Su; cloudstack-...@incubator.apache.org
*Subject:* Re: Storage Subsystem 2.0 plugin docs



Hi Vladimir,



I figured you were away and would get back to us when you could.  :)



I was talking to John Griffith.  It sounds like you worked with him on
OpenStack.



You are correct that I am interested in your Option 1:  Mapping a single VM
or a single data disk to a single volume on our SAN (via a single Datastore
for VMware, a single Storage Repository for XenServer, etc.).



I have code written that creates a XenServer Storage Repository and I am
testing code I finished writing last night to create a VMware Datastore.



We should decide where this will be placed in CloudStack because, as you
and others have commented, the storage plug-ins themselves should not have
to maintain this code.  For example, when HyperV support comes out in CS
later, we don't want to have to update all the storage plug-ins to support
it.



You don't happen to have code lying around that creates the necessary
storage objects for KVM and/or Oracle VM, do you?  :)



If not, we should start in on creating such logic at some point relatively
soon.



I'll send out my XenServer and VMware code to you and Edison when I finish
my testing (probably tomorrow).



Talk to you later!



On Wed, Mar 27, 2013 at 1:22 PM, Vladimir Popovski <
vladi...@zadarastorage.com> wrote:

Hi All,



I was away for couple of days, so sorry for the delay.



I’m completely with Mike & John (& others) on separating storage plugins
from hypervisor-related functions. If every plugin will need to implement
hypervisor-related code, it will be a big mess.



Our use-case is very similar to Mike’s – we would like to be able to
provision volumes with different QoS characteristics directly to VMs,
rather than adding them into “shared” datastores. It might be achieved in
two ways:

-  either to create separate data stores per each volume (storage
LUN), and from there to create volumes & assign to instances.

-  or to assign devices recognized by iSCSI Initiators directly to
instances (I’m not sure if it will be possible in VMware without datastores)



It looks like Mike started to work on the 1st approach. In this case, for
every volume there will be a separate datastore. If this is the preferred
direction for all storage plugins, then the hypervisor-specific logic of
datastore creation and creating/assigning volumes from the datastore will
be fairly common for all storage plug-ins. At the same time, the storage
plugin should have the control over the datastore management. It will
depend on the plugin, if dedicated or shared datastores should be created.



For the 2nd option (skipping the datastore layer) there might be plenty of
common code as well.



So, my questions are:

-  do you think it is beneficial to support both options for the CS
(or are we good with potentially huge number of datastores)?

-  are we all agree that HV-dependent storage code should be
generic and appropriate interfaces to be exposed?



Regards,

-Vladimir







*From:* Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
*Sent:* Wednesday, March 27, 2013 10:21 AM


*To:* Edison Su
*Cc:* cloudstack-...@incubator.apache.org; Vladimir Popovski
*Subject:* Re: Storage Subsystem 2.0 plugin docs



Sounds good, Edison



Last night I finished up code that uses the VI Java API to create a VMware
Datastore.



I want to test it a bit more before I have you look at it.



Today there is a Citrix CloudPlatform demo I'm participating in to handle
part of the SolidFire section of the demo, so I might not have time to do
my Datastore testing, but I should be done with it tomorrow.



Talk to you later!



On Wed, Mar 27, 2013 at 11:15 AM, Edison Su  wrote:

For vmware, current cloudstack doesn’t create a vmware datastore through
vmware’s API, admin needs to create the datastore in Vcenter at first, then
add it back into cloudstack. I am not familiar with how to create a VMware
datastore through Vmware’s API, but regarding to add a new host into a
cluster, the cur

Re: Storage Subsystem 2.0 plugin docs

[Mike Tutkowski]

Hi,

A bunch of us were talking about hypervisor limitations on the number of
iSCSI connections the other day.  Hopefully this is accurate, but the
thinking was we'd run out of VLANs first.

I sent you and Edison a little VMware code to create a datastore earlier
today.  Hopefully we can complete it and stick it in the CS storage
framework (Edison should be able to decide where) so that storage plug-ins
do not have to reproduce this code or even access it from a utility.

Talk to you later!


On Thu, Mar 28, 2013 at 1:26 PM, Vladimir Popovski <
vladi...@zadarastorage.com> wrote:

> Hi Mike,
>
>
>
> Say hi to John from me. He is an amazing guy and most likely I will meet
> him during the OS summit.
>
>
>
> We don’t have any hypervisor-specific code for manipulating with storage
> objects. There was no such a need for the OpenStack drives. Inside of our
> systems, we usually provide a direct access to the HW (PCI Passthrough) for
> our VMs and they skip the HV level all together (and access network-related
> storage resources “directly”).
>
>
>
> I hope we will not need to invent it for the CS driver/plugin.
>
>
>
> Regarding datastores per volume – I hope there will be no limitations in
> terms of number of datastores per server and per cluster/zone. Potentially,
> this approach will create thousands/millions of datastores and we must be
> ready for it.
>
>
>
> Regards,
>
> -Vladimir
>
>
>
>
>
> *From:* Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> *Sent:* Wednesday, March 27, 2013 1:18 PM
> *To:* Vladimir Popovski
> *Cc:* Edison Su; cloudstack-...@incubator.apache.org
>
> *Subject:* Re: Storage Subsystem 2.0 plugin docs
>
>
>
> Hi Vladimir,
>
>
>
> I figured you were away and would get back to us when you could.  :)
>
>
>
> I was talking to John Griffith.  It sounds like you worked with him on
> OpenStack.
>
>
>
> You are correct that I am interested in your Option 1:  Mapping a single
> VM or a single data disk to a single volume on our SAN (via a single
> Datastore for VMware, a single Storage Repository for XenServer, etc.).
>
>
>
> I have code written that creates a XenServer Storage Repository and I am
> testing code I finished writing last night to create a VMware Datastore.
>
>
>
> We should decide where this will be placed in CloudStack because, as you
> and others have commented, the storage plug-ins themselves should not have
> to maintain this code.  For example, when HyperV support comes out in CS
> later, we don't want to have to update all the storage plug-ins to support
> it.
>
>
>
> You don't happen to have code lying around that creates the necessary
> storage objects for KVM and/or Oracle VM, do you?  :)
>
>
>
> If not, we should start in on creating such logic at some point relatively
> soon.
>
>
>
> I'll send out my XenServer and VMware code to you and Edison when I finish
> my testing (probably tomorrow).
>
>
>
> Talk to you later!
>
>
>
> On Wed, Mar 27, 2013 at 1:22 PM, Vladimir Popovski <
> vladi...@zadarastorage.com> wrote:
>
> Hi All,
>
>
>
> I was away for couple of days, so sorry for the delay.
>
>
>
> I’m completely with Mike & John (& others) on separating storage plugins
> from hypervisor-related functions. If every plugin will need to implement
> hypervisor-related code, it will be a big mess.
>
>
>
> Our use-case is very similar to Mike’s – we would like to be able to
> provision volumes with different QoS characteristics directly to VMs,
> rather than adding them into “shared” datastores. It might be achieved in
> two ways:
>
> -  either to create separate data stores per each volume (storage
> LUN), and from there to create volumes & assign to instances.
>
> -  or to assign devices recognized by iSCSI Initiators directly
> to instances (I’m not sure if it will be possible in VMware without
> datastores)
>
>
>
> It looks like Mike started to work on the 1st approach. In this case, for
> every volume there will be a separate datastore. If this is the preferred
> direction for all storage plugins, then the hypervisor-specific logic of
> datastore creation and creating/assigning volumes from the datastore will
> be fairly common for all storage plug-ins. At the same time, the storage
> plugin should have the control over the datastore management. It will
> depend on the plugin, if dedicated or shared datastores should be created.
>
>
>
> For the 2nd option (skipping the datastore layer) there might be plenty
> of common code as well.
>
>
>
> So, my questions are:
>
> -  do you think it is beneficial to support both options for the
> CS (or are we good with potentially huge number of datastores)?
>
> -  are we all agree that HV-dependent storage code should be
> generic and appropriate interfaces to be exposed?
>
>
>
> Regards,
>
> -Vladimir
>
>
>
>
>
>
>
> *From:* Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> *Sent:* Wednesday, March 27, 2013 10:21 AM
>
>
> *To:* Edison Su
> *Cc:* cloudstack-...@incubator.apache.org; Vladimir 

New Committer: Animesh Chaturvedi

[Alex Huang]

The Podling Project Management Committee (PPMC) for Apache CloudStack has asked 
Animesh Chaturvedi to become a committer and we are pleased to announce that 
they have 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 me in congratulating Sateesh!



--Alex

on behalf of the CloudStack PPMC

RE: New Committer: Animesh Chaturvedi

[Pranav Saxena]

Congrats Animesh !:) . 

-Original Message-
From: Alex Huang [mailto:alex.hu...@citrix.com] 
Sent: Friday, March 29, 2013 1:27 AM
To: dev@cloudstack.apache.org
Subject: New Committer: Animesh Chaturvedi

The Podling Project Management Committee (PPMC) for Apache CloudStack has asked 
Animesh Chaturvedi to become a committer and we are pleased to announce that 
they have 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 me in congratulating Sateesh!



--Alex

on behalf of the CloudStack PPMC

Re: [QuickCloud] zero to cloud in less than a minute

[Chiradeep Vittal]

>
>Wow this is awesome. Will you consider writing a blog post about this?

Yes, sure. 

One thing that is not 'ready' is the operational / packaging side of
things.
Copying systemvm.zip around and starting daemons without some kind of init
script isn't ideal.

Also the UI still shows "0" system vms and won't display the state of
these services.

RE: New Committer: Animesh Chaturvedi

[Musayev, Ilya]

Congrats Animesh! 

> -Original Message-
> From: Alex Huang [mailto:alex.hu...@citrix.com]
> Sent: Thursday, March 28, 2013 3:57 PM
> To: dev@cloudstack.apache.org
> Subject: New Committer: Animesh Chaturvedi
> 
> The Podling Project Management Committee (PPMC) for Apache CloudStack
> has asked Animesh Chaturvedi to become a committer and we are pleased
> to announce that they have 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 me in congratulating Sateesh!
> 
> 
> 
> --Alex
> 
> on behalf of the CloudStack PPMC

Re: [MERGE] bvt branch to master

[Chiradeep Vittal]

+1

On 3/28/13 12:00 PM, "Chip Childers"  wrote:

>On Thu, Mar 28, 2013 at 07:36:58PM +0530, Prasanna Santhanam wrote:
>> I'd like to merge the bvt branch into master. The proposal [1] was to
>> stabilize master by allowing devs to quickly setup CloudStack using
>> simulated hypervisors and run some basic tests against it.
>> 
>> The bvt branch integrates the testing of cloudstack using marvin and
>> the simulator hypervisor. Alternately you may use devcloud as well
>> with the appropriate maven profiles enabled. One can try the
>> integrated tests today as described in [2]
>> 
>> While this is not to be touted as the magic pill for master stability
>> I think it is a good first step towards bringing together tests as
>> part of the build system. I've tested the steps on Linux and OSX.
>> 
>> [1] http://s.apache.org/5Lc
>> [2] https://cwiki.apache.org/confluence/x/PgvMAQ
>> 
>> Thanks,
>> 
>> -- 
>> Prasanna.,
>>
>
>+1 - this looks good to me!

Re: New Committer: Animesh Chaturvedi

[Chip Childers]

Congrats Animesh!

On Thu, Mar 28, 2013 at 12:57:24PM -0700, Alex Huang wrote:
> The Podling Project Management Committee (PPMC) for Apache CloudStack has 
> asked Animesh Chaturvedi to become a committer and we are pleased to announce 
> that they have 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 me in congratulating Sateesh!
> 
> 
> 
> --Alex
> 
> on behalf of the CloudStack PPMC
> 

RE: New Committer: Animesh Chaturvedi

[Alex Huang]

Send your congrats to Animesh. 

Sateesh should always be congratulated but he is already a committer.  :P

--Alex

> -Original Message-
> From: Alex Huang [mailto:alex.hu...@citrix.com]
> Sent: Thursday, March 28, 2013 12:57 PM
> To: dev@cloudstack.apache.org
> Subject: New Committer: Animesh Chaturvedi
> 
> The Podling Project Management Committee (PPMC) for Apache CloudStack
> has asked Animesh Chaturvedi to become a committer and we are pleased
> to announce that they have 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 me in congratulating Sateesh!
> 
> 
> 
> --Alex
> 
> on behalf of the CloudStack PPMC

Re: New Committer: Animesh Chaturvedi

[Noah Slater]

Grats!


On 28 March 2013 19:57, Alex Huang  wrote:

> The Podling Project Management Committee (PPMC) for Apache CloudStack has
> asked Animesh Chaturvedi to become a committer and we are pleased to
> announce that they have 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 me in congratulating Sateesh!
>
>
>
> --Alex
>
> on behalf of the CloudStack PPMC
>
>


-- 
NS

RE: Storage Subsystem 2.0 plugin docs

[Edison Su]

Comments embedded in below.

From: Vladimir Popovski [mailto:vladi...@zadarastorage.com]
Sent: Wednesday, March 27, 2013 12:22 PM
To: Mike Tutkowski; Edison Su
Cc: cloudstack-...@incubator.apache.org
Subject: RE: Storage Subsystem 2.0 plugin docs

Hi All,

I was away for couple of days, so sorry for the delay.

I'm completely with Mike & John (& others) on separating storage plugins from 
hypervisor-related functions. If every plugin will need to implement 
hypervisor-related code, it will be a big mess.

Our use-case is very similar to Mike's - we would like to be able to provision 
volumes with different QoS characteristics directly to VMs, rather than adding 
them into "shared" datastores. It might be achieved in two ways:

-  either to create separate data stores per each volume (storage LUN), 
and from there to create volumes & assign to instances.

-  or to assign devices recognized by iSCSI Initiators directly to 
instances (I'm not sure if it will be possible in VMware without datastores)

It looks like Mike started to work on the 1st approach. In this case, for every 
volume there will be a separate datastore. If this is the preferred direction 
for all storage plugins, then the hypervisor-specific logic of datastore 
creation and creating/assigning volumes from the datastore will be fairly 
common for all storage plug-ins. At the same time, the storage plugin should 
have the control over the datastore management. It will depend on the plugin, 
if dedicated or shared datastores should be created.

For the 2nd option (skipping the datastore layer) there might be plenty of 
common code as well.

So, my questions are:

-  do you think it is beneficial to support both options for the CS (or 
are we good with potentially huge number of datastores)?



[Edison]  CloudStack will not enforce any of these options, it's all up to 
provider's implementation. Either way is OK to me. Do you think, from 
architecture point of view, Is the current storage API enough for both options? 
If no, we can come up some new APIs.



-  are we all agree that HV-dependent storage code should be generic 
and appropriate interfaces to be exposed?



[Edison] If there are HV-dependent storage code there(I assume it should have 
some code can be shared between different storage provider at hypervisor side), 
we can generalize them and expose them.

As Mike said, the code dealing with storage pool at the hypervisor side, can be 
shared.

Regards,
-Vladimir



From: Mike Tutkowski 
[mailto:mike.tutkow...@solidfire.com]
Sent: Wednesday, March 27, 2013 10:21 AM
To: Edison Su
Cc: 
cloudstack-...@incubator.apache.org;
 Vladimir Popovski
Subject: Re: Storage Subsystem 2.0 plugin docs

Sounds good, Edison

Last night I finished up code that uses the VI Java API to create a VMware 
Datastore.

I want to test it a bit more before I have you look at it.

Today there is a Citrix CloudPlatform demo I'm participating in to handle part 
of the SolidFire section of the demo, so I might not have time to do my 
Datastore testing, but I should be done with it tomorrow.

Talk to you later!

On Wed, Mar 27, 2013 at 11:15 AM, Edison Su 
mailto:edison...@citrix.com>> wrote:
For vmware, current cloudstack doesn't create a vmware datastore through 
vmware's API, admin needs to create the datastore in Vcenter at first, then add 
it back into cloudstack. I am not familiar with how to create a VMware 
datastore through Vmware's API, but regarding to add a new host into a cluster, 
the current framework lets storage provider adding a listener which can listen 
on adding host event.

From: Mike Tutkowski 
[mailto:mike.tutkow...@solidfire.com]
Sent: Tuesday, March 26, 2013 6:45 PM

To: Edison Su
Cc: 
cloudstack-...@incubator.apache.org;
 Vladimir Popovski
Subject: Re: Storage Subsystem 2.0 plugin docs

Great - thanks, Edison!

I can take a look at that code.

I've almost gotten the VMware code written.

It's a little more involved than the XenServer code because you have to add 
static IQNs for discovery to each host in a VMware cluster (this is somehow 
handled behind the scenes, I suppose, with XenServer) before you can create a 
Datastore based on your iSCSI target.

One thing I was wondering, though, is when you add a new host to this VMware 
cluster.  It will need to "inherit" the list of IQNs to discover.  I image this 
is the case today.  Do you know anything about that?  I might just try it out 
and see if that works today.

On Tue, Mar 26, 2013 at 5:18 PM, Edison Su 
mailto:edison...@citrix.com>> wrote:
Thanks!
FYI, there are some code at both xen and kvm hypervisor resource code to deal 
with storage pool creation.
For example, in CitrixResourceBase-> getNfsSR or getIscsiSR to create a nfs SR 
or ISCSI SR. In LibvirtStorageAdaptor, which can create storage

RE: [DISCUSS]VMware Open Source APIs

[Musayev, Ilya]

The author, Steve Jin wrote this API, he also co-wrote and designed the 
original non open source VmWare APIs. (I even have one of his books).

This project is now supported by community and Steve.

I'd say the chance of it being very much similar to non opensource version - is 
very high, but I will let the more knowledge developers make that call.

Regards
ilya

> -Original Message-
> From: Ahmad Emneina [mailto:aemne...@gmail.com]
> Sent: Thursday, March 28, 2013 2:18 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [DISCUSS]VMware Open Source APIs
> 
> i agree, if there is feature parity between the sdk's we should use the
> opensource one.
> 
> 
> On Thu, Mar 28, 2013 at 11:07 AM, David Nalley  wrote:
> 
> > On Thu, Mar 28, 2013 at 2:00 PM, Musayev, Ilya 
> wrote:
> > > Stumbled upon Open Source Version of Java API for VSphere on
> > vijava.sourceforge.net
> > >
> > > Wanted to get the feel of developers if we can consider using these
> > > APIs
> > instead and make VMWare support as an Open Source build (vs nonoss as
> > of now).
> >
> >
> > Personally I think that since an open source option exists we have a
> > compelling reason to try and adopt it provided there are no adverse
> > effects. The ASF exists to build open source, freely-available,
> > software for the public good.
> >
> > --David
> >

Re: [DISCUSS]VMware Open Source APIs

[Chip Childers]

On Thu, Mar 28, 2013 at 08:14:17PM +, Musayev, Ilya wrote:
> The author, Steve Jin wrote this API, he also co-wrote and designed the 
> original non open source VmWare APIs. (I even have one of his books).
> 
> This project is now supported by community and Steve.
> 
> I'd say the chance of it being very much similar to non opensource version - 
> is very high, but I will let the more knowledge developers make that call.

Steve and I know each other, and I've suggested switching to it in the
past.  It's actually two things...  First, it exposes a *very similar*
raw set of API wrapper classes that look and feel like the VMware
proprietary SDK.  Second, it has a set of classes designed to simplify
the SDK interaction into a more sane object structure.

I'd be willing to bet that a conversion would be easy...  and I'm
willing to try if nobody else gets to it first...  After we get 4.1 out
the door, and if someone else does RM for 4.2.  ;-)

> 
> Regards
> ilya
> 
> > -Original Message-
> > From: Ahmad Emneina [mailto:aemne...@gmail.com]
> > Sent: Thursday, March 28, 2013 2:18 PM
> > To: dev@cloudstack.apache.org
> > Subject: Re: [DISCUSS]VMware Open Source APIs
> > 
> > i agree, if there is feature parity between the sdk's we should use the
> > opensource one.
> > 
> > 
> > On Thu, Mar 28, 2013 at 11:07 AM, David Nalley  wrote:
> > 
> > > On Thu, Mar 28, 2013 at 2:00 PM, Musayev, Ilya 
> > wrote:
> > > > Stumbled upon Open Source Version of Java API for VSphere on
> > > vijava.sourceforge.net
> > > >
> > > > Wanted to get the feel of developers if we can consider using these
> > > > APIs
> > > instead and make VMWare support as an Open Source build (vs nonoss as
> > > of now).
> > >
> > >
> > > Personally I think that since an open source option exists we have a
> > > compelling reason to try and adopt it provided there are no adverse
> > > effects. The ASF exists to build open source, freely-available,
> > > software for the public good.
> > >
> > > --David
> > >
> 
> 

RE: [ACS41][QA] Has anyone upgraded from 4.0 to 4.1

[Sangeetha Hariharan]

Create a doc bug for documenting these steps  - CLOUDSTACK-1837 - Additonal 
Steps ( Restart of all system Vms , copy vhd-utils) to be included in the 
upgrade procedure from 4.0 -> 4.1

-Thanks
Sangeetha
-Original Message-
From: Chip Childers [mailto:chip.child...@sungard.com] 
Sent: Thursday, March 28, 2013 12:18 PM
To: Sangeetha Hariharan
Cc: dev@cloudstack.apache.org
Subject: Re: [ACS41][QA] Has anyone upgraded from 4.0 to 4.1

On Thu, Mar 28, 2013 at 11:28:33AM -0700, Sangeetha Hariharan wrote:
> Then we can go with the option of reboot (start and stop) of all the system 
> Vms (SSVM,CPVM and routers) as part of Upgrade procedure ?

Sounds like it.  Care to add a note to the release notes wiki page to this 
effect?

> 
> -Thanks
> Sangeetha
> 
> -Original Message-
> From: Marcus Sorensen [mailto:shadow...@gmail.com]
> Sent: Thursday, March 28, 2013 11:21 AM
> To: Chip Childers
> Cc: dev@cloudstack.apache.org
> Subject: Re: [ACS41][QA] Has anyone upgraded from 4.0 to 4.1
> 
> I'm also not confident that option 1 really fixes anything. The user has to 
> reboot their system VMS eventually, and even if we fix this one thing to help 
> them get by until they do, what other lingering issues will arise?
> On Mar 28, 2013 11:38 AM, "Chip Childers"  wrote:
> 
> > On Thu, Mar 28, 2013 at 09:51:16AM -0700, Sangeetha Hariharan wrote:
> > > Can we get a confirmation on the approach we want to take?
> > >
> > > 1. We are going to fix the router for  the case - " if the router 
> > > has
> > upgraded its scripts, and then adjust how we call edithosts.sh" ?
> > > 2. Going to suggest a reboot (start and stop) of all the system 
> > > Vms
> > (SSVM,CPVM and routers) as part of Upgrade procedure?
> >
> > Option 2 is my preference.  Option 1 requires more testing, etc...
> >
> 

RE: [DISCUSS]VMware Open Source APIs

[Musayev, Ilya]

I guess a small world for you Chip :)

For those who would like to learn more or just curious, the README file has 
some interesting things we should consider.
--
WHAT IS VI JAVA API?
VI Java API is a set of Java libraries that aim to ease the usage of VI 
SDK Web Services interfaces. It's now open-sourced under BSD license.

It provides the following benefits to the Java developers:
* Enables OO programming with a well defined managed object model
* Reduces the need to use ManagedObjectReference and makes possible 
  compile time type checking
* Hides the complexity of the PropertyCollector
* Provides necessary utility classes to simplify VI SDK web interfaces
* High performance with 4+ times faster than AXIS engine

As a result, the application code using this API is much shorter (70% less) 
and much more readable than the equivalent using web service interfaces 
directly. The API itself is straight-forward and easy to learn and use. 

WHO CREATED THE API?
The VI Java API was initially created by Steve Jin from VMware Engineering. 
He is the author of VMware VI and vSphere SDK by Prentice Hall. There are 
contributions from the communities as well. See the web site for more details.  

WHAT IS INCLUDED?
Everything is packaged into one Jar file, including the Java source code, 
binary, sample code, license.
Version 2.0+ includes a high performance web service engine which is 15+ times
faster in loading and 4+ faster in de-serialization than AXIS with only 1/4
of the size, and many other features. Find out more at project home.

HOW TO GET STARTED?
To get started, check out the 5 minutes tutorial at: http://vijava.sf.net.

WHERE TO DOWNLOAD THE LATEST RELEASE? 
http://vijava.sf.net

WHERE CAN I GET HELP?
Project Forum: https://sourceforge.net/forum/forum.php?forum_id=826592
File a bug: https://sourceforge.net/tracker/?group_id=228007
Blog: http://www.doublecloud.org

COPYRIGHT & LICENSE:
BSD. See the License.txt file for details


> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Thursday, March 28, 2013 4:19 PM
> To: dev@cloudstack.apache.org
> Cc: aemne...@gmail.com
> Subject: Re: [DISCUSS]VMware Open Source APIs
> 
> On Thu, Mar 28, 2013 at 08:14:17PM +, Musayev, Ilya wrote:
> > The author, Steve Jin wrote this API, he also co-wrote and designed the
> original non open source VmWare APIs. (I even have one of his books).
> >
> > This project is now supported by community and Steve.
> >
> > I'd say the chance of it being very much similar to non opensource version -
> is very high, but I will let the more knowledge developers make that call.
> 
> Steve and I know each other, and I've suggested switching to it in the past.
> It's actually two things...  First, it exposes a *very similar* raw set of API
> wrapper classes that look and feel like the VMware proprietary SDK.  Second,
> it has a set of classes designed to simplify the SDK interaction into a more
> sane object structure.
> 
> I'd be willing to bet that a conversion would be easy...  and I'm willing to 
> try if
> nobody else gets to it first...  After we get 4.1 out the door, and if someone
> else does RM for 4.2.  ;-)
> 
> >
> > Regards
> > ilya
> >
> > > -Original Message-
> > > From: Ahmad Emneina [mailto:aemne...@gmail.com]
> > > Sent: Thursday, March 28, 2013 2:18 PM
> > > To: dev@cloudstack.apache.org
> > > Subject: Re: [DISCUSS]VMware Open Source APIs
> > >
> > > i agree, if there is feature parity between the sdk's we should use
> > > the opensource one.
> > >
> > >
> > > On Thu, Mar 28, 2013 at 11:07 AM, David Nalley  wrote:
> > >
> > > > On Thu, Mar 28, 2013 at 2:00 PM, Musayev, Ilya
> > > > 
> > > wrote:
> > > > > Stumbled upon Open Source Version of Java API for VSphere on
> > > > vijava.sourceforge.net
> > > > >
> > > > > Wanted to get the feel of developers if we can consider using
> > > > > these APIs
> > > > instead and make VMWare support as an Open Source build (vs nonoss
> > > > as of now).
> > > >
> > > >
> > > > Personally I think that since an open source option exists we have
> > > > a compelling reason to try and adopt it provided there are no
> > > > adverse effects. The ASF exists to build open source,
> > > > freely-available, software for the public good.
> > > >
> > > > --David
> > > >
> >
> >

Re: New Committer: Animesh Chaturvedi

[Joe Brockmeier]

On Thu, Mar 28, 2013, at 02:57 PM, Alex Huang wrote:
> Please join me in congratulating Animesh!

Congrats, keep up the good work!

Best,

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

Re: Review Request: Make SHA256Salt the default password encoding and authentication mechanism for cloudstack

[Venkata Siva Vijayendra Bhamidipati]

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

(Updated March 28, 2013, 8:26 p.m.)


Review request for cloudstack, Hugo Trippaers, Kelven Yang, and Min Chen.


Changes
---

+Min


Description
---

Changing default password encoding mechanism from MD5 to SHA256Salted.


This addresses bug CS-1734.


Diffs
-

  api/src/org/apache/cloudstack/api/command/admin/account/CreateAccountCmd.java 
89673ea 
  api/src/org/apache/cloudstack/api/command/admin/user/CreateUserCmd.java 
fb29e1a 
  api/src/org/apache/cloudstack/api/command/admin/user/UpdateUserCmd.java 
1f31662 
  client/tomcatconf/componentContext.xml.in 016df0a 
  client/tomcatconf/nonossComponentContext.xml.in 8f8dae5 
  developer/developer-prefill.sql 6300d35 
  
plugins/user-authenticators/ldap/src/com/cloud/server/auth/LDAPUserAuthenticator.java
 61eebe5 
  
plugins/user-authenticators/md5/src/com/cloud/server/auth/MD5UserAuthenticator.java
 026125e 
  
plugins/user-authenticators/plain-text/src/com/cloud/server/auth/PlainTextUserAuthenticator.java
 52e7cb3 
  
plugins/user-authenticators/sha256salted/src/com/cloud/server/auth/SHA256SaltedUserAuthenticator.java
 1b29f69 
  server/src/com/cloud/server/ManagementServerImpl.java b689f93 
  server/src/com/cloud/user/AccountManagerImpl.java b69f314 

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


Testing
---

Manual testing done for both oss and nonoss components. Both admin and users 
added later are encoded according to the scheme configured, and authenticated 
by the same scheme.

To change the order of the schemes, modify the following list properties in 
client/tomcatconf/nonossComponentContext.xml.in or 
client/tomcatconf/componentContext.xml.in as applicable, to the desired order:


 










 
 

 


Thanks,

Venkata Siva Vijayendra Bhamidipati

RE: [ACS4.2] master blockers

[Jessica Wang]

I just resolved all of my bugs:

>CLOUDSTACK-1730Jessica Wang
>CLOUDSTACK-1728Jessica Wang
>CLOUDSTACK-1616Jessica Wang
>CLOUDSTACK-1731Jessica Wang


-Original Message-
From: Abhinandan Prateek [mailto:abhinandan.prat...@citrix.com] 
Sent: Wednesday, March 27, 2013 10:05 PM
To: cloudstack dev
Cc: dev@cloudstack.apache.org
Subject: Re: [ACS4.2] master blockers 

Once again a reminder to close the following blockers and criticals in
master, if you are assigned but cannot figure out the issue please reach
out.

>CLOUDSTACK-1687Mice Xia
>CLOUDSTACK-1677Kelven Yang
>CLOUDSTACK-1774Rohit Yadav
>CLOUDSTACK-1721Prachi Damle
>CLOUDSTACK-1613Bharat Kumar
>CLOUDSTACK-1610frank zhang
>CLOUDSTACK-1591edison su
>CLOUDSTACK-1732Sheng Yang
>CLOUDSTACK-1739Bharat Kumar
>CLOUDSTACK-1392edison su
>CLOUDSTACK-1404edison su
>CLOUDSTACK-1753Brian Federle
>CLOUDSTACK-1730Jessica Wang
>CLOUDSTACK-1707Mice Xia
>CLOUDSTACK-1672Mice Xia
>CLOUDSTACK-1513edison su
>CLOUDSTACK-1728Jessica Wang
>CLOUDSTACK-1619frank zhang
>CLOUDSTACK-1618frank zhang
>CLOUDSTACK-1607Nitin Mehta
>CLOUDSTACK-1635edison su
>CLOUDSTACK-1614frank zhang
>CLOUDSTACK-1616Jessica Wang
>CLOUDSTACK-1639edison su
>CLOUDSTACK-1602edison su
>CLOUDSTACK-1737Anthony Xu
>CLOUDSTACK-1698Mice Xia
>CLOUDSTACK-1731Jessica Wang
>CLOUDSTACK-1440frank zhang
>CLOUDSTACK-1405edison su
>CLOUDSTACK-1646Bharat Kumar
>CLOUDSTACK-1534Bharat Kumar
>

-abhi
>