date:20141019

Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 3 in branch 4.4-RC20141014T2316

2014-10-19 Thread Daan Hoogland

We have three binding +1 and no -1. It is thin but sufices according to our
bylaws. This RC is up for GA.

After (more then) 72 hours, the vote for CloudStack 4.4.1 *passes* with
3 PMC + 3 non-PMC votes.

+1 (PMC / binding)
3 people

+1 (non binding)
3 people

0
2 people

-1
none

Thanks to everyone participating.

I will now prepare the release announcement to go out after 24 hours
to give the mirrors time to catch up.



On Fri, Oct 17, 2014 at 4:19 PM, Daan Hoogland 
wrote:

> CLOUDSTACK-7365 
> was created by you Pierre-Luc. I am looking into the other side of the
> medal. have a generic systemvm upgrade api. It is related and I haven't
> found a ticket yet.
>
> On Fri, Oct 17, 2014 at 2:43 PM, Pierre-Luc Dion 
> wrote:
>
>> Hi Rohit,
>>
>> I'm aware of this behavior, it start with 4.3.0, if you upgrade to 4.3.0
>> or
>> 4.3.1 without having the new systemvm prior the upgrade, the db upgrade
>> will fail. which is why upgrading from 4.2.x to 4.4.1 require 2 new
>> systemvm to be install prior the upgrade.
>>
>> Further more, if you have multiple hypervisor type, let say you have
>> XenServer and KVM clusters but forced system vm to run on xenserver only.
>> by default you might only install the new sysvmtemplate for xenserver,
>> but,
>>  if you upgrade without having install the kvm systemvm version the db
>> upgrade will fail.
>>
>> I think their is jira issue around this already.
>>
>> On Fri, Oct 17, 2014 at 7:36 AM, Rohit Yadav 
>> wrote:
>>
>> > Hi Pierre,
>> >
>> > On 17-Oct-2014, at 4:42 pm, Pierre-Luc Dion  wrote:
>> > > Hi Rohit,
>> > > The doc in /latest is not the 4.4.1 latest, the correct documentation
>> is
>> > in
>> > > /4.4.1 it should have been corrected for the behavior describe and
>> also
>> > > contain correct url for sysvm ( not jenkins.bac.o).
>> > >
>> > > Once the 4.4.1 is released ill change the defaut url and update issues
>> > > lists in the RN.
>> >
>> > Thanks, that would be much needed.
>> >
>> > The issue is not that docs have those links, but that the Java class
>> > (440to441, the upgrade path) that upgrades CloudStack db has hard coded
>> URL
>> > and MD5 checksums of 4.4.0 template.
>> >
>> > The real issue is when a user tries to upgrade from any prior version of
>> > CloudStack to 4.4.1 or later version, they would be required to
>> register a
>> > 4.4.0-6 template (from Wido’s repo) before the upgrade which is
>> something
>> > they skip or forget to do it which would result in messed up upgraded
>> DB.
>> > For example, if I’m on 4.2.1 and I want to upgrade to 4.4.1 or later
>> (say
>> > 4.5.0 in future) if I don’t follow the docs (i.e. register 4.4.0-06
>> > template, that too not any 4.4.0 template, but the specific one from
>> Wido’s
>> > repo or some other url) my upgrade will fail.
>> >
>> > Regards,
>> > Rohit Yadav
>> > Software Architect, ShapeBlue
>> > M. +91 88 262 30892 | rohit.ya...@shapeblue.com
>> > Blog: bhaisaab.org | Twitter: @_bhaisaab
>> >
>> > Find out more about ShapeBlue and our range of CloudStack related
>> services
>> >
>> > IaaS Cloud Design & Build<
>> > http://shapeblue.com/iaas-cloud-design-and-build//>
>> > CSForge – rapid IaaS deployment framework> >
>> > CloudStack Consulting
>> > CloudStack Infrastructure Support<
>> > http://shapeblue.com/cloudstack-infrastructure-support/>
>> > CloudStack Bootcamp Training Courses<
>> > http://shapeblue.com/cloudstack-training/>
>> >
>> > This email and any attachments to it may be confidential and are
>> intended
>> > solely for the use of the individual to whom it is addressed. Any views
>> or
>> > opinions expressed are solely those of the author and do not necessarily
>> > represent those of Shape Blue Ltd or related companies. If you are not
>> the
>> > intended recipient of this email, you must neither take any action based
>> > upon its contents, nor copy or show it to anyone. Please contact the
>> sender
>> > if you believe you have received this email in error. Shape Blue Ltd is
>> a
>> > company incorporated in England & Wales. ShapeBlue Services India LLP
>> is a
>> > company incorporated in India and is operated under license from Shape
>> Blue
>> > Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in
>> Brasil
>> > and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd
>> is
>> > a company registered by The Republic of South Africa and is traded under
>> > license from Shape Blue Ltd. ShapeBlue is a registered trademark.
>> >
>>
>
>
>
> --
> Daan
>



-- 
Daan

Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 3 in branch 4.4-RC20141014T2316

2014-10-19 Thread Rohit Yadav

Hi Daan,

Can you make the 4.4.1 tag available on the 4.4 branch, right now the tag is 
pushed/seen on origin/4.4-RC20141014T2316 branch.

Regards.

> On 20-Oct-2014, at 12:01 am, Daan Hoogland  wrote:
>
> We have three binding +1 and no -1. It is thin but sufices according to our
> bylaws. This RC is up for GA.
>
> After (more then) 72 hours, the vote for CloudStack 4.4.1 *passes* with
> 3 PMC + 3 non-PMC votes.
>
> +1 (PMC / binding)
> 3 people
>
> +1 (non binding)
> 3 people
>
> 0
> 2 people
>
> -1
> none
>
> Thanks to everyone participating.
>
> I will now prepare the release announcement to go out after 24 hours
> to give the mirrors time to catch up.
>
>
>
> On Fri, Oct 17, 2014 at 4:19 PM, Daan Hoogland 
> wrote:
>
>> CLOUDSTACK-7365 
>> was created by you Pierre-Luc. I am looking into the other side of the
>> medal. have a generic systemvm upgrade api. It is related and I haven't
>> found a ticket yet.
>>
>> On Fri, Oct 17, 2014 at 2:43 PM, Pierre-Luc Dion 
>> wrote:
>>
>>> Hi Rohit,
>>>
>>> I'm aware of this behavior, it start with 4.3.0, if you upgrade to 4.3.0
>>> or
>>> 4.3.1 without having the new systemvm prior the upgrade, the db upgrade
>>> will fail. which is why upgrading from 4.2.x to 4.4.1 require 2 new
>>> systemvm to be install prior the upgrade.
>>>
>>> Further more, if you have multiple hypervisor type, let say you have
>>> XenServer and KVM clusters but forced system vm to run on xenserver only.
>>> by default you might only install the new sysvmtemplate for xenserver,
>>> but,
>>> if you upgrade without having install the kvm systemvm version the db
>>> upgrade will fail.
>>>
>>> I think their is jira issue around this already.
>>>
>>> On Fri, Oct 17, 2014 at 7:36 AM, Rohit Yadav 
>>> wrote:
>>>
 Hi Pierre,

 On 17-Oct-2014, at 4:42 pm, Pierre-Luc Dion  wrote:
> Hi Rohit,
> The doc in /latest is not the 4.4.1 latest, the correct documentation
>>> is
 in
> /4.4.1 it should have been corrected for the behavior describe and
>>> also
> contain correct url for sysvm ( not jenkins.bac.o).
>
> Once the 4.4.1 is released ill change the defaut url and update issues
> lists in the RN.

 Thanks, that would be much needed.

 The issue is not that docs have those links, but that the Java class
 (440to441, the upgrade path) that upgrades CloudStack db has hard coded
>>> URL
 and MD5 checksums of 4.4.0 template.

 The real issue is when a user tries to upgrade from any prior version of
 CloudStack to 4.4.1 or later version, they would be required to
>>> register a
 4.4.0-6 template (from Wido’s repo) before the upgrade which is
>>> something
 they skip or forget to do it which would result in messed up upgraded
>>> DB.
 For example, if I’m on 4.2.1 and I want to upgrade to 4.4.1 or later
>>> (say
 4.5.0 in future) if I don’t follow the docs (i.e. register 4.4.0-06
 template, that too not any 4.4.0 template, but the specific one from
>>> Wido’s
 repo or some other url) my upgrade will fail.

 Regards,
 Rohit Yadav
 Software Architect, ShapeBlue
 M. +91 88 262 30892 | rohit.ya...@shapeblue.com
 Blog: bhaisaab.org | Twitter: @_bhaisaab

 Find out more about ShapeBlue and our range of CloudStack related
>>> services

 IaaS Cloud Design & Build<
 http://shapeblue.com/iaas-cloud-design-and-build//>
 CSForge – rapid IaaS deployment framework
 CloudStack Infrastructure Support<
 http://shapeblue.com/cloudstack-infrastructure-support/>
 CloudStack Bootcamp Training Courses<
 http://shapeblue.com/cloudstack-training/>

 This email and any attachments to it may be confidential and are
>>> intended
 solely for the use of the individual to whom it is addressed. Any views
>>> or
 opinions expressed are solely those of the author and do not necessarily
 represent those of Shape Blue Ltd or related companies. If you are not
>>> the
 intended recipient of this email, you must neither take any action based
 upon its contents, nor copy or show it to anyone. Please contact the
>>> sender
 if you believe you have received this email in error. Shape Blue Ltd is
>>> a
 company incorporated in England & Wales. ShapeBlue Services India LLP
>>> is a
 company incorporated in India and is operated under license from Shape
>>> Blue
 Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in
>>> Brasil
 and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd
>>> is
 a company registered by The Republic of South Africa and is traded under
 license from Shape Blue Ltd. ShapeBlue is a registered trademark.

>>>
>>
>>
>>
>> --
>> Daan
>>
>
>
>
> --
> Daan

Regards,
Rohit Yadav
Software Architect, ShapeBlue
M. +91 88 262

Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 3 in branch 4.4-RC20141014T2316

2014-10-19 Thread Rohit Yadav

Hi Pierre,

> On 17-Oct-2014, at 6:13 pm, Pierre-Luc Dion  wrote:
>
> I'm aware of this behavior, it start with 4.3.0, if you upgrade to 4.3.0 or
> 4.3.1 without having the new systemvm prior the upgrade, the db upgrade
> will fail. which is why upgrading from 4.2.x to 4.4.1 require 2 new
> systemvm to be install prior the upgrade.

From the user’s perspective, they may find it unreasonable for forcing them to 
install 4.4.0 systemvm templates just because someone’s trying to upgrade to 
4.5.0 or later. If they are upgrading to 4.4.1 from 4.4.0, I understand it’s 
reasonable step.

Regards,
Rohit Yadav
Software Architect, ShapeBlue
M. +91 88 262 30892 | rohit.ya...@shapeblue.com
Blog: bhaisaab.org | Twitter: @_bhaisaab

Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build
CSForge – rapid IaaS deployment framework
CloudStack Consulting
CloudStack Infrastructure 
Support
CloudStack Bootcamp Training Courses

This email and any attachments to it may be confidential and are intended 
solely for the use of the individual to whom it is addressed. Any views or 
opinions expressed are solely those of the author and do not necessarily 
represent those of Shape Blue Ltd or related companies. If you are not the 
intended recipient of this email, you must neither take any action based upon 
its contents, nor copy or show it to anyone. Please contact the sender if you 
believe you have received this email in error. Shape Blue Ltd is a company 
incorporated in England & Wales. ShapeBlue Services India LLP is a company 
incorporated in India and is operated under license from Shape Blue Ltd. Shape 
Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
registered by The Republic of South Africa and is traded under license from 
Shape Blue Ltd. ShapeBlue is a registered trademark.

Re: [ANNOUNCE] New PMC Member: Rajani Karuturi

2014-10-19 Thread Rajani Karuturi

Thanks everyone :)

~Rajani

On Sat, Oct 18, 2014 at 1:37 PM, Ian Duffy  wrote:

> Congrats Rajani! :)
>
> On 17 October 2014 16:47, Mike Tutkowski 
> wrote:
>
> > Congratulations!
> >
> > On Friday, October 17, 2014, Daan Hoogland 
> > wrote:
> >
> > > The Project Management Committee (PMC) for Apache CloudStack are
> pleased
> > to
> > > announce that Rajani Karuturi has accepted our invitation to join the
> > PMC.
> > >
> > > Please join me in congratulating her.
> > >
> > > On behalf of the Apache CloudStack PMC
> > > --
> > > Daan
> > >
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkow...@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the cloud
> > *™*
> >
>

Re: NetworkOrchestrator selects 2 NetworkGurus at one time....

2014-10-19 Thread Pradeep Cloudstack

Hi,
do we have solution for this in 4.5 ?

An ideal solution would be to have a single Network created, but let each of 
the NetworkGuru do the implementation

-Pradeep




 From: Chiradeep Vittal 
To: Pradeep Cloudstack ; 
"dev@cloudstack.apache.org"  
Cc: Sheng Yang ; Jayapal Reddy Uradi 
; Alena Prokharchyk 
 
Sent: Friday, June 27, 2014 12:11 AM
Subject: Re: NetworkOrchestrator selects 2 NetworkGurus at one time
 

For 4.3/4.4, I’m guessing this is the same solution.

For 4.5, here’s a couple of options we could implement:

  1.  New isolation provider (“BrocadeVLAN” or “JuniperEXVLAN”)
  2.  When creating the network offering, the administrator gets to select the 
guru
  3.  New VLAN provider mechanism.

From: Pradeep Cloudstack 
mailto:pradeepcloudst...@yahoo.com>>
Reply-To: Pradeep Cloudstack 
mailto:pradeepcloudst...@yahoo.com>>
Date: Wednesday, June 25, 2014 at 3:06 AM
To: "dev@cloudstack.apache.org" 
mailto:dev@cloudstack.apache.org>>, Chiradeep Vittal 
mailto:chiradeep.vit...@citrix.com>>
Cc: Sheng Yang mailto:sheng.y...@citrix.com>>, Jayapal 
Reddy Uradi 
mailto:jayapalreddy.ur...@citrix.com>>, Alena 
Prokharchyk mailto:alena.prokharc...@citrix.com>>
Subject: Re: NetworkOrchestrator selects 2 NetworkGurus at one time

We have a use-case where we will patch an existing 4.3 installation with our 
plugin.
We are facing the same issue .
In 4.2, we used to disable the entry for ExternalNetworkGuru in
componentContext.xml as part of installing the patch.

How do we do this in 4.3 (on an existing installation) ?

-Pradeep


From: Ritu Sabharwal mailto:rsabh...@brocade.com>>
To: "dev@cloudstack.apache.org" 
mailto:dev@cloudstack.apache.org>>; Chiradeep Vittal 
mailto:chiradeep.vit...@citrix.com>>
Cc: Sheng Yang mailto:sheng.y...@citrix.com>>; Jayapal 
Reddy Uradi 
mailto:jayapalreddy.ur...@citrix.com>>; Alena 
Prokharchyk mailto:alena.prokharc...@citrix.com>>
Sent: Thursday, June 12, 2014 12:13 AM
Subject: RE: NetworkOrchestrator selects 2 NetworkGurus at one time

Thanks Chiradeep and Murali for the reply!

I am thinking of explicitly telling ExternalNetworkGuru to skip design when 
Brocade plugin is designing the network. I don't want to disable 
ExternalNetworkGuru from default build when Brocade plugin is not present so 
won't exclude it from the spring class loader.

Thanks & Regards,
Ritu S.



-Original Message-
From: Murali Reddy 
[mailto:murali.re...@citrix.com]
Sent: Tuesday, June 10, 2014 10:54 PM
To: Chiradeep Vittal; 
dev@cloudstack.apache.org
Cc: Sheng Yang; Jayapal Reddy Uradi; Alena Prokharchyk
Subject: Re: NetworkOrchestrator selects 2 NetworkGurus at one time

This is know design issue. Unlike service orchestration (which has prescriptive 
way to tell which network elements to be called for with network offerings ) 
there is no such logic for network design. Orchestrator just loops through all 
the network guru's asking to design the network which can results in one or 
more networks. Hugo did a cleanup [1] but I believe it was not merged as there 
was no consensus. There is 1-1 mapping between isolation type and Guru but In 
this case both Brocade Guru and ExternalNetworkGuru will attempt to design the 
VLAN isolated networks.

One in-elegent solution is to hard code ExternalGuestNetworu guru to skip 
network deign when Brocade plug-in is supposed to do design the network. Other 
option could be exclude ExternalNetworkGuru bean from spring class loader.

[1] https://www.mail-archive.com/dev@cloudstack.apache.org/msg17344.html

From: Chiradeep Vittal 
mailto:chiradeep.vit...@citrix.com>>>
Date: Wednesday, 11 June 2014 6:24 AM
To: 
"dev@cloudstack.apache.org>"
 
mailto:dev@cloudstack.apache.org>>>
Cc: Sheng Yang 
mailto:sheng.y...@citrix.com>>>,
 Murali Reddy 
mailto:murali.re...@citrix.com>>>,
 Jayapal Reddy Uradi 
mailto:jayapalreddy.ur...@citrix.com>>>,
 Alena Prokharchyk 
mailto:alena.prokharc...@citrix.com>>>
Subject: Re: NetworkOrchestrator selects 2 NetworkGurus at one time

That is strange. Looks like a bug to me. That is because the 
ExternalGuestNetworkGuru returns 'true' for canHandle.

From: Ritu Sabharwal 
mailto:rsabh...@brocade.com>>>
Reply-To: 
"dev@cloudstack.apache.org

Review Request 26442: CLOUDSTACK-7685: Fixed copy template method call in test_escalations_template.py. Removed unbound method of the same name as bound method from base l ibrary and changed method ca

2014-10-19 Thread Gaurav Aradhye


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

Review request for cloudstack and SrikanteswaraRao Talluri.


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


Repository: cloudstack-git


Description
---

Error details:
unbound method copy() must be called with Template instance as first argument 
(got CloudStackAPIClient instance instead)

Reason:
There are bound and unbound methods "copy" in Template class with the same 
name. Apparently when bound and unbound methods with same name are defined, 
call to unbound method fails.

Solution:
Keep only bound method.


Diffs
-

  test/integration/component/test_escalations_templates.py 78028bc 
  tools/marvin/marvin/lib/base.py 77faeeb 

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


Testing
---

Tested with python command/pyflakes.


Thanks,

Gaurav Aradhye

Re: Review Request 26442: CLOUDSTACK-7685: Fixed copy template method call in test_escalations_template.py. Removed unbound method of the same name as bound method from base l ibrary and changed metho

2014-10-19 Thread Gaurav Aradhye


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

(Updated Oct. 20, 2014, 11:09 a.m.)


Review request for cloudstack and SrikanteswaraRao Talluri.


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


Repository: cloudstack-git


Description (updated)
---

Error details:
unbound method copy() must be called with Template instance as first argument 
(got CloudStackAPIClient instance instead)

Reason:
There are bound and unbound methods "copy" in Template class with the same 
name. Apparently when bound and unbound methods with same name are defined, 
call to unbound method fails.

Solution:
Keep only bound method.

Please note that I have ensured no test case makes call to unbound method 
(Template.copy).


Diffs
-

  test/integration/component/test_escalations_templates.py 78028bc 
  tools/marvin/marvin/lib/base.py 77faeeb 

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


Testing
---

Tested with python command/pyflakes.


Thanks,

Gaurav Aradhye

Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 3 in branch 4.4-RC20141014T2316

Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 3 in branch 4.4-RC20141014T2316

Re: [VOTE][ACS44]Apache CloudStack 4.4.1 RC 3 in branch 4.4-RC20141014T2316

Re: [ANNOUNCE] New PMC Member: Rajani Karuturi

Re: NetworkOrchestrator selects 2 NetworkGurus at one time....

Review Request 26442: CLOUDSTACK-7685: Fixed copy template method call in test_escalations_template.py. Removed unbound method of the same name as bound method from base l ibrary and changed method ca

Re: Review Request 26442: CLOUDSTACK-7685: Fixed copy template method call in test_escalations_template.py. Removed unbound method of the same name as bound method from base l ibrary and changed metho

7 matches

Site Navigation

Mail list logo

Footer information