Re: System VMs not running

[Nitin Mehta]

Glad it helped. 
Donal my friend can you add this in your blog please :)

On 26/08/13 11:44 AM, "Amit Das"  wrote:

>Thanks Nitin. This helped.
>
>Setting the verbose mode & running the script manually showed me
>'Permission Denied' error on vhd-util file.
>
>I had to change the permission on vhd-util for things to work.
>
>Regards,
>Amit
>*CloudByte Inc.* 
>
>
>On Fri, Aug 23, 2013 at 3:56 PM, Nitin Mehta 
>wrote:
>
>> Donal - nice blog.
>> One more thing you might want to add is that for these shell scripts you
>> can uncomment the set -x option in the scripts and run them yourself.
>> SmLog sometimes might not narrow down the issue but has the info about
>>the
>> script path and the arguments. Once you uncomment the set -x and run it
>> yourself you can see the verbose output of the run.
>> Or better just uncomment the set -x option in the script and rerun the
>> entire operation. You should see a verbose output :)
>>
>> Thanks,
>> -Nitin
>>
>> On 23/08/13 2:56 PM, "Amit Das"  wrote:
>>
>> >Thanks Donal for the site. It explains the issue pretty well.
>> >
>> >I had already gone through the SMLog by observing some already raised
>>jira
>> >tickets. However, did not understand much then.
>> >
>> >Now i can see some *difference *between the logs on your blog vs. the
>>ones
>> >in my XenServer.
>> >
>> >[28437] 2013-08-23 07:37:28.703267   VMOPS enter
>> > copy_vhd_from_secondarystorage 
>> >[28437] 2013-08-23 07:37:28.703390  ['bash', '/opt/xensource/bin/*
>> >copy_vhd_from_secondarystorage.sh*', '10.10.171.155:*
>> >/export/secondary/template/tmpl/1/1/*',
>> >'b45c8c85-4e55-983c-cb16-4c2f2356951c',
>> >'cloud-ebed83d7-afde-4470-b867-312bad7c21c7']
>> >[28437] 2013-08-23 07:37:28.826465  SUCCESS
>> >[28437] 2013-08-23 07:37:28.826691   VMOPS exit
>> > copy_vhd_from_secondarystorage 
>> >[28463] 2013-08-23 07:37:29.787555   VMOPS enter
>> >kill_copy_process
>> >
>> >[28463] 2013-08-23 07:37:29.787680  ['bash',
>> >'/opt/xensource/bin/kill_copy_process.sh', '']
>> >[28463] 2013-08-23 07:37:29.800439  SUCCESS
>> >[28463] 2013-08-23 07:37:29.800565   VMOPS exit
>>kill_copy_process
>> >
>> >
>> >The difference that I find here is the .vhd template is never
>>mentioned in
>> >the copy_vhd_from_secondarystorage.sh
>> >Not sure if logic has changed.
>> >
>> >
>> >Regards,
>> >Amit
>> >*CloudByte Inc.* 
>> >
>> >
>> >On Fri, Aug 23, 2013 at 1:59 PM, Donal Lafferty
>> >wrote:
>> >
>> >> HI Amit,
>> >>
>> >> Still having problems?
>> >>
>> >> Probably time to have a look at the logs on XenServer.  There's a
>>guide
>> >>
>> >>
>> 
>>http://dlafferty.blogspot.co.uk/2013/08/using-cloudstacks-log-files-xense
>> >>rver.html
>> >>
>> >> DL
>> >>
>> >> > -Original Message-
>> >> > From: Amit Das [mailto:amit@cloudbyte.com]
>> >> > Sent: 23 August 2013 05:52
>> >> > To: dev@cloudstack.apache.org; aemne...@gmail.com
>> >> > Subject: Re: System VMs not running
>> >> >
>> >> > Yes. The step was missed.
>> >> >
>> >> > However, i tried out the steps on 'vhd_util' later & restarted nfs,
>> >> rpcbind &
>> >> > management services.
>> >> >
>> >> > Do i need to reset the DB as well ?
>> >> >
>> >> > Is there any work around for this ?
>> >> >
>> >> > Regards,
>> >> > Amit
>> >> > *CloudByte Inc.* 
>> >> >
>> >> >
>> >> > On Fri, Aug 23, 2013 at 9:56 AM, Ahmad Emneina 
>> >> > wrote:
>> >> >
>> >> > > this usually indicates that you missed the step where you prep
>> >> > > vhd-util on the hypervisor.
>> >> > >
>> >> > >
>> >> > > On Thu, Aug 22, 2013 at 9:18 PM, Amit Das
>>
>> >> > wrote:
>> >> > >
>> >> > > > The step worked fine after seeding system VM into secondary
>> >>storage
>> >> > > > location.
>> >> > > >
>> >> > > > However, i see the next error:
>> >> > > >
>> >> > > > WARN  [xen.resource.CitrixResourceBase] (DirectAgent-446:)
>>Catch
>> >> > > Exception
>> >> > > > com.cloud.utils.exception.CloudRuntimeException on
>> >> > > > host:21318624-cfd9-412d-aeb4-b1418424f287 for template: nfs://
>> >> > > > 10.10.171.155/export/secondary/template/tmpl/1/1/ due to
>> >> > > > com.cloud.utils.exception.CloudRuntimeException: *can not
>>create
>> >>vdi
>> >> > > > in
>> >> > > sr
>> >> > > > *
>> >> > > > b45c8c85-4e55-983c-cb16-4c2f2356951c
>> >> > > > com.cloud.utils.exception.CloudRuntimeException: can not create
>> >>vdi
>> >> > > > in sr b45c8c85-4e55-983c-cb16-4c2f2356951c
>> >> > > > at
>> >> > > >
>> >> > > >
>> >> > >
>> >> > 
>>com.cloud.hypervisor.xen.resource.CitrixResourceBase.copy_vhd_from_sec
>> >> > > ondarystorage(CitrixResourceBase.java:2707)
>> >> > > >
>> >> > > > ...
>> >> > > >
>> >> > > > 2013-08-23 09:46:12,815 DEBUG [agent.transport.Request]
>> >> > > (secstorage-1:null)
>> >> > > > Seq 12-90517578: Sending  { Cmd , MgmtId: 268749071320359, via:
>> >>12,
>> >> Ver:
>> >> > > > v1, Flags: 100111, [{"storage.*PrimaryStorageDownloadCommand*
>> 

Re: System VM stuck in Expunging State

[Daan Hoogland]

Mike,

make sure there is no ip associated with it

On Mon, Aug 26, 2013 at 6:05 AM, Mike Tutkowski
 wrote:
> I'm not seeing any recognition from CS that this VM exists at all...no
> print outs in the console at least.
>
>
> On Sat, Aug 24, 2013 at 7:08 PM, Marcus Sorensen wrote:
>
>> Yes, there are expunge global settings.
>> On Aug 24, 2013 6:35 PM, "Mike Tutkowski" 
>> wrote:
>>
>> > That would be great.
>> >
>> > Is there a global setting for that, Marcus?
>> >
>> > Thanks
>> >
>> >
>> > On Sat, Aug 24, 2013 at 5:26 PM, Marcus Sorensen > > >wrote:
>> >
>> > > It might be better to take a look and see why it fails to expunge. In
>> > > the past I've seen things like null pointers that have led to fixed
>> > > bugs. You can turn down the expunge intervals to get it to try every
>> > > 60 seconds or something, so you can watch what goes wrong.
>> > >
>> > > On Sat, Aug 24, 2013 at 3:53 PM, Mike Tutkowski
>> > >  wrote:
>> > > > Hi,
>> > > >
>> > > > I have a VM (SSVM) that's stuck in the Expunging State.
>> > > >
>> > > > It's not interfering with anything that I'm aware of as I have
>> another
>> > > SSVM
>> > > > up and running just fine, but I'd like to remove it from the
>> database.
>> > > >
>> > > > Does anyone know which table/tables I need to modify to make sure I
>> get
>> > > rid
>> > > > of all of the necessary data?
>> > > >
>> > > > Thanks!
>> > > >
>> > > > --
>> > > > *Mike Tutkowski*
>> > > > *Senior CloudStack Developer, SolidFire Inc.*
>> > > > e: mike.tutkow...@solidfire.com
>> > > > o: 303.746.7302
>> > > > Advancing the way the world uses the
>> > > > cloud
>> > > > *™*
>> > >
>> >
>> >
>> >
>> > --
>> > *Mike Tutkowski*
>> > *Senior CloudStack Developer, SolidFire Inc.*
>> > e: mike.tutkow...@solidfire.com
>> > o: 303.746.7302
>> > Advancing the way the world uses the
>> > cloud
>> > *™*
>> >
>>
>
>
>
> --
> *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: [VOTE] Apache Cloudstack 4.2.0

[Wido den Hollander]

-1 (binding)

I am aware of Ceph bugs which are still open for 4.2, like migrating 
from primary to primary storage.


I didn't get around fixing those yet since they were reported just last 
week.


The issue: https://issues.apache.org/jira/browse/CLOUDSTACK-4423

Wido

On 08/23/2013 08:55 PM, Animesh Chaturvedi wrote:



Hi All,

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

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

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

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

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

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

Vote will be open for 72 hours.

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

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

Re: [DISCUSS/PROPOSAL] Upgrading Driver Model

[Daan Hoogland]

I could give inline answers, but let's not waste to much more time.
One point I would like to make is that the live-cycle functions that
driver writers implement take care of how (in what state) instances
are stopped.

Your point on restricting dependencies is valid and a real concern.

And to not end this discussion I would like to refer my previous post;
I would love to help on this not withstanding any objection I have on
the way to go. It seems like fun to implement:)

regards,
Daan


On Mon, Aug 26, 2013 at 5:13 AM, John Burwell  wrote:
> Daan,
>
> Please see my responses in-line below.  The TL;DR is that I am extremely 
> skeptical of the complexity and flexibility of OSGi.  My experience with it 
> in practice has not been positive.  However, I want to focus on our 
> requirements for a driver mechanism, and then determine the best 
> implementation.
>
> Thanks,
> -John
>
> On Aug 21, 2013, at 4:14 AM, Daan Hoogland  wrote:
>
>> John,
>>
>> You do want 'In-process Installation and Upgrade', 'Introspection' and
>> 'Discoverability' says that you do want flexibility. You disqualify
>> Spring and OSGi on this quality however.
>
> On the surface, it would appear the OSGi fits into In-process Installation 
> and Upgrade.  However, OSGi assumes a consistency attribute that is too rigid 
> for CloudStack.   As I understand the specification, when a bundle is 
> upgraded, all instances in the container are upgraded simultaneously.  Based 
> on my reading of it, there is no way to customize this behavior.  I think we 
> need the upgrade process will be eventually consistent where by the 
> underlying driver instance for a resource will be upgraded when it is both a 
> consistent and upgradeable state. For example, we have 10,000 KVM hosts, and 
> the KVM driver is upgraded. 9,000 of them are idle, and can take the upgrade 
> immediately.  The other 1,000 are in some state of operation (creating and 
> destroying VMs, taking snapshots, etc).  For these 1,000, we want to the 
> upgrade to happen when they complete their current work.  Most importantly, 
> we don't want any work bound for these 10,000 resources during the upgrade to 
> be lost only delayed.
>
> When I say discoverability, I mean end-users finding drivers to install.  The 
> more I think about it, the more I explicitly do not want drivers to depend on 
> each other.  Drivers should be self-contained, stateless mechanisms that 
> interact with some piece of infrastructure.  I think the path to madness lies 
> in having a messy web of cross-vendor driver dependencies.
>
>>
>> If we can restrict the use of bundles to those that adhere to some
>> interfaces we prescribe I don't think either complexity nor dependency
>> are an issue.
>
> The only restriction I see is the ability of a bundle to control what is 
> publicly exported.  However, I see no way to restrict how bundles depend on 
> each other -- opening the door to cross vendor driver dependencies.
>
>>
>> Most every bit of complexity of writing a bundle can be hidden from
>> the bundle-developer nowadays. If we can not hide enough it is not an
>> option indeed. The main focus of OSGI is life cycle management which
>> is exactly what we need. the use that eclipse makes of it is a good
>> example not to follow but doesn't disqualify the entire thing.
>
> Personally, I am dubious that a build process can mask complexity.  More 
> importantly, I don't like creating designs that require tooling and code 
> generation with a veneer of simplicity but actually create a spooky action at 
> a distance.  I prefer creating truly simple systems that can be easily 
> comprehended.
>
>>
>> The dependency hell is not different from what we have as regular
>> monolithical development group. We control what we package and how. A
>> valid point is that some libraries might have issues that prevent them
>> from being bundled and that needs investigation. So we need to package
>> those libraries as bundles ourselves so 3rd parties don't need to. We
>> package them now anyway.
>
> In my experience, the dependency management problem is magnified by the added 
> hurdle that every dependency be an OSGi bundle.  Many projects do not 
> natively ship OSGi bundles, leaving third-parties or the project itself to 
> repackage them.  Often OSGi bundled versions are behind the most current 
> project releases.
>
>>
>> The erector set fear you have is just as valid with as without osgi or
>> any existing framework.
>
> Agreed.  I prefer inaction on this topic than create said erector set.
>
>>
>> I don't insist on OSGi and I do agree with your initial set of
>> requirements. When I read it I think, "let's use OSGi". And I don't
>> see anything but fear of the beast in your arguments against it. Maybe
>> your fear is just in my perception or maybe it is very valid. I'm not
>> perceptible to it after your reply, yet.
>
> To my mind, OSGi is a wonderful idea.  We need it, or something like it, 
> standard in the JVM.  However,

Review Request 13804: CLOUDSTACK-4495: systemVM template URL is pointing to old template location in upgrade file.

[Sanjay Tripathi]

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

Review request for cloudstack, Abhinandan Prateek and Devdeep Singh.


Bugs: CLOUDSTACK-4495


Repository: cloudstack-git


Description
---

SystemVM template URL for XenServer hypervisor is pointing to old template 
location in the Upgrade410to420.java  file.

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


Diffs
-

  engine/schema/src/com/cloud/upgrade/dao/Upgrade410to420.java c3276ef 

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


Testing
---

Tests:
1. Setup CloudStack environment,
2. Check the systemVM template URL in vm_template table (it should point to the 
new location).


Thanks,

Sanjay Tripathi

Log files on add ISOs/Templates

[Amit Das]

Hi folks,

Are there any specific success/error log statements on adding ISOs or
Templates.

Can we find them in management server's catalina.out ?

Do we have any manual workaround to add ISOs or Templates ?

Regards,
Amit
*CloudByte Inc.* 

Re: System VM stuck in Expunging State

[Mike Tutkowski]

Just looked...no IPs show up in the details for the "expunging" SSVM.

How do you recommend I get rid of it?

Thanks!


On Mon, Aug 26, 2013 at 1:17 AM, Daan Hoogland wrote:

> Mike,
>
> make sure there is no ip associated with it
>
> On Mon, Aug 26, 2013 at 6:05 AM, Mike Tutkowski
>  wrote:
> > I'm not seeing any recognition from CS that this VM exists at all...no
> > print outs in the console at least.
> >
> >
> > On Sat, Aug 24, 2013 at 7:08 PM, Marcus Sorensen  >wrote:
> >
> >> Yes, there are expunge global settings.
> >> On Aug 24, 2013 6:35 PM, "Mike Tutkowski"  >
> >> wrote:
> >>
> >> > That would be great.
> >> >
> >> > Is there a global setting for that, Marcus?
> >> >
> >> > Thanks
> >> >
> >> >
> >> > On Sat, Aug 24, 2013 at 5:26 PM, Marcus Sorensen  >> > >wrote:
> >> >
> >> > > It might be better to take a look and see why it fails to expunge.
> In
> >> > > the past I've seen things like null pointers that have led to fixed
> >> > > bugs. You can turn down the expunge intervals to get it to try every
> >> > > 60 seconds or something, so you can watch what goes wrong.
> >> > >
> >> > > On Sat, Aug 24, 2013 at 3:53 PM, Mike Tutkowski
> >> > >  wrote:
> >> > > > Hi,
> >> > > >
> >> > > > I have a VM (SSVM) that's stuck in the Expunging State.
> >> > > >
> >> > > > It's not interfering with anything that I'm aware of as I have
> >> another
> >> > > SSVM
> >> > > > up and running just fine, but I'd like to remove it from the
> >> database.
> >> > > >
> >> > > > Does anyone know which table/tables I need to modify to make sure
> I
> >> get
> >> > > rid
> >> > > > of all of the necessary data?
> >> > > >
> >> > > > Thanks!
> >> > > >
> >> > > > --
> >> > > > *Mike Tutkowski*
> >> > > > *Senior CloudStack Developer, SolidFire Inc.*
> >> > > > e: mike.tutkow...@solidfire.com
> >> > > > o: 303.746.7302
> >> > > > Advancing the way the world uses the
> >> > > > cloud
> >> > > > *™*
> >> > >
> >> >
> >> >
> >> >
> >> > --
> >> > *Mike Tutkowski*
> >> > *Senior CloudStack Developer, SolidFire Inc.*
> >> > e: mike.tutkow...@solidfire.com
> >> > o: 303.746.7302
> >> > Advancing the way the world uses the
> >> > cloud
> >> > *™*
> >> >
> >>
> >
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkow...@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the
> > cloud
> > *™*
>



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

Review Request 13805: CLOUDSTACK-3806: OS Preference can not be set

[Anshul Gangwar]

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

Review request for cloudstack, Devdeep Singh and Sateesh Chodapuneedi.


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


Repository: cloudstack-git


Description
---

It was setting OS preference correctly, The problem was in host_view. It was 
using the wrong id for join parameter. It was using host_details.id instead of 
host_details.host_id. Hence the parameter was not getting updated corretly in 
view.


Diffs
-

  setup/db/db/schema-307to410.sql 70cddfd 
  setup/db/db/schema-40to410.sql f1482f8 
  setup/db/db/schema-410to420.sql 4a21898 

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


Testing
---

Verified manually on my setup


Thanks,

Anshul Gangwar

Re: System VM stuck in Expunging State

[Daan Hoogland]

I was recollecting an occassion where this was what kept vms from
being expunged. If there are no ips, probably something else is
keeping them tied to existence. My guess is some data relation, but as
I said 'my guess'. Good luck:|

On Mon, Aug 26, 2013 at 10:11 AM, Mike Tutkowski
 wrote:
> Just looked...no IPs show up in the details for the "expunging" SSVM.
>
> How do you recommend I get rid of it?
>
> Thanks!
>
>
> On Mon, Aug 26, 2013 at 1:17 AM, Daan Hoogland wrote:
>
>> Mike,
>>
>> make sure there is no ip associated with it
>>
>> On Mon, Aug 26, 2013 at 6:05 AM, Mike Tutkowski
>>  wrote:
>> > I'm not seeing any recognition from CS that this VM exists at all...no
>> > print outs in the console at least.
>> >
>> >
>> > On Sat, Aug 24, 2013 at 7:08 PM, Marcus Sorensen > >wrote:
>> >
>> >> Yes, there are expunge global settings.
>> >> On Aug 24, 2013 6:35 PM, "Mike Tutkowski" > >
>> >> wrote:
>> >>
>> >> > That would be great.
>> >> >
>> >> > Is there a global setting for that, Marcus?
>> >> >
>> >> > Thanks
>> >> >
>> >> >
>> >> > On Sat, Aug 24, 2013 at 5:26 PM, Marcus Sorensen > >> > >wrote:
>> >> >
>> >> > > It might be better to take a look and see why it fails to expunge.
>> In
>> >> > > the past I've seen things like null pointers that have led to fixed
>> >> > > bugs. You can turn down the expunge intervals to get it to try every
>> >> > > 60 seconds or something, so you can watch what goes wrong.
>> >> > >
>> >> > > On Sat, Aug 24, 2013 at 3:53 PM, Mike Tutkowski
>> >> > >  wrote:
>> >> > > > Hi,
>> >> > > >
>> >> > > > I have a VM (SSVM) that's stuck in the Expunging State.
>> >> > > >
>> >> > > > It's not interfering with anything that I'm aware of as I have
>> >> another
>> >> > > SSVM
>> >> > > > up and running just fine, but I'd like to remove it from the
>> >> database.
>> >> > > >
>> >> > > > Does anyone know which table/tables I need to modify to make sure
>> I
>> >> get
>> >> > > rid
>> >> > > > of all of the necessary data?
>> >> > > >
>> >> > > > Thanks!
>> >> > > >
>> >> > > > --
>> >> > > > *Mike Tutkowski*
>> >> > > > *Senior CloudStack Developer, SolidFire Inc.*
>> >> > > > e: mike.tutkow...@solidfire.com
>> >> > > > o: 303.746.7302
>> >> > > > Advancing the way the world uses the
>> >> > > > cloud
>> >> > > > *™*
>> >> > >
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > *Mike Tutkowski*
>> >> > *Senior CloudStack Developer, SolidFire Inc.*
>> >> > e: mike.tutkow...@solidfire.com
>> >> > o: 303.746.7302
>> >> > Advancing the way the world uses the
>> >> > cloud
>> >> > *™*
>> >> >
>> >>
>> >
>> >
>> >
>> > --
>> > *Mike Tutkowski*
>> > *Senior CloudStack Developer, SolidFire Inc.*
>> > e: mike.tutkow...@solidfire.com
>> > o: 303.746.7302
>> > Advancing the way the world uses the
>> > cloud
>> > *™*
>>
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud
> *™*

Re: System VM stuck in Expunging State

[Mike Tutkowski]

It's no big deal for me to leave it as it is. :) It's just a CS setup
people are using at VMworld this week to demo the SolidFire plug-in.

Thanks, though!


On Mon, Aug 26, 2013 at 2:18 AM, Daan Hoogland wrote:

> I was recollecting an occassion where this was what kept vms from
> being expunged. If there are no ips, probably something else is
> keeping them tied to existence. My guess is some data relation, but as
> I said 'my guess'. Good luck:|
>
> On Mon, Aug 26, 2013 at 10:11 AM, Mike Tutkowski
>  wrote:
> > Just looked...no IPs show up in the details for the "expunging" SSVM.
> >
> > How do you recommend I get rid of it?
> >
> > Thanks!
> >
> >
> > On Mon, Aug 26, 2013 at 1:17 AM, Daan Hoogland  >wrote:
> >
> >> Mike,
> >>
> >> make sure there is no ip associated with it
> >>
> >> On Mon, Aug 26, 2013 at 6:05 AM, Mike Tutkowski
> >>  wrote:
> >> > I'm not seeing any recognition from CS that this VM exists at all...no
> >> > print outs in the console at least.
> >> >
> >> >
> >> > On Sat, Aug 24, 2013 at 7:08 PM, Marcus Sorensen  >> >wrote:
> >> >
> >> >> Yes, there are expunge global settings.
> >> >> On Aug 24, 2013 6:35 PM, "Mike Tutkowski" <
> mike.tutkow...@solidfire.com
> >> >
> >> >> wrote:
> >> >>
> >> >> > That would be great.
> >> >> >
> >> >> > Is there a global setting for that, Marcus?
> >> >> >
> >> >> > Thanks
> >> >> >
> >> >> >
> >> >> > On Sat, Aug 24, 2013 at 5:26 PM, Marcus Sorensen <
> shadow...@gmail.com
> >> >> > >wrote:
> >> >> >
> >> >> > > It might be better to take a look and see why it fails to
> expunge.
> >> In
> >> >> > > the past I've seen things like null pointers that have led to
> fixed
> >> >> > > bugs. You can turn down the expunge intervals to get it to try
> every
> >> >> > > 60 seconds or something, so you can watch what goes wrong.
> >> >> > >
> >> >> > > On Sat, Aug 24, 2013 at 3:53 PM, Mike Tutkowski
> >> >> > >  wrote:
> >> >> > > > Hi,
> >> >> > > >
> >> >> > > > I have a VM (SSVM) that's stuck in the Expunging State.
> >> >> > > >
> >> >> > > > It's not interfering with anything that I'm aware of as I have
> >> >> another
> >> >> > > SSVM
> >> >> > > > up and running just fine, but I'd like to remove it from the
> >> >> database.
> >> >> > > >
> >> >> > > > Does anyone know which table/tables I need to modify to make
> sure
> >> I
> >> >> get
> >> >> > > rid
> >> >> > > > of all of the necessary data?
> >> >> > > >
> >> >> > > > Thanks!
> >> >> > > >
> >> >> > > > --
> >> >> > > > *Mike Tutkowski*
> >> >> > > > *Senior CloudStack Developer, SolidFire Inc.*
> >> >> > > > e: mike.tutkow...@solidfire.com
> >> >> > > > o: 303.746.7302
> >> >> > > > Advancing the way the world uses the
> >> >> > > > cloud
> >> >> > > > *™*
> >> >> > >
> >> >> >
> >> >> >
> >> >> >
> >> >> > --
> >> >> > *Mike Tutkowski*
> >> >> > *Senior CloudStack Developer, SolidFire Inc.*
> >> >> > e: mike.tutkow...@solidfire.com
> >> >> > o: 303.746.7302
> >> >> > Advancing the way the world uses the
> >> >> > cloud
> >> >> > *™*
> >> >> >
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> > *Mike Tutkowski*
> >> > *Senior CloudStack Developer, SolidFire Inc.*
> >> > e: mike.tutkow...@solidfire.com
> >> > o: 303.746.7302
> >> > Advancing the way the world uses the
> >> > cloud
> >> > *™*
> >>
> >
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkow...@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the
> > cloud
> > *™*
>



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

Writing to volume attached to VM

[Gaurav Aradhye]

Hi all,

Can you guide me on how to write on the external volume (DataDisk) attached
to a VM?

I am trying to mount the partition, but the list of partitions before and
after attaching the volume to vm, remains the same, so I am unable to
detect which partition has been added.

Has anybody done this before through test case?

Regards,
Gaurav

Re: Writing to volume attached to VM

[Wei ZHOU]

What is OS of your vm?
Does it support acpi hotplug?


2013/8/26 Gaurav Aradhye 

> Hi all,
>
> Can you guide me on how to write on the external volume (DataDisk) attached
> to a VM?
>
> I am trying to mount the partition, but the list of partitions before and
> after attaching the volume to vm, remains the same, so I am unable to
> detect which partition has been added.
>
> Has anybody done this before through test case?
>
> Regards,
> Gaurav
>

Re: Writing to volume attached to VM

[Prasanna Santhanam]

On Mon, Aug 26, 2013 at 02:08:19PM +0530, Gaurav Aradhye wrote:
> Hi all,
> 
> Can you guide me on how to write on the external volume (DataDisk) attached
> to a VM?
> 
> I am trying to mount the partition, but the list of partitions before and
> after attaching the volume to vm, remains the same, so I am unable to
> detect which partition has been added.

How do you 
a) identify the device on which the disk is available to be mounted
b) mount the formatted device to your VM
c) list the partitions/disks

Some commands on how you do this will help.

> 
> Has anybody done this before through test case?
> 
> Regards,
> Gaurav

-- 
Prasanna.,


Powered by BigRock.com

Re: Review Request 13736: Resolved Cloudstack: 4452 - fixed test cases in test_snapshots.py

[Prasanna Santhanam]

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

Ship it!


Applied to master and 4.2-forward but with additional changes that I had 
requested in the review. 

- Prasanna Santhanam


On Aug. 23, 2013, 11:52 a.m., Gaurav Aradhye wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/13736/
> ---
> 
> (Updated Aug. 23, 2013, 11:52 a.m.)
> 
> 
> Review request for cloudstack and Prasanna Santhanam.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Resolved cloudstack: 4452
> Changes in function is_snapshot_on_nfs to check if the snapshot is present in 
> the secondary storage.
> 
> Earlier it was trying to match the name of the snapshot present on the 
> storage with the UUID of the snapshot which is incorrect way.
> There's apparently no relation between the snapshot name on the storage and 
> the UUID of the snapshot.
> 
> Changed the function to check if the snapshotPath is valid and is indeed a 
> "File".
> 
> Also removed the VM creation (virtual_machine_without_disk) step in 
> setupClass of class TestSnapshots. It is not used anywhere and was eating up 
> the running time of test case and resources.
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_snapshot_gc.py 3cd4194 
>   test/integration/component/test_snapshot_limits.py 1bc2798 
>   test/integration/component/test_snapshots.py cc2e604 
>   tools/marvin/marvin/integration/lib/utils.py 7863bfb 
> 
> Diff: https://reviews.apache.org/r/13736/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Gaurav Aradhye
> 
>

Re: Review Request 13771: CLOUDSTACK-4346 replace URI getHost() and create(String) calls

[Dave Cahill]

Get well soon!


On Mon, Aug 26, 2013 at 3:48 PM, Daan Hoogland wrote:

> You are right, I incorporated Alex' auto format for eclipse. Sorry for
> that. Being sick at home today, I will try to submit an update without it
> tomorrow.
>
> regards,
>
>
>
> On Mon, Aug 26, 2013 at 6:04 AM, Dave Cahill  wrote:
>
>> Hi Daan,
>>
>> I started to take a look - the diff is ~10k lines long, most of which
>> appears to be whitespace changes.
>>
>> Are the whitespace changes important? Without them, the patch might be a
>> lot easier to review.
>>
>> Thanks,
>> Dave.
>>
>>
>>
>>
>> On Sun, Aug 25, 2013 at 7:37 PM, Daan Hoogland 
>> wrote:
>>
>>> Sheng, Dave, Chiradeep and Hugo,
>>>
>>> Can you please review this? In my experience the time that this patch
>>> will expire is rather short, I have been resolving conflicts on this a lot.
>>> If now, given the 4.2 release is inconvenient, I would like to set a window
>>> for submitting this in which I will rebase it a couple of times so as to
>>> make sure it works in the end.
>>>
>>> thanks,
>>> Daan
>>>
>>>
>>> On Fri, Aug 23, 2013 at 10:48 AM, daan Hoogland >> > wrote:
>>>
This is an automatically generated e-mail. To reply, visit:
 https://reviews.apache.org/r/13771/
   Review request for cloudstack, Chiradeep Vittal, Dave Cahill, Hugo
 Trippaers, and Sheng Yang.
 By daan Hoogland.
  *Bugs: * CLOUDSTACK-4346
  *Repository: * cloudstack-git
 Description

 After global search and replace all calls to retrieve ids for networks 
 from URIs using getHost() should be gone. Creating URI should now all use 
 appropriate calls as well so maitaining the way uris are built can now be 
 done centrally.

   Testing

 tested with old style uris in regular networks and vpc based networks as 
 well as in nicira based networks
 test build in nonoss but not all code has probably been touched yet. or at 
 least I am unsure of that.

   Diffs

- 
 plugins/hypervisors/baremetal/src/com/cloud/baremetal/networkservice/BaremetaNetworkGuru.java
(07ee12d)
- 
 plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/BridgeVifDriver.java
(195cf40)
- 
 plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtComputingResource.java
(a156ae6)
- 
 plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/OvsVifDriver.java
(7038d7e)
- 
 plugins/hypervisors/ovm/src/com/cloud/ovm/hypervisor/OvmResourceBase.java
(59ba001)
- 
 plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/resource/VmwareResource.java
(5ab2216)
- 
 plugins/hypervisors/xen/src/com/cloud/hypervisor/xen/resource/CitrixResourceBase.java
(ecdec1e)
- 
 plugins/network-elements/bigswitch-vns/src/com/cloud/network/element/BigSwitchVnsElement.java
(54623e9)
- 
 plugins/network-elements/cisco-vnmc/src/com/cloud/network/element/CiscoVnmcElement.java
(3ae6a08)
- 
 plugins/network-elements/f5/src/com/cloud/network/resource/F5BigIpResource.java
(1733712)
- 
 plugins/network-elements/juniper-srx/src/com/cloud/network/resource/JuniperSrxResource.java
(3d3d797)
- 
 plugins/network-elements/nicira-nvp/src/com/cloud/network/element/NiciraNvpElement.java
(c7d0884)
- 
 plugins/network-elements/nicira-nvp/src/com/cloud/network/guru/NiciraNvpGuestNetworkGuru.java
(ff238ed)
- 
 plugins/network-elements/ovs/src/com/cloud/network/ovs/OvsTunnelManagerImpl.java
(36a807f)
- server/src/com/cloud/api/ApiResponseHelper.java (c771431)
- server/src/com/cloud/configuration/ConfigurationManagerImpl.java
(57dc0b3)
- server/src/com/cloud/network/ExternalDeviceUsageManagerImpl.java
(e91dcfa)
- server/src/com/cloud/network/ExternalFirewallDeviceManagerImpl.java
(a934024)
- 
 server/src/com/cloud/network/ExternalLoadBalancerDeviceManagerImpl.java
(c14d5c7)
- server/src/com/cloud/network/NetworkManagerImpl.java (00103e3)
- server/src/com/cloud/network/guru/DirectPodBasedNetworkGuru.java
(5b87d54)
- server/src/com/cloud/network/guru/ExternalGuestNetworkGuru.java
(00598dd)
- server/src/com/cloud/network/guru/GuestNetworkGuru.java (b0da42f)
- server/src/com/cloud/network/guru/PrivateNetworkGuru.java
(6521cf4)
- server/src/com/cloud/network/guru/PublicNetworkGuru.java (d109468)
- 
 server/src/com/cloud/network/router/VpcVirtualNetworkApplianceManagerImpl.java
(ee0d058)
- utils/src/com/cloud/utils/net/NetUtils.java (05b485b)

 View Diff 

>>>
>>>
>>
>

Re: Writing to volume attached to VM

[Gaurav Aradhye]

Hi,

Answering your questions in order c,a,b.

c) I am listing the partitions on the vm using fdisk -l command.
This is giving me following output.

 ['', 'Disk /dev/vda: 8589 MB, 8589934592 bytes', '255 head

s, 63 sectors/track, 1044 cylinders', 'Units = cylinders of 16065 * 512 =
8225280 bytes', '', ' Device Boot Start End Blocks Id System',

'/dev/vda1 * 1 13 104391 83 Linux', '/dev/vda2 14 1044 8281507+ 8e Linux
LVM', '', 'Disk /dev/vdb: 1073 M

B, 1073741824 bytes', '16 heads, 63 sectors/track, 2080 cylinders', 'Units
= cylinders of 1008 * 512 = 516096 bytes', '']


As you can see two disks /dev/vda and /dev/vdb are listed.

This output remains the same after attaching a volume to the vm.


a) As I am not able to identify any new partition, not able to detect the
exact partition that needs to be mounted.

This is where I need help. How to identify the volume partitions and mount
them?


b) Once the device is identified, it can be mounted using mount command.
Right now it is mounting the root disk partitions.


Firing all these commands to using remoteSSHClient of vm.



Regards,
Gaurav


On Mon, Aug 26, 2013 at 2:16 PM, Prasanna Santhanam  wrote:

> On Mon, Aug 26, 2013 at 02:08:19PM +0530, Gaurav Aradhye wrote:
> > Hi all,
> >
> > Can you guide me on how to write on the external volume (DataDisk)
> attached
> > to a VM?
> >
> > I am trying to mount the partition, but the list of partitions before and
> > after attaching the volume to vm, remains the same, so I am unable to
> > detect which partition has been added.
>
> How do you
> a) identify the device on which the disk is available to be mounted
> b) mount the formatted device to your VM
> c) list the partitions/disks
>
> Some commands on how you do this will help.
>
> >
> > Has anybody done this before through test case?
> >
> > Regards,
> > Gaurav
>
> --
> Prasanna.,
>
> 
> Powered by BigRock.com
>
>

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

[Gaurav Aradhye]

> On Aug. 19, 2013, 11:49 a.m., Sanjay Tripathi wrote:
> > test/integration/component/cpu_limits/test_cpu_limits.py, line 526
> > 
> >
> > As the test title says "reboot_instance" , please use reboot instance 
> > API instead of stopping and then starting an instance.

Hi Sanjay,

According to test scenarios, counts should be checked after stopping, and once 
again after starting the instance.
To avoid the confusion, I will change the test name.


> On Aug. 19, 2013, 11:49 a.m., Sanjay Tripathi wrote:
> > test/integration/component/cpu_limits/test_domain_limits.py, line 255
> > 
> >
> > as the test title says "reboot_instance", please use reboot instance 
> > API.


- Gaurav


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


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

RE: Writing to volume attached to VM

[Suresh Sadhu]

/dev/vdb is your data disk

CS won't format automatically ,you have to manually create LV and format 
operations

 do the following steps:

Fdisk /dev/vdb

Option m will provide the menu in that menu select  option to create new 
pattiton
 
2.  Select n option  to create new partition  and choose/accept  the default 
value during partition creation

3. Once partition got created ,select the w option to write I node table info
4.now you can see /vbb ,vdb1  when you enter fdisk -l
5 format the the  logical partition  created in step 4  like mkfs.ext3 /dev/vdb
6. mount the disk mount /dev/vdb1 /mnt  and perform IO on mounted path(/mnt)

Hope this helps:


Regards
Sadhu


-Original Message-
From: Gaurav Aradhye [mailto:gaurav.arad...@clogeny.com] 
Sent: 26 August 2013 14:53
To: dev@cloudstack.apache.org
Subject: Re: Writing to volume attached to VM

Hi,

Answering your questions in order c,a,b.

c) I am listing the partitions on the vm using fdisk -l command.
This is giving me following output.

 ['', 'Disk /dev/vda: 8589 MB, 8589934592 bytes', '255 head

s, 63 sectors/track, 1044 cylinders', 'Units = cylinders of 16065 * 512 =
8225280 bytes', '', ' Device Boot Start End Blocks Id System',

'/dev/vda1 * 1 13 104391 83 Linux', '/dev/vda2 14 1044 8281507+ 8e Linux LVM', 
'', 'Disk /dev/vdb: 1073 M

B, 1073741824 bytes', '16 heads, 63 sectors/track, 2080 cylinders', 'Units = 
cylinders of 1008 * 512 = 516096 bytes', '']


As you can see two disks /dev/vda and /dev/vdb are listed.

This output remains the same after attaching a volume to the vm.


a) As I am not able to identify any new partition, not able to detect the exact 
partition that needs to be mounted.

This is where I need help. How to identify the volume partitions and mount them?


b) Once the device is identified, it can be mounted using mount command.
Right now it is mounting the root disk partitions.


Firing all these commands to using remoteSSHClient of vm.



Regards,
Gaurav


On Mon, Aug 26, 2013 at 2:16 PM, Prasanna Santhanam  wrote:

> On Mon, Aug 26, 2013 at 02:08:19PM +0530, Gaurav Aradhye wrote:
> > Hi all,
> >
> > Can you guide me on how to write on the external volume (DataDisk)
> attached
> > to a VM?
> >
> > I am trying to mount the partition, but the list of partitions 
> > before and after attaching the volume to vm, remains the same, so I 
> > am unable to detect which partition has been added.
>
> How do you
> a) identify the device on which the disk is available to be mounted
> b) mount the formatted device to your VM
> c) list the partitions/disks
>
> Some commands on how you do this will help.
>
> >
> > Has anybody done this before through test case?
> >
> > Regards,
> > Gaurav
>
> --
> Prasanna.,
>
> 
> Powered by BigRock.com
>
>

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

[Sanjay Tripathi]

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



test/integration/component/cpu_limits/test_project_limits.py


use listResourceLimits API to get the resource limits of respective 
account/domain.



test/integration/component/cpu_limits/test_project_limits.py


use listResourceLimits API to get the resource limit of respective 
account/domain.



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


For now, we don't have support for resource type 12 and 13. So you can 
remove them from the comment.

Also, please remove the trailing white spaces.



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


remove resource type 12 and 13 as they are not yet implemented.


- Sanjay Tripathi


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

Re: Review Request 11626: Automation: Memory limits tests from Resource Limits Tests

[Sanjay Tripathi]

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



test/integration/component/memory_limits/test_domain_limits.py


This is not required as changeServiceOffering should update the resource 
count.



test/integration/component/memory_limits/test_domain_limits.py


same reason, please remove this update call.



test/integration/component/memory_limits/test_domain_limits.py


Please change the "update resource count" to "list resource count" as we 
are list the resource count in the test.



test/integration/component/memory_limits/test_domain_limits.py


same reason, please change the description accordingly.



test/integration/component/memory_limits/test_domain_limits.py


please change the description accordingly.



test/integration/component/memory_limits/test_domain_limits.py


api_client should point to cdamin_2.



test/integration/component/memory_limits/test_memory_limits.py


please change the test name as per the test description and implementation.

Also change the description of the test accordingly.



test/integration/component/memory_limits/test_memory_limits.py


This update call is not required.



test/integration/component/memory_limits/test_memory_limits.py


This update call is not required.



test/integration/component/memory_limits/test_memory_limits.py


change the description of test according to the test implementation.



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


remove the resource type 12 and 13 as they are not yet implemented.



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


please remove the resource type 12 and 13.


- Sanjay Tripathi


On Aug. 9, 2013, 7:51 a.m., Gaurav Aradhye wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/11626/
> ---
> 
> (Updated Aug. 9, 2013, 7:51 a.m.)
> 
> 
> Review request for cloudstack, sailaja mada, Sanjay Tripathi, and Prasanna 
> Santhanam.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Adding resource limit tests related to Memory. Changes suggested in CPU 
> resource limit tests which are applicable here are incorporated too.
> 
> Updated test plan is available here: 
> https://cwiki.apache.org/confluence/download/attachments/30757590/LimitResourcesTestPlanUpdate5.xlsx?version=1&modificationDate=1366952352000
> 
> 
> Diffs
> -
> 
>   test/integration/component/memory_limits/test_domain_limits.py PRE-CREATION 
>   test/integration/component/memory_limits/test_maximum_limits.py 
> PRE-CREATION 
>   test/integration/component/memory_limits/test_memory_limits.py PRE-CREATION 
>   test/integration/component/memory_limits/test_project_limits.py 
> PRE-CREATION 
>   tools/marvin/marvin/integration/lib/base.py 695edf7 
>   tools/marvin/marvin/integration/lib/common.py 4f5acef 
> 
> Diff: https://reviews.apache.org/r/11626/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Gaurav Aradhye
> 
>

Re: Review Request 11626: Automation: Memory limits tests from Resource Limits Tests

[Sanjay Tripathi]

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


Can you please remove the trailing white spaces from the patch so that it 
applies cleanly.

- Sanjay Tripathi


On Aug. 9, 2013, 7:51 a.m., Gaurav Aradhye wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/11626/
> ---
> 
> (Updated Aug. 9, 2013, 7:51 a.m.)
> 
> 
> Review request for cloudstack, sailaja mada, Sanjay Tripathi, and Prasanna 
> Santhanam.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Adding resource limit tests related to Memory. Changes suggested in CPU 
> resource limit tests which are applicable here are incorporated too.
> 
> Updated test plan is available here: 
> https://cwiki.apache.org/confluence/download/attachments/30757590/LimitResourcesTestPlanUpdate5.xlsx?version=1&modificationDate=1366952352000
> 
> 
> Diffs
> -
> 
>   test/integration/component/memory_limits/test_domain_limits.py PRE-CREATION 
>   test/integration/component/memory_limits/test_maximum_limits.py 
> PRE-CREATION 
>   test/integration/component/memory_limits/test_memory_limits.py PRE-CREATION 
>   test/integration/component/memory_limits/test_project_limits.py 
> PRE-CREATION 
>   tools/marvin/marvin/integration/lib/base.py 695edf7 
>   tools/marvin/marvin/integration/lib/common.py 4f5acef 
> 
> Diff: https://reviews.apache.org/r/11626/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Gaurav Aradhye
> 
>

RE: [ACS42] Closing resolved issues

[Sudha Ponnaganti]

When I meant "those would also be picked up " means picked up by community for 
validation. Unfortunately there is no QA assignee or validation assignee in 
JIRA for people to identify that they wanted to validate. Comments shows the 
assignment and testing that is being done.  


-Original Message-
From: Nitin Mehta [mailto:nitin.me...@citrix.com] 
Sent: Sunday, August 25, 2013 11:47 PM
To: dev@cloudstack.apache.org; Alena Prokharchyk
Subject: Re: [ACS42] Closing resolved issues

Sudha - I understand, but its always better that another pair of eyes look into 
it. 
The fixer has already verified the fix when he/she is committing it but devs 
are always biased or looking for happy cases only :).
I have numerous bugs filed against myself as well, so better someone else 
verifies them. If you disagree, I can close them right away.

Thanks,
-Nitin

On 24/08/13 3:42 AM, "Sudha Ponnaganti" 
wrote:

>Even so, expectation is those would also be picked up and closed.
>
>From: Alena Prokharchyk
>Sent: Friday, August 23, 2013 3:08 PM
>To: dev@cloudstack.apache.org; Sudha Ponnaganti
>Subject: Re: [ACS42] Closing resolved issues
>
>Sudha, I think we should change the filter to exclude the bugs when the 
>reporter and assignee is the same person. Like I sometimes file bugs 
>for myself, and in this case the bug should be Verified/Closed by 
>somebody else.
>Do you think its a valid suggestion?
>
>Thank you,
>-Alena.
>
>From: Sudha Ponnaganti
>mailto:sudha.ponnaga...@citrix.com>>
>Reply-To: "dev@cloudstack.apache.org"
>mailto:dev@cloudstack.apache.org>>
>Date: Friday, August 23, 2013 11:46 AM
>To: "dev@cloudstack.apache.org"
>mailto:dev@cloudstack.apache.org>>
>Subject: [ACS42] Closing resolved issues
>
>Hi All,
>
>Community has closed 1477 defects in 4.2. However still another 274 
>resolved defects are pending to be closed. Please validate the fix done 
>for the issue reported by you and close it if you are happy with the fix.
>If issue is not fixed, pl reopen it so whoever fixed would get a chance 
>to review it again before release.  Below are outstanding items
>
>project = CLOUDSTACK AND issuetype = Bug AND fixVersion in ("4.2.0",
>"4.2.1") AND status = Resolved
>
>Reporter  Total
>Abhinandan Prateek  2
>Abhinav Roy   1
>Ahmad Emneina   2
>Alena Prokharchyk  18
>angeline shen3
>Anthony Xu4
>Bharat Kumar10
>Brian Angus1
>Brian Federle 1
>Brian Spindler1
>Chandan Purushothama   13
>Chiradeep Vittal   1
>Dave Brosius  1
>Dave Cahill  1
>David Noland 1
>david vz1
>Devdeep Singh 3
>Diogo Monteiro1
>edison su 1
>Fang Wang  4
>Francois Gaudreault   1
>frank zhang1
>Gaurav Aradhye   1
>Harikrishna Patnala 7
>Hiroaki Kawai 2
>Hongtu Zang  2
>Hugo Trippaers 1
>ilya musayev  3
>Isaac Chiang   3
>Jayapal Reddy   6
>Jessica Tomechak2
>Jessica Wang  2
>John Burwell  3
>Kelven Yang   2
>Kishan Kavala 9
>Koushik Das4
>Likitha Shetty 6
>Max Clark1
>Mice Xia   1
>Milamber2
>Min Chen1
>Minying Bao   1
>Murali Reddy 9
>Nick Wales  1
>Nitin Mehta20
>Parth Jagirdar1
>Paul Angus  1
>Pavan Kumar Bandarupally  1
>Prachi Damle  8
>Pranav Saxena  1
>Prasanna Santhanam 2
>Radhika Nair   4
>Rajesh Battala   4
>Ram Ganesh  2
>Rayees Namathponnan9
>roxanne chang  1
>sadhu suresh 5
>Sailaja Mada   6
>Saksham Srivastava 7
>Sangeetha Hariharan  20
>Sanjay Tripathi  1
>Sanjeev N   3
>Sateesh Chodapuneedi 11
>sebastien goasguen1
>Shane Witbeck  1
>Shanker Balan   1
>Sharad Yadav 1
>Sheng Yang 2
>shweta agarwal4
>Simon Weller 1
>Sowmya Krishnan4
>Srikanteswararao Talluri2
>Toshiaki Hatano2
>Venkata Siva Vijayendra Bhamidipati  4
>venkata swamybabu budumuru   3
>Grand Total274
>
>Thanks
>/sudha
>

RE: Writing to volume attached to VM

[Sanjeev Neelarapu]

In case of vmware vm needs to have pv-drivers installed to hot-plugin the disk. 
Otherwise vm restart will show the attached disks .

-Original Message-
From: Suresh Sadhu [mailto:suresh.sa...@citrix.com] 
Sent: Monday, August 26, 2013 3:09 PM
To: dev@cloudstack.apache.org
Subject: RE: Writing to volume attached to VM


/dev/vdb is your data disk

CS won't format automatically ,you have to manually create LV and format 
operations

 do the following steps:

Fdisk /dev/vdb

Option m will provide the menu in that menu select  option to create new 
pattiton
 
2.  Select n option  to create new partition  and choose/accept  the default 
value during partition creation

3. Once partition got created ,select the w option to write I node table info 
4.now you can see /vbb ,vdb1  when you enter fdisk -l
5 format the the  logical partition  created in step 4  like mkfs.ext3 /dev/vdb 
6. mount the disk mount /dev/vdb1 /mnt  and perform IO on mounted path(/mnt)

Hope this helps:


Regards
Sadhu


-Original Message-
From: Gaurav Aradhye [mailto:gaurav.arad...@clogeny.com]
Sent: 26 August 2013 14:53
To: dev@cloudstack.apache.org
Subject: Re: Writing to volume attached to VM

Hi,

Answering your questions in order c,a,b.

c) I am listing the partitions on the vm using fdisk -l command.
This is giving me following output.

 ['', 'Disk /dev/vda: 8589 MB, 8589934592 bytes', '255 head

s, 63 sectors/track, 1044 cylinders', 'Units = cylinders of 16065 * 512 =
8225280 bytes', '', ' Device Boot Start End Blocks Id System',

'/dev/vda1 * 1 13 104391 83 Linux', '/dev/vda2 14 1044 8281507+ 8e Linux LVM', 
'', 'Disk /dev/vdb: 1073 M

B, 1073741824 bytes', '16 heads, 63 sectors/track, 2080 cylinders', 'Units = 
cylinders of 1008 * 512 = 516096 bytes', '']


As you can see two disks /dev/vda and /dev/vdb are listed.

This output remains the same after attaching a volume to the vm.


a) As I am not able to identify any new partition, not able to detect the exact 
partition that needs to be mounted.

This is where I need help. How to identify the volume partitions and mount them?


b) Once the device is identified, it can be mounted using mount command.
Right now it is mounting the root disk partitions.


Firing all these commands to using remoteSSHClient of vm.



Regards,
Gaurav


On Mon, Aug 26, 2013 at 2:16 PM, Prasanna Santhanam  wrote:

> On Mon, Aug 26, 2013 at 02:08:19PM +0530, Gaurav Aradhye wrote:
> > Hi all,
> >
> > Can you guide me on how to write on the external volume (DataDisk)
> attached
> > to a VM?
> >
> > I am trying to mount the partition, but the list of partitions 
> > before and after attaching the volume to vm, remains the same, so I 
> > am unable to detect which partition has been added.
>
> How do you
> a) identify the device on which the disk is available to be mounted
> b) mount the formatted device to your VM
> c) list the partitions/disks
>
> Some commands on how you do this will help.
>
> >
> > Has anybody done this before through test case?
> >
> > Regards,
> > Gaurav
>
> --
> Prasanna.,
>
> 
> Powered by BigRock.com
>
>

Review Request 13806: CLOUDSTACK-4407: Use extractTemplate API to get hypervisor specific template information

[Girish Shilamkar]

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

Review request for cloudstack and Prasanna Santhanam.


Bugs: CLOUDSTACK-4407


Repository: cloudstack-git


Description
---

Template url, hypervisor and format were defined in Service class to be 
Xenserver specific
and therefore registering a new template failed on Vmware and KVM.
Fixed this to get hypervisor specific info for registering new template.

TODO: Update other tests to use the new function get_builtin_template_info


Diffs
-

  test/integration/component/test_templates.py e4599d4 
  tools/marvin/marvin/integration/lib/base.py b5d086b 
  tools/marvin/marvin/integration/lib/common.py 4f5acef 

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


Testing
---


Thanks,

Girish Shilamkar

Review Request 13807: we should not reserve memory and cpu for vmware VMs if the vmware.reserve.cpu and vmware.reserve.mem are set to false.

[bharat kumar]

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

Review request for cloudstack and Nitin Mehta.


Bugs: Cloudstack-4498


Repository: cloudstack-git


Description
---

https://issues.apache.org/jira/browse/CLOUDSTACK-4498
we should not reserve memory and cpu for vmware VMs if the vmware.reserve.cpu 
and vmware.reserve.mem are set to false.

currently overcommit dose not honor the flag vmware.reserve.mem and 
vmware.reserve.cpu. Now we have fixed this and brought down these parameters to 
cluster level.


Diffs
-

  plugins/hypervisors/vmware/src/com/cloud/hypervisor/guru/VMwareGuru.java 
8aae8c8 
  
plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/manager/VmwareManagerImpl.java
 4d24562 
  
plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/resource/VmwareResource.java
 9cb6115 
  server/src/com/cloud/configuration/Config.java 8955087 
  vmware-base/src/com/cloud/hypervisor/vmware/util/VmwareHelper.java e545c8e 

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


Testing
---

Tested on 4.2


Thanks,

bharat kumar

Review Request 13810: [ZWPS] attaching an uploaded volume to a VM is always going to first primary storage added

[Rajesh Battala]

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

Review request for cloudstack, edison su and Ram Ganesh.


Bugs: CLOUDSTACK-4475


Repository: cloudstack-git


Description
---

Attaching uploaded failing is failing as the move volume is not restricted for 
ZONE/Cluster pool scope type

Fixed Validation to allow Zone/Cluster scope pools
fixed setting image format on volume.
Fixed unnecessary moving of the Volume from secondary To Primary.


Diffs
-

  engine/schema/src/com/cloud/storage/VolumeVO.java bbecf03 
  server/src/com/cloud/storage/VolumeManagerImpl.java f7c0f86 

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


Testing
---

1. Verified by uploading the volume and attaching it to the VM running on Zone 
Scope Pool.


Thanks,

Rajesh Battala

RE: [GSoC] Branch Merge Request LdapPlugin and Master

[Musayev, Ilya]

Ian

I want  to leave you with 1 last thought, this plugin will be used on daily 
basis by hundreds (if not thousands) in the near future - all thanks to you and 
GSoC.

Thank you for your contribution. It is greatly appreciated!

Regards
ilya

PS: If you can complete the part that was out of scope in the near future when 
time allows, it will help - tremendously.


> -Original Message-
> From: Ian Duffy [mailto:i...@ianduffy.ie]
> Sent: Friday, August 23, 2013 11:26 AM
> To: CloudStack Dev
> Subject: [GSoC] Branch Merge Request LdapPlugin and Master
> 
> Hi Guys,
> 
> The work in the LdapPlugin branch is now complete in accordance to the
> proposal I submitted for the GSoC program outlining what would be
> undertaken.
> 
> I have uploaded a revised proposal to cover some of the small discrepancies.
> http://ianduffy.ie/cloudstack/cloudstack-ldap-revised.pdf
> 
> The branch is in a working state, all new additions have been unit tested and
> documented accordingly.
> 
> If somebody could code review it and merge it to master that would be
> great.
> 
> As mentioned in a previous email on the list something needs to be
> implemented to search LDAP on schedule to find deleted users and revoke
> their keys as necessary. I have been talking to Ilya and Alex about this. I 
> will
> look into doing this over the next month(Time dedicate won't be as great).
> 
> Thanks to everybody for making this opportunity possible! It has been great
> working with you guys and the GSoC programme.
> Ian

Re: Review Request 13807: we should not reserve memory and cpu for vmware VMs if the vmware.reserve.cpu and vmware.reserve.mem are set to false.

[bharat kumar]

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

(Updated Aug. 26, 2013, 3:42 p.m.)


Review request for cloudstack and Nitin Mehta.


Bugs: Cloudstack-4498


Repository: cloudstack-git


Description
---

https://issues.apache.org/jira/browse/CLOUDSTACK-4498
we should not reserve memory and cpu for vmware VMs if the vmware.reserve.cpu 
and vmware.reserve.mem are set to false.

currently overcommit dose not honor the flag vmware.reserve.mem and 
vmware.reserve.cpu. Now we have fixed this and brought down these parameters to 
cluster level.


Diffs (updated)
-

  plugins/hypervisors/vmware/src/com/cloud/hypervisor/guru/VMwareGuru.java 
8aae8c8 
  
plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/manager/VmwareManagerImpl.java
 4d24562 
  
plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/resource/VmwareResource.java
 9cb6115 
  server/src/com/cloud/configuration/Config.java 8955087 
  vmware-base/src/com/cloud/hypervisor/vmware/util/VmwareHelper.java e545c8e 

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


Testing
---

Tested on 4.2


Thanks,

bharat kumar

Re: [GSoC] Branch Merge Request LdapPlugin and Master

[Chip Childers]

Ilya,

Can you handle doing his merge request into master?

-chip

On Mon, Aug 26, 2013 at 03:23:30PM +, Musayev, Ilya wrote:
> Ian
> 
> I want  to leave you with 1 last thought, this plugin will be used on daily 
> basis by hundreds (if not thousands) in the near future - all thanks to you 
> and GSoC.
> 
> Thank you for your contribution. It is greatly appreciated!
> 
> Regards
> ilya
> 
> PS: If you can complete the part that was out of scope in the near future 
> when time allows, it will help - tremendously.
> 
> 
> > -Original Message-
> > From: Ian Duffy [mailto:i...@ianduffy.ie]
> > Sent: Friday, August 23, 2013 11:26 AM
> > To: CloudStack Dev
> > Subject: [GSoC] Branch Merge Request LdapPlugin and Master
> > 
> > Hi Guys,
> > 
> > The work in the LdapPlugin branch is now complete in accordance to the
> > proposal I submitted for the GSoC program outlining what would be
> > undertaken.
> > 
> > I have uploaded a revised proposal to cover some of the small discrepancies.
> > http://ianduffy.ie/cloudstack/cloudstack-ldap-revised.pdf
> > 
> > The branch is in a working state, all new additions have been unit tested 
> > and
> > documented accordingly.
> > 
> > If somebody could code review it and merge it to master that would be
> > great.
> > 
> > As mentioned in a previous email on the list something needs to be
> > implemented to search LDAP on schedule to find deleted users and revoke
> > their keys as necessary. I have been talking to Ilya and Alex about this. I 
> > will
> > look into doing this over the next month(Time dedicate won't be as great).
> > 
> > Thanks to everybody for making this opportunity possible! It has been great
> > working with you guys and the GSoC programme.
> > Ian

Re: [VOTE] Apache Cloudstack 4.2.0

[Chip Childers]

On Fri, Aug 23, 2013 at 06:55:03PM +, Animesh Chaturvedi wrote:
> 
> 
> Hi All,
> 
> I've created a 4.2.0 release, with the following artifacts up for a
> vote:
> 
> Git Branch and Commit SH:
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.2
> Commit: 06f28722b6fe5827d58861e9a9d47fe46aaafefa
> 
> List of changes:
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=CHANGES;hb=4.2
> 
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.2.0/
> 
> PGP release keys (signed using 94BE0D7C):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> 
> Testing instructions are here:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+procedure
> 
> Vote will be open for 72 hours.
> 
> For sanity in tallying the vote, can PMC members please be sure to indicate 
> "(binding)" with their vote?
> 
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
> 
> 

-1 (binding)

The reason is my fault.  I forgot that I committed to adding the legal
docs for this:  http://markmail.org/message/rrxypu25fwyxjdae

I am working on it now.

-chip

why 2 spaces for xml?

[Darren Shepherd]

I hate discussions about coding conventions, but I just have to ask. 
Why is XML two spaces?  Java, JavaScript, Python, all 4 spaces for 
indent.  But XML is 2.  Why is it special?


Darren

Re: why 2 spaces for xml?

[Marty Sweet]

All the XML documentation I have seen has been 4 spaces for indent, what
XML files are you talking about?

Marty


On Mon, Aug 26, 2013 at 5:11 PM, Darren Shepherd <
darren.s.sheph...@gmail.com> wrote:

> I hate discussions about coding conventions, but I just have to ask. Why
> is XML two spaces?  Java, JavaScript, Python, all 4 spaces for indent.  But
> XML is 2.  Why is it special?
>
> Darren
>

Re: [VOTE] Apache Cloudstack 4.2.0

[Chip Childers]

On Mon, Aug 26, 2013 at 12:02:32PM -0400, Chip Childers wrote:
> On Fri, Aug 23, 2013 at 06:55:03PM +, Animesh Chaturvedi wrote:
> > 
> > 
> > Hi All,
> > 
> > I've created a 4.2.0 release, with the following artifacts up for a
> > vote:
> > 
> > Git Branch and Commit SH:
> > https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.2
> > Commit: 06f28722b6fe5827d58861e9a9d47fe46aaafefa
> > 
> > List of changes:
> > https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=CHANGES;hb=4.2
> > 
> > Source release (checksums and signatures are available at the same
> > location):
> > https://dist.apache.org/repos/dist/dev/cloudstack/4.2.0/
> > 
> > PGP release keys (signed using 94BE0D7C):
> > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> > 
> > Testing instructions are here:
> > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+procedure
> > 
> > Vote will be open for 72 hours.
> > 
> > For sanity in tallying the vote, can PMC members please be sure to indicate 
> > "(binding)" with their vote?
> > 
> > [ ] +1  approve
> > [ ] +0  no opinion
> > [ ] -1  disapprove (and reason why)
> > 
> > 
> 
> -1 (binding)
> 
> The reason is my fault.  I forgot that I committed to adding the legal
> docs for this:  http://markmail.org/message/rrxypu25fwyxjdae
> 
> I am working on it now.
> 
> -chip

Resolved now in master / 4.2 / 4.2-forward

Re: why 2 spaces for xml?

[Sebastien Goasguen]

On Aug 26, 2013, at 12:22 PM, Marty Sweet  wrote:

> All the XML documentation I have seen has been 4 spaces for indent, what
> XML files are you talking about?

in the documentation I don't think we have been very consistent...

> 
> Marty
> 
> 
> On Mon, Aug 26, 2013 at 5:11 PM, Darren Shepherd <
> darren.s.sheph...@gmail.com> wrote:
> 
>> I hate discussions about coding conventions, but I just have to ask. Why
>> is XML two spaces?  Java, JavaScript, Python, all 4 spaces for indent.  But
>> XML is 2.  Why is it special?
>> 
>> Darren
>> 

Re: why 2 spaces for xml?

[Darren Shepherd]

On 08/26/2013 09:22 AM, Marty Sweet wrote:

All the XML documentation I have seen has been 4 spaces for indent, what
XML files are you talking about?



I couldn't find documented on the ACS web page or website that the 
standard was 2 spaces, but I swear I saw it written somewhere. 
Regardless, I'm looking at all the pom.xml and applicationContext*.xml 
files.


Darren

Re: why 2 spaces for xml?

[Chip Childers]

On Mon, Aug 26, 2013 at 10:12:30AM -0700, Darren Shepherd wrote:
> On 08/26/2013 09:22 AM, Marty Sweet wrote:
> >All the XML documentation I have seen has been 4 spaces for indent, what
> >XML files are you talking about?
> >
> 
> I couldn't find documented on the ACS web page or website that the
> standard was 2 spaces, but I swear I saw it written somewhere.
> Regardless, I'm looking at all the pom.xml and
> applicationContext*.xml files.
> 
> Darren
> 
>

Nothing but inconsistency causing that...  we should just use 4
everywhere IMO.

Re: CloudMonkey 5.0 (was Re: CloudMonkey's new home)

[Chip Childers]

On Sun, Aug 11, 2013 at 01:06:37PM +0200, Daan Hoogland wrote:
> ok, the down side will be that the semantics of the versioning are
> confusing when cloudstack 5 comes and the version numbers don't match.
> still a +1 from me though.

I find it confusing as well, but am OK with a stable 5.x line being the
start of the new repo's release versioning.  Since I know that Rohit is
focused on other things now, I'm going to pick this up and figure out
what is needed to get the first independent CloudMonkey release out the
door.

> 
> On Sat, Aug 10, 2013 at 8:54 PM, Rohit Yadav  wrote:
> > On Sat, Aug 10, 2013 at 10:32 PM, Daan Hoogland 
> > wrote:
> >
> >> +1 +question
> >>
> >> Is cloudmonkey 5 backwards compatible in the sense that it can talk to a
> >> 4.x ms?
> >>
> >
> > Sorry for the confusion. Yes, in fact it is. It's the same cloudmonkey and
> > is aimed to work with Apache CloudStack 4.0.0-incubating and its
> > derivatives. If it does not it's a bug.
> >
> > We're gaming the version number, since cloudmonkey-4.x was already out
> > here, it would create confusion if we release cloudmonkey-1.x. Therefore,
> > it made sense to just start with 5.0.0 and use semver from this version.
> >
> > Regards.
> >
> >
> >>
> >> On Sat, Aug 10, 2013 at 5:50 AM, David Nalley  wrote:
> >> > +1 move forward.
> >> >
> >> > On Fri, Aug 9, 2013 at 5:02 PM, Rohit Yadav 
> >> wrote:
> >> >> Hi folks,
> >> >>
> >> >> Looks like the previous thread failed to capture attention on the dev
> >> ML.
> >> >> I'm going forward with some decisions so as to move fast and as per our
> >> >> philosophy to ask for forgiveness later than just waste time on too much
> >> >> process polling now.
> >> >>
> >> >> Here are some proposals;
> >> >>
> >> >> - The version model would be to move fast, break things, release early
> >> and
> >> >> release often
> >> >> - Start with 5.0 version: Since cloudmonkey 4.x is already out there,
> >> I'm
> >> >> proposing we start new cloudmonkey releases from 5.0; This is just to
> >> make
> >> >> sure we don't end up releasing a 1.0 when we already have a 4.x
> >> >> - Using semver, we don't deviate from major version "5" until we have
> >> >> backward incompatible changes of configuration, paths, DSL etc.
> >> >> - We'll use git tags to track (unvoted) releasable or testable
> >> candidates.
> >> >> This is so we can release fast, release often. We can append a -rc for
> >> such
> >> >> releases on git and pypi.
> >> >> - A tested and voted release could take time and some process; but pypi
> >> >> channel may not be necessarily used for only official releases, but all
> >> and
> >> >> every release, even the test ones.
> >> >>
> >> >> Suggestions, flames?
> >> >>
> >> >> Moving forward, as it seems already, I may not be able to contribute on
> >> >> weekends.
> >> >>
> >> >> I may be only able to help with the first release, that too the
> >> non-process
> >> >> oriented parts, perhaps people who already have some idea about the
> >> >> internals of cloudmonkey like Prasanna or Sebastien can help lead the
> >> >> component?
> >> >>
> >> >> Regards.
> >> >>
> >> >>
> >> >> On Sun, Jul 28, 2013 at 11:04 PM, Rohit Yadav 
> >> wrote:
> >> >>
> >> >>> Based on our previous discussion thread[1], we've moved CloudMonkey
> >> out of
> >> >>> ACS's repository to its new home [2]. Now,
> >> >>> with 6f84e74a68d78705a06fe58f7927f42f61453a16 on master, we no longer
> >> have
> >> >>> cloudmonkey in tools/cli. CloudMonkey will be within CloudStack
> >> project but
> >> >>> now as an independent sub-project with its own repository and will
> >> have a
> >> >>> faster need-basis release cycle.
> >> >>>
> >> >>> For doing that, please suggest on the release process or how it should
> >> >>> work? If the present RM or someone wants to lead the release process?
> >> >>> I just want to keep it simple with fast releases whenever we have a
> >> >>> releasable candidate and semver[3] versioning. So, we ship things fast
> >> and
> >> >>> don't worry if it breaks since we'll be shipping fast. We can after a
> >> fast
> >> >>> lazy consensus/voting and publish via pypi and put the
> >> tarballs/zipballs
> >> >>> under dists/ on ASF/CloudStack.
> >> >>>
> >> >>> Regards.
> >> >>>
> >> >>> [1] http://markmail.org/message/tjlr753xfhpw4uk4
> >> >>> [2]
> >> https://git-wip-us.apache.org/repos/asf?p=cloudstack-cloudmonkey.git
> >> >>> [3] http://semver.org/
> >> >>>
> >>
> 

Re: Templates via Vagrant Provider and Veewee

[Chiradeep Vittal]

The stuff in tools/appliance is easy to customize. I built a Quagga
template with slight mods.
Methinks we can use it like Aminator
https://github.com/Netflix/aminator


On 8/25/13 10:11 AM, "Prasanna Santhanam"  wrote:

>All our systemVMs come from veewee + vagrant.
>
>see tools/appliance
>
>On Sun, Aug 25, 2013 at 05:57:50PM +0100, Ian Duffy wrote:
>> Hey,
>> 
>> Has anybody tried to use the vagrant provider through veewee in order to
>> create templates?
>
>-- 
>Prasanna.,
>
>
>Powered by BigRock.com
>

[DISCUSS] Gearing up for an official CloudMonkey independent release

[Chip Childers]

Hi all,

I'm looking at what it's going to take to get CloudMonkey out as an
official release.  Here's what I believe needs to be done:

1) Legal doc check (I think we're good here, since I just added the
NOTICE file)

2) Release process document

3) Add an initial pre-cache file to the repo itself.  I want to do this,
so that it doesn't require you to have a running 4.1+ ACS install in
order to do a CloudMonkey build.

4) Kick out a release

5) Update the cloudstack.apache.org website to provide links to the
cloudmonkey component's source repo and distinct artifacts.

Once we get this first release out, we need to probably stop publishing
to pypi outside of the *official release* process.  That being said,
it'll be easier to release CloudMonkey independently.

Thoughts, comments, flames?

-chip

Review Request 13821: CLOUDSTACK-4510 Move NS scripts to appropriate suite to avoid failures

[Sowmya Krishnan]

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

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


Bugs: CLOUDSTACK-4510


Repository: cloudstack-git


Description
---

Moved TestNwOffNetscaler from test_network_offerings to test_netscaler_nw_off 
since it's more relevant sitting in the latter.
Also, it's important that NS scripts run separately with add/remove as part of 
setup/tearDown since we assume that NS addition/deletion is handled completely 
by the script itself.

Related to this, there are some minor changes in common.py -> add_netscaler to 
accept NS services directly than the entire services object. Provides more 
flexibility this way to be able to specify which NS device should be added if 
we have more than one in the script.

Appropriate changes were also done to scripts using add_netscaler


Diffs
-

  test/integration/component/test_netscaler_lb.py 8375f25 
  test/integration/component/test_netscaler_lb_algo.py 24c1837 
  test/integration/component/test_netscaler_lb_sticky.py 7ec85a1 
  test/integration/component/test_netscaler_nw_off.py 5742f09 
  test/integration/component/test_network_offering.py e8a7b97 
  tools/marvin/marvin/integration/lib/common.py 7e8d92d 

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


Testing
---

Tested the scripts locally and they are all passing.


Thanks,

Sowmya Krishnan

Re: Log files on add ISOs/Templates

[Chiradeep Vittal]

>From the db
select id, unique_name, name, type, created, state from vm_template;
select id, template_id, download_state, error_str from template_host_ref
where template_id=

On 8/26/13 1:06 AM, "Amit Das"  wrote:

>Hi folks,
>
>Are there any specific success/error log statements on adding ISOs or
>Templates.
>
>Can we find them in management server's catalina.out ?
>
>Do we have any manual workaround to add ISOs or Templates ?
>
>Regards,
>Amit
>*CloudByte Inc.* 

Re: Log files on add ISOs/Templates

[Min Chen]

In 4.2, template_host_ref is deprecated, you should use template_store_ref.

Thanks
-min

On 8/26/13 10:46 AM, "Chiradeep Vittal" 
wrote:

>From the db
>select id, unique_name, name, type, created, state from vm_template;
>select id, template_id, download_state, error_str from template_host_ref
>where template_id=
>
>On 8/26/13 1:06 AM, "Amit Das"  wrote:
>
>>Hi folks,
>>
>>Are there any specific success/error log statements on adding ISOs or
>>Templates.
>>
>>Can we find them in management server's catalina.out ?
>>
>>Do we have any manual workaround to add ISOs or Templates ?
>>
>>Regards,
>>Amit
>>*CloudByte Inc.* 
>

VMware error

[Mike Tutkowski]

Hi,

I was wondering if one of our VMware experts out there might be able to
comment on why I'm getting the following exception when trying to add a
static iSCSI target to an ESXi host of mine:

Operation failed, diagnostics report: iScsiLibException: status(c000):
Invalid parameter; Message= IMA_AddStaticDiscoveryTarget

I've seen some comments on the web, but nothing definitive.

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

Review Request 13833: Added missing getters to UserVmResponse

[Chris Suich]

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

Review request for cloudstack.


Repository: cloudstack-git


Description
---

UserVmResponse was missing some getters, so I generated them with Eclipse.


Diffs
-

  api/src/org/apache/cloudstack/api/response/UserVmResponse.java e49e16b 

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


Testing
---


Thanks,

Chris Suich

4.3 Code Freeze

[Will Stevens]

Can someone please let me know what the code freeze date for 4.3 is?

Thanks,

Will

RE: 4.3 Code Freeze

[Animesh Chaturvedi]

Last week of october

> -Original Message-
> From: williamstev...@gmail.com [mailto:williamstev...@gmail.com] On
> Behalf Of Will Stevens
> Sent: Monday, August 26, 2013 12:28 PM
> To: dev@cloudstack.apache.org
> Subject: 4.3 Code Freeze
> 
> Can someone please let me know what the code freeze date for 4.3 is?
> 
> Thanks,
> 
> Will

RE: [VOTE] Apache Cloudstack 4.2.0

[Animesh Chaturvedi]

> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Monday, August 26, 2013 9:38 AM
> To: dev@cloudstack.apache.org
> Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> 
> On Mon, Aug 26, 2013 at 12:02:32PM -0400, Chip Childers wrote:
> > On Fri, Aug 23, 2013 at 06:55:03PM +, Animesh Chaturvedi wrote:
> > >
> > >
> > > Hi All,
> > >
> > > I've created a 4.2.0 release, with the following artifacts up for a
> > > vote:
> > >
> > > Git Branch and Commit SH:
> > > https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;
> > > h=refs/heads/4.2
> > > Commit: 06f28722b6fe5827d58861e9a9d47fe46aaafefa
> > >
> > > List of changes:
> > > https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plai
> > > n;f=CHANGES;hb=4.2
> > >
> > > Source release (checksums and signatures are available at the same
> > > location):
> > > https://dist.apache.org/repos/dist/dev/cloudstack/4.2.0/
> > >
> > > PGP release keys (signed using 94BE0D7C):
> > > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> > >
> > > Testing instructions are here:
> > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+
> > > procedure
> > >
> > > Vote will be open for 72 hours.
> > >
> > > For sanity in tallying the vote, can PMC members please be sure to
> indicate "(binding)" with their vote?
> > >
> > > [ ] +1  approve
> > > [ ] +0  no opinion
> > > [ ] -1  disapprove (and reason why)
> > >
> > >
> >
> > -1 (binding)
> >
> > The reason is my fault.  I forgot that I committed to adding the legal
> > docs for this:  http://markmail.org/message/rrxypu25fwyxjdae
> >
> > I am working on it now.
> >
> > -chip
> 
> Resolved now in master / 4.2 / 4.2-forward
[Animesh>] I will create a new RC and start a new VOTE. If this is the only 
change (mostly textual) does the VOTE has to be open for still 72 hours?

Re: [VOTE] Apache Cloudstack 4.2.0

[Mike Tutkowski]

I have actually received some critical info from VMworld about how people
what to use the SolidFire plug-in.

It is a small, but important change.

Can I put my fix in?


On Mon, Aug 26, 2013 at 2:13 PM, Animesh Chaturvedi <
animesh.chaturv...@citrix.com> wrote:

>
>
> > -Original Message-
> > From: Chip Childers [mailto:chip.child...@sungard.com]
> > Sent: Monday, August 26, 2013 9:38 AM
> > To: dev@cloudstack.apache.org
> > Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> >
> > On Mon, Aug 26, 2013 at 12:02:32PM -0400, Chip Childers wrote:
> > > On Fri, Aug 23, 2013 at 06:55:03PM +, Animesh Chaturvedi wrote:
> > > >
> > > >
> > > > Hi All,
> > > >
> > > > I've created a 4.2.0 release, with the following artifacts up for a
> > > > vote:
> > > >
> > > > Git Branch and Commit SH:
> > > > https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;
> > > > h=refs/heads/4.2
> > > > Commit: 06f28722b6fe5827d58861e9a9d47fe46aaafefa
> > > >
> > > > List of changes:
> > > > https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plai
> > > > n;f=CHANGES;hb=4.2
> > > >
> > > > Source release (checksums and signatures are available at the same
> > > > location):
> > > > https://dist.apache.org/repos/dist/dev/cloudstack/4.2.0/
> > > >
> > > > PGP release keys (signed using 94BE0D7C):
> > > > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> > > >
> > > > Testing instructions are here:
> > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+
> > > > procedure
> > > >
> > > > Vote will be open for 72 hours.
> > > >
> > > > For sanity in tallying the vote, can PMC members please be sure to
> > indicate "(binding)" with their vote?
> > > >
> > > > [ ] +1  approve
> > > > [ ] +0  no opinion
> > > > [ ] -1  disapprove (and reason why)
> > > >
> > > >
> > >
> > > -1 (binding)
> > >
> > > The reason is my fault.  I forgot that I committed to adding the legal
> > > docs for this:  http://markmail.org/message/rrxypu25fwyxjdae
> > >
> > > I am working on it now.
> > >
> > > -chip
> >
> > Resolved now in master / 4.2 / 4.2-forward
> [Animesh>] I will create a new RC and start a new VOTE. If this is the
> only change (mostly textual) does the VOTE has to be open for still 72
> hours?
>
>


-- 
*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: [VOTE] Apache Cloudstack 4.2.0

[Animesh Chaturvedi]

> -Original Message-
> From: Wido den Hollander [mailto:w...@widodh.nl]
> Sent: Monday, August 26, 2013 12:24 AM
> To: dev@cloudstack.apache.org
> Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> 
> -1 (binding)
> 
> I am aware of Ceph bugs which are still open for 4.2, like migrating
> from primary to primary storage.
> 
> I didn't get around fixing those yet since they were reported just last
> week.
> 
> The issue: https://issues.apache.org/jira/browse/CLOUDSTACK-4423
> 
> Wido
> 
[Animesh>] Wido I am going to cut another RC to pick up licensing fixes from 
Chip. Do you have a fix for the issue reported? IMO looking through that issue 
it can be covered in 4.2.1.

> On 08/23/2013 08:55 PM, Animesh Chaturvedi wrote:
> >
> >
> > Hi All,
> >
> > I've created a 4.2.0 release, with the following artifacts up for a
> > vote:
> >
> > Git Branch and Commit SH:
> > https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=
> > refs/heads/4.2
> > Commit: 06f28722b6fe5827d58861e9a9d47fe46aaafefa
> >
> > List of changes:
> > https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;
> > f=CHANGES;hb=4.2
> >
> > Source release (checksums and signatures are available at the same
> > location):
> > https://dist.apache.org/repos/dist/dev/cloudstack/4.2.0/
> >
> > PGP release keys (signed using 94BE0D7C):
> > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> >
> > Testing instructions are here:
> > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+pr
> > ocedure
> >
> > Vote will be open for 72 hours.
> >
> > For sanity in tallying the vote, can PMC members please be sure to
> indicate "(binding)" with their vote?
> >
> > [ ] +1  approve
> > [ ] +0  no opinion
> > [ ] -1  disapprove (and reason why)
> >

RE: [VOTE] Apache Cloudstack 4.2.0

[Animesh Chaturvedi]

> -Original Message-
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: Monday, August 26, 2013 1:22 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> 
> I have actually received some critical info from VMworld about how
> people what to use the SolidFire plug-in.
> 
> It is a small, but important change.
> 
> Can I put my fix in?
> 
[Animesh>] What is the nature of change and risk of regression? Can it wait for 
4.2.1? Do you have a tested fix available now?
> 
> On Mon, Aug 26, 2013 at 2:13 PM, Animesh Chaturvedi <
> animesh.chaturv...@citrix.com> wrote:
> 
> >
> >
> > > -Original Message-
> > > From: Chip Childers [mailto:chip.child...@sungard.com]
> > > Sent: Monday, August 26, 2013 9:38 AM
> > > To: dev@cloudstack.apache.org
> > > Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> > >
> > > On Mon, Aug 26, 2013 at 12:02:32PM -0400, Chip Childers wrote:
> > > > On Fri, Aug 23, 2013 at 06:55:03PM +, Animesh Chaturvedi
> wrote:
> > > > >
> > > > >
> > > > > Hi All,
> > > > >
> > > > > I've created a 4.2.0 release, with the following artifacts up
> > > > > for a
> > > > > vote:
> > > > >
> > > > > Git Branch and Commit SH:
> > > > > https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=short
> > > > > log;
> > > > > h=refs/heads/4.2
> > > > > Commit: 06f28722b6fe5827d58861e9a9d47fe46aaafefa
> > > > >
> > > > > List of changes:
> > > > > https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_
> > > > > plai
> > > > > n;f=CHANGES;hb=4.2
> > > > >
> > > > > Source release (checksums and signatures are available at the
> > > > > same
> > > > > location):
> > > > > https://dist.apache.org/repos/dist/dev/cloudstack/4.2.0/
> > > > >
> > > > > PGP release keys (signed using 94BE0D7C):
> > > > > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> > > > >
> > > > > Testing instructions are here:
> > > > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+t
> > > > > est+
> > > > > procedure
> > > > >
> > > > > Vote will be open for 72 hours.
> > > > >
> > > > > For sanity in tallying the vote, can PMC members please be sure
> > > > > to
> > > indicate "(binding)" with their vote?
> > > > >
> > > > > [ ] +1  approve
> > > > > [ ] +0  no opinion
> > > > > [ ] -1  disapprove (and reason why)
> > > > >
> > > > >
> > > >
> > > > -1 (binding)
> > > >
> > > > The reason is my fault.  I forgot that I committed to adding the
> > > > legal docs for this:  http://markmail.org/message/rrxypu25fwyxjdae
> > > >
> > > > I am working on it now.
> > > >
> > > > -chip
> > >
> > > Resolved now in master / 4.2 / 4.2-forward
> > [Animesh>] I will create a new RC and start a new VOTE. If this is the
> > only change (mostly textual) does the VOTE has to be open for still 72
> > hours?
> >
> >
> 
> 
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud
> *(tm)*

Re: [VOTE] Apache Cloudstack 4.2.0

[Wido den Hollander]

On 08/26/2013 10:25 PM, Animesh Chaturvedi wrote:




-Original Message-
From: Wido den Hollander [mailto:w...@widodh.nl]
Sent: Monday, August 26, 2013 12:24 AM
To: dev@cloudstack.apache.org
Subject: Re: [VOTE] Apache Cloudstack 4.2.0

-1 (binding)

I am aware of Ceph bugs which are still open for 4.2, like migrating
from primary to primary storage.

I didn't get around fixing those yet since they were reported just last
week.

The issue: https://issues.apache.org/jira/browse/CLOUDSTACK-4423

Wido


[Animesh>] Wido I am going to cut another RC to pick up licensing fixes from 
Chip. Do you have a fix for the issue reported? IMO looking through that issue it 
can be covered in 4.2.1.



I also sent a cherry-pick request last week for a fix which is in 
4.2-forward: 829dbaccb470431244f814a9d95fc7823a3e0201


It isn't in 4.2 yet. It fixes a different RBD issue.

Wido


On 08/23/2013 08:55 PM, Animesh Chaturvedi wrote:



Hi All,

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

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

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

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

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

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

Vote will be open for 72 hours.

For sanity in tallying the vote, can PMC members please be sure to

indicate "(binding)" with their vote?


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

Re: [VOTE] Apache Cloudstack 4.2.0

[Mike Tutkowski]

Hi Animesh,

It is related to adding an iSCSI target to ESX(i).

The 4.2 code assumes you will want to use Mutual CHAP. This fix allows the
user to not have to use Mutual CHAP.

It's only a small number of changes, pretty low risk, and should only
impact the SolidFire plug-in as no other plug-in code has been written to
date that uses the logic in the VMware code that I would need to modify.

I've written and tested the code, as well.

Talk to you later,


On Mon, Aug 26, 2013 at 2:44 PM, Wido den Hollander  wrote:

>
>
> On 08/26/2013 10:25 PM, Animesh Chaturvedi wrote:
>
>>
>>
>>  -Original Message-
>>> From: Wido den Hollander [mailto:w...@widodh.nl]
>>> Sent: Monday, August 26, 2013 12:24 AM
>>> To: dev@cloudstack.apache.org
>>> Subject: Re: [VOTE] Apache Cloudstack 4.2.0
>>>
>>> -1 (binding)
>>>
>>> I am aware of Ceph bugs which are still open for 4.2, like migrating
>>> from primary to primary storage.
>>>
>>> I didn't get around fixing those yet since they were reported just last
>>> week.
>>>
>>> The issue: 
>>> https://issues.apache.org/**jira/browse/CLOUDSTACK-4423
>>>
>>> Wido
>>>
>>>  [Animesh>] Wido I am going to cut another RC to pick up licensing fixes
>> from Chip. Do you have a fix for the issue reported? IMO looking through
>> that issue it can be covered in 4.2.1.
>>
>>
> I also sent a cherry-pick request last week for a fix which is in
> 4.2-forward: 829dbaccb470431244f814a9d95fc7**823a3e0201
>
> It isn't in 4.2 yet. It fixes a different RBD issue.
>
> Wido
>
>
>  On 08/23/2013 08:55 PM, Animesh Chaturvedi wrote:
>>>


 Hi All,

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

 Git Branch and Commit SH:
 https://git-wip-us.apache.org/**repos/asf?p=cloudstack.git;a=**
 shortlog;h=
 refs/heads/4.2
 Commit: 06f28722b6fe5827d58861e9a9d47f**e46aaafefa

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

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

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

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

 Vote will be open for 72 hours.

 For sanity in tallying the vote, can PMC members please be sure to

>>> indicate "(binding)" with their vote?
>>>

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




-- 
*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: [VOTE] Apache Cloudstack 4.2.0

[Animesh Chaturvedi]

> >>
> > [Animesh>] Wido I am going to cut another RC to pick up licensing
> fixes from Chip. Do you have a fix for the issue reported? IMO looking
> through that issue it can be covered in 4.2.1.
> >
> 
> I also sent a cherry-pick request last week for a fix which is in
> 4.2-forward: 829dbaccb470431244f814a9d95fc7823a3e0201
> 
> It isn't in 4.2 yet. It fixes a different RBD issue.
> 
> Wido
> 
[Animesh>] Yes I saw that and I will pull it in for the new RC build anyway. Do 
you have fix for CLOUDSTACK-4423? Did you check my comment on it

Re: [DISCUSS] Gearing up for an official CloudMonkey independent release

[Chiradeep Vittal]

Does the release require voting?

On 8/26/13 10:27 AM, "Chip Childers"  wrote:

>Hi all,
>
>I'm looking at what it's going to take to get CloudMonkey out as an
>official release.  Here's what I believe needs to be done:
>
>1) Legal doc check (I think we're good here, since I just added the
>NOTICE file)
>
>2) Release process document
>
>3) Add an initial pre-cache file to the repo itself.  I want to do this,
>so that it doesn't require you to have a running 4.1+ ACS install in
>order to do a CloudMonkey build.
>
>4) Kick out a release
>
>5) Update the cloudstack.apache.org website to provide links to the
>cloudmonkey component's source repo and distinct artifacts.
>
>Once we get this first release out, we need to probably stop publishing
>to pypi outside of the *official release* process.  That being said,
>it'll be easier to release CloudMonkey independently.
>
>Thoughts, comments, flames?
>
>-chip

RE: [VOTE] Apache Cloudstack 4.2.0

[Animesh Chaturvedi]

> -Original Message-
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: Monday, August 26, 2013 1:48 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> 
> Hi Animesh,
> 
> It is related to adding an iSCSI target to ESX(i).
> 
> The 4.2 code assumes you will want to use Mutual CHAP. This fix allows
> the user to not have to use Mutual CHAP.
> 
> It's only a small number of changes, pretty low risk, and should only
> impact the SolidFire plug-in as no other plug-in code has been written
> to date that uses the logic in the VMware code that I would need to
> modify.
> 
> I've written and tested the code, as well.
> 
> Talk to you later,
> 
[Animesh>] Can you put your fix in 4.2-forward ASAP

Re: [DISCUSS/PROPOSAL] Upgrading Driver Model

[Darren Shepherd]

John,

I mentioned before I'd been thinking up some ideas that go along with 
some of the things you've proposed here.  I'm working through a lot of 
different ideas right now, but I've thrown up some notes in a totally 
random part of the CloudStack wiki.  Take a look, this is a complete 
work in progress, but you can maybe get an idea of where my head is 
going (complete with really bad grammar and typos).


Wiki: 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Nothing+to+see+here...#Nothingtoseehere...-ModuleSystem


Some code too:  https://github.com/ibuildthecloud/cloudstack-modules

This is based off of stuff I've done in the past.  So nothing is too 
hand wavy.


Darren

Re: [VOTE] Apache Cloudstack 4.2.0

[Wido den Hollander]

On 08/26/2013 10:50 PM, Animesh Chaturvedi wrote:





[Animesh>] Wido I am going to cut another RC to pick up licensing

fixes from Chip. Do you have a fix for the issue reported? IMO looking
through that issue it can be covered in 4.2.1.




I also sent a cherry-pick request last week for a fix which is in
4.2-forward: 829dbaccb470431244f814a9d95fc7823a3e0201

It isn't in 4.2 yet. It fixes a different RBD issue.

Wido


[Animesh>] Yes I saw that and I will pull it in for the new RC build anyway. Do 
you have fix for CLOUDSTACK-4423? Did you check my comment on it



I do not have a fix yet, but my hope is that it is already fixed since 
it seems to be a QCOW2 <> RAW conversion problem which under the hood 
uses the same code as downloading a volume.


My plan was to check it tomorrow since I didn't have time yet to 
investigate.


Wido

Re: [DISCUSS] Gearing up for an official CloudMonkey independent release

[David Nalley]

IMO: JFDI

On Mon, Aug 26, 2013 at 1:27 PM, Chip Childers
 wrote:
> Hi all,
>
> I'm looking at what it's going to take to get CloudMonkey out as an
> official release.  Here's what I believe needs to be done:
>
> 1) Legal doc check (I think we're good here, since I just added the
> NOTICE file)
>
> 2) Release process document
>
> 3) Add an initial pre-cache file to the repo itself.  I want to do this,
> so that it doesn't require you to have a running 4.1+ ACS install in
> order to do a CloudMonkey build.
>
> 4) Kick out a release
>
> 5) Update the cloudstack.apache.org website to provide links to the
> cloudmonkey component's source repo and distinct artifacts.
>
> Once we get this first release out, we need to probably stop publishing
> to pypi outside of the *official release* process.  That being said,
> it'll be easier to release CloudMonkey independently.
>
> Thoughts, comments, flames?
>
> -chip

Re: 4.3 Code Freeze

[Will Stevens]

Thank you.  :)

ws


On Mon, Aug 26, 2013 at 4:03 PM, Animesh Chaturvedi <
animesh.chaturv...@citrix.com> wrote:

> Last week of october
>
> > -Original Message-
> > From: williamstev...@gmail.com [mailto:williamstev...@gmail.com] On
> > Behalf Of Will Stevens
> > Sent: Monday, August 26, 2013 12:28 PM
> > To: dev@cloudstack.apache.org
> > Subject: 4.3 Code Freeze
> >
> > Can someone please let me know what the code freeze date for 4.3 is?
> >
> > Thanks,
> >
> > Will
>

Please cherry pick 4 doc fixes

[Jessica Tomechak]

>From 4.2-forward

(1)

*Commit:* ecbd9ed93d71284c9764c191fd94c5f9cf63dd6d [ecbd9ed]

*Parents:* 9a6f2de70e 

*Author:* Jessica 

*Date:* August 26, 2013 1:47:41 PM PDT

*Commit Date:* August 26, 2013 1:49:42 PM PDT

*Labels:* HEAD origin/4.2-forward 4.2-forward


CLOUDSTACK-4334. Documentation for how to write an object store plugin.



(2)


*Commit:* c2cde0b463916f4be3316dd4a8572fa96392b1d5 [c2cde0b]

*Parents:* f814bd 

*Author:* Jessica 

*Date:* August 26, 2013 12:44:56 PM PDT


CLOUDSTACK-4334. Documentation for object store.


(3)

*Commit:* 9a6f2de70e8dc9252913a723b03a1cadd22c80dd [9a6f2de]

*Parents:* 40443bb5ea 

*Author:* Jessica 

*Date:* August 26, 2013 12:48:36 PM PDT


DOC. Move misplaced paragraph from Secondary Storage section to Primary
Storage section.



(4)


*Commit:* 48874c197eb466564772fed1c6b8cd3e92a9e223 [48874c1]

*Parents:* e5b7dc55ba 

*Author:* Jessica 

*Date:* August 26, 2013 12:46:31 PM PDT


DOC. Fix typo in Basic Zone Configuration.

Re: [VOTE] Apache Cloudstack 4.2.0

[Chip Childers]

On Mon, Aug 26, 2013 at 08:13:34PM +, Animesh Chaturvedi wrote:
> [Animesh>] I will create a new RC and start a new VOTE. If this is the only 
> change (mostly textual) does the VOTE has to be open for still 72 hours?

Yes.

It's important to note that voting is a method of community
engagement.  The act of the release is the output of engaging as a
community to jointly review the proposed release artifacts.  72 hours is
*at least*, and (as noted earlier) really should be 3 working days.

-chip

Re: [DISCUSS] Gearing up for an official CloudMonkey independent release

[Chip Childers]

On Mon, Aug 26, 2013 at 08:31:33PM +, Chiradeep Vittal wrote:
> Does the release require voting?

Absolutely.  If it's a release from the project, it's just like any
other release.

> 
> On 8/26/13 10:27 AM, "Chip Childers"  wrote:
> 
> >Hi all,
> >
> >I'm looking at what it's going to take to get CloudMonkey out as an
> >official release.  Here's what I believe needs to be done:
> >
> >1) Legal doc check (I think we're good here, since I just added the
> >NOTICE file)
> >
> >2) Release process document
> >
> >3) Add an initial pre-cache file to the repo itself.  I want to do this,
> >so that it doesn't require you to have a running 4.1+ ACS install in
> >order to do a CloudMonkey build.
> >
> >4) Kick out a release
> >
> >5) Update the cloudstack.apache.org website to provide links to the
> >cloudmonkey component's source repo and distinct artifacts.
> >
> >Once we get this first release out, we need to probably stop publishing
> >to pypi outside of the *official release* process.  That being said,
> >it'll be easier to release CloudMonkey independently.
> >
> >Thoughts, comments, flames?
> >
> >-chip
> 
> 

Doc] Please review: 3rd party storage plugin architecture doc

[Jessica Tomechak]

Hi,
New doc on 3rd party object store plugin architecture is ready for review.
You can view the updated text at the link below. This is checked in to both
master and 4.2-forward branch.

Please provide your feedback.

Diffs:
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ecbd9ed
and
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c2cde0b

Bug:
https://issues.apache.org/jira/browse/CLOUDSTACK-4334

Regards,
Jessica T.

RE: [VOTE] Apache Cloudstack 4.2.0

[Animesh Chaturvedi]

> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Monday, August 26, 2013 2:05 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> 
> On Mon, Aug 26, 2013 at 08:13:34PM +, Animesh Chaturvedi wrote:
> > [Animesh>] I will create a new RC and start a new VOTE. If this is the
> only change (mostly textual) does the VOTE has to be open for still 72
> hours?
> 
> Yes.
> 
> It's important to note that voting is a method of community engagement.
> The act of the release is the output of engaging as a community to
> jointly review the proposed release artifacts.  72 hours is *at least*,
> and (as noted earlier) really should be 3 working days.
> 
> -chip
[Animesh>] Well I wanted to clarify for the type of change, I will pick up few 
other fixes anyway and start a new VOTE shortly

Re: [VOTE] Apache Cloudstack 4.2.0

[Mike Tutkowski]

No problem - I'll let you know when it's there.


On Mon, Aug 26, 2013 at 2:54 PM, Animesh Chaturvedi <
animesh.chaturv...@citrix.com> wrote:

>
>
> > -Original Message-
> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> > Sent: Monday, August 26, 2013 1:48 PM
> > To: dev@cloudstack.apache.org
> > Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> >
> > Hi Animesh,
> >
> > It is related to adding an iSCSI target to ESX(i).
> >
> > The 4.2 code assumes you will want to use Mutual CHAP. This fix allows
> > the user to not have to use Mutual CHAP.
> >
> > It's only a small number of changes, pretty low risk, and should only
> > impact the SolidFire plug-in as no other plug-in code has been written
> > to date that uses the logic in the VMware code that I would need to
> > modify.
> >
> > I've written and tested the code, as well.
> >
> > Talk to you later,
> >
> [Animesh>] Can you put your fix in 4.2-forward ASAP
>



-- 
*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: [VOTE] Apache Cloudstack 4.2.0

[Animesh Chaturvedi]

> -Original Message-
> From: Wido den Hollander [mailto:w...@widodh.nl]
> Sent: Monday, August 26, 2013 1:58 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> 
> 
> 
> On 08/26/2013 10:50 PM, Animesh Chaturvedi wrote:
> >
> 
> >>> [Animesh>] Wido I am going to cut another RC to pick up licensing
> >> fixes from Chip. Do you have a fix for the issue reported? IMO
> >> looking through that issue it can be covered in 4.2.1.
> >>>
> >>
> >> I also sent a cherry-pick request last week for a fix which is in
> >> 4.2-forward: 829dbaccb470431244f814a9d95fc7823a3e0201
> >>
> >> It isn't in 4.2 yet. It fixes a different RBD issue.
> >>
> >> Wido
> >>
> > [Animesh>] Yes I saw that and I will pull it in for the new RC build
> > anyway. Do you have fix for CLOUDSTACK-4423? Did you check my comment
> > on it
> >
> 
> I do not have a fix yet, but my hope is that it is already fixed since
> it seems to be a QCOW2 <> RAW conversion problem which under the hood
> uses the same code as downloading a volume.
> 
> My plan was to check it tomorrow since I didn't have time yet to
> investigate.
> 
> Wido
> 
> >
[Animesh>] Ok I will create a new RC build with your other fix and keeps finger 
crossed that this is not an issue. If it is still an issue can you fix it for 
4.2.1?

Re: [VOTE] Apache Cloudstack 4.2.0

[Mike Tutkowski]

OK, Animesh.

My changes are in 4.2-forward now.

Thanks!


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

> No problem - I'll let you know when it's there.
>
>
> On Mon, Aug 26, 2013 at 2:54 PM, Animesh Chaturvedi <
> animesh.chaturv...@citrix.com> wrote:
>
>>
>>
>> > -Original Message-
>> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>> > Sent: Monday, August 26, 2013 1:48 PM
>> > To: dev@cloudstack.apache.org
>> > Subject: Re: [VOTE] Apache Cloudstack 4.2.0
>> >
>> > Hi Animesh,
>> >
>> > It is related to adding an iSCSI target to ESX(i).
>> >
>> > The 4.2 code assumes you will want to use Mutual CHAP. This fix allows
>> > the user to not have to use Mutual CHAP.
>> >
>> > It's only a small number of changes, pretty low risk, and should only
>> > impact the SolidFire plug-in as no other plug-in code has been written
>> > to date that uses the logic in the VMware code that I would need to
>> > modify.
>> >
>> > I've written and tested the code, as well.
>> >
>> > Talk to you later,
>> >
>> [Animesh>] Can you put your fix in 4.2-forward ASAP
>>
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the 
> cloud
> *™*
>



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

[Doc] Please review: Zone-wide primary storage doc

[Jessica Tomechak]

Hi,
New doc on zone-wide primary storage is ready for review. You can view the
updated text at the links below. Or -- since there were several changes --
simply read the files docs/en-US/primary-storage-add.xml and
about-primary-storage.xml.

Please provide your feedback.

Diffs:
By Jessica T (in master and 4.2-forward):
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=48e9c01
(sorry, committed along with doc for another feature by mistake)

By Mike T (in master and 4.2):
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9f4889a

Bugs:
By Jessica T:
https://issues.apache.org/jira/browse/CLOUDSTACK-864

By Mike T:
https://issues.apache.org/jira/browse/CLOUDSTACK-3291

Regards,
Jessica T.

[Doc] Please review: Mapping VMware Datacenter to Zone doc

[Jessica Tomechak]

Hi,
New doc on VMware Datacenters and zones is ready for review. You can view
the updated text at the link below. This is checked in to both master and
4.2-forward.

Please provide your feedback. Since the doc is very short, I have just
placed the text right in the Bug.

Bug:
https://issues.apache.org/jira/browse/CLOUDSTACK-3390

Diff:
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3dfb88e

Regards,
Jessica T.

Re: [Doc] Please review: Mapping VMware Datacenter to Zone doc

[Jessica Tomechak]

+cc Sateesh


On Mon, Aug 26, 2013 at 2:56 PM, Jessica Tomechak <
jessica.tomec...@gmail.com> wrote:

> Hi,
> New doc on VMware Datacenters and zones is ready for review. You can view
> the updated text at the link below. This is checked in to both master and
> 4.2-forward.
>
> Please provide your feedback. Since the doc is very short, I have just
> placed the text right in the Bug.
>
> Bug:
> https://issues.apache.org/jira/browse/CLOUDSTACK-3390
>
> Diff:
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3dfb88e
>
> Regards,
> Jessica T.
>

[ACS42]Cherry-pick several commits

[Min Chen]

Hi Animesh,

Here are several commits that need to cherry pick to 4.2:

f814bdfd404749bd1cbf4209fedc9a9d0f22  CLOUDSTACK-4468:template created from 
snapshot is destroyed...
f501c7bbe1ba3fca4071daa520230a34323900cb CLOUDSTACK-4481:API: listEventTypes 
returns nothing...
c6928f2f5390420ea3f578ff89885aff3caff98e CLOUDSTACK-4480: Handle DestroyCommand 
in VmwareResource...
bb78cb94afe95db2a3169c170c180c6da5f1b4e7 CLOUDSTACK-4478:API: ListSwiftsCmd API 
missing.

Thanks
-min

RE: [VOTE] Apache Cloudstack 4.2.0

[Animesh Chaturvedi]

Mike with your commit 6a2f15f94ae74b563a2d4df6da38e7f6ff44c8ac

I see a few changes to 

Ui\scripts\ui-custom\zoneWizard.js
Ui\scripts\zoneWizard.js

Are they needed for your CHAP changes? These seems unrelated to me.


Animesh

> -Original Message-
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: Monday, August 26, 2013 2:44 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> 
> OK, Animesh.
> 
> My changes are in 4.2-forward now.
> 
> Thanks!
> 
> 
> On Mon, Aug 26, 2013 at 3:18 PM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
> 
> > No problem - I'll let you know when it's there.
> >
> >
> > On Mon, Aug 26, 2013 at 2:54 PM, Animesh Chaturvedi <
> > animesh.chaturv...@citrix.com> wrote:
> >
> >>
> >>
> >> > -Original Message-
> >> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> >> > Sent: Monday, August 26, 2013 1:48 PM
> >> > To: dev@cloudstack.apache.org
> >> > Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> >> >
> >> > Hi Animesh,
> >> >
> >> > It is related to adding an iSCSI target to ESX(i).
> >> >
> >> > The 4.2 code assumes you will want to use Mutual CHAP. This fix
> >> > allows the user to not have to use Mutual CHAP.
> >> >
> >> > It's only a small number of changes, pretty low risk, and should
> >> > only impact the SolidFire plug-in as no other plug-in code has been
> >> > written to date that uses the logic in the VMware code that I would
> >> > need to modify.
> >> >
> >> > I've written and tested the code, as well.
> >> >
> >> > Talk to you later,
> >> >
> >> [Animesh>] Can you put your fix in 4.2-forward ASAP
> >>
> >
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkow...@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the
> > cloud
> > *(tm)*
> >
> 
> 
> 
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud
> *(tm)*

Re: [VOTE] Apache Cloudstack 4.2.0

[Mike Tutkowski]

I don't understand how those got in there.

I think they were merged into my code from Jessica's earlier checkin.

They are not related to my fix.


On Mon, Aug 26, 2013 at 4:41 PM, Animesh Chaturvedi <
animesh.chaturv...@citrix.com> wrote:

> Mike with your commit 6a2f15f94ae74b563a2d4df6da38e7f6ff44c8ac
>
> I see a few changes to
>
> Ui\scripts\ui-custom\zoneWizard.js
> Ui\scripts\zoneWizard.js
>
> Are they needed for your CHAP changes? These seems unrelated to me.
>
>
> Animesh
>
> > -Original Message-
> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> > Sent: Monday, August 26, 2013 2:44 PM
> > To: dev@cloudstack.apache.org
> > Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> >
> > OK, Animesh.
> >
> > My changes are in 4.2-forward now.
> >
> > Thanks!
> >
> >
> > On Mon, Aug 26, 2013 at 3:18 PM, Mike Tutkowski <
> > mike.tutkow...@solidfire.com> wrote:
> >
> > > No problem - I'll let you know when it's there.
> > >
> > >
> > > On Mon, Aug 26, 2013 at 2:54 PM, Animesh Chaturvedi <
> > > animesh.chaturv...@citrix.com> wrote:
> > >
> > >>
> > >>
> > >> > -Original Message-
> > >> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> > >> > Sent: Monday, August 26, 2013 1:48 PM
> > >> > To: dev@cloudstack.apache.org
> > >> > Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> > >> >
> > >> > Hi Animesh,
> > >> >
> > >> > It is related to adding an iSCSI target to ESX(i).
> > >> >
> > >> > The 4.2 code assumes you will want to use Mutual CHAP. This fix
> > >> > allows the user to not have to use Mutual CHAP.
> > >> >
> > >> > It's only a small number of changes, pretty low risk, and should
> > >> > only impact the SolidFire plug-in as no other plug-in code has been
> > >> > written to date that uses the logic in the VMware code that I would
> > >> > need to modify.
> > >> >
> > >> > I've written and tested the code, as well.
> > >> >
> > >> > Talk to you later,
> > >> >
> > >> [Animesh>] Can you put your fix in 4.2-forward ASAP
> > >>
> > >
> > >
> > >
> > > --
> > > *Mike Tutkowski*
> > > *Senior CloudStack Developer, SolidFire Inc.*
> > > e: mike.tutkow...@solidfire.com
> > > o: 303.746.7302
> > > Advancing the way the world uses the
> > > cloud
> > > *(tm)*
> > >
> >
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkow...@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the
> > cloud
> > *(tm)*
>



-- 
*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: Review Request 13804: CLOUDSTACK-4495: systemVM template URL is pointing to old template location in upgrade file.

[ASF Subversion and Git Services]

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


Commit 208507a42a4db252dc3d7cf299c146315423a071 in branch 
refs/heads/4.2-forward from Sanjay Tripathi
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=208507a ]

CLOUDSTACK-4495: systemVM template URL is pointing to old template location in 
upgrade file.

SystemVM template URL for XenServer hypervisor is pointing to old template 
location in the Upgrade410to420.java  file.


- ASF Subversion and Git Services


On Aug. 26, 2013, 8:02 a.m., Sanjay Tripathi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/13804/
> ---
> 
> (Updated Aug. 26, 2013, 8:02 a.m.)
> 
> 
> Review request for cloudstack, Abhinandan Prateek and Devdeep Singh.
> 
> 
> Bugs: CLOUDSTACK-4495
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> SystemVM template URL for XenServer hypervisor is pointing to old template 
> location in the Upgrade410to420.java  file.
> 
> https://issues.apache.org/jira/browse/CLOUDSTACK-4495
> 
> 
> Diffs
> -
> 
>   engine/schema/src/com/cloud/upgrade/dao/Upgrade410to420.java c3276ef 
> 
> Diff: https://reviews.apache.org/r/13804/diff/
> 
> 
> Testing
> ---
> 
> Tests:
> 1. Setup CloudStack environment,
> 2. Check the systemVM template URL in vm_template table (it should point to 
> the new location).
> 
> 
> Thanks,
> 
> Sanjay Tripathi
> 
>

Re: Review Request 13804: CLOUDSTACK-4495: systemVM template URL is pointing to old template location in upgrade file.

[Prachi Damle]

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

Ship it!


Looks correct. Applied using: 
Commit hash:208507a42a4db252dc3d7cf299c146315423a071

Contained in branches: 4.2-forward
Contained in no tag

- Prachi Damle


On Aug. 26, 2013, 8:02 a.m., Sanjay Tripathi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/13804/
> ---
> 
> (Updated Aug. 26, 2013, 8:02 a.m.)
> 
> 
> Review request for cloudstack, Abhinandan Prateek and Devdeep Singh.
> 
> 
> Bugs: CLOUDSTACK-4495
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> SystemVM template URL for XenServer hypervisor is pointing to old template 
> location in the Upgrade410to420.java  file.
> 
> https://issues.apache.org/jira/browse/CLOUDSTACK-4495
> 
> 
> Diffs
> -
> 
>   engine/schema/src/com/cloud/upgrade/dao/Upgrade410to420.java c3276ef 
> 
> Diff: https://reviews.apache.org/r/13804/diff/
> 
> 
> Testing
> ---
> 
> Tests:
> 1. Setup CloudStack environment,
> 2. Check the systemVM template URL in vm_template table (it should point to 
> the new location).
> 
> 
> Thanks,
> 
> Sanjay Tripathi
> 
>

[BUG] vSphere - VMs are force powered off by ACS

[Musayev, Ilya]

I've been trying to figure out an issue where some of my VMs will go offline if 
I restart cloudstack management service.

After digging for a bit, I found a culprit.

If you don't have vmware tools installed, ACS checks the state of vm (I.e. 
running or stopped, as well as agentState)

If VM state is running and agentState - is not (I'm under assumption vmware 
tools is agentState) then ACS powers off the guest - when ACS management server 
is restarted.

So I'm trying to figure out if this is by design or a bug?

In my case, fedora 17 does not have official vmware tools and neither do some 
other Ubuntu distros. I can try to get openvmtools to work, but I'm thinking - 
why would ACS care?

RE: [GSoC] Branch Merge Request LdapPlugin and Master

[Musayev, Ilya]

Chip,

Will do.

Regards
Ilya

> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Monday, August 26, 2013 11:51 AM
> To: dev@cloudstack.apache.org
> Subject: Re: [GSoC] Branch Merge Request LdapPlugin and Master
> 
> Ilya,
> 
> Can you handle doing his merge request into master?
> 
> -chip
> 
> On Mon, Aug 26, 2013 at 03:23:30PM +, Musayev, Ilya wrote:
> > Ian
> >
> > I want  to leave you with 1 last thought, this plugin will be used on daily
> basis by hundreds (if not thousands) in the near future - all thanks to you 
> and
> GSoC.
> >
> > Thank you for your contribution. It is greatly appreciated!
> >
> > Regards
> > ilya
> >
> > PS: If you can complete the part that was out of scope in the near future
> when time allows, it will help - tremendously.
> >
> >
> > > -Original Message-
> > > From: Ian Duffy [mailto:i...@ianduffy.ie]
> > > Sent: Friday, August 23, 2013 11:26 AM
> > > To: CloudStack Dev
> > > Subject: [GSoC] Branch Merge Request LdapPlugin and Master
> > >
> > > Hi Guys,
> > >
> > > The work in the LdapPlugin branch is now complete in accordance to
> > > the proposal I submitted for the GSoC program outlining what would
> > > be undertaken.
> > >
> > > I have uploaded a revised proposal to cover some of the small
> discrepancies.
> > > http://ianduffy.ie/cloudstack/cloudstack-ldap-revised.pdf
> > >
> > > The branch is in a working state, all new additions have been unit
> > > tested and documented accordingly.
> > >
> > > If somebody could code review it and merge it to master that would
> > > be great.
> > >
> > > As mentioned in a previous email on the list something needs to be
> > > implemented to search LDAP on schedule to find deleted users and
> > > revoke their keys as necessary. I have been talking to Ilya and Alex
> > > about this. I will look into doing this over the next month(Time dedicate
> won't be as great).
> > >
> > > Thanks to everybody for making this opportunity possible! It has
> > > been great working with you guys and the GSoC programme.
> > > Ian

[ACS42] Cherry pick CLOUDSTACK-4495

[Prachi Damle]

Hi Animesh,

Can you cherry-pick the following patch to 4.2: 
https://reviews.apache.org/r/13804/

Commit hash:   208507a42a4db252dc3d7cf299c146315423a071
Contained in branches: 4.2-forward

Thanks,
Prachi

[ACS42]Cherry pick CLOUDSTACK-3405

[Min Chen]

Hi Animesh,

Can you cherry-pick commit 5a11fe77bae1966c986e541e484ae3d56485d78f for 
CLOUDSTACK-3405? The commit is in 4.2-forward branch.

Thanks
-min

RE: [VOTE] Apache Cloudstack 4.2.0

[Animesh Chaturvedi]

Mike the commit message shows it is a merge "Merge remote-tracking branch 
'upstream/4.2-forward' into 4.2-forward"

Adding Brian and Jessica to the thread.

From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
Sent: Monday, August 26, 2013 3:45 PM
To: Animesh Chaturvedi
Cc: dev@cloudstack.apache.org; Brian Federle
Subject: Re: [VOTE] Apache Cloudstack 4.2.0

I don't understand how those got in there.

I think they were merged into my code from Jessica's earlier checkin.

They are not related to my fix.

On Mon, Aug 26, 2013 at 4:41 PM, Animesh Chaturvedi 
mailto:animesh.chaturv...@citrix.com>> wrote:
Mike with your commit 6a2f15f94ae74b563a2d4df6da38e7f6ff44c8ac

I see a few changes to

Ui\scripts\ui-custom\zoneWizard.js
Ui\scripts\zoneWizard.js

Are they needed for your CHAP changes? These seems unrelated to me.


Animesh

> -Original Message-
> From: Mike Tutkowski 
> [mailto:mike.tutkow...@solidfire.com]
> Sent: Monday, August 26, 2013 2:44 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [VOTE] Apache Cloudstack 4.2.0
>
> OK, Animesh.
>
> My changes are in 4.2-forward now.
>
> Thanks!
>
>
> On Mon, Aug 26, 2013 at 3:18 PM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
> > No problem - I'll let you know when it's there.
> >
> >
> > On Mon, Aug 26, 2013 at 2:54 PM, Animesh Chaturvedi <
> > animesh.chaturv...@citrix.com> wrote:
> >
> >>
> >>
> >> > -Original Message-
> >> > From: Mike Tutkowski 
> >> > [mailto:mike.tutkow...@solidfire.com]
> >> > Sent: Monday, August 26, 2013 1:48 PM
> >> > To: dev@cloudstack.apache.org
> >> > Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> >> >
> >> > Hi Animesh,
> >> >
> >> > It is related to adding an iSCSI target to ESX(i).
> >> >
> >> > The 4.2 code assumes you will want to use Mutual CHAP. This fix
> >> > allows the user to not have to use Mutual CHAP.
> >> >
> >> > It's only a small number of changes, pretty low risk, and should
> >> > only impact the SolidFire plug-in as no other plug-in code has been
> >> > written to date that uses the logic in the VMware code that I would
> >> > need to modify.
> >> >
> >> > I've written and tested the code, as well.
> >> >
> >> > Talk to you later,
> >> >
> >> [Animesh>] Can you put your fix in 4.2-forward ASAP
> >>
> >
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkow...@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the
> > cloud
> > *(tm)*
> >
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud
> *(tm)*



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

Re: [VOTE] Apache Cloudstack 4.2.0

[Mike Tutkowski]

Yeah, that is interesting.

My changes are only these:

https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=13a415fe8a3917a49dae5a1f3998f5ae78a61da3


On Mon, Aug 26, 2013 at 4:55 PM, Animesh Chaturvedi <
animesh.chaturv...@citrix.com> wrote:

>  Mike the commit message shows it is a merge “Merge remote-tracking
> branch 'upstream/4.2-forward' into 4.2-forward”
>
> ** **
>
> Adding Brian and Jessica to the thread. 
>
> ** **
>
> *From:* Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> *Sent:* Monday, August 26, 2013 3:45 PM
> *To:* Animesh Chaturvedi
> *Cc:* dev@cloudstack.apache.org; Brian Federle
>
> *Subject:* Re: [VOTE] Apache Cloudstack 4.2.0
>
>  ** **
>
> I don't understand how those got in there.
>
> ** **
>
> I think they were merged into my code from Jessica's earlier checkin.
>
> ** **
>
> They are not related to my fix.
>
> ** **
>
> On Mon, Aug 26, 2013 at 4:41 PM, Animesh Chaturvedi <
> animesh.chaturv...@citrix.com> wrote:
>
> Mike with your commit 6a2f15f94ae74b563a2d4df6da38e7f6ff44c8ac
>
> I see a few changes to
>
> Ui\scripts\ui-custom\zoneWizard.js
> Ui\scripts\zoneWizard.js
>
> Are they needed for your CHAP changes? These seems unrelated to me.
>
>
> Animesh
>
>
> > -Original Message-
> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>
> > Sent: Monday, August 26, 2013 2:44 PM
> > To: dev@cloudstack.apache.org
> > Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> >
> > OK, Animesh.
> >
> > My changes are in 4.2-forward now.
> >
> > Thanks!
> >
> >
> > On Mon, Aug 26, 2013 at 3:18 PM, Mike Tutkowski <
> > mike.tutkow...@solidfire.com> wrote:
> >
> > > No problem - I'll let you know when it's there.
> > >
> > >
> > > On Mon, Aug 26, 2013 at 2:54 PM, Animesh Chaturvedi <
> > > animesh.chaturv...@citrix.com> wrote:
> > >
> > >>
> > >>
> > >> > -Original Message-
> > >> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> > >> > Sent: Monday, August 26, 2013 1:48 PM
> > >> > To: dev@cloudstack.apache.org
> > >> > Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> > >> >
> > >> > Hi Animesh,
> > >> >
> > >> > It is related to adding an iSCSI target to ESX(i).
> > >> >
> > >> > The 4.2 code assumes you will want to use Mutual CHAP. This fix
> > >> > allows the user to not have to use Mutual CHAP.
> > >> >
> > >> > It's only a small number of changes, pretty low risk, and should
> > >> > only impact the SolidFire plug-in as no other plug-in code has been
> > >> > written to date that uses the logic in the VMware code that I would
> > >> > need to modify.
> > >> >
> > >> > I've written and tested the code, as well.
> > >> >
> > >> > Talk to you later,
> > >> >
> > >> [Animesh>] Can you put your fix in 4.2-forward ASAP
> > >>
> > >
> > >
> > >
> > > --
>
> > > *Mike Tutkowski*
> > > *Senior CloudStack Developer, SolidFire Inc.*
>
> > > e: mike.tutkow...@solidfire.com
> > > o: 303.746.7302
> > > Advancing the way the world uses the
>
> > > cloud
> > > *(tm)*
>
> > >
> >
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
>
> > e: mike.tutkow...@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the
>
> > cloud
> > *(tm)*
>
>
>
> 
>
> ** **
>
> --
> *Mike Tutkowski*
>
> *Senior CloudStack Developer, SolidFire Inc.*
>
> e: mike.tutkow...@solidfire.com
>
> o: 303.746.7302
>
> Advancing the way the world uses the 
> cloud
> *™*
>



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

Re: [VOTE] Apache Cloudstack 4.2.0

[Mike Tutkowski]

I probably should have done a rebase instead of a merge.

I think her changes were merged into my local 4.2-forward branch and then I
pushed my branch.


On Mon, Aug 26, 2013 at 4:56 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> Yeah, that is interesting.
>
> My changes are only these:
>
>
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=13a415fe8a3917a49dae5a1f3998f5ae78a61da3
>
>
> On Mon, Aug 26, 2013 at 4:55 PM, Animesh Chaturvedi <
> animesh.chaturv...@citrix.com> wrote:
>
>>  Mike the commit message shows it is a merge “Merge remote-tracking
>> branch 'upstream/4.2-forward' into 4.2-forward”
>>
>> ** **
>>
>> Adding Brian and Jessica to the thread. 
>>
>> ** **
>>
>> *From:* Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>> *Sent:* Monday, August 26, 2013 3:45 PM
>> *To:* Animesh Chaturvedi
>> *Cc:* dev@cloudstack.apache.org; Brian Federle
>>
>> *Subject:* Re: [VOTE] Apache Cloudstack 4.2.0
>>
>>  ** **
>>
>> I don't understand how those got in there.
>>
>> ** **
>>
>> I think they were merged into my code from Jessica's earlier checkin.
>>
>> ** **
>>
>> They are not related to my fix.
>>
>> ** **
>>
>> On Mon, Aug 26, 2013 at 4:41 PM, Animesh Chaturvedi <
>> animesh.chaturv...@citrix.com> wrote:
>>
>> Mike with your commit 6a2f15f94ae74b563a2d4df6da38e7f6ff44c8ac
>>
>> I see a few changes to
>>
>> Ui\scripts\ui-custom\zoneWizard.js
>> Ui\scripts\zoneWizard.js
>>
>> Are they needed for your CHAP changes? These seems unrelated to me.
>>
>>
>> Animesh
>>
>>
>> > -Original Message-
>> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>>
>> > Sent: Monday, August 26, 2013 2:44 PM
>> > To: dev@cloudstack.apache.org
>> > Subject: Re: [VOTE] Apache Cloudstack 4.2.0
>> >
>> > OK, Animesh.
>> >
>> > My changes are in 4.2-forward now.
>> >
>> > Thanks!
>> >
>> >
>> > On Mon, Aug 26, 2013 at 3:18 PM, Mike Tutkowski <
>> > mike.tutkow...@solidfire.com> wrote:
>> >
>> > > No problem - I'll let you know when it's there.
>> > >
>> > >
>> > > On Mon, Aug 26, 2013 at 2:54 PM, Animesh Chaturvedi <
>> > > animesh.chaturv...@citrix.com> wrote:
>> > >
>> > >>
>> > >>
>> > >> > -Original Message-
>> > >> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>> > >> > Sent: Monday, August 26, 2013 1:48 PM
>> > >> > To: dev@cloudstack.apache.org
>> > >> > Subject: Re: [VOTE] Apache Cloudstack 4.2.0
>> > >> >
>> > >> > Hi Animesh,
>> > >> >
>> > >> > It is related to adding an iSCSI target to ESX(i).
>> > >> >
>> > >> > The 4.2 code assumes you will want to use Mutual CHAP. This fix
>> > >> > allows the user to not have to use Mutual CHAP.
>> > >> >
>> > >> > It's only a small number of changes, pretty low risk, and should
>> > >> > only impact the SolidFire plug-in as no other plug-in code has been
>> > >> > written to date that uses the logic in the VMware code that I would
>> > >> > need to modify.
>> > >> >
>> > >> > I've written and tested the code, as well.
>> > >> >
>> > >> > Talk to you later,
>> > >> >
>> > >> [Animesh>] Can you put your fix in 4.2-forward ASAP
>> > >>
>> > >
>> > >
>> > >
>> > > --
>>
>> > > *Mike Tutkowski*
>> > > *Senior CloudStack Developer, SolidFire Inc.*
>>
>> > > e: mike.tutkow...@solidfire.com
>> > > o: 303.746.7302
>> > > Advancing the way the world uses the
>>
>> > > cloud
>> > > *(tm)*
>>
>> > >
>> >
>> >
>> >
>> > --
>> > *Mike Tutkowski*
>> > *Senior CloudStack Developer, SolidFire Inc.*
>>
>> > e: mike.tutkow...@solidfire.com
>> > o: 303.746.7302
>> > Advancing the way the world uses the
>>
>> > cloud
>> > *(tm)*
>>
>>
>>
>> 
>>
>> ** **
>>
>> --
>> *Mike Tutkowski*
>>
>> *Senior CloudStack Developer, SolidFire Inc.*
>>
>> e: mike.tutkow...@solidfire.com
>>
>> o: 303.746.7302
>>
>> Advancing the way the world uses the 
>> cloud
>> *™*
>>
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the 
> cloud
> *™*
>



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

RE: [VOTE] Apache Cloudstack 4.2.0

[Brian Federle]

Probably something just got messed up during the rebase, I see this commit 
below yours:

commit ae68c841f668768118bbff07f07060416fb16d48
Author: Jessica Wang 
Date:   Mon Aug 26 14:24:22 2013 -0700

CLOUDSTACK-4089: UI > zone wizard > hypervisor VMware > configure physical 
network > edit traffic type label > split

Which modifies system.js -- probably committed at the same time as you.

I only think this because I've definitely screwed stuff up in git myself in the 
past when I forget to rebase :D

-Brian

From: Animesh Chaturvedi
Sent: Monday, August 26, 2013 3:56 PM
To: Mike Tutkowski
Cc: dev@cloudstack.apache.org; Brian Federle; Jessica Wang
Subject: RE: [VOTE] Apache Cloudstack 4.2.0

Mike the commit message shows it is a merge "Merge remote-tracking branch 
'upstream/4.2-forward' into 4.2-forward"

Adding Brian and Jessica to the thread.

From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
Sent: Monday, August 26, 2013 3:45 PM
To: Animesh Chaturvedi
Cc: dev@cloudstack.apache.org; Brian Federle
Subject: Re: [VOTE] Apache Cloudstack 4.2.0

I don't understand how those got in there.

I think they were merged into my code from Jessica's earlier checkin.

They are not related to my fix.

On Mon, Aug 26, 2013 at 4:41 PM, Animesh Chaturvedi 
mailto:animesh.chaturv...@citrix.com>> wrote:
Mike with your commit 6a2f15f94ae74b563a2d4df6da38e7f6ff44c8ac

I see a few changes to

Ui\scripts\ui-custom\zoneWizard.js
Ui\scripts\zoneWizard.js

Are they needed for your CHAP changes? These seems unrelated to me.


Animesh

> -Original Message-
> From: Mike Tutkowski 
> [mailto:mike.tutkow...@solidfire.com]
> Sent: Monday, August 26, 2013 2:44 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [VOTE] Apache Cloudstack 4.2.0
>
> OK, Animesh.
>
> My changes are in 4.2-forward now.
>
> Thanks!
>
>
> On Mon, Aug 26, 2013 at 3:18 PM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
> > No problem - I'll let you know when it's there.
> >
> >
> > On Mon, Aug 26, 2013 at 2:54 PM, Animesh Chaturvedi <
> > animesh.chaturv...@citrix.com> wrote:
> >
> >>
> >>
> >> > -Original Message-
> >> > From: Mike Tutkowski 
> >> > [mailto:mike.tutkow...@solidfire.com]
> >> > Sent: Monday, August 26, 2013 1:48 PM
> >> > To: dev@cloudstack.apache.org
> >> > Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> >> >
> >> > Hi Animesh,
> >> >
> >> > It is related to adding an iSCSI target to ESX(i).
> >> >
> >> > The 4.2 code assumes you will want to use Mutual CHAP. This fix
> >> > allows the user to not have to use Mutual CHAP.
> >> >
> >> > It's only a small number of changes, pretty low risk, and should
> >> > only impact the SolidFire plug-in as no other plug-in code has been
> >> > written to date that uses the logic in the VMware code that I would
> >> > need to modify.
> >> >
> >> > I've written and tested the code, as well.
> >> >
> >> > Talk to you later,
> >> >
> >> [Animesh>] Can you put your fix in 4.2-forward ASAP
> >>
> >
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkow...@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the
> > cloud
> > *(tm)*
> >
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud
> *(tm)*



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

Re: [VOTE] Apache Cloudstack 4.2.0

[Mike Tutkowski]

Yeah, I agree. :) I think I merged instead of rebased.


On Mon, Aug 26, 2013 at 5:00 PM, Brian Federle wrote:

>  Probably something just got messed up during the rebase, I see this
> commit below yours:
>
> ** **
>
> commit ae68c841f668768118bbff07f07060416fb16d48
>
> Author: Jessica Wang 
>
> Date:   Mon Aug 26 14:24:22 2013 -0700
>
> ** **
>
> CLOUDSTACK-4089: UI > zone wizard > hypervisor VMware > configure
> physical network > edit traffic type label > split
>
> ** **
>
> Which modifies system.js -- probably committed at the same time as you.***
> *
>
> ** **
>
> I only think this because I’ve definitely screwed stuff up in git myself
> in the past when I forget to rebase :D
>
> ** **
>
> -Brian
>
> ** **
>
> *From:* Animesh Chaturvedi
> *Sent:* Monday, August 26, 2013 3:56 PM
> *To:* Mike Tutkowski
> *Cc:* dev@cloudstack.apache.org; Brian Federle; Jessica Wang
> *Subject:* RE: [VOTE] Apache Cloudstack 4.2.0
>
> ** **
>
> Mike the commit message shows it is a merge “Merge remote-tracking branch
> 'upstream/4.2-forward' into 4.2-forward”
>
> ** **
>
> Adding Brian and Jessica to the thread. 
>
> ** **
>
> *From:* Mike Tutkowski 
> [mailto:mike.tutkow...@solidfire.com]
>
> *Sent:* Monday, August 26, 2013 3:45 PM
> *To:* Animesh Chaturvedi
> *Cc:* dev@cloudstack.apache.org; Brian Federle
> *Subject:* Re: [VOTE] Apache Cloudstack 4.2.0
>
> ** **
>
> I don't understand how those got in there.
>
> ** **
>
> I think they were merged into my code from Jessica's earlier checkin.
>
> ** **
>
> They are not related to my fix.
>
> ** **
>
> On Mon, Aug 26, 2013 at 4:41 PM, Animesh Chaturvedi <
> animesh.chaturv...@citrix.com> wrote:
>
> Mike with your commit 6a2f15f94ae74b563a2d4df6da38e7f6ff44c8ac
>
> I see a few changes to
>
> Ui\scripts\ui-custom\zoneWizard.js
> Ui\scripts\zoneWizard.js
>
> Are they needed for your CHAP changes? These seems unrelated to me.
>
>
> Animesh
>
>
> > -Original Message-
> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
>
> > Sent: Monday, August 26, 2013 2:44 PM
> > To: dev@cloudstack.apache.org
> > Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> >
> > OK, Animesh.
> >
> > My changes are in 4.2-forward now.
> >
> > Thanks!
> >
> >
> > On Mon, Aug 26, 2013 at 3:18 PM, Mike Tutkowski <
> > mike.tutkow...@solidfire.com> wrote:
> >
> > > No problem - I'll let you know when it's there.
> > >
> > >
> > > On Mon, Aug 26, 2013 at 2:54 PM, Animesh Chaturvedi <
> > > animesh.chaturv...@citrix.com> wrote:
> > >
> > >>
> > >>
> > >> > -Original Message-
> > >> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> > >> > Sent: Monday, August 26, 2013 1:48 PM
> > >> > To: dev@cloudstack.apache.org
> > >> > Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> > >> >
> > >> > Hi Animesh,
> > >> >
> > >> > It is related to adding an iSCSI target to ESX(i).
> > >> >
> > >> > The 4.2 code assumes you will want to use Mutual CHAP. This fix
> > >> > allows the user to not have to use Mutual CHAP.
> > >> >
> > >> > It's only a small number of changes, pretty low risk, and should
> > >> > only impact the SolidFire plug-in as no other plug-in code has been
> > >> > written to date that uses the logic in the VMware code that I would
> > >> > need to modify.
> > >> >
> > >> > I've written and tested the code, as well.
> > >> >
> > >> > Talk to you later,
> > >> >
> > >> [Animesh>] Can you put your fix in 4.2-forward ASAP
> > >>
> > >
> > >
> > >
> > > --
>
> > > *Mike Tutkowski*
> > > *Senior CloudStack Developer, SolidFire Inc.*
>
> > > e: mike.tutkow...@solidfire.com
> > > o: 303.746.7302
> > > Advancing the way the world uses the
>
> > > cloud
> > > *(tm)*
>
> > >
> >
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
>
> > e: mike.tutkow...@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the
>
> > cloud
> > *(tm)*
>
>
>
> 
>
> ** **
>
> --
> *Mike Tutkowski*
>
> *Senior CloudStack Developer, SolidFire Inc.*
>
> e: mike.tutkow...@solidfire.com
>
> o: 303.746.7302
>
> Advancing the way the world uses the 
> cloud
> *™*
>



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

RE: [VOTE] Apache Cloudstack 4.2.0

[Animesh Chaturvedi]

Ok so git experts on the list I should skip Mike's merge commit and instead 
pick the one from Jessica?

Thanks
Animesh

From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
Sent: Monday, August 26, 2013 4:03 PM
To: Brian Federle
Cc: Animesh Chaturvedi; dev@cloudstack.apache.org; Jessica Wang
Subject: Re: [VOTE] Apache Cloudstack 4.2.0

Yeah, I agree. :) I think I merged instead of rebased.

On Mon, Aug 26, 2013 at 5:00 PM, Brian Federle 
mailto:brian.fede...@citrix.com>> wrote:
Probably something just got messed up during the rebase, I see this commit 
below yours:

commit ae68c841f668768118bbff07f07060416fb16d48
Author: Jessica Wang mailto:jessicaw...@apache.org>>
Date:   Mon Aug 26 14:24:22 2013 -0700

CLOUDSTACK-4089: UI > zone wizard > hypervisor VMware > configure physical 
network > edit traffic type label > split

Which modifies system.js -- probably committed at the same time as you.

I only think this because I've definitely screwed stuff up in git myself in the 
past when I forget to rebase :D

-Brian

From: Animesh Chaturvedi
Sent: Monday, August 26, 2013 3:56 PM
To: Mike Tutkowski
Cc: dev@cloudstack.apache.org; Brian Federle; 
Jessica Wang
Subject: RE: [VOTE] Apache Cloudstack 4.2.0

Mike the commit message shows it is a merge "Merge remote-tracking branch 
'upstream/4.2-forward' into 4.2-forward"

Adding Brian and Jessica to the thread.

From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
Sent: Monday, August 26, 2013 3:45 PM
To: Animesh Chaturvedi
Cc: dev@cloudstack.apache.org; Brian Federle
Subject: Re: [VOTE] Apache Cloudstack 4.2.0

I don't understand how those got in there.

I think they were merged into my code from Jessica's earlier checkin.

They are not related to my fix.

On Mon, Aug 26, 2013 at 4:41 PM, Animesh Chaturvedi 
mailto:animesh.chaturv...@citrix.com>> wrote:
Mike with your commit 6a2f15f94ae74b563a2d4df6da38e7f6ff44c8ac

I see a few changes to

Ui\scripts\ui-custom\zoneWizard.js
Ui\scripts\zoneWizard.js

Are they needed for your CHAP changes? These seems unrelated to me.


Animesh

> -Original Message-
> From: Mike Tutkowski 
> [mailto:mike.tutkow...@solidfire.com]
> Sent: Monday, August 26, 2013 2:44 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [VOTE] Apache Cloudstack 4.2.0
>
> OK, Animesh.
>
> My changes are in 4.2-forward now.
>
> Thanks!
>
>
> On Mon, Aug 26, 2013 at 3:18 PM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
> > No problem - I'll let you know when it's there.
> >
> >
> > On Mon, Aug 26, 2013 at 2:54 PM, Animesh Chaturvedi <
> > animesh.chaturv...@citrix.com> wrote:
> >
> >>
> >>
> >> > -Original Message-
> >> > From: Mike Tutkowski 
> >> > [mailto:mike.tutkow...@solidfire.com]
> >> > Sent: Monday, August 26, 2013 1:48 PM
> >> > To: dev@cloudstack.apache.org
> >> > Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> >> >
> >> > Hi Animesh,
> >> >
> >> > It is related to adding an iSCSI target to ESX(i).
> >> >
> >> > The 4.2 code assumes you will want to use Mutual CHAP. This fix
> >> > allows the user to not have to use Mutual CHAP.
> >> >
> >> > It's only a small number of changes, pretty low risk, and should
> >> > only impact the SolidFire plug-in as no other plug-in code has been
> >> > written to date that uses the logic in the VMware code that I would
> >> > need to modify.
> >> >
> >> > I've written and tested the code, as well.
> >> >
> >> > Talk to you later,
> >> >
> >> [Animesh>] Can you put your fix in 4.2-forward ASAP
> >>
> >
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkow...@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the
> > cloud
> > *(tm)*
> >
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud
> *(tm)*



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



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

RE: [VOTE] Apache Cloudstack 4.2.0 [Cancelled]

[Animesh Chaturvedi]

I am cancelling this VOTE and I will start another VOTE thread when I have a 
new RC build available shortly

Edison is helping me out with the git merge issue. There are a number of fixes 
that I would like to pick up so as well merge the branch from 4.2-forward

Thanks
Animesh

> -Original Message-
> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> Sent: Monday, August 26, 2013 4:05 PM
> To: Mike Tutkowski; Brian Federle
> Cc: dev@cloudstack.apache.org; Jessica Wang
> Subject: RE: [VOTE] Apache Cloudstack 4.2.0
> 
> Ok so git experts on the list I should skip Mike's merge commit and
> instead pick the one from Jessica?
> 
> Thanks
> Animesh
> 
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: Monday, August 26, 2013 4:03 PM
> To: Brian Federle
> Cc: Animesh Chaturvedi; dev@cloudstack.apache.org; Jessica Wang
> Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> 
> Yeah, I agree. :) I think I merged instead of rebased.
> 
> On Mon, Aug 26, 2013 at 5:00 PM, Brian Federle
> mailto:brian.fede...@citrix.com>> wrote:
> Probably something just got messed up during the rebase, I see this
> commit below yours:
> 
> commit ae68c841f668768118bbff07f07060416fb16d48
> Author: Jessica Wang
> mailto:jessicaw...@apache.org>>
> Date:   Mon Aug 26 14:24:22 2013 -0700
> 
> CLOUDSTACK-4089: UI > zone wizard > hypervisor VMware > configure
> physical network > edit traffic type label > split
> 
> Which modifies system.js -- probably committed at the same time as you.
> 
> I only think this because I've definitely screwed stuff up in git myself
> in the past when I forget to rebase :D
> 
> -Brian
> 
> From: Animesh Chaturvedi
> Sent: Monday, August 26, 2013 3:56 PM
> To: Mike Tutkowski
> Cc: dev@cloudstack.apache.org; Brian
> Federle; Jessica Wang
> Subject: RE: [VOTE] Apache Cloudstack 4.2.0
> 
> Mike the commit message shows it is a merge "Merge remote-tracking
> branch 'upstream/4.2-forward' into 4.2-forward"
> 
> Adding Brian and Jessica to the thread.
> 
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: Monday, August 26, 2013 3:45 PM
> To: Animesh Chaturvedi
> Cc: dev@cloudstack.apache.org; Brian
> Federle
> Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> 
> I don't understand how those got in there.
> 
> I think they were merged into my code from Jessica's earlier checkin.
> 
> They are not related to my fix.
> 
> On Mon, Aug 26, 2013 at 4:41 PM, Animesh Chaturvedi
> mailto:animesh.chaturv...@citrix.com>>
> wrote:
> Mike with your commit 6a2f15f94ae74b563a2d4df6da38e7f6ff44c8ac
> 
> I see a few changes to
> 
> Ui\scripts\ui-custom\zoneWizard.js
> Ui\scripts\zoneWizard.js
> 
> Are they needed for your CHAP changes? These seems unrelated to me.
> 
> 
> Animesh
> 
> > -Original Message-
> > From: Mike Tutkowski
> > [mailto:mike.tutkow...@solidfire.com > om>]
> > Sent: Monday, August 26, 2013 2:44 PM
> > To: dev@cloudstack.apache.org
> > Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> >
> > OK, Animesh.
> >
> > My changes are in 4.2-forward now.
> >
> > Thanks!
> >
> >
> > On Mon, Aug 26, 2013 at 3:18 PM, Mike Tutkowski <
> > mike.tutkow...@solidfire.com>
> wrote:
> >
> > > No problem - I'll let you know when it's there.
> > >
> > >
> > > On Mon, Aug 26, 2013 at 2:54 PM, Animesh Chaturvedi <
> > > animesh.chaturv...@citrix.com>
> wrote:
> > >
> > >>
> > >>
> > >> > -Original Message-
> > >> > From: Mike Tutkowski
> > >> > [mailto:mike.tutkow...@solidfire.com > >> > ire.com>]
> > >> > Sent: Monday, August 26, 2013 1:48 PM
> > >> > To: dev@cloudstack.apache.org
> > >> > Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> > >> >
> > >> > Hi Animesh,
> > >> >
> > >> > It is related to adding an iSCSI target to ESX(i).
> > >> >
> > >> > The 4.2 code assumes you will want to use Mutual CHAP. This fix
> > >> > allows the user to not have to use Mutual CHAP.
> > >> >
> > >> > It's only a small number of changes, pretty low risk, and should
> > >> > only impact the SolidFire plug-in as no other plug-in code has
> > >> > been written to date that uses the logic in the VMware code that
> > >> > I would need to modify.
> > >> >
> > >> > I've written and tested the code, as well.
> > >> >
> > >> > Talk to you later,
> > >> >
> > >> [Animesh>] Can you put your fix in 4.2-forward ASAP
> > >>
> > >
> > >
> > >
> > > --
> > > *Mike Tutkowski*
> > > *Senior CloudStack Developer, SolidFire Inc.*
> > > e: mike.tutkow...@solidfire.com
> > > o: 303.746.7302
> > > Advancing the way the world uses the
> > > cloud
> > > *(tm)*
> > >
> >
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*

Re: [VOTE] Apache Cloudstack 4.2.0

[Dave Cahill]

Hi,

I reported CLOUDSTACK-4466 4 days ago and submitted a patch. It's
restricted to plugin code, so should be a simple and isolated change to
grab.

Although my vote would be non-binding, I would be -1 without the change, as
it fixes DHCP functionality which was broken by a recent commit in core code
.

Thanks,
Dave.
2013年8月27日火曜日 Animesh Chaturvedi animesh.chaturv...@citrix.com:

> Ok so git experts on the list I should skip Mike's merge commit and
> instead pick the one from Jessica?
>
> Thanks
> Animesh
>
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com ]
> Sent: Monday, August 26, 2013 4:03 PM
> To: Brian Federle
> Cc: Animesh Chaturvedi; dev@cloudstack.apache.org ; Jessica
> Wang
> Subject: Re: [VOTE] Apache Cloudstack 4.2.0
>
> Yeah, I agree. :) I think I merged instead of rebased.
>
> On Mon, Aug 26, 2013 at 5:00 PM, Brian Federle 
> 
> > wrote:
> Probably something just got messed up during the rebase, I see this commit
> below yours:
>
> commit ae68c841f668768118bbff07f07060416fb16d48
> Author: Jessica Wang  jessicaw...@apache.org >>
> Date:   Mon Aug 26 14:24:22 2013 -0700
>
> CLOUDSTACK-4089: UI > zone wizard > hypervisor VMware > configure
> physical network > edit traffic type label > split
>
> Which modifies system.js -- probably committed at the same time as you.
>
> I only think this because I've definitely screwed stuff up in git myself
> in the past when I forget to rebase :D
>
> -Brian
>
> From: Animesh Chaturvedi
> Sent: Monday, August 26, 2013 3:56 PM
> To: Mike Tutkowski
> Cc: dev@cloudstack.apache.org  dev@cloudstack.apache.org >; Brian Federle; Jessica Wang
> Subject: RE: [VOTE] Apache Cloudstack 4.2.0
>
> Mike the commit message shows it is a merge "Merge remote-tracking branch
> 'upstream/4.2-forward' into 4.2-forward"
>
> Adding Brian and Jessica to the thread.
>
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com ]
> Sent: Monday, August 26, 2013 3:45 PM
> To: Animesh Chaturvedi
> Cc: dev@cloudstack.apache.org  dev@cloudstack.apache.org >; Brian Federle
> Subject: Re: [VOTE] Apache Cloudstack 4.2.0
>
> I don't understand how those got in there.
>
> I think they were merged into my code from Jessica's earlier checkin.
>
> They are not related to my fix.
>
> On Mon, Aug 26, 2013 at 4:41 PM, Animesh Chaturvedi <
> animesh.chaturv...@citrix.com  animesh.chaturv...@citrix.com >> wrote:
> Mike with your commit 6a2f15f94ae74b563a2d4df6da38e7f6ff44c8ac
>
> I see a few changes to
>
> Ui\scripts\ui-custom\zoneWizard.js
> Ui\scripts\zoneWizard.js
>
> Are they needed for your CHAP changes? These seems unrelated to me.
>
>
> Animesh
>
> > -Original Message-
> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com 
> ]
> > Sent: Monday, August 26, 2013 2:44 PM
> > To: dev@cloudstack.apache.org  dev@cloudstack.apache.org >
> > Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> >
> > OK, Animesh.
> >
> > My changes are in 4.2-forward now.
> >
> > Thanks!
> >
> >
> > On Mon, Aug 26, 2013 at 3:18 PM, Mike Tutkowski <
> > mike.tutkow...@solidfire.com  mike.tutkow...@solidfire.com >> wrote:
> >
> > > No problem - I'll let you know when it's there.
> > >
> > >
> > > On Mon, Aug 26, 2013 at 2:54 PM, Animesh Chaturvedi <
> > > animesh.chaturv...@citrix.com  animesh.chaturv...@citrix.com >> wrote:
> > >
> > >>
> > >>
> > >> > -Original Message-
> > >> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com
> ]
> > >> > Sent: Monday, August 26, 2013 1:48 PM
> > >> > To: dev@cloudstack.apache.org  dev@cloudstack.apache.org >
> > >> > Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> > >> >
> > >> > Hi Animesh,
> > >> >
> > >> > It is related to adding an iSCSI target to ESX(i).
> > >> >
> > >> > The 4.2 code assumes you will want to use Mutual CHAP. This fix
> > >> > allows the user to not have to use Mutual CHAP.
> > >> >
> > >> > It's only a small number of changes, pretty low risk, and should
> > >> > only impact the SolidFire plug-in as no other plug-in code has been
> > >> > written to date that uses the logic in the VMware code that I would
> > >> > need to modify.
> > >> >
> > >> > I've written and tested the code, as well.
> > >> >
> > >> > Talk to you later,
> > >> >
> > >> [Animesh>] Can you put your fix in 4.2-forward ASAP
> > >>
> > >
> > >
> > >
> > > --
> > > *Mike Tutkowski*
> > > *Senior CloudStack Developer, SolidFire Inc.*
> > > e: mike.tutkow...@solidfire.com  mike.tutkow...@solidfire.com >
> > > o: 303.746.7302
> > > Advancing the way the world uses the
> > > cloud
> > > *(tm)*
> > >
> >
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkow...@solidfire.com  mike.tutkow...@solidfire.com >
> > o: 303.746.7302
> > Advancing the way the world uses the
> > cloud
> > *(tm)*
>
>
>
> --
> Mik

Re: Review Request 13804: CLOUDSTACK-4495: systemVM template URL is pointing to old template location in upgrade file.

[ASF Subversion and Git Services]

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


Commit 208507a42a4db252dc3d7cf299c146315423a071 in branch refs/heads/4.2 from 
Sanjay Tripathi
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=208507a ]

CLOUDSTACK-4495: systemVM template URL is pointing to old template location in 
upgrade file.

SystemVM template URL for XenServer hypervisor is pointing to old template 
location in the Upgrade410to420.java  file.


- ASF Subversion and Git Services


On Aug. 26, 2013, 8:02 a.m., Sanjay Tripathi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/13804/
> ---
> 
> (Updated Aug. 26, 2013, 8:02 a.m.)
> 
> 
> Review request for cloudstack, Abhinandan Prateek and Devdeep Singh.
> 
> 
> Bugs: CLOUDSTACK-4495
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> SystemVM template URL for XenServer hypervisor is pointing to old template 
> location in the Upgrade410to420.java  file.
> 
> https://issues.apache.org/jira/browse/CLOUDSTACK-4495
> 
> 
> Diffs
> -
> 
>   engine/schema/src/com/cloud/upgrade/dao/Upgrade410to420.java c3276ef 
> 
> Diff: https://reviews.apache.org/r/13804/diff/
> 
> 
> Testing
> ---
> 
> Tests:
> 1. Setup CloudStack environment,
> 2. Check the systemVM template URL in vm_template table (it should point to 
> the new location).
> 
> 
> Thanks,
> 
> Sanjay Tripathi
> 
>

Re: [VOTE] Apache Cloudstack 4.2.0

[Sheng Yang]

Animesh,

You can just pick up the single commits. e.g.

commit 13a415fe8a3917a49dae5a1f3998f5ae78a61da3
Author: Mike Tutkowski 
Date:   Mon Aug 26 15:33:39 2013 -0600

Not everyone wants to use Mutual CHAP with VMware - make it optional.

--Sheng


On Mon, Aug 26, 2013 at 4:05 PM, Animesh Chaturvedi <
animesh.chaturv...@citrix.com> wrote:

> Ok so git experts on the list I should skip Mike's merge commit and
> instead pick the one from Jessica?
>
> Thanks
> Animesh
>
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: Monday, August 26, 2013 4:03 PM
> To: Brian Federle
> Cc: Animesh Chaturvedi; dev@cloudstack.apache.org; Jessica Wang
> Subject: Re: [VOTE] Apache Cloudstack 4.2.0
>
> Yeah, I agree. :) I think I merged instead of rebased.
>
> On Mon, Aug 26, 2013 at 5:00 PM, Brian Federle  > wrote:
> Probably something just got messed up during the rebase, I see this commit
> below yours:
>
> commit ae68c841f668768118bbff07f07060416fb16d48
> Author: Jessica Wang mailto:jessicaw...@apache.org
> >>
> Date:   Mon Aug 26 14:24:22 2013 -0700
>
> CLOUDSTACK-4089: UI > zone wizard > hypervisor VMware > configure
> physical network > edit traffic type label > split
>
> Which modifies system.js -- probably committed at the same time as you.
>
> I only think this because I've definitely screwed stuff up in git myself
> in the past when I forget to rebase :D
>
> -Brian
>
> From: Animesh Chaturvedi
> Sent: Monday, August 26, 2013 3:56 PM
> To: Mike Tutkowski
> Cc: dev@cloudstack.apache.org; Brian
> Federle; Jessica Wang
> Subject: RE: [VOTE] Apache Cloudstack 4.2.0
>
> Mike the commit message shows it is a merge "Merge remote-tracking branch
> 'upstream/4.2-forward' into 4.2-forward"
>
> Adding Brian and Jessica to the thread.
>
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: Monday, August 26, 2013 3:45 PM
> To: Animesh Chaturvedi
> Cc: dev@cloudstack.apache.org; Brian
> Federle
> Subject: Re: [VOTE] Apache Cloudstack 4.2.0
>
> I don't understand how those got in there.
>
> I think they were merged into my code from Jessica's earlier checkin.
>
> They are not related to my fix.
>
> On Mon, Aug 26, 2013 at 4:41 PM, Animesh Chaturvedi <
> animesh.chaturv...@citrix.com>
> wrote:
> Mike with your commit 6a2f15f94ae74b563a2d4df6da38e7f6ff44c8ac
>
> I see a few changes to
>
> Ui\scripts\ui-custom\zoneWizard.js
> Ui\scripts\zoneWizard.js
>
> Are they needed for your CHAP changes? These seems unrelated to me.
>
>
> Animesh
>
> > -Original Message-
> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com mike.tutkow...@solidfire.com>]
> > Sent: Monday, August 26, 2013 2:44 PM
> > To: dev@cloudstack.apache.org
> > Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> >
> > OK, Animesh.
> >
> > My changes are in 4.2-forward now.
> >
> > Thanks!
> >
> >
> > On Mon, Aug 26, 2013 at 3:18 PM, Mike Tutkowski <
> > mike.tutkow...@solidfire.com>
> wrote:
> >
> > > No problem - I'll let you know when it's there.
> > >
> > >
> > > On Mon, Aug 26, 2013 at 2:54 PM, Animesh Chaturvedi <
> > > animesh.chaturv...@citrix.com>
> wrote:
> > >
> > >>
> > >>
> > >> > -Original Message-
> > >> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com mike.tutkow...@solidfire.com>]
> > >> > Sent: Monday, August 26, 2013 1:48 PM
> > >> > To: dev@cloudstack.apache.org
> > >> > Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> > >> >
> > >> > Hi Animesh,
> > >> >
> > >> > It is related to adding an iSCSI target to ESX(i).
> > >> >
> > >> > The 4.2 code assumes you will want to use Mutual CHAP. This fix
> > >> > allows the user to not have to use Mutual CHAP.
> > >> >
> > >> > It's only a small number of changes, pretty low risk, and should
> > >> > only impact the SolidFire plug-in as no other plug-in code has been
> > >> > written to date that uses the logic in the VMware code that I would
> > >> > need to modify.
> > >> >
> > >> > I've written and tested the code, as well.
> > >> >
> > >> > Talk to you later,
> > >> >
> > >> [Animesh>] Can you put your fix in 4.2-forward ASAP
> > >>
> > >
> > >
> > >
> > > --
> > > *Mike Tutkowski*
> > > *Senior CloudStack Developer, SolidFire Inc.*
> > > e: mike.tutkow...@solidfire.com
> > > o: 303.746.7302
> > > Advancing the way the world uses the
> > > cloud
> > > *(tm)*
> > >
> >
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkow...@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the
> > cloud
> > *(tm)*
>
>
>
> --
> Mike Tutkows

RE: [VOTE] Apache Cloudstack 4.2.0

[Animesh Chaturvedi]

Your patch is in review board and not committed yet. It needs to be reviewed 
and committed in a branch before it can be picked up for 4.2 RC build. Copying 
Hugo (called out as reviewer in review board) and Chiradeep


Thanks
Animesh

> -Original Message-
> From: Dave Cahill [mailto:dcah...@midokura.com]
> Sent: Monday, August 26, 2013 4:25 PM
> To: dev@cloudstack.apache.org
> Cc: Mike Tutkowski; Brian Federle; Jessica Wang
> Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> 
> Hi,
> 
> I reported CLOUDSTACK-4466 4 days ago and submitted a patch. It's
> restricted to plugin code, so should be a simple and isolated change to
> grab.
> 
> Although my vote would be non-binding, I would be -1 without the change,
> as it fixes DHCP functionality which was broken by a recent commit in
> core code .

Re: [VOTE] Apache Cloudstack 4.2.0

[Sheng Yang]

Hi Dave,

I've taken a look at the patch. The dhcp capability fix is pretty simple,
but the name changing part involved much more modifications. Can the name
change done after 4.2? It should reduce the patch size a lot.

--Sheng


On Mon, Aug 26, 2013 at 4:24 PM, Dave Cahill  wrote:

> Hi,
>
> I reported CLOUDSTACK-4466 4 days ago and submitted a patch. It's
> restricted to plugin code, so should be a simple and isolated change to
> grab.
>
> Although my vote would be non-binding, I would be -1 without the change, as
> it fixes DHCP functionality which was broken by a recent commit in core
> code
> .
>
> Thanks,
> Dave.
> 2013年8月27日火曜日 Animesh Chaturvedi animesh.chaturv...@citrix.com:
>
> > Ok so git experts on the list I should skip Mike's merge commit and
> > instead pick the one from Jessica?
> >
> > Thanks
> > Animesh
> >
> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> > Sent: Monday, August 26, 2013 4:03 PM
> > To: Brian Federle
> > Cc: Animesh Chaturvedi; dev@cloudstack.apache.org ;
> Jessica
> > Wang
> > Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> >
> > Yeah, I agree. :) I think I merged instead of rebased.
> >
> > On Mon, Aug 26, 2013 at 5:00 PM, Brian Federle  
> > > wrote:
> > Probably something just got messed up during the rebase, I see this
> commit
> > below yours:
> >
> > commit ae68c841f668768118bbff07f07060416fb16d48
> > Author: Jessica Wang  > jessicaw...@apache.org >>
> > Date:   Mon Aug 26 14:24:22 2013 -0700
> >
> > CLOUDSTACK-4089: UI > zone wizard > hypervisor VMware > configure
> > physical network > edit traffic type label > split
> >
> > Which modifies system.js -- probably committed at the same time as you.
> >
> > I only think this because I've definitely screwed stuff up in git myself
> > in the past when I forget to rebase :D
> >
> > -Brian
> >
> > From: Animesh Chaturvedi
> > Sent: Monday, August 26, 2013 3:56 PM
> > To: Mike Tutkowski
> > Cc: dev@cloudstack.apache.org  > dev@cloudstack.apache.org >; Brian Federle; Jessica Wang
> > Subject: RE: [VOTE] Apache Cloudstack 4.2.0
> >
> > Mike the commit message shows it is a merge "Merge remote-tracking branch
> > 'upstream/4.2-forward' into 4.2-forward"
> >
> > Adding Brian and Jessica to the thread.
> >
> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> > Sent: Monday, August 26, 2013 3:45 PM
> > To: Animesh Chaturvedi
> > Cc: dev@cloudstack.apache.org  > dev@cloudstack.apache.org >; Brian Federle
> > Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> >
> > I don't understand how those got in there.
> >
> > I think they were merged into my code from Jessica's earlier checkin.
> >
> > They are not related to my fix.
> >
> > On Mon, Aug 26, 2013 at 4:41 PM, Animesh Chaturvedi <
> > animesh.chaturv...@citrix.com  > animesh.chaturv...@citrix.com >> wrote:
> > Mike with your commit 6a2f15f94ae74b563a2d4df6da38e7f6ff44c8ac
> >
> > I see a few changes to
> >
> > Ui\scripts\ui-custom\zoneWizard.js
> > Ui\scripts\zoneWizard.js
> >
> > Are they needed for your CHAP changes? These seems unrelated to me.
> >
> >
> > Animesh
> >
> > > -Original Message-
> > > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com
> > ]
> > > Sent: Monday, August 26, 2013 2:44 PM
> > > To: dev@cloudstack.apache.org  > dev@cloudstack.apache.org >
> > > Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> > >
> > > OK, Animesh.
> > >
> > > My changes are in 4.2-forward now.
> > >
> > > Thanks!
> > >
> > >
> > > On Mon, Aug 26, 2013 at 3:18 PM, Mike Tutkowski <
> > > mike.tutkow...@solidfire.com  > mike.tutkow...@solidfire.com >> wrote:
> > >
> > > > No problem - I'll let you know when it's there.
> > > >
> > > >
> > > > On Mon, Aug 26, 2013 at 2:54 PM, Animesh Chaturvedi <
> > > > animesh.chaturv...@citrix.com  > animesh.chaturv...@citrix.com >> wrote:
> > > >
> > > >>
> > > >>
> > > >> > -Original Message-
> > > >> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com
> 
> > ]
> > > >> > Sent: Monday, August 26, 2013 1:48 PM
> > > >> > To: dev@cloudstack.apache.org  > dev@cloudstack.apache.org >
> > > >> > Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> > > >> >
> > > >> > Hi Animesh,
> > > >> >
> > > >> > It is related to adding an iSCSI target to ESX(i).
> > > >> >
> > > >> > The 4.2 code assumes you will want to use Mutual CHAP. This fix
> > > >> > allows the user to not have to use Mutual CHAP.
> > > >> >
> > > >> > It's only a small number of changes, pretty low risk, and should
> > > >> > only impact the SolidFire plug-in as no other plug-in code has
> been
> > > >> > written to date that uses the logic in the VMware code that I
> would
> > > >> > need to modify.
> > > >> >
> > > >> > I've written and tested the code, as well.
> > > >> >
> > > >> > Talk to you later,
> > > >> >
> > > >> [Animesh>] Can you put your fix in 4.2-forward ASAP
> > > >>
> > > >
> > > >
> > > >
> > > > --
> > > > *Mike Tutk

[VOTE][CANCELLED] Apache Cloudstack 4.2.0

[Animesh Chaturvedi]

Cancelling this VOTE officially. I will start a new VOTE soon

> -Original Message-
> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> Sent: Friday, August 23, 2013 11:55 AM
> To: dev@cloudstack.apache.org
> Subject: [VOTE] Apache Cloudstack 4.2.0
> 
> 
> 
> Hi All,
> 
> I've created a 4.2.0 release, with the following artifacts up for a
> vote:
> 
> Git Branch and Commit SH:
> https://git-wip-
> us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.2
> Commit: 06f28722b6fe5827d58861e9a9d47fe46aaafefa
> 
> List of changes:
> https://git-wip-
> us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=CHANGES;hb=4.2
> 
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.2.0/
> 
> PGP release keys (signed using 94BE0D7C):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> 
> Testing instructions are here:
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+test+proc
> edure
> 
> Vote will be open for 72 hours.
> 
> For sanity in tallying the vote, can PMC members please be sure to
> indicate "(binding)" with their vote?
> 
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)

Re: why 2 spaces for xml?

[Darren Shepherd]

On Aug 26, 2013, at 10:21 AM, Chip Childers  wrote:

> On Mon, Aug 26, 2013 at 10:12:30AM -0700, Darren Shepherd wrote:
>> On 08/26/2013 09:22 AM, Marty Sweet wrote:
>>> All the XML documentation I have seen has been 4 spaces for indent, what
>>> XML files are you talking about?
>> 
>> I couldn't find documented on the ACS web page or website that the
>> standard was 2 spaces, but I swear I saw it written somewhere.
>> Regardless, I'm looking at all the pom.xml and
>> applicationContext*.xml files.
>> 
>> Darren
> 
> Nothing but inconsistency causing that...  we should just use 4
> everywhere IMO.

Alright, I will sleep better at night knowing I can use 4 spaces in XML. 

Darren

Re: [VOTE] Apache Cloudstack 4.2.0

[Dave Cahill]

Hi Sheng,

Thanks for reviewing.

The name change is also necessary for 4.2. Since the code changes are
entirely restricted to plugin code (all within the midonet dir), I think
it's a very safe change.

Thanks,
Dave.



On Tue, Aug 27, 2013 at 8:36 AM, Sheng Yang  wrote:

> Hi Dave,
>
> I've taken a look at the patch. The dhcp capability fix is pretty simple,
> but the name changing part involved much more modifications. Can the name
> change done after 4.2? It should reduce the patch size a lot.
>
> --Sheng
>
>
> On Mon, Aug 26, 2013 at 4:24 PM, Dave Cahill  wrote:
>
> > Hi,
> >
> > I reported CLOUDSTACK-4466 4 days ago and submitted a patch. It's
> > restricted to plugin code, so should be a simple and isolated change to
> > grab.
> >
> > Although my vote would be non-binding, I would be -1 without the change,
> as
> > it fixes DHCP functionality which was broken by a recent commit in core
> > code
> > .
> >
> > Thanks,
> > Dave.
> > 2013年8月27日火曜日 Animesh Chaturvedi animesh.chaturv...@citrix.com:
> >
> > > Ok so git experts on the list I should skip Mike's merge commit and
> > > instead pick the one from Jessica?
> > >
> > > Thanks
> > > Animesh
> > >
> > > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com
> ]
> > > Sent: Monday, August 26, 2013 4:03 PM
> > > To: Brian Federle
> > > Cc: Animesh Chaturvedi; dev@cloudstack.apache.org ;
> > Jessica
> > > Wang
> > > Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> > >
> > > Yeah, I agree. :) I think I merged instead of rebased.
> > >
> > > On Mon, Aug 26, 2013 at 5:00 PM, Brian Federle <
> brian.fede...@citrix.com
> > 
> > > > wrote:
> > > Probably something just got messed up during the rebase, I see this
> > commit
> > > below yours:
> > >
> > > commit ae68c841f668768118bbff07f07060416fb16d48
> > > Author: Jessica Wang  > > jessicaw...@apache.org >>
> > > Date:   Mon Aug 26 14:24:22 2013 -0700
> > >
> > > CLOUDSTACK-4089: UI > zone wizard > hypervisor VMware > configure
> > > physical network > edit traffic type label > split
> > >
> > > Which modifies system.js -- probably committed at the same time as you.
> > >
> > > I only think this because I've definitely screwed stuff up in git
> myself
> > > in the past when I forget to rebase :D
> > >
> > > -Brian
> > >
> > > From: Animesh Chaturvedi
> > > Sent: Monday, August 26, 2013 3:56 PM
> > > To: Mike Tutkowski
> > > Cc: dev@cloudstack.apache.org  > > dev@cloudstack.apache.org >; Brian Federle; Jessica Wang
> > > Subject: RE: [VOTE] Apache Cloudstack 4.2.0
> > >
> > > Mike the commit message shows it is a merge "Merge remote-tracking
> branch
> > > 'upstream/4.2-forward' into 4.2-forward"
> > >
> > > Adding Brian and Jessica to the thread.
> > >
> > > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com
> ]
> > > Sent: Monday, August 26, 2013 3:45 PM
> > > To: Animesh Chaturvedi
> > > Cc: dev@cloudstack.apache.org  > > dev@cloudstack.apache.org >; Brian Federle
> > > Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> > >
> > > I don't understand how those got in there.
> > >
> > > I think they were merged into my code from Jessica's earlier checkin.
> > >
> > > They are not related to my fix.
> > >
> > > On Mon, Aug 26, 2013 at 4:41 PM, Animesh Chaturvedi <
> > > animesh.chaturv...@citrix.com  > > animesh.chaturv...@citrix.com >> wrote:
> > > Mike with your commit 6a2f15f94ae74b563a2d4df6da38e7f6ff44c8ac
> > >
> > > I see a few changes to
> > >
> > > Ui\scripts\ui-custom\zoneWizard.js
> > > Ui\scripts\zoneWizard.js
> > >
> > > Are they needed for your CHAP changes? These seems unrelated to me.
> > >
> > >
> > > Animesh
> > >
> > > > -Original Message-
> > > > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com
> 
> > > ]
> > > > Sent: Monday, August 26, 2013 2:44 PM
> > > > To: dev@cloudstack.apache.org  > > dev@cloudstack.apache.org >
> > > > Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> > > >
> > > > OK, Animesh.
> > > >
> > > > My changes are in 4.2-forward now.
> > > >
> > > > Thanks!
> > > >
> > > >
> > > > On Mon, Aug 26, 2013 at 3:18 PM, Mike Tutkowski <
> > > > mike.tutkow...@solidfire.com  > > mike.tutkow...@solidfire.com >> wrote:
> > > >
> > > > > No problem - I'll let you know when it's there.
> > > > >
> > > > >
> > > > > On Mon, Aug 26, 2013 at 2:54 PM, Animesh Chaturvedi <
> > > > > animesh.chaturv...@citrix.com  > > animesh.chaturv...@citrix.com >> wrote:
> > > > >
> > > > >>
> > > > >>
> > > > >> > -Original Message-
> > > > >> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com
> > 
> > > ]
> > > > >> > Sent: Monday, August 26, 2013 1:48 PM
> > > > >> > To: dev@cloudstack.apache.org  > > dev@cloudstack.apache.org >
> > > > >> > Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> > > > >> >
> > > > >> > Hi Animesh,
> > > > >> >
> > > > >> > It is related to adding an iSCSI target to ESX(i).
> > > > >> >
> > > > >> > The 4.2 code assumes you will want

Re: [VOTE] Apache Cloudstack 4.2.0 [Cancelled]

[Mike Tutkowski]

Thanks, guys!

I should have done a rebase. Sorry about that.


On Mon, Aug 26, 2013 at 5:24 PM, Animesh Chaturvedi <
animesh.chaturv...@citrix.com> wrote:

>
> I am cancelling this VOTE and I will start another VOTE thread when I have
> a new RC build available shortly
>
> Edison is helping me out with the git merge issue. There are a number of
> fixes that I would like to pick up so as well merge the branch from
> 4.2-forward
>
> Thanks
> Animesh
>
> > -Original Message-
> > From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> > Sent: Monday, August 26, 2013 4:05 PM
> > To: Mike Tutkowski; Brian Federle
> > Cc: dev@cloudstack.apache.org; Jessica Wang
> > Subject: RE: [VOTE] Apache Cloudstack 4.2.0
> >
> > Ok so git experts on the list I should skip Mike's merge commit and
> > instead pick the one from Jessica?
> >
> > Thanks
> > Animesh
> >
> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> > Sent: Monday, August 26, 2013 4:03 PM
> > To: Brian Federle
> > Cc: Animesh Chaturvedi; dev@cloudstack.apache.org; Jessica Wang
> > Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> >
> > Yeah, I agree. :) I think I merged instead of rebased.
> >
> > On Mon, Aug 26, 2013 at 5:00 PM, Brian Federle
> > mailto:brian.fede...@citrix.com>> wrote:
> > Probably something just got messed up during the rebase, I see this
> > commit below yours:
> >
> > commit ae68c841f668768118bbff07f07060416fb16d48
> > Author: Jessica Wang
> > mailto:jessicaw...@apache.org>>
> > Date:   Mon Aug 26 14:24:22 2013 -0700
> >
> > CLOUDSTACK-4089: UI > zone wizard > hypervisor VMware > configure
> > physical network > edit traffic type label > split
> >
> > Which modifies system.js -- probably committed at the same time as you.
> >
> > I only think this because I've definitely screwed stuff up in git myself
> > in the past when I forget to rebase :D
> >
> > -Brian
> >
> > From: Animesh Chaturvedi
> > Sent: Monday, August 26, 2013 3:56 PM
> > To: Mike Tutkowski
> > Cc: dev@cloudstack.apache.org; Brian
> > Federle; Jessica Wang
> > Subject: RE: [VOTE] Apache Cloudstack 4.2.0
> >
> > Mike the commit message shows it is a merge "Merge remote-tracking
> > branch 'upstream/4.2-forward' into 4.2-forward"
> >
> > Adding Brian and Jessica to the thread.
> >
> > From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> > Sent: Monday, August 26, 2013 3:45 PM
> > To: Animesh Chaturvedi
> > Cc: dev@cloudstack.apache.org; Brian
> > Federle
> > Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> >
> > I don't understand how those got in there.
> >
> > I think they were merged into my code from Jessica's earlier checkin.
> >
> > They are not related to my fix.
> >
> > On Mon, Aug 26, 2013 at 4:41 PM, Animesh Chaturvedi
> > mailto:animesh.chaturv...@citrix.com>>
> > wrote:
> > Mike with your commit 6a2f15f94ae74b563a2d4df6da38e7f6ff44c8ac
> >
> > I see a few changes to
> >
> > Ui\scripts\ui-custom\zoneWizard.js
> > Ui\scripts\zoneWizard.js
> >
> > Are they needed for your CHAP changes? These seems unrelated to me.
> >
> >
> > Animesh
> >
> > > -Original Message-
> > > From: Mike Tutkowski
> > > [mailto:mike.tutkow...@solidfire.com > > om>]
> > > Sent: Monday, August 26, 2013 2:44 PM
> > > To: dev@cloudstack.apache.org
> > > Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> > >
> > > OK, Animesh.
> > >
> > > My changes are in 4.2-forward now.
> > >
> > > Thanks!
> > >
> > >
> > > On Mon, Aug 26, 2013 at 3:18 PM, Mike Tutkowski <
> > > mike.tutkow...@solidfire.com>
> > wrote:
> > >
> > > > No problem - I'll let you know when it's there.
> > > >
> > > >
> > > > On Mon, Aug 26, 2013 at 2:54 PM, Animesh Chaturvedi <
> > > > animesh.chaturv...@citrix.com>
> > wrote:
> > > >
> > > >>
> > > >>
> > > >> > -Original Message-
> > > >> > From: Mike Tutkowski
> > > >> > [mailto:mike.tutkow...@solidfire.com > > >> > ire.com>]
> > > >> > Sent: Monday, August 26, 2013 1:48 PM
> > > >> > To: dev@cloudstack.apache.org
> > > >> > Subject: Re: [VOTE] Apache Cloudstack 4.2.0
> > > >> >
> > > >> > Hi Animesh,
> > > >> >
> > > >> > It is related to adding an iSCSI target to ESX(i).
> > > >> >
> > > >> > The 4.2 code assumes you will want to use Mutual CHAP. This fix
> > > >> > allows the user to not have to use Mutual CHAP.
> > > >> >
> > > >> > It's only a small number of changes, pretty low risk, and should
> > > >> > only impact the SolidFire plug-in as no other plug-in code has
> > > >> > been written to date that uses the logic in the VMware code that
> > > >> > I would need to modify.
> > > >> >
> > > >> > I've written and tested the code, as well.
> > > >> >
> > > >> > Talk to you later,
> > > >> >
> > > >> [Animesh>] Can you put your fix in 4.2-forward ASAP
> > 

RE: Please cherry pick 4 doc fixes

[Animesh Chaturvedi]

Done will be in RC2

From: Jessica Tomechak [mailto:jessica.tomec...@gmail.com]
Sent: Monday, August 26, 2013 2:02 PM
To: dev@cloudstack.apache.org
Cc: Animesh Chaturvedi
Subject: Please cherry pick 4 doc fixes

>From 4.2-forward

(1)
Commit: ecbd9ed93d71284c9764c191fd94c5f9cf63dd6d [ecbd9ed]
Parents: 9a6f2de70e
Author: Jessica 
mailto:jessica.tomec...@citrix.com>>
Date: August 26, 2013 1:47:41 PM PDT
Commit Date: August 26, 2013 1:49:42 PM PDT
Labels: HEAD origin/4.2-forward 4.2-forward

CLOUDSTACK-4334. Documentation for how to write an object store plugin.


(2)

Commit: c2cde0b463916f4be3316dd4a8572fa96392b1d5 [c2cde0b]
Parents: f814bd
Author: Jessica 
mailto:jessica.tomec...@citrix.com>>
Date: August 26, 2013 12:44:56 PM PDT

CLOUDSTACK-4334. Documentation for object store.

(3)
Commit: 9a6f2de70e8dc9252913a723b03a1cadd22c80dd [9a6f2de]
Parents: 40443bb5ea
Author: Jessica 
mailto:jessica.tomec...@citrix.com>>
Date: August 26, 2013 12:48:36 PM PDT

DOC. Move misplaced paragraph from Secondary Storage section to Primary Storage 
section.


(4)

Commit: 48874c197eb466564772fed1c6b8cd3e92a9e223 [48874c1]
Parents: e5b7dc55ba
Author: Jessica 
mailto:jessica.tomec...@citrix.com>>
Date: August 26, 2013 12:46:31 PM PDT

DOC. Fix typo in Basic Zone Configuration.

RE: [ACS42] cherry pick commit 5b319ba0cb46160451ec05de32a8409b44a08f5b

[Animesh Chaturvedi]

Done will be in RC2

> -Original Message-
> From: Devdeep Singh [mailto:devdeep.si...@citrix.com]
> Sent: Friday, August 23, 2013 2:50 AM
> To: dev@cloudstack.apache.org
> Subject: [ACS42] cherry pick commit
> 5b319ba0cb46160451ec05de32a8409b44a08f5b
> 
> Hi Animesh,
> 
> This is a fix for bug https://issues.apache.org/jira/browse/CLOUDSTACK-
> 4470. Can you cherry pick commit
> 5b319ba0cb46160451ec05de32a8409b44a08f5b to 4.2 branch?
> 
> Regards,
> Devdeep

RE: why 2 spaces for xml?

[Alex Huang]

I have always preferred two spaces because xml can be indented so far so 
quickly that often the main part of the xml must be scrolled horizontally to 
read but I'm open to have it at four.

--Alex

> -Original Message-
> From: Darren Shepherd [mailto:darren.s.sheph...@gmail.com]
> Sent: Monday, August 26, 2013 4:49 PM
> To: dev@cloudstack.apache.org
> Cc: dev@cloudstack.apache.org
> Subject: Re: why 2 spaces for xml?
> 
> 
> 
> On Aug 26, 2013, at 10:21 AM, Chip Childers 
> wrote:
> 
> > On Mon, Aug 26, 2013 at 10:12:30AM -0700, Darren Shepherd wrote:
> >> On 08/26/2013 09:22 AM, Marty Sweet wrote:
> >>> All the XML documentation I have seen has been 4 spaces for indent,
> >>> what XML files are you talking about?
> >>
> >> I couldn't find documented on the ACS web page or website that the
> >> standard was 2 spaces, but I swear I saw it written somewhere.
> >> Regardless, I'm looking at all the pom.xml and
> >> applicationContext*.xml files.
> >>
> >> Darren
> >
> > Nothing but inconsistency causing that...  we should just use 4
> > everywhere IMO.
> 
> Alright, I will sleep better at night knowing I can use 4 spaces in XML.
> 
> Darren

please

[陈珂]

dev@cloudstack.apache.org


发自 Windows 邮件

Re: Templates via Vagrant Provider and Veewee

[Prasanna Santhanam]

Aminator looks cool. I've been working on a cloudstack builder for a
tool named packer [1] that does the same but cross-provider. It has
support for AMIs, vmware, digital ocean and virtual box so far. And it
has a plugin model for extending other builders.

Is Quagga going to be for extending/replacing the VR?

[1] www.packer.io

On Mon, Aug 26, 2013 at 05:25:13PM +, Chiradeep Vittal wrote:
> The stuff in tools/appliance is easy to customize. I built a Quagga
> template with slight mods.
> Methinks we can use it like Aminator
> https://github.com/Netflix/aminator
> 
> 
> On 8/25/13 10:11 AM, "Prasanna Santhanam"  wrote:
> 
> >All our systemVMs come from veewee + vagrant.
> >
> >see tools/appliance
> >
> >On Sun, Aug 25, 2013 at 05:57:50PM +0100, Ian Duffy wrote:
> >> Hey,
> >> 
> >> Has anybody tried to use the vagrant provider through veewee in order to
> >> create templates?
> >
> >-- 
> >Prasanna.,
> >
> >
> >Powered by BigRock.com
> >

-- 
Prasanna.,


Powered by BigRock.com