Re: Review Request 12545: CLOUDSTACK-1800: Add automation tests for reset sshkey to access VM

[Harikrishna Patnala]

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

Ship it!


Ship It!

- Harikrishna Patnala


On Sept. 14, 2013, 7:46 a.m., Girish Shilamkar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/12545/
> ---
> 
> (Updated Sept. 14, 2013, 7:46 a.m.)
> 
> 
> Review request for cloudstack, Harikrishna Patnala and Prasanna Santhanam.
> 
> 
> Bugs: CLOUDSTACK-1800
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> CLOUDSTACK-1800: Add automation tests for reset sshkey to access VM
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_reset_ssh_keypair.py PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/12545/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Girish Shilamkar
> 
>

Re: 4.1 new feature post release?

[Wido den Hollander]

On 09/15/2013 07:32 AM, Marcus Sorensen wrote:

Hi guys, I was just pulling in updates from the 4.1 branch and noticed
commit 706e23623c3227d92ae498529166ca73d2a2bf4e, This looks like a new
feature. There's not a bug attached to it. It seems to allow admins to
set the CPU mode for KVM guests, e.g. host-passthrough, which makes
the VM show the actual CPU model of the host (and breaks live
migration in some cases), etc.

I see no reason off hand why this should have been cherry-picked into
4.1.  It's been awhile, and I'm not sure whether or not we'll release
a 4.1.2, but we may want to review/revert it if we don't find out why
it was picked.



Good point. 4.1.2 release or not, there shouldn't be any new features in 
the 4.1 branch.


Wei, can you comment on this?

Wido


commit 706e23623c3227d92ae498529166ca73d2a2bf4e
Author: JijunLiu 
Date:   Sun Jul 14 11:21:39 2013 +0800

 Add cpu model for kvm guest.Now all the kvm guest's cpu model is
'QEMU Virtual CPU version xxx'. This will affect the activati

 Signed-off-by: Wei Zhou 
 (cherry picked from commit 2903bb5fd9d59803980102854d11e33ebe56088b)

RE: 4.1 new feature post release?

[Wei Zhou]

Marcus and Wido,
Sorry I just saw this Email.
I will create a JIRA ticket for them (both code and docs) later. I regarded it 
as an improvement, not a new feature, this is why I cherry-picked it into 4.1 
branch. If you guys object it, I will revert it.

Marcus, could you create tickets for the issues you mentioned? The commit is in 
4.2 and master branch as well. We need to fix potential issues.


Kind Regards,

Wei ZHOU
Innovation Engineer Cloud, LeaseWeb B.V.
w.z...@leaseweb.com

-Original Message-
From: Wido den Hollander [mailto:w...@widodh.nl] 
Sent: 16 September 2013 09:22
To: dev@cloudstack.apache.org
Cc: Wei Zhou
Subject: Re: 4.1 new feature post release?



On 09/15/2013 07:32 AM, Marcus Sorensen wrote:
> Hi guys, I was just pulling in updates from the 4.1 branch and noticed 
> commit 706e23623c3227d92ae498529166ca73d2a2bf4e, This looks like a new 
> feature. There's not a bug attached to it. It seems to allow admins to 
> set the CPU mode for KVM guests, e.g. host-passthrough, which makes 
> the VM show the actual CPU model of the host (and breaks live 
> migration in some cases), etc.
>
> I see no reason off hand why this should have been cherry-picked into 
> 4.1.  It's been awhile, and I'm not sure whether or not we'll release 
> a 4.1.2, but we may want to review/revert it if we don't find out why 
> it was picked.
>

Good point. 4.1.2 release or not, there shouldn't be any new features in the 
4.1 branch.

Wei, can you comment on this?

Wido

> commit 706e23623c3227d92ae498529166ca73d2a2bf4e
> Author: JijunLiu 
> Date:   Sun Jul 14 11:21:39 2013 +0800
>
>  Add cpu model for kvm guest.Now all the kvm guest's cpu model is 
> 'QEMU Virtual CPU version xxx'. This will affect the activati
>
>  Signed-off-by: Wei Zhou 
>  (cherry picked from commit 
> 2903bb5fd9d59803980102854d11e33ebe56088b)
>

RE: createVPCOffering (Was:RE: Marvin tests for VPC - why create VPC offering?)

[Sowmya Krishnan]

Filed https://issues.apache.org/jira/browse/CLOUDSTACK-4679 for the API issue.

> -Original Message-
> From: Alena Prokharchyk
> Sent: Friday, September 13, 2013 9:58 PM
> To: Sowmya Krishnan; dev@cloudstack.apache.org
> Cc: Venkata SwamyBabu Budumuru
> Subject: Re: createVPCOffering (Was:RE: Marvin tests for VPC - why create VPC
> offering?)
> 
> On 9/12/13 11:39 PM, "Sowmya Krishnan" 
> wrote:
> 
> >But we don't have an option to choose service providers with
> >createVPCOffering. It's always VPC VR for all services. If let's say, I
> >want to create a VPC Offering with LB as Netscaler and say, the
> >following services only: DNS, DHCP and SourceNat - it isn¹t possible from the
> API..
> >However this mapping *is* being done internally as can be seen from
> >vpc_offering_service_map table.
> >So providing flexibility to create a VPC with chosen set to services
> >but without the ability to choose providers is confusing and perhaps
> >limiting in a way?
> 
> Sounds like an api bug to me. We should allow having NS and internal LB as a
> provider. Please file it.
> 
> >
> >On the other hand, I am wondering what is the use case for exposing
> >createVPCOffering at all? Can we not stick to the default offerings of
> >VPC already provided?
> 
> The original intent for introducing VPC offering was - push all the
> services/providers from network offerings of the tiers to the VPC offering, 
> and
> make it serve the services for VPC just like network offering does for 
> network.
> Due to lack of time, it was easier back then to proxy services for VPC tiers 
> via
> network offering of the tier using existing implementation of
> NetworkAsAService. In the future all services/providers should be defined on 
> the
> VPC level instead of network level. By then, createVPCOffering functionality
> shouldn't be exposed in the UI.
> 
> 
> >
> >> -Original Message-
> >> From: Alena Prokharchyk
> >> Sent: Thursday, September 12, 2013 10:54 PM
> >> To: dev@cloudstack.apache.org; Sowmya Krishnan
> >> Cc: Venkata SwamyBabu Budumuru
> >> Subject: Re: Marvin tests for VPC - why create VPC offering?
> >>
> >>
> >> On 9/12/13 10:12 AM, "Rajesh Battala"  wrote:
> >>
> >> >My observations are
> >> >1. VPC offering is to tell what are all the services can be
> >> >available if you create tiers in the vpc.
> >>
> >> Correct
> >>
> >> >2. There should be some default providers for each service.(but
> >> >currently its only VpcVR). Or set of providers for each service it
> >> >can
> >>provider.
> >> >When vpc_network_offering is created, when this network is getting
> >> >implemented inside this vpc and those services/service providers are
> >> >validated against what are the services/providers can be provided.
> >>
> >>
> >> Only VPC VR/NS/Internal LB vm are supported as VPC providers
> >>
> >>
> >> >
> >> >I feel while creating "VPC_Offering" flexibility should be provided
> >> >at VPC level  such that what are the services provided and possible
> >> >service providers.
> >> >But currently there only only 3 possible providers one is VPcVR and
> >> >Netscaler(only for External LB) and internalLB Provider.
> >> >
> >> >As there are fixed set of providers and the possible combination of
> >> >VPC services offerings are created by default we should be using
> >> >them to create a VPC.
> >> >
> >> >If user wants to create a new VPC offering it will become a copy of
> >> >the existing VPC offering because possible VPC offerings are created
> >> >by VPCManager.
> >>
> >> Only Admin can create a VPC offering. And this offering doesn't
> >>become a copy.
> >> >
> >> >Thanks
> >> >Rajesh Battala
> >> >
> >> >-Original Message-
> >> >From: Sowmya Krishnan
> >> >Sent: Thursday, September 12, 2013 8:13 PM
> >> >To: dev@cloudstack.apache.org
> >> >Cc: Rajesh Battala; Venkata SwamyBabu Budumuru
> >> >Subject: RE: Marvin tests for VPC - why create VPC offering?
> >> >
> >> >
> >> >> -Original Message-
> >> >> From: Prasanna Santhanam [mailto:t...@apache.org]
> >> >> Sent: Thursday, September 12, 2013 11:55 AM
> >> >> To: dev@cloudstack.apache.org
> >> >> Cc: Rajesh Battala; Venkata SwamyBabu Budumuru
> >> >> Subject: Re: Marvin tests for VPC - why create VPC offering?
> >> >>
> >> >> See inline, there seems to be a bug in the design.
> >> >>
> >> >> On Thu, Sep 12, 2013 at 05:53:45AM +, Sowmya Krishnan wrote:
> >> >> > > -Original Message-
> >> >> > > From: Prasanna Santhanam [mailto:t...@apache.org]
> >> >> > > Sent: Thursday, September 12, 2013 11:07 AM
> >> >> > > To: dev@cloudstack.apache.org
> >> >> > > Subject: Re: Marvin tests for VPC - why create VPC offering?
> >> >> > >
> >> >> > > On Thu, Sep 12, 2013 at 05:15:16AM +, Sowmya Krishnan wrote:
> >> >> > > > I find for most of the VPC tests we create a new VPC
> >> >> > > > Offering which provides almost the same set of services as
> >> >> > > > the "Default VPC
> >> >> Offering"
> >> >> > > > already available by default. We also have a separat

RE: Apache CloudStack 4.2.0 (fifth round)

[Likitha Shetty]

+1 
Tested VM life cycle with VMware in advanced zone and AWSAPI EC2 interface.

Thanks,
Likitha 

>-Original Message-
>From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
>Sent: Saturday, September 14, 2013 4:43 AM
>To: dev@cloudstack.apache.org
>Subject: Apache CloudStack 4.2.0 (fifth round)
>
>
>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: c1e24ff89f6d14d6ae74d12dbca108c35449030f
>
>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+proced
>ure
>
>Vote will be open for 72 hours (Wednesday 9/18 End of Day PST).
>
>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 CloudMonkey 5.0.0 (first round)

[sebgoa]

+1 (binding)


Started this wiki page:

https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudMonkey+testing+procedure



On Sep 15, 2013, at 6:52 PM, Marcus Sorensen  wrote:

> +1 (binding)
> 
> Downloaded release artifacts, installed in ubuntu devcloud-kvm, tested
> various sync, async calls and cloudmonkey scripts. Seems to work as
> well or better than previous releases.
> 
> On Sun, Sep 15, 2013 at 6:09 AM, Rohit Yadav  wrote:
>> +1
>> 
>> Build with cache, checked readme etc. files and installed:
>> https://pbs.twimg.com/media/BUM97ZjCQAAOM5v.png:large
>> 
>> Since the build cache was created from/against ACS 4.2, as long as the APIs
>> were compatible so will cloudmonkey be for 4.2 and previous releases
>> including 4.x, 3.x ones.
>> 
>> Thanks Chip!
>> 
>> Regards.
>> 
>> 
>> On Fri, Sep 13, 2013 at 6:53 PM, Chip Childers 
>> wrote:
>> 
>>> I've created a 5.0.0 release of cloudmonkey, with the following artifacts
>>> up for a
>>> vote:
>>> 
>>> Git Branch and Commit SH:
>>> 
>>> https://git-wip-us.apache.org/repos/asf?p=cloudstack-cloudmonkey.git;a=shortlog;h=refs/heads/5.0
>>> Commit: 767bfbe084e24d441f1ad73ace183c09f26a276b
>>> 
>>> List of changes:
>>> 
>>> https://git-wip-us.apache.org/repos/asf?p=cloudstack-cloudmonkey.git;a=blob;f=CHANGES;h=54f2e32357b0a726dc6f202e4897ed4af531f8ab;hb=refs/heads/5.0
>>> 
>>> Source release (checksums and signatures are available at the same
>>> location):
>>> https://dist.apache.org/repos/dist/dev/cloudstack/cloudmonkey-5.0.0/
>>> 
>>> PGP release keys (signed using 94BE0D7C):
>>> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>>> 
>>> I have not created testing instructions for this release artifact, but
>>> would appreciate help documenting it as people to it.
>>> 
>>> Vote will be open for at least 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)
>>> 
>>> Thanks,
>>> 
>>> -chip
>>> 

Re: [VOTE] Apache CloudStack CloudMonkey 5.0.0 (first round)

[Ian Duffy]

+1

Download, installed in clean virtualenv. Executed commands against the
cloudstack simulator.


On 16 September 2013 09:24, sebgoa  wrote:

> +1 (binding)
>
>
> Started this wiki page:
>
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudMonkey+testing+procedure
>
>
>
> On Sep 15, 2013, at 6:52 PM, Marcus Sorensen  wrote:
>
> > +1 (binding)
> >
> > Downloaded release artifacts, installed in ubuntu devcloud-kvm, tested
> > various sync, async calls and cloudmonkey scripts. Seems to work as
> > well or better than previous releases.
> >
> > On Sun, Sep 15, 2013 at 6:09 AM, Rohit Yadav 
> wrote:
> >> +1
> >>
> >> Build with cache, checked readme etc. files and installed:
> >> https://pbs.twimg.com/media/BUM97ZjCQAAOM5v.png:large
> >>
> >> Since the build cache was created from/against ACS 4.2, as long as the
> APIs
> >> were compatible so will cloudmonkey be for 4.2 and previous releases
> >> including 4.x, 3.x ones.
> >>
> >> Thanks Chip!
> >>
> >> Regards.
> >>
> >>
> >> On Fri, Sep 13, 2013 at 6:53 PM, Chip Childers <
> chip.child...@sungard.com>wrote:
> >>
> >>> I've created a 5.0.0 release of cloudmonkey, with the following
> artifacts
> >>> up for a
> >>> vote:
> >>>
> >>> Git Branch and Commit SH:
> >>>
> >>>
> https://git-wip-us.apache.org/repos/asf?p=cloudstack-cloudmonkey.git;a=shortlog;h=refs/heads/5.0
> >>> Commit: 767bfbe084e24d441f1ad73ace183c09f26a276b
> >>>
> >>> List of changes:
> >>>
> >>>
> https://git-wip-us.apache.org/repos/asf?p=cloudstack-cloudmonkey.git;a=blob;f=CHANGES;h=54f2e32357b0a726dc6f202e4897ed4af531f8ab;hb=refs/heads/5.0
> >>>
> >>> Source release (checksums and signatures are available at the same
> >>> location):
> >>> https://dist.apache.org/repos/dist/dev/cloudstack/cloudmonkey-5.0.0/
> >>>
> >>> PGP release keys (signed using 94BE0D7C):
> >>> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> >>>
> >>> I have not created testing instructions for this release artifact, but
> >>> would appreciate help documenting it as people to it.
> >>>
> >>> Vote will be open for at least 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)
> >>>
> >>> Thanks,
> >>>
> >>> -chip
> >>>
>
>

[Responsiveness report] users 2013w37

[Daan Hoogland]

http://markmail.org/message/cido22ky72rfxldm Failed to start instance
VM[DomainRouter by Andreas Huser
http://markmail.org/message/zd75ljjvipvaaq2u cs 4.2 HA by Valery Ciareszka
http://markmail.org/message/cpz2qgg2bdxcehqt stumped on Adv Network,
SNAT by Noel Kendall

Re: [VOTE] Apache CloudStack CloudMonkey 5.0.0 (first round)

[sebgoa]

On Sep 16, 2013, at 10:36 AM, Ian Duffy  wrote:

> +1
> 
> Download, installed in clean virtualenv. Executed commands against the
> cloudstack simulator.
> 
> 

Ian, do you mind added that bit on virtualenv in the wiki page I started…thx

> On 16 September 2013 09:24, sebgoa  wrote:
> 
>> +1 (binding)
>> 
>> 
>> Started this wiki page:
>> 
>> 
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudMonkey+testing+procedure
>> 
>> 
>> 
>> On Sep 15, 2013, at 6:52 PM, Marcus Sorensen  wrote:
>> 
>>> +1 (binding)
>>> 
>>> Downloaded release artifacts, installed in ubuntu devcloud-kvm, tested
>>> various sync, async calls and cloudmonkey scripts. Seems to work as
>>> well or better than previous releases.
>>> 
>>> On Sun, Sep 15, 2013 at 6:09 AM, Rohit Yadav 
>> wrote:
 +1
 
 Build with cache, checked readme etc. files and installed:
 https://pbs.twimg.com/media/BUM97ZjCQAAOM5v.png:large
 
 Since the build cache was created from/against ACS 4.2, as long as the
>> APIs
 were compatible so will cloudmonkey be for 4.2 and previous releases
 including 4.x, 3.x ones.
 
 Thanks Chip!
 
 Regards.
 
 
 On Fri, Sep 13, 2013 at 6:53 PM, Chip Childers <
>> chip.child...@sungard.com>wrote:
 
> I've created a 5.0.0 release of cloudmonkey, with the following
>> artifacts
> up for a
> vote:
> 
> Git Branch and Commit SH:
> 
> 
>> https://git-wip-us.apache.org/repos/asf?p=cloudstack-cloudmonkey.git;a=shortlog;h=refs/heads/5.0
> Commit: 767bfbe084e24d441f1ad73ace183c09f26a276b
> 
> List of changes:
> 
> 
>> https://git-wip-us.apache.org/repos/asf?p=cloudstack-cloudmonkey.git;a=blob;f=CHANGES;h=54f2e32357b0a726dc6f202e4897ed4af531f8ab;hb=refs/heads/5.0
> 
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/cloudmonkey-5.0.0/
> 
> PGP release keys (signed using 94BE0D7C):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> 
> I have not created testing instructions for this release artifact, but
> would appreciate help documenting it as people to it.
> 
> Vote will be open for at least 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)
> 
> Thanks,
> 
> -chip
> 
>> 
>> 

Re: Apache CloudStack 4.2.0 (fifth round)

[sebgoa]

+1 (binding)

Followed testing procedure.
Added Cloudmonkey 5.0.0 basic tests
Ran AWSAPI server and started instance with boto

-sebastien

On Sep 16, 2013, at 10:18 AM, Likitha Shetty  wrote:

> +1 
> Tested VM life cycle with VMware in advanced zone and AWSAPI EC2 interface.
> 
> Thanks,
> Likitha 
> 
>> -Original Message-
>> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
>> Sent: Saturday, September 14, 2013 4:43 AM
>> To: dev@cloudstack.apache.org
>> Subject: Apache CloudStack 4.2.0 (fifth round)
>> 
>> 
>> 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: c1e24ff89f6d14d6ae74d12dbca108c35449030f
>> 
>> 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+proced
>> ure
>> 
>> Vote will be open for 72 hours (Wednesday 9/18 End of Day PST).
>> 
>> 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 CloudMonkey 5.0.0 (first round)

[Ian Duffy]

> Ian, do you mind added that bit on virtualenv in the wiki page I
started…thx

Will do, setting up virtualenv is OS specific. Will cover it for CentOS.


On 16 September 2013 09:40, sebgoa  wrote:

>
> On Sep 16, 2013, at 10:36 AM, Ian Duffy  wrote:
>
> > +1
> >
> > Download, installed in clean virtualenv. Executed commands against the
> > cloudstack simulator.
> >
> >
>
> Ian, do you mind added that bit on virtualenv in the wiki page I
> started…thx
>
> > On 16 September 2013 09:24, sebgoa  wrote:
> >
> >> +1 (binding)
> >>
> >>
> >> Started this wiki page:
> >>
> >>
> >>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudMonkey+testing+procedure
> >>
> >>
> >>
> >> On Sep 15, 2013, at 6:52 PM, Marcus Sorensen 
> wrote:
> >>
> >>> +1 (binding)
> >>>
> >>> Downloaded release artifacts, installed in ubuntu devcloud-kvm, tested
> >>> various sync, async calls and cloudmonkey scripts. Seems to work as
> >>> well or better than previous releases.
> >>>
> >>> On Sun, Sep 15, 2013 at 6:09 AM, Rohit Yadav 
> >> wrote:
>  +1
> 
>  Build with cache, checked readme etc. files and installed:
>  https://pbs.twimg.com/media/BUM97ZjCQAAOM5v.png:large
> 
>  Since the build cache was created from/against ACS 4.2, as long as the
> >> APIs
>  were compatible so will cloudmonkey be for 4.2 and previous releases
>  including 4.x, 3.x ones.
> 
>  Thanks Chip!
> 
>  Regards.
> 
> 
>  On Fri, Sep 13, 2013 at 6:53 PM, Chip Childers <
> >> chip.child...@sungard.com>wrote:
> 
> > I've created a 5.0.0 release of cloudmonkey, with the following
> >> artifacts
> > up for a
> > vote:
> >
> > Git Branch and Commit SH:
> >
> >
> >>
> https://git-wip-us.apache.org/repos/asf?p=cloudstack-cloudmonkey.git;a=shortlog;h=refs/heads/5.0
> > Commit: 767bfbe084e24d441f1ad73ace183c09f26a276b
> >
> > List of changes:
> >
> >
> >>
> https://git-wip-us.apache.org/repos/asf?p=cloudstack-cloudmonkey.git;a=blob;f=CHANGES;h=54f2e32357b0a726dc6f202e4897ed4af531f8ab;hb=refs/heads/5.0
> >
> > Source release (checksums and signatures are available at the same
> > location):
> > https://dist.apache.org/repos/dist/dev/cloudstack/cloudmonkey-5.0.0/
> >
> > PGP release keys (signed using 94BE0D7C):
> > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> >
> > I have not created testing instructions for this release artifact,
> but
> > would appreciate help documenting it as people to it.
> >
> > Vote will be open for at least 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)
> >
> > Thanks,
> >
> > -chip
> >
> >>
> >>
>
>

[Responsiveness report] dev 2013w36

[Daan Hoogland]

http://markmail.org/message/yk4y5va2arcun7b6 Error - duplicate entry
for public ip address by Gaurav Aradhye
http://markmail.org/message/7ejdx3dsc5u5hpr4 unable to add host in 4.2
using Devcloud2 environment by Punith s
http://markmail.org/message/winj27dosfesf5gr create ubuntu 12.04
template from snapshot,then create new vm from this template and the
new vm failed to start!!! by William Jiang

Request for Comments on responsiveness reports

[Daan Hoogland]

H,

I made a short summary of how I have been working on the weekly reports so far.
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Responsiveness+report

any comment is welcome,
Daan

Re: Handling Public network traffic in a plugin

[Daan Hoogland]

Dave,

As I suspected I used guest type for this offering:

   def createPrivateGatewayNetworkOffering(self, conn):
  offers = self.listNetworkOfferings(conn,
name="NiciraNvpPrivateGatewayNetwork")
  if offers != None:
 return offers[0].id
  # else create it
  cno = createNetworkOffering.createNetworkOfferingCmd()
  cno.name = "NiciraNvpPrivateGatewayNetwork"
  cno.displaytext = "VPC private gateway network offering with Nicira NVP"
  cno.traffictype = "GUEST"
  cno.specifyvlan = True
  cno.specifyipranges = True
  cno.availability = "Optional"
  cno.conservemode = True
  cno.guestiptype = "Isolated"
  cno.usevpc = True
  cno.systemonly = True
  cno.supportedservices = [ "Connectivity" ]
  cno.serviceproviderlist = [ { "service": "Connectivity",
"provider": "NiciraNVP"} ]
  #cno.servicecapabilitylist
  cno.tags = [ "nicira-based" ]
  #cno.networkrate
  #cno.serviceofferingid

  try:
 resp = conn.marvin_request(cno)
  except:
 print "nicira based offering already exists"
 #todo query and return

Do you know if this is going to be a problem? It works for me and I
don't see any objections to it.

regards,
Daan

On Fri, Sep 6, 2013 at 12:30 PM, Daan Hoogland  wrote:
> H Dave,
>
> I actually didn't give 'guest' to much thought. I had to change the
> vpcvirtualrouter. It calls the right guru based on the netoffer.
> I feel I am not answering your question.
> Are you in Amsterdam the 22th of november? A hackathon on this seems
> appropriate.
>
> mobile biligual spell checker used
>
> Op 5 sep. 2013 03:08 schreef "Dave Cahill"  het
> volgende:
>
>> Hi,
>>
>> The creste neroffer api accepts system=true. The creation should be part
>> of
>> > the plugin install, though.
>>
>>
>> Ah, sounds interesting! Does it also accept creating networkofferings for
>> Traffic types other than Guest? Looking at 4.2, createNetworkOffering does
>> a check to restrict to Guest traffic only (from ConfigurationManagerImpl):
>>
>> // Only GUEST traffic type is supported in Acton
>> if (trafficType != TrafficType.Guest) {
>> throw new InvalidParameterValueException("Only traffic type " +
>> TrafficType.Guest
>> + " is supported in the current release");
>> }
>>
>> One question I had about the external hosted private gateways VPC feature
>> was whether the change involves allowing plugins to handle VPC itself
>> (routing between VPC subnets etc) instead of the VpcVirtualRouter? Last
>> time I looked at having our plugin provide VPC (a few months ago), the
>> VpcVirtualRouter was hardcoded in several places as the only provider.
>>
>> Thanks,
>> Dave.
>>
>>
>>
>>
>> On Thu, Sep 5, 2013 at 4:08 AM, Daan Hoogland
>> wrote:
>>
>> > H Dave,
>> >
>> > Sorry about the white space.
>> >
>> > The creste neroffer api accepts system=true. The creation should be part
>> > of
>> > the plugin install, though.
>> >
>> > I will have to write more doc and any specific questions would help.
>> >
>> > mobile biligual spell checker used
>> > Op 4 sep. 2013 11:45 schreef "Dave Cahill"  het
>> > volgende:
>> >
>> > > Hi Daan,
>> > >
>> > > My take on things is to add a network offering for vpc private
>> > > gateways.
>> > I
>> > > > extend the api
>> > > > call with the optional netoffer.
>> > >
>> > >
>> > > I read the wiki page on that feature [1] and the most recent code
>> > > review,
>> > > but I don't fully understand it yet - is there any other documentation
>> > > /
>> > > code around?
>> > >
>> > > replacing the guru does not seem like the way to go to me. I'd
>> > > > say that the offer is what drives what guru/element to use.
>> > >
>> > >
>> > > That would be nicer. When we implemented Public traffic via MidoNet
>> > > back
>> > in
>> > > February / March, it wasn't possible to create System offerings /
>> > > private
>> > > offerings - if that changed, it would be great.
>> > >
>> > > Thanks,
>> > > Dave.
>> > >
>> > > [1]
>> > >
>> > >
>> >
>> > https://cwiki.apache.org/confluence/display/CLOUDSTACK/external+hosted+private+gateways
>> > >
>> > >
>> > > On Tue, Sep 3, 2013 at 9:25 PM, Daan Hoogland > > > >wrote:
>> > >
>> > > > H Dave,
>> > > >
>> > > > It seems we are working on similar things, David. My take on things
>> > > > is
>> > > > to add a network offering for vpc private gateways. I extend the api
>> > > > call with the optional netoffer. It sounds like you are doing
>> > > > something slightly different but we are bound to break each others
>> > > > code as well, even when i am working with private networks and you
>> > > > with public ones.
>> > > >
>> > > > In general the extensibility of net-implementations does need some
>> > > > work. replacing the guru does not seem like the way to go to me. I'd
>> > > > say that the offer is what drives what guru/element to use.
>> > > >
>> > > > regards,
>> > > > Daan
>> > > >
>> > > > On Tue, Sep 3, 2013 at 12:02 PM, Dave Cahill 
>> > > wrote:
>> > > > > Hi,

Re: Error - duplicate entry for public ip address

[Gaurav Aradhye]

HI all,

That was a bug in CS and is discussed on another mail thread.
This thread can be safely ignored.

Regards,
Gaurav


On Mon, Sep 2, 2013 at 3:04 PM, Gaurav Aradhye
wrote:

> Hi all,
>
> While associating a portable public ip, I'm getting following error:
>
> errorText:Entity already exists:
>
> Log says:
> com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException:
> Duplicate entry 'x.x.x.x - x' for key 'public_ip_address'.
>
> While the ip address has not been associated before, and I can see it
> marked as free, Can anyone point to possible reason why is this happening?
> If the IP address lists as free, how does it have entry in associated ips
> already?
>
> A "non-portable" ip address get assiciated properly, but error is for
> portable one.
>
> Regards,
> Gaurav
>

Re: [Responsiveness report] dev 2013w36

[Gaurav Aradhye]

Hello,

http://markmail.org/message/yk4y5va2arcun7b6 Error - duplicate entry
for public ip address by Gaurav Aradhye

This can be safely ignored. Just sent out a mail.

Regards,
Gaurav


On Mon, Sep 16, 2013 at 2:18 PM, Daan Hoogland wrote:

> http://markmail.org/message/yk4y5va2arcun7b6 Error - duplicate entry
> for public ip address by Gaurav Aradhye
> http://markmail.org/message/7ejdx3dsc5u5hpr4 unable to add host in 4.2
> using Devcloud2 environment by Punith s
> http://markmail.org/message/winj27dosfesf5gr create ubuntu 12.04
> template from snapshot,then create new vm from this template and the
> new vm failed to start!!! by William Jiang
>

Re: HA redundant virtual router

[Daan Hoogland]

H Sheng,

>From your doc I don't read the reasons for disabling HA for RVR.

I do see some possible glitches though. One is that a newly installed
router should always have higher prio if the master cannot be reached.
Something similar should happen on rule programming.

To deal with the 255 limit on prios they could be reset to the minimum
as soon as both routers are found again.

Am I correct?

thanks,
Daan

On Fri, Sep 6, 2013 at 12:27 AM, Sheng Yang  wrote:
> Here is the doc.
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Redundant+Virtual+Router+Functional+Spec
>
> It's not extremely detail, but describe today's design generally.
>
> --Sheng
>
>
> On Thu, Aug 29, 2013 at 8:17 AM, Daan Hoogland 
> wrote:
>>
>> ok,
>>
>> let's postpone the discussion till you are at least halve done. We
>> will of course continue to deliberate on what we need internally.
>>
>> Daan
>>
>> On Thu, Aug 29, 2013 at 5:08 PM, Sheng Yang  wrote:
>> > Hi Daan,
>> >
>> > As I said, I am writing a design doc to describe the current redundant
>> > router policy, to help understanding redundant router. Current it
>> > doesn't
>> > support VPC, so how to implement it in VPC is still open to discuss.
>> >
>> > --Sheng
>> >
>> >
>> > On Thu, Aug 29, 2013 at 4:26 AM, Daan Hoogland 
>> > wrote:
>> >>
>> >> Sheng,
>> >>
>> >> just to make sure; You are going to write this document? I see Roeland
>> >> understood your mail like this.
>> >>
>> >> When you do, I'd like you to keep in mind that we also want redundant
>> >> routers within a VPC to ensure ACS upgrades are more seamless for
>> >> customer application groups and - dtap streets. If you need any help
>> >> on writing such a doc, let me know.
>> >>
>> >> kind regards,
>> >> Daan
>> >>
>> >> On Thu, Aug 29, 2013 at 1:13 PM, Roeland Kuipers
>> >>  wrote:
>> >> > Hi Sheng,
>> >> >
>> >> > Thanks for the info. Looking forward to the design doc, I trust this
>> >> > will make things clearer.
>> >> > In the meantime will be doing some research and thinking too, to see
>> >> > how
>> >> > we can improve things to also have HA on the RvR in a safe way.
>> >> > We will share this once ready.
>> >> >
>> >> > Thanks,
>> >> > Roeland
>> >> >
>> >> >
>> >> > From: Sheng Yang [mailto:sh...@yasker.org]
>> >> > Sent: donderdag 29 augustus 2013 0:19
>> >> > To: 
>> >> > Cc: int-cloud; Daan Hoogland
>> >> > Subject: Re: HA redundant virtual router
>> >> >
>> >> > Hi Roeland,
>> >> >
>> >> > I would write a design doc to explain how redundant router works
>> >> > currently. For example, for the point 2, we have to force BACKUP
>> >> > become
>> >> > MASTER because:
>> >> >
>> >> > 1. CS cannot communicate with MASTER at the time
>> >> > 2. CS can communicate with BACKUP.
>> >> > 3. Rule has to be programmed immediately.
>> >> > 4. In case old MASTER come back, it should yield to the VR with
>> >> > updated
>> >> > rule, rather than preempt the updated VR.
>> >> >
>> >> > In this case, CS need to communicate with RvR to program the new
>> >> > rule,
>> >> > thus it need to intervene the RvR to ensure that if there is only one
>> >> > VR got
>> >> > the rule, it should become MASTER.
>> >> >
>> >> > Still, I would write a doc later to try to cover every concern of RvR
>> >> > design.
>> >> >
>> >> > --Sheng
>> >> >
>> >> > On Tue, Aug 27, 2013 at 3:40 AM, Roeland Kuipers
>> >> > mailto:rkuip...@schubergphilis.com>>
>> >> > wrote:
>> >> > Hi Sheng,
>> >> >
>> >> > Thanks for your reply. I'll see if we can replay this scenario.
>> >> >
>> >> > With respect to point 1: a good principal IMHO.
>> >> >
>> >> > Point 2: Why do we force a keepalived node to become master and not
>> >> > wait
>> >> > for keepalived to become master? This way there is less reason to
>> >> > intervene
>> >> > and less risk of multiple masters? As we have seen this behavior with
>> >> > RvR
>> >> > without HA in the past. The downside that updates to rules do not
>> >> > function
>> >> > until backup becomes master. But maybe this is wise anyways since
>> >> > there is
>> >> > something wrong. This conflicts a bit with point 2 as we do intervene
>> >> > here.
>> >> >
>> >> > Point 3: In my opinion keepalived is solid enough to leave this
>> >> > responsibility with keepalived and that CS just should check the
>> >> > state and
>> >> > not fiddle with priorities to force masters. Because there is
>> >> > obviously a
>> >> > reason why BACKUP refuses to become master.
>> >> > I think we should let keepalived prevent multiple master as is
>> >> > designed
>> >> > to prevent this. Or do I miss something here?
>> >> > Actually in the scenario you described, with a functioning guest
>> >> > network, keepalived should be able to handle this situation if we
>> >> > make sure
>> >> > all routers have different prios.
>> >> >
>> >> > I still have the opinion HA and RvR are different mechanisms.
>> >> >
>> >> > So what do you think is necessary to have the possibility of HA icw
>> >> > RvR?
>> >> > We have a clear business requir

Re: Error - duplicate entry for public ip address

[Wei ZHOU]

What is the ticket for this issue? More details?


2013/9/16 Gaurav Aradhye 

> HI all,
>
> That was a bug in CS and is discussed on another mail thread.
> This thread can be safely ignored.
>
> Regards,
> Gaurav
>
>
> On Mon, Sep 2, 2013 at 3:04 PM, Gaurav Aradhye
> wrote:
>
> > Hi all,
> >
> > While associating a portable public ip, I'm getting following error:
> >
> > errorText:Entity already exists:
> >
> > Log says:
> >
> com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException:
> > Duplicate entry 'x.x.x.x - x' for key 'public_ip_address'.
> >
> > While the ip address has not been associated before, and I can see it
> > marked as free, Can anyone point to possible reason why is this
> happening?
> > If the IP address lists as free, how does it have entry in associated ips
> > already?
> >
> > A "non-portable" ip address get assiciated properly, but error is for
> > portable one.
> >
> > Regards,
> > Gaurav
> >
>

Re: Error - duplicate entry for public ip address

[Gaurav Aradhye]

HI Wei,

Here's the ticket: https://issues.apache.org/jira/browse/CLOUDSTACK-4596

The issue is that CS is allowing two public or portable ip ranges to
overlap, with different vlan IDs. This is not a valid behavior.

Regards,
Gaurav


On Mon, Sep 16, 2013 at 3:06 PM, Wei ZHOU  wrote:

> What is the ticket for this issue? More details?
>
>
> 2013/9/16 Gaurav Aradhye 
>
> > HI all,
> >
> > That was a bug in CS and is discussed on another mail thread.
> > This thread can be safely ignored.
> >
> > Regards,
> > Gaurav
> >
> >
> > On Mon, Sep 2, 2013 at 3:04 PM, Gaurav Aradhye
> > wrote:
> >
> > > Hi all,
> > >
> > > While associating a portable public ip, I'm getting following error:
> > >
> > > errorText:Entity already exists:
> > >
> > > Log says:
> > >
> >
> com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException:
> > > Duplicate entry 'x.x.x.x - x' for key 'public_ip_address'.
> > >
> > > While the ip address has not been associated before, and I can see it
> > > marked as free, Can anyone point to possible reason why is this
> > happening?
> > > If the IP address lists as free, how does it have entry in associated
> ips
> > > already?
> > >
> > > A "non-portable" ip address get assiciated properly, but error is for
> > > portable one.
> > >
> > > Regards,
> > > Gaurav
> > >
> >
>

Re: Apache CloudStack 4.2.0 (fifth round)

[Wido den Hollander]

+1 (binding)

I verified what I could:

- Build DEB packages
- Installed DEB packages
- Tested RBD/Ceph functionality

CloudStack is a big project, so I only tested the portion of CloudStack 
I'm most familiar with and my vote is based on that.


Wido

On 09/16/2013 10:41 AM, sebgoa wrote:

+1 (binding)

Followed testing procedure.
Added Cloudmonkey 5.0.0 basic tests
Ran AWSAPI server and started instance with boto

-sebastien

On Sep 16, 2013, at 10:18 AM, Likitha Shetty  wrote:


+1
Tested VM life cycle with VMware in advanced zone and AWSAPI EC2 interface.

Thanks,
Likitha


-Original Message-
From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
Sent: Saturday, September 14, 2013 4:43 AM
To: dev@cloudstack.apache.org
Subject: Apache CloudStack 4.2.0 (fifth round)


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: c1e24ff89f6d14d6ae74d12dbca108c35449030f

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+proced
ure

Vote will be open for 72 hours (Wednesday 9/18 End of Day PST).

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)

Libvirt-java 0.5.0 has been released

[Wido den Hollander]

Hi,

I worked with the RedHat guys last week to get libvirt-java 0.5.0 
released which has some nice new features for us:


- Supports different XML on destination host during migration
- Supports resizing volumes
- Supports more snapshot functionalities

I took the liberty to depend on 0.5.0 in master and also merge in the 
code for the VNC listen, we now no longer listen on 0.0.0.0 for VNC, 
which was a security issue imho.


The reason I'm bringing this to the list is that we can simplify some 
code around resizing volumes and snapshotting where we currently have 
some nasty scripts to do the work.


See my commits in libvirt-java: 
http://www.libvirt.org/git/?p=libvirt-java.git;a=summary


So keep in mind libvirt-java has some new features!

Wido

Re: Review Request 14063: CLOUDSTACK - 4640: Fixed indentation issues in CPU limits tests

[sailaja mada]

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

Ship it!


Ship It!

- sailaja mada


On Sept. 11, 2013, 6:22 a.m., Gaurav Aradhye wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/14063/
> ---
> 
> (Updated Sept. 11, 2013, 6:22 a.m.)
> 
> 
> Review request for cloudstack and Prasanna Santhanam.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Resolved issue 4640:
> Fixed indentation issue in CPU limits files - test_cpu_limits.py and 
> test_project_limits.py
> 
> 
> Diffs
> -
> 
>   test/integration/component/cpu_limits/test_cpu_limits.py 8acf8b7 
>   test/integration/component/cpu_limits/test_project_limits.py 3c432db 
> 
> Diff: https://reviews.apache.org/r/14063/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Gaurav Aradhye
> 
>

Review Request 14147: marvin tests for Persistent networks without running a VM

[Anshul Gangwar]

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

Review request for cloudstack, Likitha Shetty, sailaja mada, and Prasanna 
Santhanam.


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


Repository: cloudstack-git


Description
---

marvin tests for Persistent networks without running a VM


Diffs
-

  test/integration/component/test_persistent_networks.py PRE-CREATION 
  tools/marvin/marvin/integration/lib/base.py 9e46065 

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


Testing
---

ran successfully on  my local advanced zone setup


Thanks,

Anshul Gangwar

Re: Review Request 14063: CLOUDSTACK - 4640: Fixed indentation issues in CPU limits tests

[sailaja mada]

> On Sept. 16, 2013, 10:15 a.m., sailaja mada wrote:
> > Ship It!

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


- sailaja


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


On Sept. 11, 2013, 6:22 a.m., Gaurav Aradhye wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/14063/
> ---
> 
> (Updated Sept. 11, 2013, 6:22 a.m.)
> 
> 
> Review request for cloudstack and Prasanna Santhanam.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Resolved issue 4640:
> Fixed indentation issue in CPU limits files - test_cpu_limits.py and 
> test_project_limits.py
> 
> 
> Diffs
> -
> 
>   test/integration/component/cpu_limits/test_cpu_limits.py 8acf8b7 
>   test/integration/component/cpu_limits/test_project_limits.py 3c432db 
> 
> Diff: https://reviews.apache.org/r/14063/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Gaurav Aradhye
> 
>

Re: Apache CloudStack 4.2.0 (fifth round)

[Prasanna Santhanam]

+1 (binding)

The test infra has deployed advanced zone with kvm and xenserver 6.2
since Saturday and I dont see any new failures [1]. So no regressions.
Also ran the simulator against 4.2 [2]

[1] 
http://jenkins.buildacloud.org/view/cloudstack-qa/job/test-regression-matrix/
[2] http://jenkins.buildacloud.org/view/simulator/job/run-checkin-tests/

On Sun, Sep 15, 2013 at 10:18:48PM -0400, Chip Childers wrote:
> +1 (binding)
> 
> Tested with simulator.
> 
> 
> 
> On Sep 14, 2013, at 5:59 PM, Marcus Sorensen  wrote:
> 
> > +1 (binding)
> >
> > Tested CentOS 6.4 and Ubuntu 12.04.3:
> > create advanced zone
> > create VPC
> > register template
> > create VPC tier
> > create VM on tier w/NFS
> > create VM on tier w/CLM
> > create VM on tier w/Local storage
> > create static NAT to vm, ssh in
> >
> > On Sat, Sep 14, 2013 at 10:28 AM, Rajesh Battala
> >  wrote:
> >> +1
> >>
> >> Tested VM Life cycle in Xenserver and KVM with Advance Zone configuration.
> >>
> >> Thanks
> >> Rajesh Battala
> >>
> >> -Original Message-
> >> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> >> Sent: Saturday, September 14, 2013 4:43 AM
> >> To: dev@cloudstack.apache.org
> >> Subject: Apache CloudStack 4.2.0 (fifth round)
> >>
> >>
> >> 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: c1e24ff89f6d14d6ae74d12dbca108c35449030f
> >>
> >> 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 (Wednesday 9/18 End of Day PST).
> >>
> >> 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)
> >

-- 
Prasanna.,


Powered by BigRock.com

Re: Error - duplicate entry for public ip address

[Wei ZHOU]

got it, thanks
Murali is working on it.


2013/9/16 Gaurav Aradhye 

> HI Wei,
>
> Here's the ticket: https://issues.apache.org/jira/browse/CLOUDSTACK-4596
>
> The issue is that CS is allowing two public or portable ip ranges to
> overlap, with different vlan IDs. This is not a valid behavior.
>
> Regards,
> Gaurav
>
>
> On Mon, Sep 16, 2013 at 3:06 PM, Wei ZHOU  wrote:
>
> > What is the ticket for this issue? More details?
> >
> >
> > 2013/9/16 Gaurav Aradhye 
> >
> > > HI all,
> > >
> > > That was a bug in CS and is discussed on another mail thread.
> > > This thread can be safely ignored.
> > >
> > > Regards,
> > > Gaurav
> > >
> > >
> > > On Mon, Sep 2, 2013 at 3:04 PM, Gaurav Aradhye
> > > wrote:
> > >
> > > > Hi all,
> > > >
> > > > While associating a portable public ip, I'm getting following error:
> > > >
> > > > errorText:Entity already exists:
> > > >
> > > > Log says:
> > > >
> > >
> >
> com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException:
> > > > Duplicate entry 'x.x.x.x - x' for key 'public_ip_address'.
> > > >
> > > > While the ip address has not been associated before, and I can see it
> > > > marked as free, Can anyone point to possible reason why is this
> > > happening?
> > > > If the IP address lists as free, how does it have entry in associated
> > ips
> > > > already?
> > > >
> > > > A "non-portable" ip address get assiciated properly, but error is for
> > > > portable one.
> > > >
> > > > Regards,
> > > > Gaurav
> > > >
> > >
> >
>

Re: Review Request 14061: CLOUDSTACK - 4635: CPU LImits/ test_domain-limits.py - Fixed indentation issue

[sailaja mada]

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

Ship it!


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

- sailaja mada


On Sept. 10, 2013, 12:43 p.m., Gaurav Aradhye wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/14061/
> ---
> 
> (Updated Sept. 10, 2013, 12:43 p.m.)
> 
> 
> Review request for cloudstack and Prasanna Santhanam.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Fixed indentation issue in the test case. Instance was not getting created 
> when api_client not passed.
> Please let me know if you can't apply this patch.  Patch is getting 
> downloaded and is correct, but not getting displayed in RB.
> 
> 
> Diffs
> -
> 
>   test/integration/component/cpu_limits/test_domain_limits.py 2668204 
> 
> Diff: https://reviews.apache.org/r/14061/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Gaurav Aradhye
> 
>

RE: Libvirt-java 0.5.0 has been released

[Rajesh Battala]

Thanks Wido, for resize volume we can call libvirt api instead of script right.
http://libvirt.org/git/?p=libvirt-java.git;a=commit;h=cd00a4b8f25944f6fe2ce3ecb2ac00cbcad8db8d
 

Thanks
Rajesh Battala

-Original Message-
From: Wido den Hollander [mailto:w...@widodh.nl] 
Sent: Monday, September 16, 2013 3:38 PM
To: dev@cloudstack.apache.org
Subject: Libvirt-java 0.5.0 has been released

Hi,

I worked with the RedHat guys last week to get libvirt-java 0.5.0 released 
which has some nice new features for us:

- Supports different XML on destination host during migration
- Supports resizing volumes
- Supports more snapshot functionalities

I took the liberty to depend on 0.5.0 in master and also merge in the code for 
the VNC listen, we now no longer listen on 0.0.0.0 for VNC, which was a 
security issue imho.

The reason I'm bringing this to the list is that we can simplify some code 
around resizing volumes and snapshotting where we currently have some nasty 
scripts to do the work.

See my commits in libvirt-java: 
http://www.libvirt.org/git/?p=libvirt-java.git;a=summary

So keep in mind libvirt-java has some new features!

Wido

Re: Review Request 14060: CLOUDSTACK-4634 - CPU Limits/ test_maximum_limits.py - -Fixed issues arising due to wrong indentation

[ASF Subversion and Git Services]

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


Commit 51da534cce7bd07dcbf1e828a32e27a716b5b0f8 in branch refs/heads/master 
from Gaurav Aradhye
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=51da534 ]

CLOUDSTACK-4634: Fixed issue arising due to wrong indentation


- ASF Subversion and Git Services


On Sept. 10, 2013, 11:22 a.m., Gaurav Aradhye wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/14060/
> ---
> 
> (Updated Sept. 10, 2013, 11:22 a.m.)
> 
> 
> Review request for cloudstack and Prasanna Santhanam.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> The indentation in createInstance function was wrong. Whenever we would pass 
> value to api_client parameter, the instance would not get created. Fixed the 
> indentation.
> 
> 
> Diffs
> -
> 
>   test/integration/component/cpu_limits/test_maximum_limits.py 2302504 
> 
> Diff: https://reviews.apache.org/r/14060/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Gaurav Aradhye
> 
>

Re: Apache CloudStack 4.2.0 (fifth round)

[Ian Duffy]

+1

Ran against simulator.


On 16 September 2013 11:25, Prasanna Santhanam  wrote:

> +1 (binding)
>
> The test infra has deployed advanced zone with kvm and xenserver 6.2
> since Saturday and I dont see any new failures [1]. So no regressions.
> Also ran the simulator against 4.2 [2]
>
> [1]
> http://jenkins.buildacloud.org/view/cloudstack-qa/job/test-regression-matrix/
> [2] http://jenkins.buildacloud.org/view/simulator/job/run-checkin-tests/
>
> On Sun, Sep 15, 2013 at 10:18:48PM -0400, Chip Childers wrote:
> > +1 (binding)
> >
> > Tested with simulator.
> >
> >
> >
> > On Sep 14, 2013, at 5:59 PM, Marcus Sorensen 
> wrote:
> >
> > > +1 (binding)
> > >
> > > Tested CentOS 6.4 and Ubuntu 12.04.3:
> > > create advanced zone
> > > create VPC
> > > register template
> > > create VPC tier
> > > create VM on tier w/NFS
> > > create VM on tier w/CLM
> > > create VM on tier w/Local storage
> > > create static NAT to vm, ssh in
> > >
> > > On Sat, Sep 14, 2013 at 10:28 AM, Rajesh Battala
> > >  wrote:
> > >> +1
> > >>
> > >> Tested VM Life cycle in Xenserver and KVM with Advance Zone
> configuration.
> > >>
> > >> Thanks
> > >> Rajesh Battala
> > >>
> > >> -Original Message-
> > >> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> > >> Sent: Saturday, September 14, 2013 4:43 AM
> > >> To: dev@cloudstack.apache.org
> > >> Subject: Apache CloudStack 4.2.0 (fifth round)
> > >>
> > >>
> > >> 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: c1e24ff89f6d14d6ae74d12dbca108c35449030f
> > >>
> > >> 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 (Wednesday 9/18 End of Day PST).
> > >>
> > >> 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)
> > >
>
> --
> Prasanna.,
>
> 
> Powered by BigRock.com
>
>

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

[sailaja mada]

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

Ship it!


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

- sailaja mada


On Sept. 12, 2013, 10:19 a.m., Gaurav Aradhye wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/11626/
> ---
> 
> (Updated Sept. 12, 2013, 10:19 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 
> 
> Diff: https://reviews.apache.org/r/11626/diff/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Gaurav Aradhye
> 
>

Re: Libvirt-java 0.5.0 has been released

[Wei ZHOU]

Thanks Wido.

Do you know the minimal requirement of libvirt if we use libvirt-java 0.5.0
?


2013/9/16 Wido den Hollander 

> Hi,
>
> I worked with the RedHat guys last week to get libvirt-java 0.5.0 released
> which has some nice new features for us:
>
> - Supports different XML on destination host during migration
> - Supports resizing volumes
> - Supports more snapshot functionalities
>
> I took the liberty to depend on 0.5.0 in master and also merge in the code
> for the VNC listen, we now no longer listen on 0.0.0.0 for VNC, which was a
> security issue imho.
>
> The reason I'm bringing this to the list is that we can simplify some code
> around resizing volumes and snapshotting where we currently have some nasty
> scripts to do the work.
>
> See my commits in libvirt-java: http://www.libvirt.org/git/?p=**
> libvirt-java.git;a=summary
>
> So keep in mind libvirt-java has some new features!
>
> Wido
>

Re: Review Request 14079: marvin tests for IP Address reservation within a network

[Anshul Gangwar]

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

(Updated Sept. 16, 2013, 11:11 a.m.)


Review request for cloudstack, Saksham Srivastava and Prasanna Santhanam.


Changes
---

removed the extraneous parameters from virtual_machine json


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


Repository: cloudstack-git


Description
---

marvin tests for IP Address reservation within a network 


Diffs (updated)
-

  test/integration/component/test_ip_reservation.py PRE-CREATION 
  tools/marvin/marvin/integration/lib/base.py fa4cc82 

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


Testing
---

ran successfully on  my local advanced zone setup


Thanks,

Anshul Gangwar

Re: Review Request 14079: marvin tests for IP Address reservation within a network

[abhinav roy]

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

Ship it!


Ship It!

- abhinav roy


On Sept. 16, 2013, 11:11 a.m., Anshul Gangwar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/14079/
> ---
> 
> (Updated Sept. 16, 2013, 11:11 a.m.)
> 
> 
> Review request for cloudstack, Saksham Srivastava and Prasanna Santhanam.
> 
> 
> Bugs: https://issues.apache.org/jira/browse/CLOUDSTACK-2266
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> marvin tests for IP Address reservation within a network 
> 
> 
> Diffs
> -
> 
>   test/integration/component/test_ip_reservation.py PRE-CREATION 
>   tools/marvin/marvin/integration/lib/base.py fa4cc82 
> 
> Diff: https://reviews.apache.org/r/14079/diff/
> 
> 
> Testing
> ---
> 
> ran successfully on  my local advanced zone setup
> 
> 
> Thanks,
> 
> Anshul Gangwar
> 
>

Primary store (PS) failure/outage

[Koushik Das]

Currently the way Cloudstack deals with PS failure is to reboot all hosts 
associated with the cluster. Selectively cleaning up the affected VMs would 
have been the best option, but since issues were seen with stopping VMs on the 
hypervisors (at least in Xenserver 5.6 [1]) reboot was the next option. The 
down side with this approach is if there are more than one PS in the cluster 
then healthy VMs will unnecessarily get affected due to host reboots.

Recently I tried this scenario using both XS 6.1 and 6.2. On 6.1 I think the 
behaviour is similar to 5.6, if the PS is not available then any operation the 
VM like shutdown would hang (waited for more than 30 mins and the operation was 
still stuck). But on 6.2 looks like these scenarios are handled more 
gracefully. In 6.2 on doing a shutdown the VMs power state was changed to 
'halted' and then it was possible to even destroy the VM. Based on this I think 
that at least for XS 6.2 we can do a selective VM cleanup if the PS is not 
available. For older XS version the existing approach would still be used.

Thoughts/comments?

Also for KVM the same approach is used. Can someone let me know if newer 
versions of KVM can handle primary storage failure in a better way wrt to VM 
operations? In that case for KVM also the behaviour can be changed.

For Vmware since it is an externally managed cluster I don't think this issue 
exists.

Thanks,
Koushik

[1] https://issues.apache.org/jira/browse/CLOUDSTACK-3367
[2] http://comments.gmane.org/gmane.comp.apache.cloudstack.user/4254

Re: Libvirt-java 0.5.0 has been released

[Jörgen Maas]

Great work Wido!


On Mon, Sep 16, 2013 at 12:51 PM, Wei ZHOU  wrote:

> Thanks Wido.
>
> Do you know the minimal requirement of libvirt if we use libvirt-java 0.5.0
> ?
>
>
> 2013/9/16 Wido den Hollander 
>
> > Hi,
> >
> > I worked with the RedHat guys last week to get libvirt-java 0.5.0
> released
> > which has some nice new features for us:
> >
> > - Supports different XML on destination host during migration
> > - Supports resizing volumes
> > - Supports more snapshot functionalities
> >
> > I took the liberty to depend on 0.5.0 in master and also merge in the
> code
> > for the VNC listen, we now no longer listen on 0.0.0.0 for VNC, which
> was a
> > security issue imho.
> >
> > The reason I'm bringing this to the list is that we can simplify some
> code
> > around resizing volumes and snapshotting where we currently have some
> nasty
> > scripts to do the work.
> >
> > See my commits in libvirt-java: http://www.libvirt.org/git/?p=**
> > libvirt-java.git;a=summary<
> http://www.libvirt.org/git/?p=libvirt-java.git;a=summary>
> >
> > So keep in mind libvirt-java has some new features!
> >
> > Wido
> >
>



-- 
Grtz,
Jörgen Maas

Re: Review Request 14147: marvin tests for Persistent networks without running a VM

[Anshul Gangwar]

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

(Updated Sept. 16, 2013, 11:26 a.m.)


Review request for cloudstack, Likitha Shetty, sailaja mada, and Prasanna 
Santhanam.


Changes
---

tagged the tests for adavnced zone and removed extraneous parameters from 
virtual_machine json


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


Repository: cloudstack-git


Description
---

marvin tests for Persistent networks without running a VM


Diffs (updated)
-

  test/integration/component/test_persistent_networks.py PRE-CREATION 
  tools/marvin/marvin/integration/lib/base.py 9e46065 

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


Testing
---

ran successfully on  my local advanced zone setup


Thanks,

Anshul Gangwar

Re: [PROPOSAL][SIMPLIFY] Future ACS RC testing

[sebgoa]

On Sep 15, 2013, at 8:24 PM, Daan Hoogland  wrote:

> Sebastien,
> 
> Are you thinking november in Amsterdam, or before?

I was thinking about a conference call - way before Amsterdam-

> 
> On Thu, Sep 12, 2013 at 9:06 AM, sebgoa  wrote:
>> 
>> On Sep 11, 2013, at 5:25 PM, "Musayev, Ilya"  wrote:
>> 
>>> As mentioned on private, I think the reason we have so few responders when 
>>> it comes to voting - is because it takes considerable amount of time to 
>>> build, test and QA. And if you take voting serious as everyone should, you 
>>> have to QA before you can vote.
>>> 
>>> 
>>> 
>>> Perhaps we should spent some time on automation and take an automation step 
>>> further.
>>> 
>>> 
>>> 
>>> My next dream project is to create a set of 3 virtual appliances.
>>> 
>>> 
>>> 
>>> Set 1:
>>> 
>>> 2 KVM Hypervisors preconfigured with NFS
>>> 
>>> 1 CloudStack MS with latest RC code
>>> 
>>> 
>>> 
>>> Set 2:
>>> 
>>> 2 XEN Hypervisors preconfigured with NFS
>>> 
>>> 1 CloudStack MS with latest RC code
>>> 
>>> 
>>> 
>>> Set 3:
>>> 
>>> 1 CloudStack MS with latest RC code
>>> 
>>> 
>>> 
>>> Set 3 get a bit hairy because of Virtual Center and licensing, so we 
>>> abstract it and let folks QA what they have.
>>> 
>>> -
>>> 
>>> Do you find this approach useful, or do you believe the build tests we do 
>>> is sufficient?
>>> 
>>> Who can join or atleast share scripts they use to automate provisioning of 
>>> KVM and XEN hosts?
>>> 
>>> I'm looking for set of "post" scripts they can configure XEN and KVM end 2 
>>> end.
>>> 
>>> Thanks
>>> ilya
>> 
>> Ilya, I think this is in-line with what Marcus is proposing.
>> 
>> In another thread on testing I proposed to have a meeting where anyone 
>> interested in testing can join and where we can hash out a plan, then report 
>> back to the list.
>> 
>> 
>> 
>> -sebastien

Re: Libvirt-java 0.5.0 has been released

[Wido den Hollander]

On 09/16/2013 12:51 PM, Wei ZHOU wrote:

Thanks Wido.

Do you know the minimal requirement of libvirt if we use libvirt-java 0.5.0
?



There shouldn't be a difference in the required libvirt version. I 
implemented a couple of methods in the bindings which were already in 
libvirt for a long time, but the bindings was just missing them.


Wido



2013/9/16 Wido den Hollander 


Hi,

I worked with the RedHat guys last week to get libvirt-java 0.5.0 released
which has some nice new features for us:

- Supports different XML on destination host during migration
- Supports resizing volumes
- Supports more snapshot functionalities

I took the liberty to depend on 0.5.0 in master and also merge in the code
for the VNC listen, we now no longer listen on 0.0.0.0 for VNC, which was a
security issue imho.

The reason I'm bringing this to the list is that we can simplify some code
around resizing volumes and snapshotting where we currently have some nasty
scripts to do the work.

See my commits in libvirt-java: http://www.libvirt.org/git/?p=**
libvirt-java.git;a=summary

So keep in mind libvirt-java has some new features!

Wido

Re: Call for 4.3 and 4.2.1 Release Managers!

[Daan Hoogland]

Animesh, I am passing till next time, I am willing though if really no
one can be found.

Daan

On Wed, Sep 11, 2013 at 7:57 AM, Animesh Chaturvedi
 wrote:
> Folks
>
> Now that 4.2.0 VOTE has passed I want to call out for any committers who are 
> interested in taking over as the release manager for the upcoming 4.2.1 
> maintenance release and the 4.3.0 release.
>
>
> Following our 4 month release cycle the feature freeze for 4.3.0 should be by 
> end of October and as community we need to figure out the timelines for 4.2.1 
> maintenance release.
>
> I will update my experience and learning from the 4.2.0 release in the wiki 
> shortly after the formal release announcement  later this week.
>
> Thanks
> Animesh
>
>
>
>

Re: [PROPOSAL][SIMPLIFY] Future ACS RC testing

[Daan Hoogland]

shoot a time, you will miss some of us. how about wednesday 19:00 cet
this is the time the irc meeting used to be.

On Mon, Sep 16, 2013 at 1:27 PM, sebgoa  wrote:
>
> On Sep 15, 2013, at 8:24 PM, Daan Hoogland  wrote:
>
>> Sebastien,
>>
>> Are you thinking november in Amsterdam, or before?
>
> I was thinking about a conference call - way before Amsterdam-
>
>>
>> On Thu, Sep 12, 2013 at 9:06 AM, sebgoa  wrote:
>>>
>>> On Sep 11, 2013, at 5:25 PM, "Musayev, Ilya"  wrote:
>>>
 As mentioned on private, I think the reason we have so few responders when 
 it comes to voting - is because it takes considerable amount of time to 
 build, test and QA. And if you take voting serious as everyone should, you 
 have to QA before you can vote.



 Perhaps we should spent some time on automation and take an automation 
 step further.



 My next dream project is to create a set of 3 virtual appliances.



 Set 1:

 2 KVM Hypervisors preconfigured with NFS

 1 CloudStack MS with latest RC code



 Set 2:

 2 XEN Hypervisors preconfigured with NFS

 1 CloudStack MS with latest RC code



 Set 3:

 1 CloudStack MS with latest RC code



 Set 3 get a bit hairy because of Virtual Center and licensing, so we 
 abstract it and let folks QA what they have.

 -

 Do you find this approach useful, or do you believe the build tests we do 
 is sufficient?

 Who can join or atleast share scripts they use to automate provisioning of 
 KVM and XEN hosts?

 I'm looking for set of "post" scripts they can configure XEN and KVM end 2 
 end.

 Thanks
 ilya
>>>
>>> Ilya, I think this is in-line with what Marcus is proposing.
>>>
>>> In another thread on testing I proposed to have a meeting where anyone 
>>> interested in testing can join and where we can hash out a plan, then 
>>> report back to the list.
>>>
>>>
>>>
>>> -sebastien
>

Re: Primary store (PS) failure/outage

[Wido den Hollander]

On 09/16/2013 01:21 PM, Koushik Das wrote:

Currently the way Cloudstack deals with PS failure is to reboot all hosts 
associated with the cluster. Selectively cleaning up the affected VMs would 
have been the best option, but since issues were seen with stopping VMs on the 
hypervisors (at least in Xenserver 5.6 [1]) reboot was the next option. The 
down side with this approach is if there are more than one PS in the cluster 
then healthy VMs will unnecessarily get affected due to host reboots.

Recently I tried this scenario using both XS 6.1 and 6.2. On 6.1 I think the 
behaviour is similar to 5.6, if the PS is not available then any operation the 
VM like shutdown would hang (waited for more than 30 mins and the operation was 
still stuck). But on 6.2 looks like these scenarios are handled more 
gracefully. In 6.2 on doing a shutdown the VMs power state was changed to 
'halted' and then it was possible to even destroy the VM. Based on this I think 
that at least for XS 6.2 we can do a selective VM cleanup if the PS is not 
available. For older XS version the existing approach would still be used.

Thoughts/comments?

Also for KVM the same approach is used. Can someone let me know if newer 
versions of KVM can handle primary storage failure in a better way wrt to VM 
operations? In that case for KVM also the behaviour can be changed.



I can't comment on this specifically, but when you are using NFS your 
Qemu process will go into status "D" and can't be killed.


So that will lead to the only other option: Reboot the host

With NFS though, you can stop the NFS server and bring it back 2 hours 
later and with KVM all the VMs will recover within 15 min without any 
intervention.


CS shouldn't start doing all kinds of things when PS fails.

Wido


For Vmware since it is an externally managed cluster I don't think this issue 
exists.

Thanks,
Koushik

[1] https://issues.apache.org/jira/browse/CLOUDSTACK-3367
[2] http://comments.gmane.org/gmane.comp.apache.cloudstack.user/4254

DevCloud Download Issue

[Alexander Hitchins]

All,

I'm trying to download the DevCloud image from the following URL :

http://people.apache.org/~bhaisaab/cloudstack/devcloud/devcloud2.ova 



Everytime I attempt the download it fails. I got this location from the 
Wiki, is there a better/other location I can try?


Many thanks,

--

Alexander Hitchins
-
e: a...@alexhitchins.com
w: alexhitchins.com
m: 07788 423 969

mido client

[Daan Hoogland]

H Dave,

I noticed some mails on this but did not find a workaround; I am
trying to build master and it looks for midonet-client 1.1.0. I have
removed it from the plugins pom file. Next I do want to test with
midonet however as it touches networks what I am doing. Do you have
some advice on how to build while you are uploading it somewhere?
Meaning cen you place it somewhere or mail me a copy?

regards,

Re: DevCloud Download Issue

[Daan Hoogland]

On Mon, Sep 16, 2013 at 2:25 PM, Alexander Hitchins
 wrote:
> I'm trying to download the DevCloud image from the following URL :
>
> http://people.apache.org/~bhaisaab/cloudstack/devcloud/devcloud2.ova

Alexander,

I am downloading from this location as we write. It seems slow but is
working so far. I will get back if ti fails (eta: 15 mins to go but
highly variable)

regards,
Daan

Re: mido client

[Dave Cahill]

Copying part of the IM conversation just now in case anyone else has the
same question.

As Prasanna mentioned in this thread [1]:
"If you are using a nexus proxy in the way of your build, you'll have
to add a 3rd party repo and the jars will be automatically indexed and
downloaded."

Thanks,
Dave.

[1]
http://markmail.org/message/e46n5isogps5g723#query:+page:1+mid:x37wudx5qoxop7ag+state:results


On Mon, Sep 16, 2013 at 9:46 PM, Daan Hoogland wrote:

> H Dave,
>
> I noticed some mails on this but did not find a workaround; I am
> trying to build master and it looks for midonet-client 1.1.0. I have
> removed it from the plugins pom file. Next I do want to test with
> midonet however as it touches networks what I am doing. Do you have
> some advice on how to build while you are uploading it somewhere?
> Meaning cen you place it somewhere or mail me a copy?
>
> regards,
>

Re: Handling Public network traffic in a plugin

[Dave Cahill]

That looks perfectly fine.

I was just saying it would be nice if it were also possible to create
network offerings for traffic types other than Guest - it would, for
example, provide a mechanism for network plugins to handle other traffic
types.

Thanks,
Dave.


On Mon, Sep 16, 2013 at 6:07 PM, Daan Hoogland wrote:

> Dave,
>
> As I suspected I used guest type for this offering:
>
>def createPrivateGatewayNetworkOffering(self, conn):
>   offers = self.listNetworkOfferings(conn,
> name="NiciraNvpPrivateGatewayNetwork")
>   if offers != None:
>  return offers[0].id
>   # else create it
>   cno = createNetworkOffering.createNetworkOfferingCmd()
>   cno.name = "NiciraNvpPrivateGatewayNetwork"
>   cno.displaytext = "VPC private gateway network offering with Nicira
> NVP"
>   cno.traffictype = "GUEST"
>   cno.specifyvlan = True
>   cno.specifyipranges = True
>   cno.availability = "Optional"
>   cno.conservemode = True
>   cno.guestiptype = "Isolated"
>   cno.usevpc = True
>   cno.systemonly = True
>   cno.supportedservices = [ "Connectivity" ]
>   cno.serviceproviderlist = [ { "service": "Connectivity",
> "provider": "NiciraNVP"} ]
>   #cno.servicecapabilitylist
>   cno.tags = [ "nicira-based" ]
>   #cno.networkrate
>   #cno.serviceofferingid
>
>   try:
>  resp = conn.marvin_request(cno)
>   except:
>  print "nicira based offering already exists"
>  #todo query and return
>
> Do you know if this is going to be a problem? It works for me and I
> don't see any objections to it.
>
> regards,
> Daan
>
> On Fri, Sep 6, 2013 at 12:30 PM, Daan Hoogland 
> wrote:
> > H Dave,
> >
> > I actually didn't give 'guest' to much thought. I had to change the
> > vpcvirtualrouter. It calls the right guru based on the netoffer.
> > I feel I am not answering your question.
> > Are you in Amsterdam the 22th of november? A hackathon on this seems
> > appropriate.
> >
> > mobile biligual spell checker used
> >
> > Op 5 sep. 2013 03:08 schreef "Dave Cahill"  het
> > volgende:
> >
> >> Hi,
> >>
> >> The creste neroffer api accepts system=true. The creation should be part
> >> of
> >> > the plugin install, though.
> >>
> >>
> >> Ah, sounds interesting! Does it also accept creating networkofferings
> for
> >> Traffic types other than Guest? Looking at 4.2, createNetworkOffering
> does
> >> a check to restrict to Guest traffic only (from
> ConfigurationManagerImpl):
> >>
> >> // Only GUEST traffic type is supported in Acton
> >> if (trafficType != TrafficType.Guest) {
> >> throw new InvalidParameterValueException("Only traffic type " +
> >> TrafficType.Guest
> >> + " is supported in the current release");
> >> }
> >>
> >> One question I had about the external hosted private gateways VPC
> feature
> >> was whether the change involves allowing plugins to handle VPC itself
> >> (routing between VPC subnets etc) instead of the VpcVirtualRouter? Last
> >> time I looked at having our plugin provide VPC (a few months ago), the
> >> VpcVirtualRouter was hardcoded in several places as the only provider.
> >>
> >> Thanks,
> >> Dave.
> >>
> >>
> >>
> >>
> >> On Thu, Sep 5, 2013 at 4:08 AM, Daan Hoogland
> >> wrote:
> >>
> >> > H Dave,
> >> >
> >> > Sorry about the white space.
> >> >
> >> > The creste neroffer api accepts system=true. The creation should be
> part
> >> > of
> >> > the plugin install, though.
> >> >
> >> > I will have to write more doc and any specific questions would help.
> >> >
> >> > mobile biligual spell checker used
> >> > Op 4 sep. 2013 11:45 schreef "Dave Cahill"  het
> >> > volgende:
> >> >
> >> > > Hi Daan,
> >> > >
> >> > > My take on things is to add a network offering for vpc private
> >> > > gateways.
> >> > I
> >> > > > extend the api
> >> > > > call with the optional netoffer.
> >> > >
> >> > >
> >> > > I read the wiki page on that feature [1] and the most recent code
> >> > > review,
> >> > > but I don't fully understand it yet - is there any other
> documentation
> >> > > /
> >> > > code around?
> >> > >
> >> > > replacing the guru does not seem like the way to go to me. I'd
> >> > > > say that the offer is what drives what guru/element to use.
> >> > >
> >> > >
> >> > > That would be nicer. When we implemented Public traffic via MidoNet
> >> > > back
> >> > in
> >> > > February / March, it wasn't possible to create System offerings /
> >> > > private
> >> > > offerings - if that changed, it would be great.
> >> > >
> >> > > Thanks,
> >> > > Dave.
> >> > >
> >> > > [1]
> >> > >
> >> > >
> >> >
> >> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/external+hosted+private+gateways
> >> > >
> >> > >
> >> > > On Tue, Sep 3, 2013 at 9:25 PM, Daan Hoogland <
> daan.hoogl...@gmail.com
> >> > > >wrote:
> >> > >
> >> > > > H Dave,
> >> > > >
> >> > > > It seems we are working on similar things, David. My take on
> things
> >> > > > is
> >> > > > to add a network offering for v

Re: mido client

[Daan Hoogland]

http://cs-maven.midokura.com/releases/ is the right location, right? I
get a blank page there (no pom or jar) or is it somewhere else?

On Mon, Sep 16, 2013 at 3:17 PM, Dave Cahill  wrote:
> Copying part of the IM conversation just now in case anyone else has the
> same question.
>
> As Prasanna mentioned in this thread [1]:
> "If you are using a nexus proxy in the way of your build, you'll have
> to add a 3rd party repo and the jars will be automatically indexed and
> downloaded."
>
> Thanks,
> Dave.
>
> [1]
> http://markmail.org/message/e46n5isogps5g723#query:+page:1+mid:x37wudx5qoxop7ag+state:results
>
>
> On Mon, Sep 16, 2013 at 9:46 PM, Daan Hoogland 
> wrote:
>>
>> H Dave,
>>
>> I noticed some mails on this but did not find a workaround; I am
>> trying to build master and it looks for midonet-client 1.1.0. I have
>> removed it from the plugins pom file. Next I do want to test with
>> midonet however as it touches networks what I am doing. Do you have
>> some advice on how to build while you are uploading it somewhere?
>> Meaning cen you place it somewhere or mail me a copy?
>>
>> regards,
>
>

Re: Handling Public network traffic in a plugin

[Daan Hoogland]

Yes Dave,

And maybe more generic: plugin installation procedures would be yet
another level of api permission. They would be allowed to do even more
then admins.

Like add our system network offerings.

regards,
Daan

On Mon, Sep 16, 2013 at 3:19 PM, Dave Cahill  wrote:
> That looks perfectly fine.
>
> I was just saying it would be nice if it were also possible to create
> network offerings for traffic types other than Guest - it would, for
> example, provide a mechanism for network plugins to handle other traffic
> types.
>
> Thanks,
> Dave.
>
>
> On Mon, Sep 16, 2013 at 6:07 PM, Daan Hoogland 
> wrote:
>>
>> Dave,
>>
>> As I suspected I used guest type for this offering:
>>
>>def createPrivateGatewayNetworkOffering(self, conn):
>>   offers = self.listNetworkOfferings(conn,
>> name="NiciraNvpPrivateGatewayNetwork")
>>   if offers != None:
>>  return offers[0].id
>>   # else create it
>>   cno = createNetworkOffering.createNetworkOfferingCmd()
>>   cno.name = "NiciraNvpPrivateGatewayNetwork"
>>   cno.displaytext = "VPC private gateway network offering with Nicira
>> NVP"
>>   cno.traffictype = "GUEST"
>>   cno.specifyvlan = True
>>   cno.specifyipranges = True
>>   cno.availability = "Optional"
>>   cno.conservemode = True
>>   cno.guestiptype = "Isolated"
>>   cno.usevpc = True
>>   cno.systemonly = True
>>   cno.supportedservices = [ "Connectivity" ]
>>   cno.serviceproviderlist = [ { "service": "Connectivity",
>> "provider": "NiciraNVP"} ]
>>   #cno.servicecapabilitylist
>>   cno.tags = [ "nicira-based" ]
>>   #cno.networkrate
>>   #cno.serviceofferingid
>>
>>   try:
>>  resp = conn.marvin_request(cno)
>>   except:
>>  print "nicira based offering already exists"
>>  #todo query and return
>>
>> Do you know if this is going to be a problem? It works for me and I
>> don't see any objections to it.
>>
>> regards,
>> Daan
>>
>> On Fri, Sep 6, 2013 at 12:30 PM, Daan Hoogland 
>> wrote:
>> > H Dave,
>> >
>> > I actually didn't give 'guest' to much thought. I had to change the
>> > vpcvirtualrouter. It calls the right guru based on the netoffer.
>> > I feel I am not answering your question.
>> > Are you in Amsterdam the 22th of november? A hackathon on this seems
>> > appropriate.
>> >
>> > mobile biligual spell checker used
>> >
>> > Op 5 sep. 2013 03:08 schreef "Dave Cahill"  het
>> > volgende:
>> >
>> >> Hi,
>> >>
>> >> The creste neroffer api accepts system=true. The creation should be
>> >> part
>> >> of
>> >> > the plugin install, though.
>> >>
>> >>
>> >> Ah, sounds interesting! Does it also accept creating networkofferings
>> >> for
>> >> Traffic types other than Guest? Looking at 4.2, createNetworkOffering
>> >> does
>> >> a check to restrict to Guest traffic only (from
>> >> ConfigurationManagerImpl):
>> >>
>> >> // Only GUEST traffic type is supported in Acton
>> >> if (trafficType != TrafficType.Guest) {
>> >> throw new InvalidParameterValueException("Only traffic type " +
>> >> TrafficType.Guest
>> >> + " is supported in the current release");
>> >> }
>> >>
>> >> One question I had about the external hosted private gateways VPC
>> >> feature
>> >> was whether the change involves allowing plugins to handle VPC itself
>> >> (routing between VPC subnets etc) instead of the VpcVirtualRouter? Last
>> >> time I looked at having our plugin provide VPC (a few months ago), the
>> >> VpcVirtualRouter was hardcoded in several places as the only provider.
>> >>
>> >> Thanks,
>> >> Dave.
>> >>
>> >>
>> >>
>> >>
>> >> On Thu, Sep 5, 2013 at 4:08 AM, Daan Hoogland
>> >> wrote:
>> >>
>> >> > H Dave,
>> >> >
>> >> > Sorry about the white space.
>> >> >
>> >> > The creste neroffer api accepts system=true. The creation should be
>> >> > part
>> >> > of
>> >> > the plugin install, though.
>> >> >
>> >> > I will have to write more doc and any specific questions would help.
>> >> >
>> >> > mobile biligual spell checker used
>> >> > Op 4 sep. 2013 11:45 schreef "Dave Cahill"  het
>> >> > volgende:
>> >> >
>> >> > > Hi Daan,
>> >> > >
>> >> > > My take on things is to add a network offering for vpc private
>> >> > > gateways.
>> >> > I
>> >> > > > extend the api
>> >> > > > call with the optional netoffer.
>> >> > >
>> >> > >
>> >> > > I read the wiki page on that feature [1] and the most recent code
>> >> > > review,
>> >> > > but I don't fully understand it yet - is there any other
>> >> > > documentation
>> >> > > /
>> >> > > code around?
>> >> > >
>> >> > > replacing the guru does not seem like the way to go to me. I'd
>> >> > > > say that the offer is what drives what guru/element to use.
>> >> > >
>> >> > >
>> >> > > That would be nicer. When we implemented Public traffic via MidoNet
>> >> > > back
>> >> > in
>> >> > > February / March, it wasn't possible to create System offerings /
>> >> > > private
>> >> > > offerings - if that changed, it would be great.
>> >> > >
>> >> >

Re: Apache CloudStack 4.2.0 (fifth round)

[Daan Hoogland]

At Schuberg Philis, we did some tests and noted that the xe-deamon on
router vms is not started and that xenstore no longer exist under that
name.
The xenstore binary is copied to xenstore-write, --ls etc so this
could be solved.

I am sure how to formulate this as to convince you all this is a
blocker but am inclined to do so.

more accurate report will follow,
Daan

On Mon, Sep 16, 2013 at 12:40 PM, Ian Duffy  wrote:
> +1
>
> Ran against simulator.
>
>
> On 16 September 2013 11:25, Prasanna Santhanam  wrote:
>
>> +1 (binding)
>>
>> The test infra has deployed advanced zone with kvm and xenserver 6.2
>> since Saturday and I dont see any new failures [1]. So no regressions.
>> Also ran the simulator against 4.2 [2]
>>
>> [1]
>> http://jenkins.buildacloud.org/view/cloudstack-qa/job/test-regression-matrix/
>> [2] http://jenkins.buildacloud.org/view/simulator/job/run-checkin-tests/
>>
>> On Sun, Sep 15, 2013 at 10:18:48PM -0400, Chip Childers wrote:
>> > +1 (binding)
>> >
>> > Tested with simulator.
>> >
>> >
>> >
>> > On Sep 14, 2013, at 5:59 PM, Marcus Sorensen 
>> wrote:
>> >
>> > > +1 (binding)
>> > >
>> > > Tested CentOS 6.4 and Ubuntu 12.04.3:
>> > > create advanced zone
>> > > create VPC
>> > > register template
>> > > create VPC tier
>> > > create VM on tier w/NFS
>> > > create VM on tier w/CLM
>> > > create VM on tier w/Local storage
>> > > create static NAT to vm, ssh in
>> > >
>> > > On Sat, Sep 14, 2013 at 10:28 AM, Rajesh Battala
>> > >  wrote:
>> > >> +1
>> > >>
>> > >> Tested VM Life cycle in Xenserver and KVM with Advance Zone
>> configuration.
>> > >>
>> > >> Thanks
>> > >> Rajesh Battala
>> > >>
>> > >> -Original Message-
>> > >> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
>> > >> Sent: Saturday, September 14, 2013 4:43 AM
>> > >> To: dev@cloudstack.apache.org
>> > >> Subject: Apache CloudStack 4.2.0 (fifth round)
>> > >>
>> > >>
>> > >> 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: c1e24ff89f6d14d6ae74d12dbca108c35449030f
>> > >>
>> > >> 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 (Wednesday 9/18 End of Day PST).
>> > >>
>> > >> 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)
>> > >
>>
>> --
>> Prasanna.,
>>
>> 
>> Powered by BigRock.com
>>
>>

Test procedure for upgrade from 4.1.x to 4.2 RC

[Simon Weller]

All, 

Could someone provide the documented upgrade procedure for those upgrading from 
4.1.x to 4.2? It's quite possible I'm just not looking in the correct place, 
but I've been unable to locate it thus far. 
I'd like to test this in our lab environment today for the voting round. I do 
have nonoss rpms built for it from the latest RC round. 

Our lab environment is RHEL 6.3, KVM using CLVM to a Compellent SAN with 
advanced networking. 

Thanks, 

- Si 

Re: Primary store (PS) failure/outage

[Ove Ewerlid]

The PS behaviour of NFS hits an install with predominant local storage 
for production badly. Why use NFS primary storage at all in such an 
install? The SSVM will not start in a zone with only local storage, 
additional types of primary storage needs to be added and a dummy 
primary NFS share is easy to add.


A primary "dummy" NFS share can be removed after SSVM has started to 
avoid issues with dummy NFS share, but that adds additional hazzles 
restarting the SSVM.


Anyone know a configuration oriented solution to this?

In this case the environment is KVM/OEL64.

/Ove

On 09/16/2013 01:54 PM, Wido den Hollander wrote:

On 09/16/2013 01:21 PM, Koushik Das wrote:

Currently the way Cloudstack deals with PS failure is to reboot all
hosts associated with the cluster. Selectively cleaning up the
affected VMs would have been the best option, but since issues were
seen with stopping VMs on the hypervisors (at least in Xenserver 5.6
[1]) reboot was the next option. The down side with this approach is
if there are more than one PS in the cluster then healthy VMs will
unnecessarily get affected due to host reboots.

Recently I tried this scenario using both XS 6.1 and 6.2. On 6.1 I
think the behaviour is similar to 5.6, if the PS is not available then
any operation the VM like shutdown would hang (waited for more than 30
mins and the operation was still stuck). But on 6.2 looks like these
scenarios are handled more gracefully. In 6.2 on doing a shutdown the
VMs power state was changed to 'halted' and then it was possible to
even destroy the VM. Based on this I think that at least for XS 6.2 we
can do a selective VM cleanup if the PS is not available. For older XS
version the existing approach would still be used.

Thoughts/comments?

Also for KVM the same approach is used. Can someone let me know if
newer versions of KVM can handle primary storage failure in a better
way wrt to VM operations? In that case for KVM also the behaviour can
be changed.



I can't comment on this specifically, but when you are using NFS your
Qemu process will go into status "D" and can't be killed.

So that will lead to the only other option: Reboot the host

With NFS though, you can stop the NFS server and bring it back 2 hours
later and with KVM all the VMs will recover within 15 min without any
intervention.

CS shouldn't start doing all kinds of things when PS fails.

Wido


For Vmware since it is an externally managed cluster I don't think
this issue exists.

Thanks,
Koushik

[1] https://issues.apache.org/jira/browse/CLOUDSTACK-3367
[2] http://comments.gmane.org/gmane.comp.apache.cloudstack.user/4254






--
Ove Everlid
System Administrator / Architect / SDN- & Automation- & Linux-hacker
Mobile: +46706662363 (dedicated work mobile)
Country: Sweden, timezone; Middle Europan Time (MET or GMT+1)

Re: Apache CloudStack 4.2.0 (fifth round)

[Marcus Sorensen]

I'm not sure I understand... my impression from your message is the
stock 4.2 image works.  This is for Xen, right?  Does this mean that
there's a step missing in building a custom system vm to make it match
the stock image?

On Mon, Sep 16, 2013 at 9:30 AM, Daan Hoogland  wrote:
> H,
>
> The problem is when creating a newer image for the system template as
> we did on our installations. It will not work with the 4.2 scripts. I
> am not making hard my thread of this being a blocker but it is a
> serious impediment for people wanting to harden their cloudstack
> environment.
>
> I am voting a +0 here as I think we are not going to use this distro
> for this reason.
>
> regards,
> Daan
>
> On Mon, Sep 16, 2013 at 4:05 PM, Daan Hoogland  
> wrote:
>> At Schuberg Philis, we did some tests and noted that the xe-deamon on
>> router vms is not started and that xenstore no longer exist under that
>> name.
>> The xenstore binary is copied to xenstore-write, --ls etc so this
>> could be solved.
>>
>> I am sure how to formulate this as to convince you all this is a
>> blocker but am inclined to do so.
>>
>> more accurate report will follow,
>> Daan
>>
>> On Mon, Sep 16, 2013 at 12:40 PM, Ian Duffy  wrote:
>>> +1
>>>
>>> Ran against simulator.
>>>
>>>
>>> On 16 September 2013 11:25, Prasanna Santhanam  wrote:
>>>
 +1 (binding)

 The test infra has deployed advanced zone with kvm and xenserver 6.2
 since Saturday and I dont see any new failures [1]. So no regressions.
 Also ran the simulator against 4.2 [2]

 [1]
 http://jenkins.buildacloud.org/view/cloudstack-qa/job/test-regression-matrix/
 [2] http://jenkins.buildacloud.org/view/simulator/job/run-checkin-tests/

 On Sun, Sep 15, 2013 at 10:18:48PM -0400, Chip Childers wrote:
 > +1 (binding)
 >
 > Tested with simulator.
 >
 >
 >
 > On Sep 14, 2013, at 5:59 PM, Marcus Sorensen 
 wrote:
 >
 > > +1 (binding)
 > >
 > > Tested CentOS 6.4 and Ubuntu 12.04.3:
 > > create advanced zone
 > > create VPC
 > > register template
 > > create VPC tier
 > > create VM on tier w/NFS
 > > create VM on tier w/CLM
 > > create VM on tier w/Local storage
 > > create static NAT to vm, ssh in
 > >
 > > On Sat, Sep 14, 2013 at 10:28 AM, Rajesh Battala
 > >  wrote:
 > >> +1
 > >>
 > >> Tested VM Life cycle in Xenserver and KVM with Advance Zone
 configuration.
 > >>
 > >> Thanks
 > >> Rajesh Battala
 > >>
 > >> -Original Message-
 > >> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
 > >> Sent: Saturday, September 14, 2013 4:43 AM
 > >> To: dev@cloudstack.apache.org
 > >> Subject: Apache CloudStack 4.2.0 (fifth round)
 > >>
 > >>
 > >> 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: c1e24ff89f6d14d6ae74d12dbca108c35449030f
 > >>
 > >> 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 (Wednesday 9/18 End of Day PST).
 > >>
 > >> 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)
 > >

 --
 Prasanna.,

 
 Powered by BigRock.com

Re: 4.1 new feature post release?

[Marcus Sorensen]

My impression is that once we freeze for release, we only apply fixes
to bugs. Even if something works better, if the current implementation
works it doesn't change.

I don't have any objections to it being in 4.2 or master, just for
clarification, as it went in so long ago.

On Mon, Sep 16, 2013 at 1:40 AM, Wei Zhou  wrote:
> Marcus and Wido,
> Sorry I just saw this Email.
> I will create a JIRA ticket for them (both code and docs) later. I regarded 
> it as an improvement, not a new feature, this is why I cherry-picked it into 
> 4.1 branch. If you guys object it, I will revert it.
>
> Marcus, could you create tickets for the issues you mentioned? The commit is 
> in 4.2 and master branch as well. We need to fix potential issues.
>
>
> Kind Regards,
>
> Wei ZHOU
> Innovation Engineer Cloud, LeaseWeb B.V.
> w.z...@leaseweb.com
>
> -Original Message-
> From: Wido den Hollander [mailto:w...@widodh.nl]
> Sent: 16 September 2013 09:22
> To: dev@cloudstack.apache.org
> Cc: Wei Zhou
> Subject: Re: 4.1 new feature post release?
>
>
>
> On 09/15/2013 07:32 AM, Marcus Sorensen wrote:
>> Hi guys, I was just pulling in updates from the 4.1 branch and noticed
>> commit 706e23623c3227d92ae498529166ca73d2a2bf4e, This looks like a new
>> feature. There's not a bug attached to it. It seems to allow admins to
>> set the CPU mode for KVM guests, e.g. host-passthrough, which makes
>> the VM show the actual CPU model of the host (and breaks live
>> migration in some cases), etc.
>>
>> I see no reason off hand why this should have been cherry-picked into
>> 4.1.  It's been awhile, and I'm not sure whether or not we'll release
>> a 4.1.2, but we may want to review/revert it if we don't find out why
>> it was picked.
>>
>
> Good point. 4.1.2 release or not, there shouldn't be any new features in the 
> 4.1 branch.
>
> Wei, can you comment on this?
>
> Wido
>
>> commit 706e23623c3227d92ae498529166ca73d2a2bf4e
>> Author: JijunLiu 
>> Date:   Sun Jul 14 11:21:39 2013 +0800
>>
>>  Add cpu model for kvm guest.Now all the kvm guest's cpu model is
>> 'QEMU Virtual CPU version xxx'. This will affect the activati
>>
>>  Signed-off-by: Wei Zhou 
>>  (cherry picked from commit
>> 2903bb5fd9d59803980102854d11e33ebe56088b)
>>

Re: Q's about UserAuthenticators and getName()

[Darren Shepherd]

I'll clean it up and submit a patch then. 

Darren

On Sep 15, 2013, at 9:36 PM, Abhinandan Prateek  
wrote:

> On 13/09/13 10:04 pm, "Darren Shepherd" 
> wrote:
> 
>> On 09/13/2013 03:48 AM, Abhinandan Prateek wrote:
>>> The code already has the name set to ³LDAP² in 4.2. What branch are you
>>> on
>>> ?
>>> Will also prefer if we can use getClass().getSimpleName() to get the
>>> classname, but we should check the possibility of the adapter classnames
>>> getting enhanced by underlying framework.
>> 
>> I'm on master but that doesn't matter, its actually broke in 4.2 also.
>> I originally stated that the DefaultUserAuthenticator masks _name in
>> ComponentLifecycleBase so even though the XML is setting the property to
>> LDAP it doesn't work.  That was sort of my original question, why was it
>> done like that?
>> 
>> I can clean up all the authenticators and submit a patch if we want.
> 
> 
> Looking at git history it appears that _name got masked when the
> DefaultUserAuthenticator was made to extend AdapterBase.
> A cleanup will help.
> 
> -abhi
> 
> 

Re: [PROPOSAL][SIMPLIFY] Future ACS RC testing

[David Nalley]

On Mon, Sep 16, 2013 at 11:34 AM, Marcus Sorensen  wrote:
> I think this discussion should be linked with the discussion about minimum
> requirements for a release (release criteria). It seems this discussion is
> already being had to some degree.


Agreed. I think release criteria are important - but really - release
criteria should be commit criteria (or at least commit to a
release/master branch) I think we get a better release by enforcing
better quality standards all of the time - essentially keeping
CloudStack 'releasable' at any point.

--David

Re: Libvirt-java 0.5.0 has been released

[Marcus Sorensen]

There are some minimum requirements in Libvirt for volblockresize if I
recall, but I think all of our platforms include it.

On Mon, Sep 16, 2013 at 5:28 AM, Wido den Hollander  wrote:
> On 09/16/2013 12:51 PM, Wei ZHOU wrote:
>>
>> Thanks Wido.
>>
>> Do you know the minimal requirement of libvirt if we use libvirt-java
>> 0.5.0
>> ?
>>
>
> There shouldn't be a difference in the required libvirt version. I
> implemented a couple of methods in the bindings which were already in
> libvirt for a long time, but the bindings was just missing them.
>
> Wido
>
>
>>
>> 2013/9/16 Wido den Hollander 
>>
>>> Hi,
>>>
>>> I worked with the RedHat guys last week to get libvirt-java 0.5.0
>>> released
>>> which has some nice new features for us:
>>>
>>> - Supports different XML on destination host during migration
>>> - Supports resizing volumes
>>> - Supports more snapshot functionalities
>>>
>>> I took the liberty to depend on 0.5.0 in master and also merge in the
>>> code
>>> for the VNC listen, we now no longer listen on 0.0.0.0 for VNC, which was
>>> a
>>> security issue imho.
>>>
>>> The reason I'm bringing this to the list is that we can simplify some
>>> code
>>> around resizing volumes and snapshotting where we currently have some
>>> nasty
>>> scripts to do the work.
>>>
>>> See my commits in libvirt-java: http://www.libvirt.org/git/?p=**
>>>
>>> libvirt-java.git;a=summary
>>>
>>> So keep in mind libvirt-java has some new features!
>>>
>>> Wido
>>>
>>
>

Re: [PROPOSAL][SIMPLIFY] Future ACS RC testing

[Daan Hoogland]

A worthy cause, and we should all strive for it.  It does put extra
constraints on things like db upgrade scripts however. If ACS is
releasable at all times, can users make their own release and expect
all upgrade paths to work?

I disagreed with you on documentation as a commit criteria in another
thread, David. I do favor (extensive) unit tests as criteria.

Daan

On Mon, Sep 16, 2013 at 6:05 PM, David Nalley  wrote:
> On Mon, Sep 16, 2013 at 11:34 AM, Marcus Sorensen  wrote:
>> I think this discussion should be linked with the discussion about minimum
>> requirements for a release (release criteria). It seems this discussion is
>> already being had to some degree.
>
>
> Agreed. I think release criteria are important - but really - release
> criteria should be commit criteria (or at least commit to a
> release/master branch) I think we get a better release by enforcing
> better quality standards all of the time - essentially keeping
> CloudStack 'releasable' at any point.
>
> --David

Re: Apache CloudStack 4.2.0 (fifth round)

[Daan Hoogland]

This is for xen.
the stock image works and it is build in february 2012.
We did some further investigation. It turns out that due to license
issues the xen server tools where removed the 6th of september 2012.
any template newer should not work unless you install
xe-guest-utilities yourself. bug 29 says
"patches/systemvm/debian/iptables_1.4.8-3local1checksum1_i386.deb is
present in the source tree.

This is both a binary and a GPLed software and thus forbidden on two counts."

in 3db9736a0754388d782b45d31e8e36c9966c508e this and another deb file
and a kernel module where removed from the cloudstack repo.
patches/systemvm/debian/xe-guest-utilities_5.6.0-595_i386.deb contains
the service  responsible for starting the xe-daemon.

also xe-update-guest-attrs contains calls to 'xestore write', write as
parameter. On wheezy only xestore-write exists (maybe because of the
deb files that where not installed) the same goes for 'xenstore rm'.
Strangely it does contain a call to xenstore-read as well. A cp of
xenstore-ls to xenstore fixes this as all binaries are copies and is
it clever about its name.

more is bound to follow,
Daan


On Mon, Sep 16, 2013 at 5:41 PM, Marcus Sorensen  wrote:
> I'm not sure I understand... my impression from your message is the
> stock 4.2 image works.  This is for Xen, right?  Does this mean that
> there's a step missing in building a custom system vm to make it match
> the stock image?
>
> On Mon, Sep 16, 2013 at 9:30 AM, Daan Hoogland  
> wrote:
>> H,
>>
>> The problem is when creating a newer image for the system template as
>> we did on our installations. It will not work with the 4.2 scripts. I
>> am not making hard my thread of this being a blocker but it is a
>> serious impediment for people wanting to harden their cloudstack
>> environment.
>>
>> I am voting a +0 here as I think we are not going to use this distro
>> for this reason.
>>
>> regards,
>> Daan
>>
>> On Mon, Sep 16, 2013 at 4:05 PM, Daan Hoogland  
>> wrote:
>>> At Schuberg Philis, we did some tests and noted that the xe-deamon on
>>> router vms is not started and that xenstore no longer exist under that
>>> name.
>>> The xenstore binary is copied to xenstore-write, --ls etc so this
>>> could be solved.
>>>
>>> I am sure how to formulate this as to convince you all this is a
>>> blocker but am inclined to do so.
>>>
>>> more accurate report will follow,
>>> Daan
>>>
>>> On Mon, Sep 16, 2013 at 12:40 PM, Ian Duffy  wrote:
 +1

 Ran against simulator.


 On 16 September 2013 11:25, Prasanna Santhanam  wrote:

> +1 (binding)
>
> The test infra has deployed advanced zone with kvm and xenserver 6.2
> since Saturday and I dont see any new failures [1]. So no regressions.
> Also ran the simulator against 4.2 [2]
>
> [1]
> http://jenkins.buildacloud.org/view/cloudstack-qa/job/test-regression-matrix/
> [2] http://jenkins.buildacloud.org/view/simulator/job/run-checkin-tests/
>
> On Sun, Sep 15, 2013 at 10:18:48PM -0400, Chip Childers wrote:
> > +1 (binding)
> >
> > Tested with simulator.
> >
> >
> >
> > On Sep 14, 2013, at 5:59 PM, Marcus Sorensen 
> wrote:
> >
> > > +1 (binding)
> > >
> > > Tested CentOS 6.4 and Ubuntu 12.04.3:
> > > create advanced zone
> > > create VPC
> > > register template
> > > create VPC tier
> > > create VM on tier w/NFS
> > > create VM on tier w/CLM
> > > create VM on tier w/Local storage
> > > create static NAT to vm, ssh in
> > >
> > > On Sat, Sep 14, 2013 at 10:28 AM, Rajesh Battala
> > >  wrote:
> > >> +1
> > >>
> > >> Tested VM Life cycle in Xenserver and KVM with Advance Zone
> configuration.
> > >>
> > >> Thanks
> > >> Rajesh Battala
> > >>
> > >> -Original Message-
> > >> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> > >> Sent: Saturday, September 14, 2013 4:43 AM
> > >> To: dev@cloudstack.apache.org
> > >> Subject: Apache CloudStack 4.2.0 (fifth round)
> > >>
> > >>
> > >> 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: c1e24ff89f6d14d6ae74d12dbca108c35449030f
> > >>
> > >> 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

Re: Managed storage with KVM

[Marcus Sorensen]

It will still register the pool.  You still have a primary storage
pool that you registered, whether it's local, cluster or zone wide.
NFS is optionally zone wide as well (I'm assuming customers can launch
your storage only cluster-wide if they choose for resource
partitioning), but it registers the pool in Libvirt prior to use.

Here's a better explanation of what I meant.  AttachVolumeCommand gets
both pool and volume info. It first looks up the pool:

KVMStoragePool primary = _storagePoolMgr.getStoragePool(
cmd.getPooltype(),
cmd.getPoolUuid());

Then it looks up the disk from that pool:

KVMPhysicalDisk disk = primary.getPhysicalDisk(cmd.getVolumePath());

Most of the commands only pass volume info like this (getVolumePath
generally means the uuid of the volume), since it looks up the pool
separately. If you don't save the pool info in a map in your custom
class when createStoragePool is called, then getStoragePool won't be
able to find it. This is a simple thing in your implementation of
createStoragePool, just thought I'd mention it because it is key. Just
create a map of pool uuid and pool object and save them so they're
available across all implementations of that class.

On Mon, Sep 16, 2013 at 10:43 AM, Mike Tutkowski
 wrote:
> Thanks, Marcus
>
> About this:
>
> "When the agent connects to the
> management server, it registers all pools in the cluster with the
> agent."
>
> So, my plug-in allows you to create zone-wide primary storage. This just
> means that any cluster can use the SAN (the SAN was registered as primary
> storage as opposed to a preallocated volume from the SAN). Once you create a
> primary storage based on this plug-in, the storage framework will invoke the
> plug-in, as needed, to create and delete volumes on the SAN. For example,
> you could have one SolidFire primary storage (zone wide) and currently have
> 100 volumes created on the SAN to support it.
>
> In this case, what will the management server be registering with the agent
> in ModifyStoragePool? If only the storage pool (primary storage) is passed
> in, that will be too vague as it does not contain information on what
> volumes have been created for the agent.
>
> Thanks
>
>
> On Sun, Sep 15, 2013 at 11:53 PM, Marcus Sorensen 
> wrote:
>>
>> Yes, see my previous email from the 13th. You can create your own
>> KVMStoragePool class, and StorageAdaptor class, like the libvirt ones
>> have. The previous email outlines how to add your own StorageAdaptor
>> alongside LibvirtStorageAdaptor to take over all of the calls
>> (createStoragePool, getStoragePool, etc). As mentioned,
>> getPhysicalDisk I believe will be the one you use to actually attach a
>> lun.
>>
>> Ignore CreateStoragePoolCommand. When the agent connects to the
>> management server, it registers all pools in the cluster with the
>> agent. It will call ModifyStoragePoolCommand, passing your storage
>> pool object (with all of the settings for your SAN). This in turn
>> calls _storagePoolMgr.createStoragePool, which will route through
>> KVMStoragePoolManager to your storage adapter that you've registered.
>> The last argument to createStoragePool is the pool type, which is used
>> to select a StorageAdaptor.
>>
>> From then on, most calls will only pass the volume info, and the
>> volume will have the uuid of the storage pool. For this reason, your
>> adaptor class needs to have a static Map variable that contains pool
>> uuid and pool object. Whenever they call createStoragePool on your
>> adaptor you add that pool to the map so that subsequent volume calls
>> can look up the pool details for the volume by pool uuid. With the
>> Libvirt adaptor, libvirt keeps track of that for you.
>>
>> When createStoragePool is called, you can log into the iscsi target
>> (or make sure you are already logged in, as it can be called over
>> again at any time), and when attach volume commands are fired off, you
>> can attach individual LUNs that are asked for, or rescan (say that the
>> plugin created a new ACL just prior to calling attach), or whatever is
>> necessary.
>>
>> KVM is a bit more work, but you can do anything you want. Actually, I
>> think you can call host scripts with Xen, but having the agent there
>> that runs your own code gives you the flexibility to do whatever.
>>
>> On Sun, Sep 15, 2013 at 10:44 PM, Mike Tutkowski
>>  wrote:
>> > I see right now LibvirtComputingResource.java has the following method
>> > that
>> > I might be able to leverage (it's probably not called at present and
>> > would
>> > need to be implemented in my case to discover my iSCSI target and log in
>> > to
>> > it):
>> >
>> > protected Answer execute(CreateStoragePoolCommand cmd) {
>> >
>> > return new Answer(cmd, true, "success");
>> >
>> > }
>> >
>> > I would probably be able to call the KVMStorageManager to have it use my
>> > StorageAdaptor to do what's necessary here.
>> >
>> >
>> >
>> >
>> > On Sun, Sep 15, 2013 a

Re: Apache CloudStack 4.2.0 (fifth round)

[Daan Hoogland]

On Mon, Sep 16, 2013 at 7:11 PM, Marcus Sorensen  wrote:
>
> Xenserver
> http://download.cloud.com/templates/4.2/systemvmtemplate-2013-07-12-master-xen.vhd.bz2

I know, it does not have the xenstore binary on board that is called
by xe-update-guest-attrs

Re: [PROPOSAL][SIMPLIFY] Future ACS RC testing

[Daan Hoogland]

On Mon, Sep 16, 2013 at 7:12 PM, David Nalley  wrote:
> I do favor (extensive) unit tests as criteria.
>
> Disagreeing is fine - no one (least of all me) says that my opinion is
> right all of the time. :)
>
> Over time I've become less concerned about a feature working, and more
> concerned about changes in a feature breaking the rest of CloudStack.

I will interpret this as a 'I concur' ;)

Re: Apache CloudStack 4.2.0 (fifth round)

[Marcus Sorensen]

Ok, so you mean even the stock one does not work for Xen.  Can anyone
else who as been testing Xen comment?

On Mon, Sep 16, 2013 at 11:14 AM, Daan Hoogland  wrote:
> On Mon, Sep 16, 2013 at 7:11 PM, Marcus Sorensen  wrote:
>>
>> Xenserver
>> http://download.cloud.com/templates/4.2/systemvmtemplate-2013-07-12-master-xen.vhd.bz2
>
> I know, it does not have the xenstore binary on board that is called
> by xe-update-guest-attrs

Re: [jira] [Commented] (CLOUDSTACK-3565) Restarting libvirtd service leading to destroy storage pool

[Marcus Sorensen]

I agree, it makes things more complicated. However, updating libvirt
should be a maintenance mode thing; I've seen it lose track of VMs
between major libvirt upgrades and have to kill/restart all vms to
reregister them with libvirt, best to be in maintenance.

If I remember right, the issues with persistent storage definitiions
were primarily related to failure scenarios, things like hard power
off of host, host would build up dozens of primary storage definitions
that it didn't need, creating unnecessary dependencies and potential
unnecessary outages (see other email about what happens when storage
goes down).

If edison has a patch then that's great. One idea I head was that if
the pool fails to register due to mountpoint already existing, we
could use an alternate mount point to register it. Old stuff will keep
working, new stuff will continue.

On Mon, Sep 16, 2013 at 3:43 AM, Wei Zhou (JIRA)  wrote:
>
> [ 
> https://issues.apache.org/jira/browse/CLOUDSTACK-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13768197#comment-13768197
>  ]
>
> Wei Zhou commented on CLOUDSTACK-3565:
> --
>
> Marcus,
>
> The change of the host to maintenance one by one makes upgrade/change 
> complicated.
> Edison has changed the source to support re-creating storage pool in the fix 
> of CLOUDSTACK-2729.
> However, the test failed in my environment.
>
> By the way, I did not see any other issue when I used cloudstack 4.0 while 
> the storage pools are persistent.
> I do not know what issue will be leader by it.
>
>> Restarting libvirtd service leading to destroy storage pool
>> ---
>>
>> Key: CLOUDSTACK-3565
>> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3565
>> Project: CloudStack
>>  Issue Type: Bug
>>  Security Level: Public(Anyone can view this level - this is the 
>> default.)
>>  Components: KVM
>>Affects Versions: 4.2.0
>> Environment: KVM
>> Branch 4.2
>>Reporter: Rayees Namathponnan
>>Assignee: Marcus Sorensen
>>Priority: Blocker
>>  Labels: documentation
>> Fix For: 4.2.0
>>
>>
>> Steps to reproduce
>> Step 1 : Create cloudstack step in kvm
>> Step 2 : From kvm host check "virsh pool-list"
>> Step 3:  Stop and start libvirtd service
>> Step 4 : Check "virsh pool-list"
>> Actual Result
>> "virsh pool-list"  is blank after restart libvird service
>> [root@Rack2Host12 agent]# virsh pool-list
>> Name State  Autostart
>> -
>> 41b632b5-40b3-3024-a38b-ea259c72579f active no
>> 469da865-0712-4d4b-a4cf-a2d68f99f1b6 active no
>> fff90cb5-06dd-33b3-8815-d78c08ca01d9 active no
>> [root@Rack2Host12 agent]# service cloudstack-agent stop
>> Stopping Cloud Agent:
>> [root@Rack2Host12 agent]# virsh pool-list
>> Name State  Autostart
>> -
>> 41b632b5-40b3-3024-a38b-ea259c72579f active no
>> 469da865-0712-4d4b-a4cf-a2d68f99f1b6 active no
>> fff90cb5-06dd-33b3-8815-d78c08ca01d9 active no
>> [root@Rack2Host12 agent]# virsh list
>>  IdName   State
>> 
>> [root@Rack2Host12 agent]# service libvirtd stop
>> Stopping libvirtd daemon:  [  OK  ]
>> [root@Rack2Host12 agent]# service libvirtd start
>> Starting libvirtd daemon:  [  OK  ]
>> [root@Rack2Host12 agent]# virsh pool-list
>> Name State  Autostart
>> -
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA administrators
> For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Apache CloudStack 4.2.0 (fifth round)

[Marcus Sorensen]

Sorry, july.

Xenserver
http://download.cloud.com/templates/4.2/systemvmtemplate-2013-07-12-master-xen.vhd.bz2


KVM 
http://download.cloud.com/templates/4.2/systemvmtemplate-2013-06-12-master-kvm.qcow2.bz2


VMware (generic)
http://download.cloud.com/templates/4.2/systemvmtemplate-4.2-vh7.ova

On Mon, Sep 16, 2013 at 11:10 AM, Marcus Sorensen  wrote:
> The stock image is actually from June 2013, I believe.  There is a
> requirement for a new system vm in 4.2 to support some of the newer
> features. It's absolutely necessary to use this image (or one with the
> same capabilities) in KVM, maybe less so with Xen.
>
> On Mon, Sep 16, 2013 at 10:59 AM, Daan Hoogland  
> wrote:
>> This is for xen.
>> the stock image works and it is build in february 2012.
>> We did some further investigation. It turns out that due to license
>> issues the xen server tools where removed the 6th of september 2012.
>> any template newer should not work unless you install
>> xe-guest-utilities yourself. bug 29 says
>> "patches/systemvm/debian/iptables_1.4.8-3local1checksum1_i386.deb is
>> present in the source tree.
>>
>> This is both a binary and a GPLed software and thus forbidden on two counts."
>>
>> in 3db9736a0754388d782b45d31e8e36c9966c508e this and another deb file
>> and a kernel module where removed from the cloudstack repo.
>> patches/systemvm/debian/xe-guest-utilities_5.6.0-595_i386.deb contains
>> the service  responsible for starting the xe-daemon.
>>
>> also xe-update-guest-attrs contains calls to 'xestore write', write as
>> parameter. On wheezy only xestore-write exists (maybe because of the
>> deb files that where not installed) the same goes for 'xenstore rm'.
>> Strangely it does contain a call to xenstore-read as well. A cp of
>> xenstore-ls to xenstore fixes this as all binaries are copies and is
>> it clever about its name.
>>
>> more is bound to follow,
>> Daan
>>
>>
>> On Mon, Sep 16, 2013 at 5:41 PM, Marcus Sorensen  wrote:
>>> I'm not sure I understand... my impression from your message is the
>>> stock 4.2 image works.  This is for Xen, right?  Does this mean that
>>> there's a step missing in building a custom system vm to make it match
>>> the stock image?
>>>
>>> On Mon, Sep 16, 2013 at 9:30 AM, Daan Hoogland  
>>> wrote:
 H,

 The problem is when creating a newer image for the system template as
 we did on our installations. It will not work with the 4.2 scripts. I
 am not making hard my thread of this being a blocker but it is a
 serious impediment for people wanting to harden their cloudstack
 environment.

 I am voting a +0 here as I think we are not going to use this distro
 for this reason.

 regards,
 Daan

 On Mon, Sep 16, 2013 at 4:05 PM, Daan Hoogland  
 wrote:
> At Schuberg Philis, we did some tests and noted that the xe-deamon on
> router vms is not started and that xenstore no longer exist under that
> name.
> The xenstore binary is copied to xenstore-write, --ls etc so this
> could be solved.
>
> I am sure how to formulate this as to convince you all this is a
> blocker but am inclined to do so.
>
> more accurate report will follow,
> Daan
>
> On Mon, Sep 16, 2013 at 12:40 PM, Ian Duffy  wrote:
>> +1
>>
>> Ran against simulator.
>>
>>
>> On 16 September 2013 11:25, Prasanna Santhanam  wrote:
>>
>>> +1 (binding)
>>>
>>> The test infra has deployed advanced zone with kvm and xenserver 6.2
>>> since Saturday and I dont see any new failures [1]. So no regressions.
>>> Also ran the simulator against 4.2 [2]
>>>
>>> [1]
>>> http://jenkins.buildacloud.org/view/cloudstack-qa/job/test-regression-matrix/
>>> [2] http://jenkins.buildacloud.org/view/simulator/job/run-checkin-tests/
>>>
>>> On Sun, Sep 15, 2013 at 10:18:48PM -0400, Chip Childers wrote:
>>> > +1 (binding)
>>> >
>>> > Tested with simulator.
>>> >
>>> >
>>> >
>>> > On Sep 14, 2013, at 5:59 PM, Marcus Sorensen 
>>> wrote:
>>> >
>>> > > +1 (binding)
>>> > >
>>> > > Tested CentOS 6.4 and Ubuntu 12.04.3:
>>> > > create advanced zone
>>> > > create VPC
>>> > > register template
>>> > > create VPC tier
>>> > > create VM on tier w/NFS
>>> > > create VM on tier w/CLM
>>> > > create VM on tier w/Local storage
>>> > > create static NAT to vm, ssh in
>>> > >
>>> > > On Sat, Sep 14, 2013 at 10:28 AM, Rajesh Battala
>>> > >  wrote:
>>> > >> +1
>>> > >>
>>> > >> Tested VM Life cycle in Xenserver and KVM with Advance Zone
>>> configuration.
>>> > >>
>>> > >> Thanks
>>> > >> Rajesh Battala
>>> > >>
>>> > >> -Original Message-
>>> > >> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
>>> > >> Sent: Saturday, September 14, 2013 4:43 AM
>>> > >> To: dev@cloudstack.apache.org
>>> > >> Subject: Apache Clo

Re: Apache CloudStack 4.2.0 (fifth round)

[Daan Hoogland]

H,

The problem is when creating a newer image for the system template as
we did on our installations. It will not work with the 4.2 scripts. I
am not making hard my thread of this being a blocker but it is a
serious impediment for people wanting to harden their cloudstack
environment.

I am voting a +0 here as I think we are not going to use this distro
for this reason.

regards,
Daan

On Mon, Sep 16, 2013 at 4:05 PM, Daan Hoogland  wrote:
> At Schuberg Philis, we did some tests and noted that the xe-deamon on
> router vms is not started and that xenstore no longer exist under that
> name.
> The xenstore binary is copied to xenstore-write, --ls etc so this
> could be solved.
>
> I am sure how to formulate this as to convince you all this is a
> blocker but am inclined to do so.
>
> more accurate report will follow,
> Daan
>
> On Mon, Sep 16, 2013 at 12:40 PM, Ian Duffy  wrote:
>> +1
>>
>> Ran against simulator.
>>
>>
>> On 16 September 2013 11:25, Prasanna Santhanam  wrote:
>>
>>> +1 (binding)
>>>
>>> The test infra has deployed advanced zone with kvm and xenserver 6.2
>>> since Saturday and I dont see any new failures [1]. So no regressions.
>>> Also ran the simulator against 4.2 [2]
>>>
>>> [1]
>>> http://jenkins.buildacloud.org/view/cloudstack-qa/job/test-regression-matrix/
>>> [2] http://jenkins.buildacloud.org/view/simulator/job/run-checkin-tests/
>>>
>>> On Sun, Sep 15, 2013 at 10:18:48PM -0400, Chip Childers wrote:
>>> > +1 (binding)
>>> >
>>> > Tested with simulator.
>>> >
>>> >
>>> >
>>> > On Sep 14, 2013, at 5:59 PM, Marcus Sorensen 
>>> wrote:
>>> >
>>> > > +1 (binding)
>>> > >
>>> > > Tested CentOS 6.4 and Ubuntu 12.04.3:
>>> > > create advanced zone
>>> > > create VPC
>>> > > register template
>>> > > create VPC tier
>>> > > create VM on tier w/NFS
>>> > > create VM on tier w/CLM
>>> > > create VM on tier w/Local storage
>>> > > create static NAT to vm, ssh in
>>> > >
>>> > > On Sat, Sep 14, 2013 at 10:28 AM, Rajesh Battala
>>> > >  wrote:
>>> > >> +1
>>> > >>
>>> > >> Tested VM Life cycle in Xenserver and KVM with Advance Zone
>>> configuration.
>>> > >>
>>> > >> Thanks
>>> > >> Rajesh Battala
>>> > >>
>>> > >> -Original Message-
>>> > >> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
>>> > >> Sent: Saturday, September 14, 2013 4:43 AM
>>> > >> To: dev@cloudstack.apache.org
>>> > >> Subject: Apache CloudStack 4.2.0 (fifth round)
>>> > >>
>>> > >>
>>> > >> 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: c1e24ff89f6d14d6ae74d12dbca108c35449030f
>>> > >>
>>> > >> 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 (Wednesday 9/18 End of Day PST).
>>> > >>
>>> > >> 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)
>>> > >
>>>
>>> --
>>> Prasanna.,
>>>
>>> 
>>> Powered by BigRock.com
>>>
>>>

Review Request 14148: Cleanup DefaultUserAuthenticator and removed masking _name variable

[Darren Shepherd]

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

Review request for cloudstack and Abhinandan Prateek.


Repository: cloudstack-git


Description
---

DefaultUserAuthenticator maskes the _name varible in ComponentLifecycleBase 
making the setName() method not work as expected.  This patch cleans up the 
code such that getName() will be getClass().getSimpleName() unless overridden 
in the Spring configuration.


Diffs
-

  
plugins/user-authenticators/ldap/src/org/apache/cloudstack/ldap/LdapAuthenticator.java
 e62a3d8 
  
plugins/user-authenticators/md5/src/com/cloud/server/auth/MD5UserAuthenticator.java
 e5b169f 
  
plugins/user-authenticators/plain-text/src/com/cloud/server/auth/PlainTextUserAuthenticator.java
 f102275 
  
plugins/user-authenticators/sha256salted/src/com/cloud/server/auth/SHA256SaltedUserAuthenticator.java
 91be922 
  server/src/com/cloud/server/auth/DefaultUserAuthenticator.java 952f724 

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


Testing
---


Thanks,

Darren Shepherd

Re: Call for 4.3 and 4.2.1 Release Managers!

[Abhinandan Prateek]

If it is fine with community I am willing to take up 4.2.1 maintenance
release. 

-abhi

On 16/09/13 5:05 pm, "Daan Hoogland"  wrote:

>Animesh, I am passing till next time, I am willing though if really no
>one can be found.
>
>Daan
>
>On Wed, Sep 11, 2013 at 7:57 AM, Animesh Chaturvedi
> wrote:
>> Folks
>>
>> Now that 4.2.0 VOTE has passed I want to call out for any committers
>>who are interested in taking over as the release manager for the
>>upcoming 4.2.1 maintenance release and the 4.3.0 release.
>>
>>
>> Following our 4 month release cycle the feature freeze for 4.3.0 should
>>be by end of October and as community we need to figure out the
>>timelines for 4.2.1 maintenance release.
>>
>> I will update my experience and learning from the 4.2.0 release in the
>>wiki shortly after the formal release announcement  later this week.
>>
>> Thanks
>> Animesh
>>
>>
>>
>>

Re: [PROPOSAL][SIMPLIFY] Future ACS RC testing

[Marcus Sorensen]

I think this discussion should be linked with the discussion about minimum
requirements for a release (release criteria). It seems this discussion is
already being had to some degree.
On Sep 16, 2013 5:27 AM, "sebgoa"  wrote:

>
> On Sep 15, 2013, at 8:24 PM, Daan Hoogland 
> wrote:
>
> > Sebastien,
> >
> > Are you thinking november in Amsterdam, or before?
>
> I was thinking about a conference call - way before Amsterdam-
>
> >
> > On Thu, Sep 12, 2013 at 9:06 AM, sebgoa  wrote:
> >>
> >> On Sep 11, 2013, at 5:25 PM, "Musayev, Ilya" 
> wrote:
> >>
> >>> As mentioned on private, I think the reason we have so few responders
> when it comes to voting - is because it takes considerable amount of time
> to build, test and QA. And if you take voting serious as everyone should,
> you have to QA before you can vote.
> >>>
> >>>
> >>>
> >>> Perhaps we should spent some time on automation and take an automation
> step further.
> >>>
> >>>
> >>>
> >>> My next dream project is to create a set of 3 virtual appliances.
> >>>
> >>>
> >>>
> >>> Set 1:
> >>>
> >>> 2 KVM Hypervisors preconfigured with NFS
> >>>
> >>> 1 CloudStack MS with latest RC code
> >>>
> >>>
> >>>
> >>> Set 2:
> >>>
> >>> 2 XEN Hypervisors preconfigured with NFS
> >>>
> >>> 1 CloudStack MS with latest RC code
> >>>
> >>>
> >>>
> >>> Set 3:
> >>>
> >>> 1 CloudStack MS with latest RC code
> >>>
> >>>
> >>>
> >>> Set 3 get a bit hairy because of Virtual Center and licensing, so we
> abstract it and let folks QA what they have.
> >>>
> >>> -
> >>>
> >>> Do you find this approach useful, or do you believe the build tests we
> do is sufficient?
> >>>
> >>> Who can join or atleast share scripts they use to automate
> provisioning of KVM and XEN hosts?
> >>>
> >>> I'm looking for set of "post" scripts they can configure XEN and KVM
> end 2 end.
> >>>
> >>> Thanks
> >>> ilya
> >>
> >> Ilya, I think this is in-line with what Marcus is proposing.
> >>
> >> In another thread on testing I proposed to have a meeting where anyone
> interested in testing can join and where we can hash out a plan, then
> report back to the list.
> >>
> >>
> >>
> >> -sebastien
>
>

Re: Apache CloudStack 4.2.0 (fifth round)

[Daan Hoogland]

It does not not work completely. It has no xe-daemon running when
instantiated so migration would fail is the theory, also some of our
monitoring scripts fail.

We failed to see it at first as well as it starts up and networking works

On Mon, Sep 16, 2013 at 7:17 PM, Marcus Sorensen  wrote:
> Ok, so you mean even the stock one does not work for Xen.  Can anyone
> else who as been testing Xen comment?
>
> On Mon, Sep 16, 2013 at 11:14 AM, Daan Hoogland  
> wrote:
>> On Mon, Sep 16, 2013 at 7:11 PM, Marcus Sorensen  wrote:
>>>
>>> Xenserver
>>> http://download.cloud.com/templates/4.2/systemvmtemplate-2013-07-12-master-xen.vhd.bz2
>>
>> I know, it does not have the xenstore binary on board that is called
>> by xe-update-guest-attrs

Re: Apache CloudStack 4.2.0 (fifth round)

[Marcus Sorensen]

The stock image is actually from June 2013, I believe.  There is a
requirement for a new system vm in 4.2 to support some of the newer
features. It's absolutely necessary to use this image (or one with the
same capabilities) in KVM, maybe less so with Xen.

On Mon, Sep 16, 2013 at 10:59 AM, Daan Hoogland  wrote:
> This is for xen.
> the stock image works and it is build in february 2012.
> We did some further investigation. It turns out that due to license
> issues the xen server tools where removed the 6th of september 2012.
> any template newer should not work unless you install
> xe-guest-utilities yourself. bug 29 says
> "patches/systemvm/debian/iptables_1.4.8-3local1checksum1_i386.deb is
> present in the source tree.
>
> This is both a binary and a GPLed software and thus forbidden on two counts."
>
> in 3db9736a0754388d782b45d31e8e36c9966c508e this and another deb file
> and a kernel module where removed from the cloudstack repo.
> patches/systemvm/debian/xe-guest-utilities_5.6.0-595_i386.deb contains
> the service  responsible for starting the xe-daemon.
>
> also xe-update-guest-attrs contains calls to 'xestore write', write as
> parameter. On wheezy only xestore-write exists (maybe because of the
> deb files that where not installed) the same goes for 'xenstore rm'.
> Strangely it does contain a call to xenstore-read as well. A cp of
> xenstore-ls to xenstore fixes this as all binaries are copies and is
> it clever about its name.
>
> more is bound to follow,
> Daan
>
>
> On Mon, Sep 16, 2013 at 5:41 PM, Marcus Sorensen  wrote:
>> I'm not sure I understand... my impression from your message is the
>> stock 4.2 image works.  This is for Xen, right?  Does this mean that
>> there's a step missing in building a custom system vm to make it match
>> the stock image?
>>
>> On Mon, Sep 16, 2013 at 9:30 AM, Daan Hoogland  
>> wrote:
>>> H,
>>>
>>> The problem is when creating a newer image for the system template as
>>> we did on our installations. It will not work with the 4.2 scripts. I
>>> am not making hard my thread of this being a blocker but it is a
>>> serious impediment for people wanting to harden their cloudstack
>>> environment.
>>>
>>> I am voting a +0 here as I think we are not going to use this distro
>>> for this reason.
>>>
>>> regards,
>>> Daan
>>>
>>> On Mon, Sep 16, 2013 at 4:05 PM, Daan Hoogland  
>>> wrote:
 At Schuberg Philis, we did some tests and noted that the xe-deamon on
 router vms is not started and that xenstore no longer exist under that
 name.
 The xenstore binary is copied to xenstore-write, --ls etc so this
 could be solved.

 I am sure how to formulate this as to convince you all this is a
 blocker but am inclined to do so.

 more accurate report will follow,
 Daan

 On Mon, Sep 16, 2013 at 12:40 PM, Ian Duffy  wrote:
> +1
>
> Ran against simulator.
>
>
> On 16 September 2013 11:25, Prasanna Santhanam  wrote:
>
>> +1 (binding)
>>
>> The test infra has deployed advanced zone with kvm and xenserver 6.2
>> since Saturday and I dont see any new failures [1]. So no regressions.
>> Also ran the simulator against 4.2 [2]
>>
>> [1]
>> http://jenkins.buildacloud.org/view/cloudstack-qa/job/test-regression-matrix/
>> [2] http://jenkins.buildacloud.org/view/simulator/job/run-checkin-tests/
>>
>> On Sun, Sep 15, 2013 at 10:18:48PM -0400, Chip Childers wrote:
>> > +1 (binding)
>> >
>> > Tested with simulator.
>> >
>> >
>> >
>> > On Sep 14, 2013, at 5:59 PM, Marcus Sorensen 
>> wrote:
>> >
>> > > +1 (binding)
>> > >
>> > > Tested CentOS 6.4 and Ubuntu 12.04.3:
>> > > create advanced zone
>> > > create VPC
>> > > register template
>> > > create VPC tier
>> > > create VM on tier w/NFS
>> > > create VM on tier w/CLM
>> > > create VM on tier w/Local storage
>> > > create static NAT to vm, ssh in
>> > >
>> > > On Sat, Sep 14, 2013 at 10:28 AM, Rajesh Battala
>> > >  wrote:
>> > >> +1
>> > >>
>> > >> Tested VM Life cycle in Xenserver and KVM with Advance Zone
>> configuration.
>> > >>
>> > >> Thanks
>> > >> Rajesh Battala
>> > >>
>> > >> -Original Message-
>> > >> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
>> > >> Sent: Saturday, September 14, 2013 4:43 AM
>> > >> To: dev@cloudstack.apache.org
>> > >> Subject: Apache CloudStack 4.2.0 (fifth round)
>> > >>
>> > >>
>> > >> 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: c1e24ff89f6d14d6ae74d12dbca108c35449030f
>> > >>
>> > >> List of changes:
>> > >>
>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;

Re: Managed storage with KVM

[Mike Tutkowski]

Thanks, Marcus

About this:

"When the agent connects to the
management server, it registers all pools in the cluster with the
agent."

So, my plug-in allows you to create zone-wide primary storage. This just
means that any cluster can use the SAN (the SAN was registered as primary
storage as opposed to a preallocated volume from the SAN). Once you create
a primary storage based on this plug-in, the storage framework will invoke
the plug-in, as needed, to create and delete volumes on the SAN. For
example, you could have one SolidFire primary storage (zone wide) and
currently have 100 volumes created on the SAN to support it.

In this case, what will the management server be registering with the agent
in ModifyStoragePool? If only the storage pool (primary storage) is passed
in, that will be too vague as it does not contain information on what
volumes have been created for the agent.

Thanks


On Sun, Sep 15, 2013 at 11:53 PM, Marcus Sorensen wrote:

> Yes, see my previous email from the 13th. You can create your own
> KVMStoragePool class, and StorageAdaptor class, like the libvirt ones
> have. The previous email outlines how to add your own StorageAdaptor
> alongside LibvirtStorageAdaptor to take over all of the calls
> (createStoragePool, getStoragePool, etc). As mentioned,
> getPhysicalDisk I believe will be the one you use to actually attach a
> lun.
>
> Ignore CreateStoragePoolCommand. When the agent connects to the
> management server, it registers all pools in the cluster with the
> agent. It will call ModifyStoragePoolCommand, passing your storage
> pool object (with all of the settings for your SAN). This in turn
> calls _storagePoolMgr.createStoragePool, which will route through
> KVMStoragePoolManager to your storage adapter that you've registered.
> The last argument to createStoragePool is the pool type, which is used
> to select a StorageAdaptor.
>
> From then on, most calls will only pass the volume info, and the
> volume will have the uuid of the storage pool. For this reason, your
> adaptor class needs to have a static Map variable that contains pool
> uuid and pool object. Whenever they call createStoragePool on your
> adaptor you add that pool to the map so that subsequent volume calls
> can look up the pool details for the volume by pool uuid. With the
> Libvirt adaptor, libvirt keeps track of that for you.
>
> When createStoragePool is called, you can log into the iscsi target
> (or make sure you are already logged in, as it can be called over
> again at any time), and when attach volume commands are fired off, you
> can attach individual LUNs that are asked for, or rescan (say that the
> plugin created a new ACL just prior to calling attach), or whatever is
> necessary.
>
> KVM is a bit more work, but you can do anything you want. Actually, I
> think you can call host scripts with Xen, but having the agent there
> that runs your own code gives you the flexibility to do whatever.
>
> On Sun, Sep 15, 2013 at 10:44 PM, Mike Tutkowski
>  wrote:
> > I see right now LibvirtComputingResource.java has the following method
> that
> > I might be able to leverage (it's probably not called at present and
> would
> > need to be implemented in my case to discover my iSCSI target and log in
> to
> > it):
> >
> > protected Answer execute(CreateStoragePoolCommand cmd) {
> >
> > return new Answer(cmd, true, "success");
> >
> > }
> >
> > I would probably be able to call the KVMStorageManager to have it use my
> > StorageAdaptor to do what's necessary here.
> >
> >
> >
> >
> > On Sun, Sep 15, 2013 at 10:37 PM, Mike Tutkowski
> >  wrote:
> >>
> >> Hey Marcus,
> >>
> >> When I implemented support in the XenServer and VMware plug-ins for
> >> "managed" storage, I started at the execute(AttachVolumeCommand)
> methods in
> >> both plug-ins.
> >>
> >> The code there was changed to check the AttachVolumeCommand instance
> for a
> >> "managed" property.
> >>
> >> If managed was false, the normal attach/detach logic would just run and
> >> the volume would be attached or detached.
> >>
> >> If managed was true, new 4.2 logic would run to create (let's talk
> >> XenServer here) a new SR and a new VDI inside of that SR (or to
> reattach an
> >> existing VDI inside an existing SR, if this wasn't the first time the
> volume
> >> was attached). If managed was true and we were detaching the volume,
> the SR
> >> would be detached from the XenServer hosts.
> >>
> >> I am currently walking through the execute(AttachVolumeCommand) in
> >> LibvirtComputingResource.java.
> >>
> >> I see how the XML is constructed to describe whether a disk should be
> >> attached or detached. I also see how we call in to get a StorageAdapter
> (and
> >> how I will likely need to write a new one of these).
> >>
> >> So, talking in XenServer terminology again, I was wondering if you think
> >> the approach we took in 4.2 with creating and deleting SRs in the
> >> execute(AttachVolumeCommand) method would work here or if there 

Re: [PROPOSAL][SIMPLIFY] Future ACS RC testing

[David Nalley]

On Mon, Sep 16, 2013 at 1:05 PM, Daan Hoogland  wrote:
> A worthy cause, and we should all strive for it.  It does put extra
> constraints on things like db upgrade scripts however. If ACS is
> releasable at all times, can users make their own release and expect
> all upgrade paths to work?
>
> I disagreed with you on documentation as a commit criteria in another
> thread, David. I do favor (extensive) unit tests as criteria.

Disagreeing is fine - no one (least of all me) says that my opinion is
right all of the time. :)

Over time I've become less concerned about a feature working, and more
concerned about changes in a feature breaking the rest of CloudStack.
Both are important - but I am to the point that I think that new
features (and bugfixes) need to demonstrate that they don't harm the
rest of ACS in the process. The real problem is that CloudStack is so
large in scope that not many understand the full scope of
interactions.

--David

Re: [jira] [Commented] (CLOUDSTACK-3565) Restarting libvirtd service leading to destroy storage pool

[Marcus Sorensen]

I think it seems easy to rename the mount when registering the pool, either
the old one (if that works) or the new one. Yes, HA has a bad habit of
remounting primary nfs in certain circumstances too.
On Sep 16, 2013 11:47 AM, "Wei Zhou (JIRA)"  wrote:

>
> [
> https://issues.apache.org/jira/browse/CLOUDSTACK-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13768543#comment-13768543]
>
> Wei Zhou commented on CLOUDSTACK-3565:
> --
>
> Marcus, Thanks for your reply.
> As Edison committed for CLOUDSTACK-4405 (the issue exists in 4.1 as well),
> he added a libvirt hook so libvirt is needed to restart.
> If storage pool is not persistent, it may take very long time to upgrade
> cloudstack and fix the issue.
> In libvirt, the define/create of storage pool will fail if the mountpoint
> is already mounted (I tested in 0.9.13 and 0.10.2).
> I will have a look the patches for CLOUDSTACK-3535 to see if the storage
> pool affect the HA or not.
>
> > Restarting libvirtd service leading to destroy storage pool
> > ---
> >
> > Key: CLOUDSTACK-3565
> > URL:
> https://issues.apache.org/jira/browse/CLOUDSTACK-3565
> > Project: CloudStack
> >  Issue Type: Bug
> >  Security Level: Public(Anyone can view this level - this is the
> default.)
> >  Components: KVM
> >Affects Versions: 4.2.0
> > Environment: KVM
> > Branch 4.2
> >Reporter: Rayees Namathponnan
> >Assignee: Marcus Sorensen
> >Priority: Blocker
> >  Labels: documentation
> > Fix For: 4.2.0
> >
> >
> > Steps to reproduce
> > Step 1 : Create cloudstack step in kvm
> > Step 2 : From kvm host check "virsh pool-list"
> > Step 3:  Stop and start libvirtd service
> > Step 4 : Check "virsh pool-list"
> > Actual Result
> > "virsh pool-list"  is blank after restart libvird service
> > [root@Rack2Host12 agent]# virsh pool-list
> > Name State  Autostart
> > -
> > 41b632b5-40b3-3024-a38b-ea259c72579f active no
> > 469da865-0712-4d4b-a4cf-a2d68f99f1b6 active no
> > fff90cb5-06dd-33b3-8815-d78c08ca01d9 active no
> > [root@Rack2Host12 agent]# service cloudstack-agent stop
> > Stopping Cloud Agent:
> > [root@Rack2Host12 agent]# virsh pool-list
> > Name State  Autostart
> > -
> > 41b632b5-40b3-3024-a38b-ea259c72579f active no
> > 469da865-0712-4d4b-a4cf-a2d68f99f1b6 active no
> > fff90cb5-06dd-33b3-8815-d78c08ca01d9 active no
> > [root@Rack2Host12 agent]# virsh list
> >  IdName   State
> > 
> > [root@Rack2Host12 agent]# service libvirtd stop
> > Stopping libvirtd daemon:  [  OK  ]
> > [root@Rack2Host12 agent]# service libvirtd start
> > Starting libvirtd daemon:  [  OK  ]
> > [root@Rack2Host12 agent]# virsh pool-list
> > Name State  Autostart
> > -
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA
> administrators
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>

RE: Apache CloudStack 4.2.0 (fifth round)

[Anthony Xu]

Xe-daemon is used to collect cpu/memory usage info inside VM, the VM cannot 
migrate without installing xe-daemon in XenServer,
But CloudStack has  a script scripts/vm/hypervisor/xenserver/make_migratable.sh 
to make VM migratable without xe-daemon, because user might forget to install 
xe-daemon inside Linux VM.


Anthony

-Original Message-
From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] 
Sent: Monday, September 16, 2013 10:23 AM
To: dev
Subject: Re: Apache CloudStack 4.2.0 (fifth round)

It does not not work completely. It has no xe-daemon running when instantiated 
so migration would fail is the theory, also some of our monitoring scripts fail.

We failed to see it at first as well as it starts up and networking works

On Mon, Sep 16, 2013 at 7:17 PM, Marcus Sorensen  wrote:
> Ok, so you mean even the stock one does not work for Xen.  Can anyone 
> else who as been testing Xen comment?
>
> On Mon, Sep 16, 2013 at 11:14 AM, Daan Hoogland  
> wrote:
>> On Mon, Sep 16, 2013 at 7:11 PM, Marcus Sorensen  wrote:
>>>
>>> Xenserver
>>> http://download.cloud.com/templates/4.2/systemvmtemplate-2013-07-12-
>>> master-xen.vhd.bz2
>>
>> I know, it does not have the xenstore binary on board that is called 
>> by xe-update-guest-attrs

Re: Apache CloudStack 4.2.0 (fifth round)

[Abhinandan Prateek]

In general we are maintaining tested stock images of system vm templates
and they have been now tested by the community for couple of months.
The cloudstack migration and HA is not dependant on the xe-daemon running
on the VM, that is the reason nobody noticed it.

-abhi



On 16/09/13 10:53 pm, "Daan Hoogland"  wrote:

>It does not not work completely. It has no xe-daemon running when
>instantiated so migration would fail is the theory, also some of our
>monitoring scripts fail.
>
>We failed to see it at first as well as it starts up and networking works
>
>On Mon, Sep 16, 2013 at 7:17 PM, Marcus Sorensen 
>wrote:
>> Ok, so you mean even the stock one does not work for Xen.  Can anyone
>> else who as been testing Xen comment?
>>
>> On Mon, Sep 16, 2013 at 11:14 AM, Daan Hoogland
>> wrote:
>>> On Mon, Sep 16, 2013 at 7:11 PM, Marcus Sorensen 
>>>wrote:

 Xenserver
 
http://download.cloud.com/templates/4.2/systemvmtemplate-2013-07-12-mas
ter-xen.vhd.bz2
>>>
>>> I know, it does not have the xenstore binary on board that is called
>>> by xe-update-guest-attrs

Re: Managed storage with KVM

[Mike Tutkowski]

Hey Marcus,

Thanks for that clarification.

Sorry if this is a redundant question:

When the AttachVolumeCommand comes in, it sounds like we thought the best
approach would be for me to discover and log in to the iSCSI target using
iscsiadm.

This will create a new device: /dev/sdX.

We would then pass this new device into the VM (passing XML into the
appropriate Libvirt API).

If this is an accurate understanding, can you tell me: Do you think we
should be using a Disk Storage Pool or an iSCSI Storage Pool?

I believe I recall you leaning toward a Disk Storage Pool because we will
have already discovered the iSCSI target and, as such, will already have a
device to pass into the VM.

It seems like either way would work.

Maybe I need to study Libvirt's iSCSI Storage Pools more to understand if
they would do the work of discovering the iSCSI target for me (and maybe
avoid me having to use iscsiadm).

Thanks for the clarification! :)


On Mon, Sep 16, 2013 at 11:08 AM, Marcus Sorensen wrote:

> It will still register the pool.  You still have a primary storage
> pool that you registered, whether it's local, cluster or zone wide.
> NFS is optionally zone wide as well (I'm assuming customers can launch
> your storage only cluster-wide if they choose for resource
> partitioning), but it registers the pool in Libvirt prior to use.
>
> Here's a better explanation of what I meant.  AttachVolumeCommand gets
> both pool and volume info. It first looks up the pool:
>
> KVMStoragePool primary = _storagePoolMgr.getStoragePool(
> cmd.getPooltype(),
> cmd.getPoolUuid());
>
> Then it looks up the disk from that pool:
>
> KVMPhysicalDisk disk = primary.getPhysicalDisk(cmd.getVolumePath());
>
> Most of the commands only pass volume info like this (getVolumePath
> generally means the uuid of the volume), since it looks up the pool
> separately. If you don't save the pool info in a map in your custom
> class when createStoragePool is called, then getStoragePool won't be
> able to find it. This is a simple thing in your implementation of
> createStoragePool, just thought I'd mention it because it is key. Just
> create a map of pool uuid and pool object and save them so they're
> available across all implementations of that class.
>
> On Mon, Sep 16, 2013 at 10:43 AM, Mike Tutkowski
>  wrote:
> > Thanks, Marcus
> >
> > About this:
> >
> > "When the agent connects to the
> > management server, it registers all pools in the cluster with the
> > agent."
> >
> > So, my plug-in allows you to create zone-wide primary storage. This just
> > means that any cluster can use the SAN (the SAN was registered as primary
> > storage as opposed to a preallocated volume from the SAN). Once you
> create a
> > primary storage based on this plug-in, the storage framework will invoke
> the
> > plug-in, as needed, to create and delete volumes on the SAN. For example,
> > you could have one SolidFire primary storage (zone wide) and currently
> have
> > 100 volumes created on the SAN to support it.
> >
> > In this case, what will the management server be registering with the
> agent
> > in ModifyStoragePool? If only the storage pool (primary storage) is
> passed
> > in, that will be too vague as it does not contain information on what
> > volumes have been created for the agent.
> >
> > Thanks
> >
> >
> > On Sun, Sep 15, 2013 at 11:53 PM, Marcus Sorensen 
> > wrote:
> >>
> >> Yes, see my previous email from the 13th. You can create your own
> >> KVMStoragePool class, and StorageAdaptor class, like the libvirt ones
> >> have. The previous email outlines how to add your own StorageAdaptor
> >> alongside LibvirtStorageAdaptor to take over all of the calls
> >> (createStoragePool, getStoragePool, etc). As mentioned,
> >> getPhysicalDisk I believe will be the one you use to actually attach a
> >> lun.
> >>
> >> Ignore CreateStoragePoolCommand. When the agent connects to the
> >> management server, it registers all pools in the cluster with the
> >> agent. It will call ModifyStoragePoolCommand, passing your storage
> >> pool object (with all of the settings for your SAN). This in turn
> >> calls _storagePoolMgr.createStoragePool, which will route through
> >> KVMStoragePoolManager to your storage adapter that you've registered.
> >> The last argument to createStoragePool is the pool type, which is used
> >> to select a StorageAdaptor.
> >>
> >> From then on, most calls will only pass the volume info, and the
> >> volume will have the uuid of the storage pool. For this reason, your
> >> adaptor class needs to have a static Map variable that contains pool
> >> uuid and pool object. Whenever they call createStoragePool on your
> >> adaptor you add that pool to the map so that subsequent volume calls
> >> can look up the pool details for the volume by pool uuid. With the
> >> Libvirt adaptor, libvirt keeps track of that for you.
> >>
> >> When createStoragePool is called, you can log into the iscsi target
> >> (o

com.cloud.network.ExternalIpAddressAllocator and com.cloud.network.IpAddrAllocator used?

[Darren Shepherd]

I can't find any reference to com.cloud.network.ExternalIpAddressAllocator
or com.cloud.network.IpAddrAllocator.  What are these classes for?

Darren

RE: [PROPOSAL][SIMPLIFY] Future ACS RC testing

[Musayev, Ilya]

+1 for meeting, I was not aware that Marcus had a similar thread.

I'm good for 17CET on Wednesday or if I'm reading this right, 11AM EST.

http://www.worldtimebuddy.com/cet-to-est-converter



> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Monday, September 16, 2013 1:17 PM
> To: dev
> Subject: Re: [PROPOSAL][SIMPLIFY] Future ACS RC testing
> 
> On Mon, Sep 16, 2013 at 7:12 PM, David Nalley  wrote:
> > I do favor (extensive) unit tests as criteria.
> >
> > Disagreeing is fine - no one (least of all me) says that my opinion is
> > right all of the time. :)
> >
> > Over time I've become less concerned about a feature working, and more
> > concerned about changes in a feature breaking the rest of CloudStack.
> 
> I will interpret this as a 'I concur' ;)

RE: Call for 4.3 and 4.2.1 Release Managers!

[Animesh Chaturvedi]

Abhi thanks for offering taking up 4.2.1 anyone else willing to take up 4.2.1 
or 4.3.0?

> -Original Message-
> From: Abhinandan Prateek [mailto:abhinandan.prat...@citrix.com]
> Sent: Monday, September 16, 2013 10:18 AM
> To: dev@cloudstack.apache.org
> Subject: Re: Call for 4.3 and 4.2.1 Release Managers!
> 
> If it is fine with community I am willing to take up 4.2.1 maintenance
> release.
> 
> -abhi
> 
> On 16/09/13 5:05 pm, "Daan Hoogland"  wrote:
> 
> >Animesh, I am passing till next time, I am willing though if really no
> >one can be found.
> >
> >Daan
> >
> >On Wed, Sep 11, 2013 at 7:57 AM, Animesh Chaturvedi
> > wrote:
> >> Folks
> >>
> >> Now that 4.2.0 VOTE has passed I want to call out for any committers
> >>who are interested in taking over as the release manager for the
> >>upcoming 4.2.1 maintenance release and the 4.3.0 release.
> >>
> >>
> >> Following our 4 month release cycle the feature freeze for 4.3.0
> >>should be by end of October and as community we need to figure out the
> >>timelines for 4.2.1 maintenance release.
> >>
> >> I will update my experience and learning from the 4.2.0 release in
> >>the wiki shortly after the formal release announcement  later this
> week.
> >>
> >> Thanks
> >> Animesh
> >>
> >>
> >>
> >>

Re: Apache CloudStack 4.2.0 (fifth round)

[Abhinandan Prateek]

Daan,
   It will be interesting to know the monitoring use cases, if the
community likes these in general we can include these in the maintenance
release.
The templates can be modified and generated independently as working
copies are maintained separately from the artefacts put for vote here.
We should start a thread to discuss these as I am also interested in
contributing in that area.

-abhi

On 16/09/13 10:53 pm, "Daan Hoogland"  wrote:

>It does not not work completely. It has no xe-daemon running when
>instantiated so migration would fail is the theory, also some of our
>monitoring scripts fail.
>
>We failed to see it at first as well as it starts up and networking works
>
>On Mon, Sep 16, 2013 at 7:17 PM, Marcus Sorensen 
>wrote:
>> Ok, so you mean even the stock one does not work for Xen.  Can anyone
>> else who as been testing Xen comment?
>>
>> On Mon, Sep 16, 2013 at 11:14 AM, Daan Hoogland
>> wrote:
>>> On Mon, Sep 16, 2013 at 7:11 PM, Marcus Sorensen 
>>>wrote:

 Xenserver
 
http://download.cloud.com/templates/4.2/systemvmtemplate-2013-07-12-mas
ter-xen.vhd.bz2
>>>
>>> I know, it does not have the xenstore binary on board that is called
>>> by xe-update-guest-attrs

RE: Call for 4.3 and 4.2.1 Release Managers!

[Animesh Chaturvedi]

> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Monday, September 16, 2013 4:35 AM
> To: dev
> Subject: Re: Call for 4.3 and 4.2.1 Release Managers!
> 
> Animesh, I am passing till next time, I am willing though if really no
> one can be found.
> 
> Dann

[Animesh>] Daan thanks for the offer, I was getting worried that no one wants 
to be RM. Let's see who else turns up. 

> 
> On Wed, Sep 11, 2013 at 7:57 AM, Animesh Chaturvedi
>  wrote:
> > Folks
> >
> > Now that 4.2.0 VOTE has passed I want to call out for any committers
> who are interested in taking over as the release manager for the
> upcoming 4.2.1 maintenance release and the 4.3.0 release.
> >
> >
> > Following our 4 month release cycle the feature freeze for 4.3.0
> should be by end of October and as community we need to figure out the
> timelines for 4.2.1 maintenance release.
> >
> > I will update my experience and learning from the 4.2.0 release in the
> wiki shortly after the formal release announcement  later this week.
> >
> > Thanks
> > Animesh
> >
> >
> >
> >

RE: 4.1 new feature post release?

[Musayev, Ilya]

I believe there was an issue with AWS API integration and 4.1.2 has to be 
released. 

Since I'm the Release Manager for 4.1.x, I plan to begin the work on it next 
week - and it may take a  time for me to get the publican docs right.

Marcus, do you believe we need to revert the commit below? I have no KVM infra 
to test.

Please confirm,

Thanks
ilya


> -Original Message-
> From: Wei Zhou [mailto:w.z...@leaseweb.com]
> Sent: Monday, September 16, 2013 3:41 AM
> To: Wido den Hollander; dev@cloudstack.apache.org
> Subject: RE: 4.1 new feature post release?
> 
> Marcus and Wido,
> Sorry I just saw this Email.
> I will create a JIRA ticket for them (both code and docs) later. I regarded 
> it as
> an improvement, not a new feature, this is why I cherry-picked it into 4.1
> branch. If you guys object it, I will revert it.
> 
> Marcus, could you create tickets for the issues you mentioned? The commit
> is in 4.2 and master branch as well. We need to fix potential issues.
> 
> 
> Kind Regards,
> 
> Wei ZHOU
> Innovation Engineer Cloud, LeaseWeb B.V.
> w.z...@leaseweb.com
> 
> -Original Message-
> From: Wido den Hollander [mailto:w...@widodh.nl]
> Sent: 16 September 2013 09:22
> To: dev@cloudstack.apache.org
> Cc: Wei Zhou
> Subject: Re: 4.1 new feature post release?
> 
> 
> 
> On 09/15/2013 07:32 AM, Marcus Sorensen wrote:
> > Hi guys, I was just pulling in updates from the 4.1 branch and noticed
> > commit 706e23623c3227d92ae498529166ca73d2a2bf4e, This looks like a
> new
> > feature. There's not a bug attached to it. It seems to allow admins to
> > set the CPU mode for KVM guests, e.g. host-passthrough, which makes
> > the VM show the actual CPU model of the host (and breaks live
> > migration in some cases), etc.
> >
> > I see no reason off hand why this should have been cherry-picked into
> > 4.1.  It's been awhile, and I'm not sure whether or not we'll release
> > a 4.1.2, but we may want to review/revert it if we don't find out why
> > it was picked.
> >
> 
> Good point. 4.1.2 release or not, there shouldn't be any new features in the
> 4.1 branch.
> 
> Wei, can you comment on this?
> 
> Wido
> 
> > commit 706e23623c3227d92ae498529166ca73d2a2bf4e
> > Author: JijunLiu 
> > Date:   Sun Jul 14 11:21:39 2013 +0800
> >
> >  Add cpu model for kvm guest.Now all the kvm guest's cpu model is
> > 'QEMU Virtual CPU version xxx'. This will affect the activati
> >
> >  Signed-off-by: Wei Zhou 
> >  (cherry picked from commit
> > 2903bb5fd9d59803980102854d11e33ebe56088b)
> >

Re: [PROPOSAL][SIMPLIFY] Future ACS RC testing

[Marcus Sorensen]

It's Dave Nalley's thread :-)

On Mon, Sep 16, 2013 at 1:05 PM, Musayev, Ilya  wrote:
> +1 for meeting, I was not aware that Marcus had a similar thread.
>
> I'm good for 17CET on Wednesday or if I'm reading this right, 11AM EST.
>
> http://www.worldtimebuddy.com/cet-to-est-converter
>
>
>
>> -Original Message-
>> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
>> Sent: Monday, September 16, 2013 1:17 PM
>> To: dev
>> Subject: Re: [PROPOSAL][SIMPLIFY] Future ACS RC testing
>>
>> On Mon, Sep 16, 2013 at 7:12 PM, David Nalley  wrote:
>> > I do favor (extensive) unit tests as criteria.
>> >
>> > Disagreeing is fine - no one (least of all me) says that my opinion is
>> > right all of the time. :)
>> >
>> > Over time I've become less concerned about a feature working, and more
>> > concerned about changes in a feature breaking the rest of CloudStack.
>>
>> I will interpret this as a 'I concur' ;)
>
>

Re: [jira] [Commented] (CLOUDSTACK-3565) Restarting libvirtd service leading to destroy storage pool

[Wido den Hollander]

On 09/16/2013 07:16 PM, Marcus Sorensen wrote:

I agree, it makes things more complicated. However, updating libvirt
should be a maintenance mode thing; I've seen it lose track of VMs
between major libvirt upgrades and have to kill/restart all vms to
reregister them with libvirt, best to be in maintenance.

If I remember right, the issues with persistent storage definitiions
were primarily related to failure scenarios, things like hard power
off of host, host would build up dozens of primary storage definitions
that it didn't need, creating unnecessary dependencies and potential
unnecessary outages (see other email about what happens when storage
goes down).

If edison has a patch then that's great. One idea I head was that if
the pool fails to register due to mountpoint already existing, we
could use an alternate mount point to register it. Old stuff will keep
working, new stuff will continue.


No! That will break migrations to machines which don't have that 
mountpoint. Backing devices with QCOW2 will also break on the longer run.


Please do not do that.

Wido



On Mon, Sep 16, 2013 at 3:43 AM, Wei Zhou (JIRA)  wrote:


 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13768197#comment-13768197
 ]

Wei Zhou commented on CLOUDSTACK-3565:
--

Marcus,

The change of the host to maintenance one by one makes upgrade/change 
complicated.
Edison has changed the source to support re-creating storage pool in the fix of 
CLOUDSTACK-2729.
However, the test failed in my environment.

By the way, I did not see any other issue when I used cloudstack 4.0 while the 
storage pools are persistent.
I do not know what issue will be leader by it.


Restarting libvirtd service leading to destroy storage pool
---

 Key: CLOUDSTACK-3565
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3565
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the default.)
  Components: KVM
Affects Versions: 4.2.0
 Environment: KVM
Branch 4.2
Reporter: Rayees Namathponnan
Assignee: Marcus Sorensen
Priority: Blocker
  Labels: documentation
 Fix For: 4.2.0


Steps to reproduce
Step 1 : Create cloudstack step in kvm
Step 2 : From kvm host check "virsh pool-list"
Step 3:  Stop and start libvirtd service
Step 4 : Check "virsh pool-list"
Actual Result
"virsh pool-list"  is blank after restart libvird service
[root@Rack2Host12 agent]# virsh pool-list
Name State  Autostart
-
41b632b5-40b3-3024-a38b-ea259c72579f active no
469da865-0712-4d4b-a4cf-a2d68f99f1b6 active no
fff90cb5-06dd-33b3-8815-d78c08ca01d9 active no
[root@Rack2Host12 agent]# service cloudstack-agent stop
Stopping Cloud Agent:
[root@Rack2Host12 agent]# virsh pool-list
Name State  Autostart
-
41b632b5-40b3-3024-a38b-ea259c72579f active no
469da865-0712-4d4b-a4cf-a2d68f99f1b6 active no
fff90cb5-06dd-33b3-8815-d78c08ca01d9 active no
[root@Rack2Host12 agent]# virsh list
  IdName   State

[root@Rack2Host12 agent]# service libvirtd stop
Stopping libvirtd daemon:  [  OK  ]
[root@Rack2Host12 agent]# service libvirtd start
Starting libvirtd daemon:  [  OK  ]
[root@Rack2Host12 agent]# virsh pool-list
Name State  Autostart
-


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Managed storage with KVM

[Mike Tutkowski]

I understand what you're saying now, Marcus.

I wasn't sure if the Libvirt iSCSI Storage Pool was still an option
(looking into that still), but I see what you mean: If it is, we don't need
a new adaptor; otherwise, we do.

If Libivirt's iSCSI Storage Pool does work, I could update the current
adaptor, if need be, to make use of it.


On Mon, Sep 16, 2013 at 12:24 PM, Marcus Sorensen wrote:

> Well, you'd use neither of the two pool types, because you are not letting
> libvirt handle the pool, you are doing it with your own pool and adaptor
> class. Libvirt will be unaware of everything but the disk XML you attach to
> a vm. You'd only use those if libvirts functions were advantageous, I.e. if
> it already did everything you want. Since neither of those seem to provide
> both iscsi and the 1:1 mapping you want that's why we are talking about
> your own pool/adaptor.
>
> You can log into the target via your implementation of getPhysicalDisk as
> you mention in AttachVolumeCommand, or log in during your implementation of
> createStoragePool and simply rescan for luns in getPhysicalDisk. Presumably
> in most cases the host will be logged in already and new luns have been
> created in the meantime.
> On Sep 16, 2013 12:09 PM, "Mike Tutkowski" 
> wrote:
>
>> Hey Marcus,
>>
>> Thanks for that clarification.
>>
>> Sorry if this is a redundant question:
>>
>> When the AttachVolumeCommand comes in, it sounds like we thought the best
>> approach would be for me to discover and log in to the iSCSI target using
>> iscsiadm.
>>
>> This will create a new device: /dev/sdX.
>>
>> We would then pass this new device into the VM (passing XML into the
>> appropriate Libvirt API).
>>
>> If this is an accurate understanding, can you tell me: Do you think we
>> should be using a Disk Storage Pool or an iSCSI Storage Pool?
>>
>> I believe I recall you leaning toward a Disk Storage Pool because we will
>> have already discovered the iSCSI target and, as such, will already have a
>> device to pass into the VM.
>>
>> It seems like either way would work.
>>
>> Maybe I need to study Libvirt's iSCSI Storage Pools more to understand if
>> they would do the work of discovering the iSCSI target for me (and maybe
>> avoid me having to use iscsiadm).
>>
>> Thanks for the clarification! :)
>>
>>
>> On Mon, Sep 16, 2013 at 11:08 AM, Marcus Sorensen wrote:
>>
>>> It will still register the pool.  You still have a primary storage
>>> pool that you registered, whether it's local, cluster or zone wide.
>>> NFS is optionally zone wide as well (I'm assuming customers can launch
>>> your storage only cluster-wide if they choose for resource
>>> partitioning), but it registers the pool in Libvirt prior to use.
>>>
>>> Here's a better explanation of what I meant.  AttachVolumeCommand gets
>>> both pool and volume info. It first looks up the pool:
>>>
>>> KVMStoragePool primary = _storagePoolMgr.getStoragePool(
>>> cmd.getPooltype(),
>>> cmd.getPoolUuid());
>>>
>>> Then it looks up the disk from that pool:
>>>
>>> KVMPhysicalDisk disk = primary.getPhysicalDisk(cmd.getVolumePath());
>>>
>>> Most of the commands only pass volume info like this (getVolumePath
>>> generally means the uuid of the volume), since it looks up the pool
>>> separately. If you don't save the pool info in a map in your custom
>>> class when createStoragePool is called, then getStoragePool won't be
>>> able to find it. This is a simple thing in your implementation of
>>> createStoragePool, just thought I'd mention it because it is key. Just
>>> create a map of pool uuid and pool object and save them so they're
>>> available across all implementations of that class.
>>>
>>> On Mon, Sep 16, 2013 at 10:43 AM, Mike Tutkowski
>>>  wrote:
>>> > Thanks, Marcus
>>> >
>>> > About this:
>>> >
>>> > "When the agent connects to the
>>> > management server, it registers all pools in the cluster with the
>>> > agent."
>>> >
>>> > So, my plug-in allows you to create zone-wide primary storage. This
>>> just
>>> > means that any cluster can use the SAN (the SAN was registered as
>>> primary
>>> > storage as opposed to a preallocated volume from the SAN). Once you
>>> create a
>>> > primary storage based on this plug-in, the storage framework will
>>> invoke the
>>> > plug-in, as needed, to create and delete volumes on the SAN. For
>>> example,
>>> > you could have one SolidFire primary storage (zone wide) and currently
>>> have
>>> > 100 volumes created on the SAN to support it.
>>> >
>>> > In this case, what will the management server be registering with the
>>> agent
>>> > in ModifyStoragePool? If only the storage pool (primary storage) is
>>> passed
>>> > in, that will be too vague as it does not contain information on what
>>> > volumes have been created for the agent.
>>> >
>>> > Thanks
>>> >
>>> >
>>> > On Sun, Sep 15, 2013 at 11:53 PM, Marcus Sorensen >> >
>>> > wrote:
>>> >>
>>> >> Yes, see my previous email from the 13th. You can create your 

Re: Libvirt-java 0.5.0 has been released

[Wido den Hollander]

On 09/16/2013 07:46 PM, Min Chen wrote:

I got the following test failure in building master:

Running com.cloud.hypervisor.kvm.resource.LibvirtComputingResourceTest
Tests run: 3, Failures: 0, Errors: 2, Skipped: 1, Time elapsed: 0.059 sec
<<< FAILURE!
testCreateVMFromSpecLegacy(com.cloud.hypervisor.kvm.resource.LibvirtComputi
ngResourceTest)  Time elapsed: 0.018 sec  <<< ERROR!
java.lang.UnsupportedClassVersionError: org/libvirt/LibvirtException :
Unsupported major.minor version 51.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)
at java.lang.ClassLoader.defineClass(ClassLoader.java:615)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)
at java.net.URLClassLoader.access$000(URLClassLoader.java:58)
at java.net.URLClassLoader$1.run(URLClassLoader.java:197)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResourceTest.testCreateVM
FromSpecLegacy(LibvirtComputingResourceTest.java:64)


Wido, is this related to this libvirt change?



I think so. I'll test this tomorrow, but I think the RedHat guys build 
the bindings with Java 7 since they all work on a recent Fedora version.


Wido



Thanks
-min



On 9/16/13 4:28 AM, "Wido den Hollander"  wrote:


On 09/16/2013 12:51 PM, Wei ZHOU wrote:

Thanks Wido.

Do you know the minimal requirement of libvirt if we use libvirt-java
0.5.0
?



There shouldn't be a difference in the required libvirt version. I
implemented a couple of methods in the bindings which were already in
libvirt for a long time, but the bindings was just missing them.

Wido



2013/9/16 Wido den Hollander 


Hi,

I worked with the RedHat guys last week to get libvirt-java 0.5.0
released
which has some nice new features for us:

- Supports different XML on destination host during migration
- Supports resizing volumes
- Supports more snapshot functionalities

I took the liberty to depend on 0.5.0 in master and also merge in the
code
for the VNC listen, we now no longer listen on 0.0.0.0 for VNC, which
was a
security issue imho.

The reason I'm bringing this to the list is that we can simplify some
code
around resizing volumes and snapshotting where we currently have some
nasty
scripts to do the work.

See my commits in libvirt-java: http://www.libvirt.org/git/?p=**

libvirt-java.git;a=summary

So keep in mind libvirt-java has some new features!

Wido

Re: Managed storage with KVM

[Marcus Sorensen]

That's right
On Sep 16, 2013 12:31 PM, "Mike Tutkowski" 
wrote:

> I understand what you're saying now, Marcus.
>
> I wasn't sure if the Libvirt iSCSI Storage Pool was still an option
> (looking into that still), but I see what you mean: If it is, we don't need
> a new adaptor; otherwise, we do.
>
> If Libivirt's iSCSI Storage Pool does work, I could update the current
> adaptor, if need be, to make use of it.
>
>
> On Mon, Sep 16, 2013 at 12:24 PM, Marcus Sorensen wrote:
>
>> Well, you'd use neither of the two pool types, because you are not
>> letting libvirt handle the pool, you are doing it with your own pool and
>> adaptor class. Libvirt will be unaware of everything but the disk XML you
>> attach to a vm. You'd only use those if libvirts functions were
>> advantageous, I.e. if it already did everything you want. Since neither of
>> those seem to provide both iscsi and the 1:1 mapping you want that's why we
>> are talking about your own pool/adaptor.
>>
>> You can log into the target via your implementation of getPhysicalDisk as
>> you mention in AttachVolumeCommand, or log in during your implementation of
>> createStoragePool and simply rescan for luns in getPhysicalDisk. Presumably
>> in most cases the host will be logged in already and new luns have been
>> created in the meantime.
>> On Sep 16, 2013 12:09 PM, "Mike Tutkowski" 
>> wrote:
>>
>>> Hey Marcus,
>>>
>>> Thanks for that clarification.
>>>
>>> Sorry if this is a redundant question:
>>>
>>> When the AttachVolumeCommand comes in, it sounds like we thought the
>>> best approach would be for me to discover and log in to the iSCSI target
>>> using iscsiadm.
>>>
>>> This will create a new device: /dev/sdX.
>>>
>>> We would then pass this new device into the VM (passing XML into the
>>> appropriate Libvirt API).
>>>
>>> If this is an accurate understanding, can you tell me: Do you think we
>>> should be using a Disk Storage Pool or an iSCSI Storage Pool?
>>>
>>> I believe I recall you leaning toward a Disk Storage Pool because we
>>> will have already discovered the iSCSI target and, as such, will already
>>> have a device to pass into the VM.
>>>
>>> It seems like either way would work.
>>>
>>> Maybe I need to study Libvirt's iSCSI Storage Pools more to understand
>>> if they would do the work of discovering the iSCSI target for me (and maybe
>>> avoid me having to use iscsiadm).
>>>
>>> Thanks for the clarification! :)
>>>
>>>
>>> On Mon, Sep 16, 2013 at 11:08 AM, Marcus Sorensen 
>>> wrote:
>>>
 It will still register the pool.  You still have a primary storage
 pool that you registered, whether it's local, cluster or zone wide.
 NFS is optionally zone wide as well (I'm assuming customers can launch
 your storage only cluster-wide if they choose for resource
 partitioning), but it registers the pool in Libvirt prior to use.

 Here's a better explanation of what I meant.  AttachVolumeCommand gets
 both pool and volume info. It first looks up the pool:

 KVMStoragePool primary = _storagePoolMgr.getStoragePool(
 cmd.getPooltype(),
 cmd.getPoolUuid());

 Then it looks up the disk from that pool:

 KVMPhysicalDisk disk = primary.getPhysicalDisk(cmd.getVolumePath());

 Most of the commands only pass volume info like this (getVolumePath
 generally means the uuid of the volume), since it looks up the pool
 separately. If you don't save the pool info in a map in your custom
 class when createStoragePool is called, then getStoragePool won't be
 able to find it. This is a simple thing in your implementation of
 createStoragePool, just thought I'd mention it because it is key. Just
 create a map of pool uuid and pool object and save them so they're
 available across all implementations of that class.

 On Mon, Sep 16, 2013 at 10:43 AM, Mike Tutkowski
  wrote:
 > Thanks, Marcus
 >
 > About this:
 >
 > "When the agent connects to the
 > management server, it registers all pools in the cluster with the
 > agent."
 >
 > So, my plug-in allows you to create zone-wide primary storage. This
 just
 > means that any cluster can use the SAN (the SAN was registered as
 primary
 > storage as opposed to a preallocated volume from the SAN). Once you
 create a
 > primary storage based on this plug-in, the storage framework will
 invoke the
 > plug-in, as needed, to create and delete volumes on the SAN. For
 example,
 > you could have one SolidFire primary storage (zone wide) and
 currently have
 > 100 volumes created on the SAN to support it.
 >
 > In this case, what will the management server be registering with the
 agent
 > in ModifyStoragePool? If only the storage pool (primary storage) is
 passed
 > in, that will be too vague as it does not contain information on what
 > volumes have been created fo

OpenDayLight Project

[Soheil Eizadi]

Is there anyone on the development community involved in the OpenDayLight 
Project?
(http://www.opendaylight.org/)
-Soheil

Re: [jira] [Commented] (CLOUDSTACK-3565) Restarting libvirtd service leading to destroy storage pool

[Marcus Sorensen]

Good point, we'd have to modify the destination xml, which is kind of hairy.

I actually cant reproduce this on ubuntu 12.04 and the 4.2 RC. I mean,
'virsh pool-list' is blank as the bug reports, but so what? Is there a
separate bug we're discussing now?

 I created nfs primary storage, launched a vm on it, then restarted
libvirt. I verified the pools were erased via 'virsh pool-list', and
then attempted to launch a new vm with the nfs storage tag. It
registered in Libvirt and the VM is now running.  My intent was to try
a "umount -l", expecting that the existing VM's open filehandles would
stay working, and it would allow a fresh mount of the primary storage,
but there was no issue observed. Maybe I'm missing the root of the
issue reported.

root@devcloud-kvm-u:~# virsh pool-list
Name State  Autostart
-
2fe9a944-505e-38cb-bf87-72623634be4a active no  <--- nfs primary
609d4339-e66a-4298-909d-74dca7205a7b active no
vg0  active no  <--- clvm storage

root@devcloud-kvm-u:~# /etc/init.d/libvirt-bin restart
libvirt-bin stop/waiting
libvirt-bin start/running, process 7652

root@devcloud-kvm-u:~# virsh pool-list
Name State  Autostart
-

... wait for new vm to start

root@devcloud-kvm-u:~# virsh pool-list
Name State  Autostart
-
2fe9a944-505e-38cb-bf87-72623634be4a active no <--- nfs primary is back

... launch clvm storage-based vm, wait for it to start

root@devcloud-kvm-u:~# virsh pool-list
Name State  Autostart
-
2fe9a944-505e-38cb-bf87-72623634be4a active no
609d4339-e66a-4298-909d-74dca7205a7b active no
vg0  active no   <--- clvm



On Mon, Sep 16, 2013 at 2:15 PM, Wido den Hollander  wrote:
>
>
> On 09/16/2013 07:16 PM, Marcus Sorensen wrote:
>>
>> I agree, it makes things more complicated. However, updating libvirt
>> should be a maintenance mode thing; I've seen it lose track of VMs
>> between major libvirt upgrades and have to kill/restart all vms to
>> reregister them with libvirt, best to be in maintenance.
>>
>> If I remember right, the issues with persistent storage definitiions
>> were primarily related to failure scenarios, things like hard power
>> off of host, host would build up dozens of primary storage definitions
>> that it didn't need, creating unnecessary dependencies and potential
>> unnecessary outages (see other email about what happens when storage
>> goes down).
>>
>> If edison has a patch then that's great. One idea I head was that if
>> the pool fails to register due to mountpoint already existing, we
>> could use an alternate mount point to register it. Old stuff will keep
>> working, new stuff will continue.
>
>
> No! That will break migrations to machines which don't have that mountpoint.
> Backing devices with QCOW2 will also break on the longer run.
>
> Please do not do that.
>
> Wido
>
>
>>
>> On Mon, Sep 16, 2013 at 3:43 AM, Wei Zhou (JIRA)  wrote:
>>>
>>>
>>>  [
>>> https://issues.apache.org/jira/browse/CLOUDSTACK-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13768197#comment-13768197
>>> ]
>>>
>>> Wei Zhou commented on CLOUDSTACK-3565:
>>> --
>>>
>>> Marcus,
>>>
>>> The change of the host to maintenance one by one makes upgrade/change
>>> complicated.
>>> Edison has changed the source to support re-creating storage pool in the
>>> fix of CLOUDSTACK-2729.
>>> However, the test failed in my environment.
>>>
>>> By the way, I did not see any other issue when I used cloudstack 4.0
>>> while the storage pools are persistent.
>>> I do not know what issue will be leader by it.
>>>
 Restarting libvirtd service leading to destroy storage pool
 ---

  Key: CLOUDSTACK-3565
  URL:
 https://issues.apache.org/jira/browse/CLOUDSTACK-3565
  Project: CloudStack
   Issue Type: Bug
   Security Level: Public(Anyone can view this level - this is the
 default.)
   Components: KVM
 Affects Versions: 4.2.0
  Environment: KVM
 Branch 4.2
 Reporter: Rayees Namathponnan
 Assignee: Marcus Sorensen
 Priority: Blocker
   Labels: documentation
  Fix For: 4.2.0


 Steps to reproduce
 Step 1 : Create cloudstack step in kvm
 Step 2 : From kvm host check "virsh pool-list"
 Step 3:  Stop and start libvirtd service
 Step 4 : Check "virsh pool-list"
 Actual Result
 "virsh pool-list"  is blank after restart libvird service
 [root@Rack2Host12 agent]# virsh pool-list
 Name State  Autostart
>

contrail virtual network controller

[Pedro Roque Marques]

Myself and a few others in the Contrail team have been working on a cloudstack 
network plugin that interfaces with the contrail VNC 
(http://www.opencontrail.org). At the moment the plugin provides isolated guest 
networks (and a virtualized "Public" network) as an overlay that is capable of 
interconnecting directly with routers/switches that implement the existing 
standard for network virtualization (RFC 4364).

We would like to contribute this code to CloudStack. We intend to continue to 
enhance it in order to add full support for functionality one would expect out 
of the EC2 VPN API.

What is the process to do that ?

thanks,
  Pedro.

Re: [PROPOSAL][SIMPLIFY] Future ACS RC testing

[David Nalley]

On Mon, Sep 16, 2013 at 1:17 PM, Daan Hoogland  wrote:
> On Mon, Sep 16, 2013 at 7:12 PM, David Nalley  wrote:
>> I do favor (extensive) unit tests as criteria.
>>
>> Disagreeing is fine - no one (least of all me) says that my opinion is
>> right all of the time. :)
>>
>> Over time I've become less concerned about a feature working, and more
>> concerned about changes in a feature breaking the rest of CloudStack.
>
> I will interpret this as a 'I concur' ;)

:) Yes - that.

--David

Re: OpenDayLight Project

[Chiradeep Vittal]

I am following it from a distance :). I will be on a panel discussing it
on Wednesday:

http://sched.co/1dvmNgt

If anybody has any comments / wishes from OpenDayLight for CloudStack, let
me know.


On 9/16/13 1:46 PM, "Soheil Eizadi"  wrote:

>Is there anyone on the development community involved in the OpenDayLight
>Project?
>(http://www.opendaylight.org/)
>-Soheil

Re: Libvirt-java 0.5.0 has been released

[Min Chen]

I got the following test failure in building master:

Running com.cloud.hypervisor.kvm.resource.LibvirtComputingResourceTest
Tests run: 3, Failures: 0, Errors: 2, Skipped: 1, Time elapsed: 0.059 sec
<<< FAILURE!
testCreateVMFromSpecLegacy(com.cloud.hypervisor.kvm.resource.LibvirtComputi
ngResourceTest)  Time elapsed: 0.018 sec  <<< ERROR!
java.lang.UnsupportedClassVersionError: org/libvirt/LibvirtException :
Unsupported major.minor version 51.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)
at java.lang.ClassLoader.defineClass(ClassLoader.java:615)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)
at java.net.URLClassLoader.access$000(URLClassLoader.java:58)
at java.net.URLClassLoader$1.run(URLClassLoader.java:197)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at 
com.cloud.hypervisor.kvm.resource.LibvirtComputingResourceTest.testCreateVM
FromSpecLegacy(LibvirtComputingResourceTest.java:64)


Wido, is this related to this libvirt change?


Thanks
-min



On 9/16/13 4:28 AM, "Wido den Hollander"  wrote:

>On 09/16/2013 12:51 PM, Wei ZHOU wrote:
>> Thanks Wido.
>>
>> Do you know the minimal requirement of libvirt if we use libvirt-java
>>0.5.0
>> ?
>>
>
>There shouldn't be a difference in the required libvirt version. I
>implemented a couple of methods in the bindings which were already in
>libvirt for a long time, but the bindings was just missing them.
>
>Wido
>
>>
>> 2013/9/16 Wido den Hollander 
>>
>>> Hi,
>>>
>>> I worked with the RedHat guys last week to get libvirt-java 0.5.0
>>>released
>>> which has some nice new features for us:
>>>
>>> - Supports different XML on destination host during migration
>>> - Supports resizing volumes
>>> - Supports more snapshot functionalities
>>>
>>> I took the liberty to depend on 0.5.0 in master and also merge in the
>>>code
>>> for the VNC listen, we now no longer listen on 0.0.0.0 for VNC, which
>>>was a
>>> security issue imho.
>>>
>>> The reason I'm bringing this to the list is that we can simplify some
>>>code
>>> around resizing volumes and snapshotting where we currently have some
>>>nasty
>>> scripts to do the work.
>>>
>>> See my commits in libvirt-java: http://www.libvirt.org/git/?p=**
>>> 
>>>libvirt-java.git;a=summary>>t;a=summary>
>>>
>>> So keep in mind libvirt-java has some new features!
>>>
>>> Wido
>>>
>>
>

Re: HA redundant virtual router

[Sheng Yang]

The reason for no HA as I said before, due to the complexity. E.g, if there
can be 3 routers in the network(which control network is down but not the
guest network), and it would cause two of them with the same priority(at
certain time). The doc is mainly for describing the current policy and
reason, as the basic for possible improvement.

I haven't thought much about redundant router with HA, but many times we're
dealing with intermittent network issue, so you try to plug off then plug
in the network cable to see if HA works as expect.

The priority cannot changed on the fly, it's a parameter of keepalived
process, which is running. So at least both router need to be stopped
before priority reset. And it's not reset to minimum, since the value can
go up or down based on the different cases.

--Sheng


On Mon, Sep 16, 2013 at 2:25 AM, Daan Hoogland wrote:

> H Sheng,
>
> From your doc I don't read the reasons for disabling HA for RVR.
>
> I do see some possible glitches though. One is that a newly installed
> router should always have higher prio if the master cannot be reached.
> Something similar should happen on rule programming.
>
> To deal with the 255 limit on prios they could be reset to the minimum
> as soon as both routers are found again.
>
> Am I correct?
>
> thanks,
> Daan
>
> On Fri, Sep 6, 2013 at 12:27 AM, Sheng Yang  wrote:
> > Here is the doc.
> >
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Redundant+Virtual+Router+Functional+Spec
> >
> > It's not extremely detail, but describe today's design generally.
> >
> > --Sheng
> >
> >
> > On Thu, Aug 29, 2013 at 8:17 AM, Daan Hoogland 
> > wrote:
> >>
> >> ok,
> >>
> >> let's postpone the discussion till you are at least halve done. We
> >> will of course continue to deliberate on what we need internally.
> >>
> >> Daan
> >>
> >> On Thu, Aug 29, 2013 at 5:08 PM, Sheng Yang  wrote:
> >> > Hi Daan,
> >> >
> >> > As I said, I am writing a design doc to describe the current redundant
> >> > router policy, to help understanding redundant router. Current it
> >> > doesn't
> >> > support VPC, so how to implement it in VPC is still open to discuss.
> >> >
> >> > --Sheng
> >> >
> >> >
> >> > On Thu, Aug 29, 2013 at 4:26 AM, Daan Hoogland <
> daan.hoogl...@gmail.com>
> >> > wrote:
> >> >>
> >> >> Sheng,
> >> >>
> >> >> just to make sure; You are going to write this document? I see
> Roeland
> >> >> understood your mail like this.
> >> >>
> >> >> When you do, I'd like you to keep in mind that we also want redundant
> >> >> routers within a VPC to ensure ACS upgrades are more seamless for
> >> >> customer application groups and - dtap streets. If you need any help
> >> >> on writing such a doc, let me know.
> >> >>
> >> >> kind regards,
> >> >> Daan
> >> >>
> >> >> On Thu, Aug 29, 2013 at 1:13 PM, Roeland Kuipers
> >> >>  wrote:
> >> >> > Hi Sheng,
> >> >> >
> >> >> > Thanks for the info. Looking forward to the design doc, I trust
> this
> >> >> > will make things clearer.
> >> >> > In the meantime will be doing some research and thinking too, to
> see
> >> >> > how
> >> >> > we can improve things to also have HA on the RvR in a safe way.
> >> >> > We will share this once ready.
> >> >> >
> >> >> > Thanks,
> >> >> > Roeland
> >> >> >
> >> >> >
> >> >> > From: Sheng Yang [mailto:sh...@yasker.org]
> >> >> > Sent: donderdag 29 augustus 2013 0:19
> >> >> > To: 
> >> >> > Cc: int-cloud; Daan Hoogland
> >> >> > Subject: Re: HA redundant virtual router
> >> >> >
> >> >> > Hi Roeland,
> >> >> >
> >> >> > I would write a design doc to explain how redundant router works
> >> >> > currently. For example, for the point 2, we have to force BACKUP
> >> >> > become
> >> >> > MASTER because:
> >> >> >
> >> >> > 1. CS cannot communicate with MASTER at the time
> >> >> > 2. CS can communicate with BACKUP.
> >> >> > 3. Rule has to be programmed immediately.
> >> >> > 4. In case old MASTER come back, it should yield to the VR with
> >> >> > updated
> >> >> > rule, rather than preempt the updated VR.
> >> >> >
> >> >> > In this case, CS need to communicate with RvR to program the new
> >> >> > rule,
> >> >> > thus it need to intervene the RvR to ensure that if there is only
> one
> >> >> > VR got
> >> >> > the rule, it should become MASTER.
> >> >> >
> >> >> > Still, I would write a doc later to try to cover every concern of
> RvR
> >> >> > design.
> >> >> >
> >> >> > --Sheng
> >> >> >
> >> >> > On Tue, Aug 27, 2013 at 3:40 AM, Roeland Kuipers
> >> >> > mailto:rkuip...@schubergphilis.com>>
> >> >> > wrote:
> >> >> > Hi Sheng,
> >> >> >
> >> >> > Thanks for your reply. I'll see if we can replay this scenario.
> >> >> >
> >> >> > With respect to point 1: a good principal IMHO.
> >> >> >
> >> >> > Point 2: Why do we force a keepalived node to become master and not
> >> >> > wait
> >> >> > for keepalived to become master? This way there is less reason to
> >> >> > intervene
> >> >> > and less risk of multiple masters? As we have seen this behavior
> with
> >> >> > Rv

Re: Where is the latest system vm template file?

[Chiradeep Vittal]

I enabled cloudfront on this so that folks in
S.America/Africa/Europe/Asia/Oceania can have better speeds.
Just substitute d21ifhcun6b1t2.cloudfront.net for download.cloud.com


On 9/10/13 10:23 PM, "Yoshikazu Nojima"  wrote:

>Thank you! That's my looking for.
>
>Yoshikazu Nojima 
>
>2013/9/10 Harikrishna Patnala :
>> Hi,
>>
>> Xenserver   
>>http://download.cloud.com/templates/4.2/systemvmtemplate-2013-07-12-maste
>>r-xen.vhd.bz2
>>
>>
>> KVM 
>>http://download.cloud.com/templates/4.2/systemvmtemplate-2013-06-12-maste
>>r-kvm.qcow2.bz2
>>
>>
>> VMware (generic)
>>http://download.cloud.com/templates/4.2/systemvmtemplate-4.2-vh7.ova
>>
>> -Harikrishna
>> On 11-Sep-2013, at 10:04 AM, Yoshikazu Nojima
>>mailto:m...@ynojima.net>>
>>  wrote:
>>
>> Hi,
>>
>> I'm looking for latest system vm template file.
>> It seems jenkins job( build-systemvm-master ) does not generates an
>>artifact.
>> http://jenkins.cloudstack.org/view/master/job/build-systemvm-master/
>>
>> Do you know where can we download the latest latest system vm template
>>file?
>>
>> Thanks,
>>
>> Yoshikazu Nojima 
>>

Re: DhcpServiceProvider

[Sheng Yang]

That's the good reason to have explicitly remove the old dhcp entries.
Patches are welcome!

--Sheng


On Sat, Sep 14, 2013 at 3:38 PM, Soheil Eizadi  wrote:

> Thanks for highlighting why remove entry is not implemented. The interface
> works for internal implementation where you have the MS database and a
> separate table in the DHCP server that you are managing. If the DHCP
> Provider is external and authoritative on the IP Address Management or
> trying to provide discovery view this assumption is not valid, and you need
> to explicitly inform it when you want to add an entry and remove one. It
> looks like most External DHCP providers are going to use the standard
> Plugin prepare/release interface, like I have for our solution.
> -Soheil
> 
> From: Sheng Yang [sh...@yasker.org]
> Sent: Friday, September 13, 2013 4:23 PM
> To: 
> Subject: Re: DhcpServiceProvider
>
> In the original implementation, the new dhcp entry would automatically
> override the old one, so the old entry hasn't been removed explicitly.
>
> But still, it would be better to get it done explicitly of course.
>
> --Sheng
>
>
> On Fri, Sep 13, 2013 at 1:20 PM, Chiradeep Vittal <
> chiradeep.vit...@citrix.com> wrote:
>
> > Soheil, agree that it needs to moved to NetworkElement and also needs
> > complementary remove()
> > It seems half-thought-out.
> >
> > On 9/13/13 11:31 AM, "Soheil Eizadi"  wrote:
> >
> > >Posting my questions again... -Soheil
> > >
> > >From: Soheil Eizadi [seiz...@infoblox.com]
> > >Sent: Friday, September 06, 2013 3:13 PM
> > >To: dev@cloudstack.apache.org
> > >Subject: DhcpServiceProvider
> > >
> > >I had not looked at the DhcpServiceProvider NetworkElement before, but
> > >after recent problem, I got a chance to look at it in more detail. I am
> > >new to CloudStack and don't have a lot of the history and had some
> > >questions.
> > >
> > >Is there a link to documentation for the DhcpServiceProvider work?
> > >
> > >I assume the main use case for DhcpServiceProvider is to support DHCP
> > >Daemon like DNSMasq, are there other use cases?
> > >
> > >The interface is simple enough:
> > >
> > >
> > >public interface DhcpServiceProvider extends NetworkElement {
> > >
> > >boolean addDhcpEntry(...) ...;
> > >
> > >boolean configDhcpSupportForSubnet(...) ...;
> > >
> > >boolean  removeDhcpSupportForSubnet(...) ...;
> > >
> > >}
> > >
> > >
> > >Is there a reason why the companion entry to addDhcpEntry() e.g.
> > >removeDhcpEntry() is missing?
> > >
> > >
> > >What is the motivation in adding this code to the NetworkManager versus
> > >contain it inside the NetworkElement providing the DHCP? (The logic I
> see
> > >in NetworkManager does not seem to be adding any value. Also it is
> adding
> > >a specific network function DHCP to the NetworkManager, where we are
> > >moving functions e.g. IP Address Allocation out.)
> >
> >
>

Re: Error in start MS in master

[Kelven Yang]

You need to use command line like

mvn -Dnonoss -pl client jetty:run

Kelven

On 9/13/13 1:56 PM, "Min Chen"  wrote:

>Hi there,
>
>Did anybody experience any issues in starting MS in latest master? I ran
>into the following issue:
>
>org.springframework.beans.factory.BeanCreationException: Could not
>autowire field: 
>org.apache.cloudstack.framework.config.dao.ConfigurationDao
>org.apache.cloudstack.framework.config.impl.ConfigDepotImpl._configDao;
>nested exception is
>org.springframework.beans.factory.CannotLoadBeanClassException: Cannot
>find class [com.cloud.ha.VmwareFencer] for bean with name 'VmwareFencer'
>defined in class path resource [nonossComponentContext.xml]; nested
>exception is java.lang.ClassNotFoundException: com.cloud.ha.VmwareFencer
>at 
>org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostPr
>ocessor.postProcessPropertyValues(AutowiredAnnotationBeanPostProcessor.jav
>a:287)
>at 
>org.springframework.beans.factory.support.AbstractAutowireCapableBeanFacto
>ry.populateBean(AbstractAutowireCapableBeanFactory.java:1106)
>at 
>org.springframework.beans.factory.support.AbstractAutowireCapableBeanFacto
>ry.doCreateBean(AbstractAutowireCapableBeanFactory.java:517)
>
>
>Thanks
>-min

Re: Managed storage with KVM

[Marcus Sorensen]

Well, you'd use neither of the two pool types, because you are not letting
libvirt handle the pool, you are doing it with your own pool and adaptor
class. Libvirt will be unaware of everything but the disk XML you attach to
a vm. You'd only use those if libvirts functions were advantageous, I.e. if
it already did everything you want. Since neither of those seem to provide
both iscsi and the 1:1 mapping you want that's why we are talking about
your own pool/adaptor.

You can log into the target via your implementation of getPhysicalDisk as
you mention in AttachVolumeCommand, or log in during your implementation of
createStoragePool and simply rescan for luns in getPhysicalDisk. Presumably
in most cases the host will be logged in already and new luns have been
created in the meantime.
On Sep 16, 2013 12:09 PM, "Mike Tutkowski" 
wrote:

> Hey Marcus,
>
> Thanks for that clarification.
>
> Sorry if this is a redundant question:
>
> When the AttachVolumeCommand comes in, it sounds like we thought the best
> approach would be for me to discover and log in to the iSCSI target using
> iscsiadm.
>
> This will create a new device: /dev/sdX.
>
> We would then pass this new device into the VM (passing XML into the
> appropriate Libvirt API).
>
> If this is an accurate understanding, can you tell me: Do you think we
> should be using a Disk Storage Pool or an iSCSI Storage Pool?
>
> I believe I recall you leaning toward a Disk Storage Pool because we will
> have already discovered the iSCSI target and, as such, will already have a
> device to pass into the VM.
>
> It seems like either way would work.
>
> Maybe I need to study Libvirt's iSCSI Storage Pools more to understand if
> they would do the work of discovering the iSCSI target for me (and maybe
> avoid me having to use iscsiadm).
>
> Thanks for the clarification! :)
>
>
> On Mon, Sep 16, 2013 at 11:08 AM, Marcus Sorensen wrote:
>
>> It will still register the pool.  You still have a primary storage
>> pool that you registered, whether it's local, cluster or zone wide.
>> NFS is optionally zone wide as well (I'm assuming customers can launch
>> your storage only cluster-wide if they choose for resource
>> partitioning), but it registers the pool in Libvirt prior to use.
>>
>> Here's a better explanation of what I meant.  AttachVolumeCommand gets
>> both pool and volume info. It first looks up the pool:
>>
>> KVMStoragePool primary = _storagePoolMgr.getStoragePool(
>> cmd.getPooltype(),
>> cmd.getPoolUuid());
>>
>> Then it looks up the disk from that pool:
>>
>> KVMPhysicalDisk disk = primary.getPhysicalDisk(cmd.getVolumePath());
>>
>> Most of the commands only pass volume info like this (getVolumePath
>> generally means the uuid of the volume), since it looks up the pool
>> separately. If you don't save the pool info in a map in your custom
>> class when createStoragePool is called, then getStoragePool won't be
>> able to find it. This is a simple thing in your implementation of
>> createStoragePool, just thought I'd mention it because it is key. Just
>> create a map of pool uuid and pool object and save them so they're
>> available across all implementations of that class.
>>
>> On Mon, Sep 16, 2013 at 10:43 AM, Mike Tutkowski
>>  wrote:
>> > Thanks, Marcus
>> >
>> > About this:
>> >
>> > "When the agent connects to the
>> > management server, it registers all pools in the cluster with the
>> > agent."
>> >
>> > So, my plug-in allows you to create zone-wide primary storage. This just
>> > means that any cluster can use the SAN (the SAN was registered as
>> primary
>> > storage as opposed to a preallocated volume from the SAN). Once you
>> create a
>> > primary storage based on this plug-in, the storage framework will
>> invoke the
>> > plug-in, as needed, to create and delete volumes on the SAN. For
>> example,
>> > you could have one SolidFire primary storage (zone wide) and currently
>> have
>> > 100 volumes created on the SAN to support it.
>> >
>> > In this case, what will the management server be registering with the
>> agent
>> > in ModifyStoragePool? If only the storage pool (primary storage) is
>> passed
>> > in, that will be too vague as it does not contain information on what
>> > volumes have been created for the agent.
>> >
>> > Thanks
>> >
>> >
>> > On Sun, Sep 15, 2013 at 11:53 PM, Marcus Sorensen 
>> > wrote:
>> >>
>> >> Yes, see my previous email from the 13th. You can create your own
>> >> KVMStoragePool class, and StorageAdaptor class, like the libvirt ones
>> >> have. The previous email outlines how to add your own StorageAdaptor
>> >> alongside LibvirtStorageAdaptor to take over all of the calls
>> >> (createStoragePool, getStoragePool, etc). As mentioned,
>> >> getPhysicalDisk I believe will be the one you use to actually attach a
>> >> lun.
>> >>
>> >> Ignore CreateStoragePoolCommand. When the agent connects to the
>> >> management server, it registers all pools in the cluster with the
>> >> ag

keystore generation problem when bringing up mgmt server on devcloud

[Vijayendra Bhamidipati]

I'm setting up devcloud on mac os x and am running into this problem when 
bringing up the mgmt server (following the instructions on 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/DevCloud, this is in 
step 7.3)


INFO  [utils.component.ComponentContext] (Timer-2:) Configuring 
com.cloud.upgrade.DatabaseIntegrityChecker_EnhancerByCloudStack_372ea153
INFO  [utils.component.ComponentContext] (Timer-2:) Configuring 
com.cloud.server.ConfigurationServerImpl_EnhancerByCloudStack_f2e47214
INFO  [cloud.server.ConfigurationServerImpl] (Timer-2:) Processing 
updateSSLKeyStore
INFO  [cloud.server.ConfigurationServerImpl] (Timer-2:) SSL keystore located at 
/Users/vijay/work/cloudstack-ws/asf/cloudstack-apache/client/target/cloud-client-ui-4.2.0/WEB-INF/classes/cloud.keystore
Password:WARN  [utils.script.Script] (Script-1:) Interrupting script.
WARN  [utils.script.Script] (Timer-2:) Timed out: sudo keytool -genkey 
-keystore 
/Users/vijay/work/cloudstack-ws/asf/cloudstack-apache/client/target/cloud-client-ui-4.2.0/WEB-INF/classes/cloud.keystore
 -storepass vmops.com -keypass vmops.com -keyalg RSA -validity 3650 -dname 
cn="Cloudstack User",ou="local.citrite.net",o="local.citrite.net",c="Unknown" . 
 Output is:
WARN  [cloud.server.ConfigurationServerImpl] (Timer-2:) Would use fail-safe 
keystore to continue.
java.io.IOException: Fail to generate certificate!: timeout
at 
com.cloud.server.ConfigurationServerImpl.generateDefaultKeystore(ConfigurationServerImpl.java:496)
at 
com.cloud.server.ConfigurationServerImpl.updateSSLKeystore(ConfigurationServerImpl.java:517)
at 
com.cloud.server.ConfigurationServerImpl.persistDefaultValues(ConfigurationServerImpl.java:289)
at 
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at 
com.cloud.server.ConfigurationServerImpl.configure(ConfigurationServerImpl.java:157)
at 
com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:111)
at com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:54)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
INFO  [cloud.server.ConfigurationServerImpl] (Timer-2:) Processing 
updateKeyPairs
INFO  [cloud.server.ConfigurationServerImpl] (Timer-2:) Keypairs already in 
database, updating local copy
INFO  [cloud.server.ConfigurationServerImpl] (Timer-2:) Going to update 
systemvm iso with generated keypairs if needed
Password:



I'm running 4.2 however – not master. Why am I being prompted for a password 
again? The default keystore generation kicked in, so I cannot understand this 
repeated prompt – can't seem to find whether/where sudo keytool is being 
invoked again/retried – has anyone run into this issue before? Would be helpful 
if anyone running devcloud currently on os x could provide pointers.

Thanks!
Regards,
Vijay