Review Request 14247: added support for ispersistent parameter in networkoffering create method in marvin

[Anshul Gangwar]

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

Review request for cloudstack and Prasanna Santhanam.


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


Repository: cloudstack-git


Description
---

added support for ispersistent parameter in networkoffering create method in 
marvin


Diffs
-

  tools/marvin/marvin/integration/lib/base.py df81406 

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


Testing
---


Thanks,

Anshul Gangwar

Re: Call for 4.3 and 4.2.1 Release Managers!

[Daan Hoogland]

H Animesh and the rest,

I had some consults at home and at Schuberg Philis. The conclusion is
that it is not wise to take up the task as release manager right now.
I will be glad to take it up some future iteration.

sorry to lay this burden back,
Daan

On Wed, Sep 18, 2013 at 10:24 AM, Daan Hoogland  wrote:
> Community,
>
> And especially our friends at Citrix, i am willing but am kind of a dictator
> in this role. Im an experienced developper but not in such a big oss
> project. I know i havey style and obsessions that some of you might not
> like. A fixation on automated tests os one that i know is likely to be
> accepted. Others will come out of the hat.
>
> Thought i had to warm you all,
> Daan
>
> mobile biligual spell checker used
>
> Op 18 sep. 2013 07:22 schreef "Animesh Chaturvedi"
>  het volgende:
>
>>
>>
>> > -Original Message-
>> > From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
>> > Sent: Monday, September 16, 2013 10:30 AM
>> > To: dev@cloudstack.apache.org
>> > Subject: RE: Call for 4.3 and 4.2.1 Release Managers!
>> >
>> >
>> >
>> > > -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.
>> >
>> [Animesh>] Daan do you want to take up 4.3.0? I have added  a 4.3.0
>> release page with tentative dates for now. If you don't want to do it now, I
>> can continue for 4.3.0.
>> > >
>> > > 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: conflicting dependencies between CloudStack and Whirr

[Sebastien Goasguen]

On Sep 20, 2013, at 12:45 AM, Hugo Trippaers  wrote:

> 
> The Nicira NVP plugin is also depending on gson. If we make any changes we 
> need to validate against their api to ensure that the interface still works.
> 
> If we put the changes in a separate branch i'd be happy to run the changes 
> against the api.
> 
> Cheers,
> 
> Hugo

So how can Meng get out of this bind, she is trying to complete her google 
summer of code project.

thanks,

-Sebastien

> 
> 
> On Sep 20, 2013, at 12:08 PM, Darren Shepherd  
> wrote:
> 
>> After much searching I found the two lines of code I needed to get it to 
>> serialize right.  I'll keep looking and see if I find other snags.  Maybe we 
>> can just move to jackson we'll see, haven't tried to deserialize yet.  
>> 
>> Darren
>> 
>>> On Sep 19, 2013, at 4:25 PM, Alex Huang  wrote:
>>> 
>>> Darren,
>>> 
>>> When I looked into updating to the latest gson, the problem, IIRC, is 
>>> things that weren't considered cyclical dependencies are suddenly 
>>> considered cyclical with the latest.  I don't recall where though. 
>>> 
>>> --Alex
>>> 
 -Original Message-
 From: Darren Shepherd [mailto:darren.s.sheph...@gmail.com]
 Sent: Thursday, September 19, 2013 1:33 PM
 To: dev@cloudstack.apache.org
 Subject: Re: conflicting dependencies between CloudStack and Whirr
 
 Alright, I looked into this and it will take a bit more work to switch to 
 Jackson.
 The snag I hit was how we serialize commands for the agents.  We use a
 customer typeadatper in gson to produce a format like { "org.MyClass"
 : {...} }.  In jackson I don't see producing a similar format as being so 
 straight
 forward.  I'm sure there's an elegant solution, but I didn't immediately 
 find it.
 The problem is if you use a custom serializer in jackson and do
 writeObjectField(x.getClass().getName(), x), you'll get stuck in a loop
 because it will call your serializer again.  So if somebody can figure out 
 how to
 do this format easily in jackson, the rest looks simple enough.
 
 So, being that it is not an obvious switch to using jackson, what is the 
 impact
 of moving to the latest gson?  What were the issue encountered when
 people tried it before?
 
 Darren
 
 
 On Wed, Sep 18, 2013 at 4:42 PM, Darren Shepherd <
 darren.s.sheph...@gmail.com> wrote:
 
> I can do some analysis on this.  I'm always up for a terribly painful
> refactor :)
> 
> Darren
> 
> 
>> On Wed, Sep 18, 2013 at 4:06 PM, Alex Huang 
> wrote:
> 
>> I actually did a quick try to update cloudstack to use newest gson
>> version about 3 months back.  Had to roll it back but I didn't try
>> very hard though.  Part of the reason why I decided to rollback is
>> due to gson is used differently by various components in CloudStack
>> and I didn't have time to get into each component to see if I break
>> anything.  The other is also I thought using Jackson would be much
>> better and thought our next attempt should be with Jackson.
>> 
>> Not that any of these helps you.  Just know updating CloudStack to
>> latest gson is not simple.
>> 
>> --Alex
>> 
>>> -Original Message-
>>> From: Andrei Savu [mailto:savu.and...@gmail.com]
>>> Sent: Wednesday, September 18, 2013 10:53 AM
>>> To: d...@whirr.apache.org
>>> Cc: dev@cloudstack.apache.org
>>> Subject: Re: conflicting dependencies between CloudStack and Whirr
>>> 
>>> It's easy to usr jclouds and whirr inside an OSGi container - just
>>> add
>> the
>>> feature url. Bonus: you can also use jclouds shell interface (part
>>> of
>> jclouds cli).
>>> 
>>> Another option is to upgrade the CloudStack API to use the new version.
 On Sep 18, 2013 5:14 AM, "Han,Meng"  wrote:
 
 Dear all,
 
 I am adding an API to CloudStack which utilizes Whirr to launch
 various clusters on CloudStack. Now I am facing a dependency
>> conflicting
>>> issue.
 
 Whirr 0.8.2 requires gson 2.2.2 while CloudStack API requires
 gson
>> 1.7.1.
 If I use gson 1.7.1 for Whirr, the following error will happen:
 
 com.google.common.util.**concurrent.ExecutionError:
>>> java.lang.**NoClassDefFoundError:
 com/google/gson/TypeAdapter
 
 This TypeAdapter class can be found inside gson-2.2.2.jar.
 However if I modify CloudStack to use gson 2.2.2 CloudStack will
 not build successfully due to the following test error.
 
 [INFO] Building Apache CloudStack Core 4.1.1 [INFO]
 --**--**
 
 [INFO]
 [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @
 cloud-core
 --- [INFO] Deleting /h

Re: Tips for git rebase

[Punith s]

hi ,

 which platform are you using for development ??  because you can get lot
of git gui's for windows and mac .
 this document may help you for the release
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+Procedure

 thanks,

punth s
cloudbyte







On Fri, Sep 20, 2013 at 7:32 AM, Nguyen Anh Tu  wrote:

> Hi guys,
>
> Could anyone share some tips or GUI tool for making git rebase easier? I
> have to rebase my working branch with master but get many many conflicts
> which I have no idea about these pieces of code.
>
> Thanks for any help,
>
> --
>
> N.g.U.y.e.N.A.n.H.t.U
>

RE: Volunteers to Complete the 4.2 Release Notes

[Radhika Puthiyetath]

Thanks Indra.

I shall attach the PDF file at 
https://issues.apache.org/jira/browse/CLOUDSTACK-4245.



From: Indra Pramana [mailto:in...@sg.or.id]
Sent: Friday, September 20, 2013 12:07 PM
To: Radhika Puthiyetath
Cc: us...@cloudstack.apache.org
Subject: Re: Volunteers to Complete the 4.2 Release Notes

Hi Radhika,

May I know how can I view the release notes in normal HTML format, instead of 
the original XML format?

Does it specifically contain migration steps from 4.1.1 to 4.2.0?

Would like to try again to upgrade my current CloudStack 4.1.1 to 4.2.0, 
provided I can get the detailed instruction on what to do. Last time I tried to 
follow the existing documentation on the .tar.bz2 file (provided by Animesh 
when he started the vote) and some of the steps seem to be not applicable 
anymore, and I might have missed out some other steps which are actually 
required.

Looking forward to your reply, thank you.

Cheers.


On Thu, Sep 19, 2013 at 2:42 PM, Radhika Puthiyetath 
mailto:radhika.puthiyet...@citrix.com>> wrote:
This has been updated. Could someone please validate the API section ?

-Original Message-
From: Animesh Chaturvedi 
[mailto:animesh.chaturv...@citrix.com]
Sent: Sunday, September 15, 2013 4:16 AM
To: mailto:us...@cloudstack.apache.org>>
Cc: dev@cloudstack.apache.org; 
us...@cloudstack.apache.org
Subject: Re: Volunteers to Complete the 4.2 Release Notes

I have added a public filters for known issues and fixed issues that we can put 
in release notes. This way the data is dynamic and up to date

Thanks
Animesh

On Sep 13, 2013, at 8:53 AM, "Radhika Puthiyetath" 
mailto:radhika.puthiyet...@citrix.com>> wrote:

> Who is volunteering to provide the list of Fixed issues for the RN?
>
> -Original Message-
> From: Animesh Chaturvedi 
> [mailto:animesh.chaturv...@citrix.com]
> Sent: Wednesday, August 28, 2013 4:40 AM
> To: dev@cloudstack.apache.org; 
> us...@cloudstack.apache.org
> Subject: RE: Volunteers to Complete the 4.2 Release Notes
>
> Community help is needed to fix up the release notes, any volunteers
>
> Animesh
>
>> -Original Message-
>> From: Radhika Puthiyetath 
>> [mailto:radhika.puthiyet...@citrix.com]
>> Sent: Tuesday, August 13, 2013 1:01 AM
>> To: dev@cloudstack.apache.org; 
>> us...@cloudstack.apache.org
>> Subject: Volunteers to Complete the 4.2 Release Notes
>>
>> Hi,
>>
>> Looking for volunteers to help me with the 4.2 Release Notes.
>>
>> I have started filling in the new feature section, and checked in to the
>> 4.2 branch.
>>
>> A defect is filed https://issues.apache.org/jira/browse/CLOUDSTACK-4245.
>>
>> Thanks for the help
>> -Radhika

Re: Review Request 12228: static resource compression

[Laszlo Hornyak]

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

(Updated Sept. 20, 2013, 10:01 a.m.)


Review request for cloudstack.


Changes
---

Second version of the patch:
- does not build anything on jetty's behavior anymore adds a servlet to handle 
the static resources
- servlet mapped to css and js files
- unit test included for the servlet


Repository: cloudstack-git


Description
---

Just to share the idea.

Jetty can use the gzipped version of static resource files (html, js, css) to 
serve requests of browsers that accept gzip compression. This allows faster 
page loads and/or save bandwidth. CloudStack at this point has 2.4 MB of 
javascript files and a few hundred KB css files, which adds up to roughly 3 MB, 
with gzip compression it is just a few hundred KB.

This solution uses my custom maven plugin written for the purpose, other 
aporach may work as well.


Diffs (updated)
-

  client/WEB-INF/web.xml e5c05d3 
  client/pom.xml 119c96e 
  server/src/com/cloud/servlet/StaticResourceServlet.java PRE-CREATION 
  server/test/com/cloud/servlet/StaticResourceServletTest.java PRE-CREATION 

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


Testing
---


Thanks,

Laszlo Hornyak

Re: Tips for git rebase

[Nguyen Anh Tu]

2013/9/20 Punith s 

> which platform are you using for development ??  because you can get lot
> of git gui's for windows and mac .
>

I'm using Linux Mint, a based-debian distro, likely Ubuntu. Great to hear
about the GIT GUI tool. Thanks for help.


-- 

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

Moved the systemvm to its own maven project

[Hugo Trippaers]

Hey all,

Just a heads-up that i pushed this commit to master:

commit 6c261042821c5597dab8d6be85dc59c948424e13
Author: Hugo Trippaers 
Date:   Fri Sep 20 18:08:20 2013 +0800

Move the system vm to a separate maven project.

All (almost) files belonging to the systemvm aer now centralize in the 
systemvm directory. The code for the separate functions is still in the 
services directory. This will make the code easier to understa


This commit effectively separates the code in the console-proxy from the actual 
building of the systemvm.iso. The systemvm profile (mvn -Psystemvm) will now 
control if the systemvm will be build entirely instead of just determining if 
the iso will be built. For slight speed up in the complete compile just leave 
the systemvm profile disabled.

I think this will make it more clear for everybody where the systemvm is 
located as its current location in console-proxy was a bit confusing.

Testing done:
 * Setting up devcloud with new build and new systemvm.iso
 * Verified ssvm operation (nfs secondary storage)
 * Verified  cvm operation

As with all maven changes don't forget to update the maven configuration in 
your IDE. (For eclipse users, right-click on the project, Maven -> Update 
Project)

Cheers,

Hugo

Cloud Bar Camp in San Francisco

[Lakmal Warusawithana]

Hi Devs,

I am from Apache Stratos project. we are in the process of organizing a
Cloud Bar camp in San Francisco @ Mission Bay Conference Center on October
28th, 2013. There's no written agenda, we are planning to start at 2pm and
go till approx. 5pm and have some drinks in a nearby bar afterwards.

The main purpose is cloud people to get together in a relaxed barcamp style
atmosphere and hang out. Many Stratos Commiters and PPMC members will
coming for this. We would be delighted to have cloudstack community over
there.

So if you are in the bay area, and willing to join this, please reply to
this mail. It will helpful us to arrange the logistics.

thanks

-- 
Lakmal Warusawithana
Software Architect; WSO2 Inc.
Mobile : +94714289692
Blog : http://lakmalsview.blogspot.com/

Re: NetApp&Citrix Storage plugin meeting notes -- Sep 17, 2013

[SuichII, Christopher]

Just as some background, I'm the Chris from 'NetApp: Chris, David'

So, the *_details table is perfect for storing pieces of information that are 
specific to storage pools or image stores. The kind of information we need to 
save are global settings and configurations. Things like, enabling enabling 
reduplication by default when provisioning, provisioning storage as thin/thick, 
connections & credentials to controllers, etc. That kind of information is not 
associated with any one zone, pod, cluster, host, storage pool, image store, 
etc.

By all means, feel free to put information in the *_details table, if that is 
where it belongs. The point of number 5 is that the ConfigDepot can be used by 
plugins to store global configuration information.

-- 
Chris Suich
chris.su...@netapp.com
NetApp Software Engineer
Data Center Platforms – Cloud Solutions
Citrix, Cisco & Red Hat

On Sep 20, 2013, at 1:29 AM, Amit Das  wrote:

> Thanks Edison, the meeting notes were helpful.
> 
> I am implementing a storage plugin for CloudByte & am using *_details table
> for storing the plugin related info.
> 
> Can anyone explain what kind/type of plugin data is not suitable in
> *_details table (referring to point 5).
> 
> Regards,
> Amit
> *CloudByte Inc.* 
> 
> 
> On Fri, Sep 20, 2013 at 5:35 AM, Edison Su  wrote:
> 
>> Meeting notes:
>> 
>> Date: Sep 17, 2013
>> 
>> Attendees:
>> 
>> NetApp: Chris, David
>> 
>> Citrix: Alex, Animesh, Edison, Srinivas
>> 
>> 
>> 
>> 1. TakeSnapshot method on storage plugin.
>> 
>>Chris: TakeSnapshot method is implemented, but backup snapshot is
>> failed on the hypervisor side, as the default backup snapshot procedure
>> will send a copycommand to Xenserver resource, which can't recognize the
>> snapshot created by NetApp storage plugin.
>> 
>>   Edison: take snapshot, then backup snapshot to secondary storage
>> immediately is the default behavior in CloudStack. There is a way to
>> customize it, by extends SnapshotStrategy interface. For example, we can
>> write a SnapshotStrategy, which doesn't back up unless anther backup
>> snapshot API is called. Or we can add a global configuration parameter to
>> disable backup.
>> 
>>   Chris: backup snapshot is fine, but we need a way to customize the
>> backup logic. Should we need to let hypervisor knows the snapshot created
>> by NetApp, Xenserver has an API to introduce a volume/snapshot, but VMware
>> seems doesn't have that kind of API.
>> 
>>   Edison: There is ways to customize the copy logic, by extending
>> copyAsync in storage plugin. Everytime, mgt server sends a copycommand, it
>> will go through both source storage provider and destination storage
>> provider, If any of them  knows how to handle the copycommand, then mgt
>> server will handle it to storage provider, otherwise, mgt server will
>> handle it to DataMotionService. So there are two ways to customize
>> copycommand:
>> 
>>  a. implement copyAsync in storage plugin,
>> 
>>  b. add a new DataMotionService.
>> 
>>  Method a, is easier than method b.
>> 
>>   In copyAsync implementation, we can send the copyCommand to SSVM to
>> handle the actual snapshot copy, instead of sending to hypervisor host.
>> 
>>   Chris: Need the detail about how to implement copyAsync in storage
>> plugin:
>> 
>>  [Action]: Edison needs to provide detailed information on how to
>> implementation of copyAsync
>> 
>> 
>> 
>> 2. RevertSnapshot
>> 
>>Chris: RevertSnapshot is never been called in CloudStack.
>> 
>>Edison: CloudStack always assumes the snapshot is created, then will
>> be backed up to image store immediately, so no need to revert snapshot.
>> 
>>Chris: need to add revert snapshot functionality on the UI, and API to
>> implement revert Snapshot functionality, as the snapshot created on NetApp
>> can be reverted back.
>> 
>>[Action]: Edison needs to implement RevertSnapshot, and call storage
>> plugin's RevertSnapshot accordingly.
>> 
>> 
>> 
>> 3.  NetApp volume snapshot.
>> 
>>   David: Due to the limitation of NetApp hardware(the number of snapshots
>> can be stored on one NetApp volume is limited, less than 255?), we need to
>> implement volume snapshot, instead of per VM volume snapshot.
>> 
>>   David: Need to change storage plugin API to take snapshots for all the
>> VMs created on the primary storage, instead of per one volume, such as
>> takeSnapshot(List vms), then NetApp can take only one snapshot on the
>> whole NetApp volume.
>> 
>>   Animesh: Does NetApp's hardware has the information for VM's each
>> volumes, as there is only one snapshot taking on primary storage?
>> 
>>   David: Yes, there is information per volume, we can store them in
>> snapshot's path column in CloudStack DB.
>> 
>>   Alex: How about queue taking snapshot methods call in storage plugin?
>> For example, queue the taking snapshot for several minutes, then issue only
>> one take-snapshot command to NetApp hardware.
>> 
>>   David: It's doable, but ma

Re: Review Request 14148: Cleanup DefaultUserAuthenticator and removed masking _name variable

[Abhinandan Prateek]

> On Sept. 19, 2013, 4:20 a.m., Abhinandan Prateek wrote:
> > Ship It!
> 
> Abhinandan Prateek wrote:
> when i try to apply the patch git am says "Patch format detection 
> failed.".

Committed !

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


- Abhinandan


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


On Sept. 18, 2013, 5:39 a.m., Darren Shepherd wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/14148/
> ---
> 
> (Updated Sept. 18, 2013, 5:39 a.m.)
> 
> 
> Review request for cloudstack, Abhinandan Prateek and Kelven Yang.
> 
> 
> 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
> 
>

FW: (CLOUDSTACK-692) The CleanupSnapshotBackup process on SSVM deletes snapshots that are still in the process of being copied to secondary storage

[Joris van Lieshout]

Hi Min and Edison,

I hope you don't mind me addressing you directly. I see that you two have done 
most of the work on the Snapshot parts of CS. 
We've been having production impacting issues due to the bug I tried to 
describe below (and in ticket 692). Yes, it's my first time engaging in the 
community so I hope I've took the right approach. :)
Also I've did some digging around in the CS 4.0, 4.1 and 4.2 code bases and see 
that large parts of the Snapshot process have been revised in 4.2. The issue 
that we have been having where using the 4.0 and 4.1 code bases and, more 
particularly, due to "snapshot ... is not recorded in DB, remove it" in 
CleanupSnapshotBackupCommand of NfsSecondaryStorageResource.java.
Because CleanupSnapshotBackupCommand has been removed in commit 
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=27133fba7daefcea6ddba943efb9c96f23dacef2
 I wonder if therefore this bug has also been solved?

Thanks in advanced.

Kind regards, 
Joris van Lieshout

-Original Message-
From: Joris van Lieshout [mailto:jvanliesh...@schubergphilis.com] 
Sent: dinsdag 17 september 2013 15:56
To: 'dev@cloudstack.apache.org'
Subject: (CLOUDSTACK-692) The CleanupSnapshotBackup process on SSVM deletes 
snapshots that are still in the process of being copied to secondary storage

Hi there,

I was wondering if anyone can help us with this issue? There seems to be a 
situation where the CleanupSnapshotBackup process deletes vhd files belonging 
to an active BackupSnapshot process. I've created CLOUDSTACK-692 for it and 
logged as much info as possible, including the steps I use to clean the mess up 
after we have hit this. We have seen it happen in CS 4.0 and 4.1.1, and from 
what I have seen in the code it probably also exists in 4.2.
I haven't reproduced the issue in a lab because we are hitting it quite often 
in production and uat so I have all the examples I need. :) But I guess the 
best way to reproduce it is to create a vm with quite some io activity (so 
snapshots will be big), enable hourly snapshot and shorten the 
storage.cleanup.interval global setting so the cleanup process gets trigger 
more frequently.
We are hitting this on XenServer 6.0.2 but if this snapshot cleanup and backup 
process is generally the same across other HVs type I would image this is 
relevant for that as well...

Kind regards,
Joris van Lieshout

Review Request 14248: CLOUDSTACK: 4537 - test_vpc_vm_life_cycle.py - Fixed vpc and shared network test cases

[Gaurav Aradhye]

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

Review request for cloudstack, Rayees Namathponnan and Prasanna Santhanam.


Repository: cloudstack-git


Description
---

Fixed Test case test_vpc_vm_life_cycle.py: TestVMLifeCycleSharedNwVPC failed 
with Insufficient address capacity error

Changes:
1) Shared network requires start ip and end ip shile creating it, if you want 
to deploy vm in it. Else it throws Insufficient address capacity error
2) Removed addition of multiple vms in load balancing rule (VMs belonging to 
multiple networks). Because this is not allowed.
3) For test case test_05_destroy_instance_in_network, added wait for cleanup of 
vm. So that after it proceeds to check the network rules.
4) Removed white spaces and unnecessary comments.


Diffs
-

  test/integration/component/test_vpc_vm_life_cycle.py 9844c1f 

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


Testing
---

Tested locally


Thanks,

Gaurav Aradhye

Re: Review Request 14148: Cleanup DefaultUserAuthenticator and removed masking _name variable

[Abhinandan Prateek]

> On Sept. 19, 2013, 4:20 a.m., Abhinandan Prateek wrote:
> > Ship It!
> 
> Abhinandan Prateek wrote:
> when i try to apply the patch git am says "Patch format detection 
> failed.".
> 
> Abhinandan Prateek wrote:
> Committed !
> 
> 
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=4d01ce8fc766423d795955bd5784b56969ce11a8

reverting it for now as I see build failure, do not have time right now to look 
for the cause. Will put it back tomorrow.


- Abhinandan


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


On Sept. 18, 2013, 5:39 a.m., Darren Shepherd wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/14148/
> ---
> 
> (Updated Sept. 18, 2013, 5:39 a.m.)
> 
> 
> Review request for cloudstack, Abhinandan Prateek and Kelven Yang.
> 
> 
> 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
> 
>

[EVENTS] Couple european events to keep in mind

[Sebastien Goasguen]

Hi folks,

A quick reminder of couple european events coming up in the coming months

-Sept 25th http://bacdgeneve.eventbrite.com Geneve, Switzerland
-October 10th http://buildacloudlondon.eventbrite.com London
-October 21-23rd http://events.linuxfoundation.org/events/linuxcon-europe 
Edinburgh

And of course:

-November 20-22nd, CloudStack collab, Amsterdam: http://www.cloudstackcollab.org
The CFP is open until October 1st, a short bio and a 200-400 word abstract. 
Share you experiences, wishes and thoughts about the cloud.

See you at one of those,

Cheers,

-Sebastien

Re: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fifth round)

[Tracy Phillips]

I agree with the respin.

Cloudstack is still a young open source project and we don't need any
negative press/tweets/blogs/gossip :)


On Fri, Sep 20, 2013 at 1:03 AM, Animesh Chaturvedi <
animesh.chaturv...@citrix.com> wrote:

>
>
> > -Original Message-
> > From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> > Sent: Thursday, September 19, 2013 5:15 PM
> > To: dev@cloudstack.apache.org
> > Subject: RE: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fifth
> > round)
> >
> >
> >
> > > -Original Message-
> > > From: Marcus Sorensen [mailto:shadow...@gmail.com]
> > > Sent: Thursday, September 19, 2013 4:46 PM
> > > To: dev@cloudstack.apache.org
> > > Subject: Re: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fifth
> > > round)
> > >
> > > I prefer a respin, as painful as that seems. VPC is a major feature,
> > > do we really want to release something that we know will break anyone
> > > who tries to upgrade?  I could deal with #1 if we are able to include
> > > the hotfix script in the packaging, such that the release notes can
> > > provide dead simple instructions for upgrade (no 'go download this
> > > script'). I'm just not clear on what we can change and what we can't
> > post-vote.
> >
> > [Animesh>] I don't think the  release artifacts can be changed so the
> > script will have to be downloaded. David/Chip/Wido any thoughts on that?
> > We can have the script available before the release announcement if we
> > continue with current VOTE.
> >
> > >
> [Animesh>] Only Marcus, Indra and Simon have responded I am prepared to
> respin tomorrow after VPC testing is complete with fixes from Alena. I
> would like to stick to 72 hour VOTE including weekend since last time most
> of the VOTEs were received over weekend.
>
>
> > > On Thu, Sep 19, 2013 at 3:59 PM, Animesh Chaturvedi
> > >  wrote:
> > > >
> > > >
> > > >> -Original Message-
> > > >> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> > > >> Sent: Thursday, September 19, 2013 10:43 AM
> > > >> To: dev@cloudstack.apache.org
> > > >> Subject: RE: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fifth
> > > >> round)
> > > >>
> > > >>
> > > >>
> > > >> > -Original Message-
> > > >> > From: Marcus Sorensen [mailto:shadow...@gmail.com]
> > > >> > Sent: Thursday, September 19, 2013 9:49 AM
> > > >> > To: dev@cloudstack.apache.org
> > > >> > Subject: RE: [VOTE][RESULTS] Release Apache CloudStack 4.2.0
> > > >> > (fifth
> > > >> > round)
> > > >> >
> > > >> > We do need to ensure that we have the db upgrade fix that was
> > > >> > mentioned on the other thread, otherwise people going from 4.1 to
> > > >> > 4.2 will have their VPCs break. Looks like we are waiting on a
> > > >> > script. It sounds like the plan will be to provide instructions
> > > >> > in the release notes. Really wish we would have caught that, its
> > > >> > not just that we find bugs at RC, but the severity of ones we
> > > >> > miss is astounding
> > > >> sometimes.
> > > >>
> > > >> [Animesh>] I am also stumped why this was not caught earlier.
> > > >> Kishan has a fix that is being tested.
> > > > [Animesh>] So while the fix  is being tested we have two options
> > > >
> > > > 1. Release 4.2, release note this issue, provide a separate script
> > > > that would have to be run if someone was using VPC in 4.1 and
> > > > upgraded to 4.2, fix this issue in 4.2.1
> > > >
> > > > 2. Since we have not released 4.2 yet, respin another RC and another
> > > > round of VOTE. That would be a record 6th RC Vote and 2 recalls
> > > > after successful votes :(
> > > >
> > > > Thoughts?
> > > >
> > > >>
> > > >> > On Sep 19, 2013 10:18 AM, "Animesh Chaturvedi" <
> > > >> > animesh.chaturv...@citrix.com> wrote:
> > > >> >
> > > >> > >
> > > >> > >
> > > >> > > > -Original Message-
> > > >> > > > From: Wido den Hollander [mailto:w...@widodh.nl]
> > > >> > > > Sent: Wednesday, September 18, 2013 4:55 PM
> > > >> > > > To: dev@cloudstack.apache.org
> > > >> > > > Subject: Re: [VOTE][RESULTS] Release Apache CloudStack 4.2.0
> > > >> > > > (fifth
> > > >> > > > round)
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > > >> > > > On 09/19/2013 01:28 AM, Animesh Chaturvedi wrote:
> > > >> > > > >
> > > >> > > > > The vote has *passed* with the following results (binding
> > > >> > > > > PMC votes
> > > >> > > > indicated with a "*" next to their name:
> > > >> > > > >
> > > >> > > > > +1 : Alex*, Chip*, Sebastien*, Prasanna*, Hugo*, Marcus*,
> > > >> > > > > +Wido*, Sebastien, Rajesh Batala, Sheng, Vijay, Abhi,
> > > >> > > > > +Likitha, Ian, Gavin, Daan, Amogh, Simon Weller,
> > > >> > > > >
> > > >> > > > > I'm going to proceed with moving the release into the
> > > >> > > > > distribution
> > > >> > > > repo now and work on release notes and other documentation
> > > tasks.
> > > >> > > > >
> > > >> > > > Who is going to build the RPM and Deb packages?
> > > >> > > >
> > > >> > > > I think I should build the .deb packages since I'm th

Re: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fifth round)

[Simon Weller]

Animesh, 


Are you aware of any proposed upgrade documentation as of yet? I'd really like 
to try a couple of upgrades to test the procedure. 


- Si 

- Original Message -

From: "Animesh Chaturvedi"  
To: dev@cloudstack.apache.org 
Sent: Friday, September 20, 2013 12:03:41 AM 
Subject: RE: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fifth round) 



> -Original Message- 
> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] 
> Sent: Thursday, September 19, 2013 5:15 PM 
> To: dev@cloudstack.apache.org 
> Subject: RE: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fifth 
> round) 
> 
> 
> 
> > -Original Message- 
> > From: Marcus Sorensen [mailto:shadow...@gmail.com] 
> > Sent: Thursday, September 19, 2013 4:46 PM 
> > To: dev@cloudstack.apache.org 
> > Subject: Re: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fifth 
> > round) 
> > 
> > I prefer a respin, as painful as that seems. VPC is a major feature, 
> > do we really want to release something that we know will break anyone 
> > who tries to upgrade? I could deal with #1 if we are able to include 
> > the hotfix script in the packaging, such that the release notes can 
> > provide dead simple instructions for upgrade (no 'go download this 
> > script'). I'm just not clear on what we can change and what we can't 
> post-vote. 
> 
> [Animesh>] I don't think the release artifacts can be changed so the 
> script will have to be downloaded. David/Chip/Wido any thoughts on that? 
> We can have the script available before the release announcement if we 
> continue with current VOTE. 
> 
> > 
[Animesh>] Only Marcus, Indra and Simon have responded I am prepared to respin 
tomorrow after VPC testing is complete with fixes from Alena. I would like to 
stick to 72 hour VOTE including weekend since last time most of the VOTEs were 
received over weekend. 


> > On Thu, Sep 19, 2013 at 3:59 PM, Animesh Chaturvedi 
> >  wrote: 
> > > 
> > > 
> > >> -Original Message- 
> > >> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] 
> > >> Sent: Thursday, September 19, 2013 10:43 AM 
> > >> To: dev@cloudstack.apache.org 
> > >> Subject: RE: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fifth 
> > >> round) 
> > >> 
> > >> 
> > >> 
> > >> > -Original Message- 
> > >> > From: Marcus Sorensen [mailto:shadow...@gmail.com] 
> > >> > Sent: Thursday, September 19, 2013 9:49 AM 
> > >> > To: dev@cloudstack.apache.org 
> > >> > Subject: RE: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 
> > >> > (fifth 
> > >> > round) 
> > >> > 
> > >> > We do need to ensure that we have the db upgrade fix that was 
> > >> > mentioned on the other thread, otherwise people going from 4.1 to 
> > >> > 4.2 will have their VPCs break. Looks like we are waiting on a 
> > >> > script. It sounds like the plan will be to provide instructions 
> > >> > in the release notes. Really wish we would have caught that, its 
> > >> > not just that we find bugs at RC, but the severity of ones we 
> > >> > miss is astounding 
> > >> sometimes. 
> > >> 
> > >> [Animesh>] I am also stumped why this was not caught earlier. 
> > >> Kishan has a fix that is being tested. 
> > > [Animesh>] So while the fix is being tested we have two options 
> > > 
> > > 1. Release 4.2, release note this issue, provide a separate script 
> > > that would have to be run if someone was using VPC in 4.1 and 
> > > upgraded to 4.2, fix this issue in 4.2.1 
> > > 
> > > 2. Since we have not released 4.2 yet, respin another RC and another 
> > > round of VOTE. That would be a record 6th RC Vote and 2 recalls 
> > > after successful votes :( 
> > > 
> > > Thoughts? 
> > > 
> > >> 
> > >> > On Sep 19, 2013 10:18 AM, "Animesh Chaturvedi" < 
> > >> > animesh.chaturv...@citrix.com> wrote: 
> > >> > 
> > >> > > 
> > >> > > 
> > >> > > > -Original Message- 
> > >> > > > From: Wido den Hollander [mailto:w...@widodh.nl] 
> > >> > > > Sent: Wednesday, September 18, 2013 4:55 PM 
> > >> > > > To: dev@cloudstack.apache.org 
> > >> > > > Subject: Re: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 
> > >> > > > (fifth 
> > >> > > > round) 
> > >> > > > 
> > >> > > > 
> > >> > > > 
> > >> > > > On 09/19/2013 01:28 AM, Animesh Chaturvedi wrote: 
> > >> > > > > 
> > >> > > > > The vote has *passed* with the following results (binding 
> > >> > > > > PMC votes 
> > >> > > > indicated with a "*" next to their name: 
> > >> > > > > 
> > >> > > > > +1 : Alex*, Chip*, Sebastien*, Prasanna*, Hugo*, Marcus*, 
> > >> > > > > +Wido*, Sebastien, Rajesh Batala, Sheng, Vijay, Abhi, 
> > >> > > > > +Likitha, Ian, Gavin, Daan, Amogh, Simon Weller, 
> > >> > > > > 
> > >> > > > > I'm going to proceed with moving the release into the 
> > >> > > > > distribution 
> > >> > > > repo now and work on release notes and other documentation 
> > tasks. 
> > >> > > > > 
> > >> > > > Who is going to build the RPM and Deb packages? 
> > >> > > > 
> > >> > > > I think I should build the .deb pack

RE: http://jenkins.cloudstack.org/ is down ?

[Animesh Chaturvedi]

NS lookup fails

animeshc@SJCLANIMESHC01 
$ nslookup cloudstack.org
*** sjcpdc04.citrite.net can't find cloudstack.org: Server failed
Server:  sjcpdc04.citrite.net
Address:  10.216.4.21


> -Original Message-
> From: Rayees Namathponnan [mailto:rayees.namathpon...@citrix.com]
> Sent: Friday, September 20, 2013 10:04 AM
> To: dev@cloudstack.apache.org
> Subject: http://jenkins.cloudstack.org/ is down ?
> 

RE: http://jenkins.cloudstack.org/ is down ?

[Kelly Hair]

The domain is still in the process of transferring apparently.  Would
assume it may be addressable by IP address if that's known...
On Sep 20, 2013 1:17 PM, "Animesh Chaturvedi" 
wrote:

> NS lookup fails
>
> animeshc@SJCLANIMESHC01
> $ nslookup cloudstack.org
> *** sjcpdc04.citrite.net can't find cloudstack.org: Server failed
> Server:  sjcpdc04.citrite.net
> Address:  10.216.4.21
>
>
> > -Original Message-
> > From: Rayees Namathponnan [mailto:rayees.namathpon...@citrix.com]
> > Sent: Friday, September 20, 2013 10:04 AM
> > To: dev@cloudstack.apache.org
> > Subject: http://jenkins.cloudstack.org/ is down ?
> >
>
>

RE: (CLOUDSTACK-692) The CleanupSnapshotBackup process on SSVM deletes snapshots that are still in the process of being copied to secondary storage

[Funs Kessen]

Hi Gents,

For now Daan and I put in a temporary fix for 4.1.1 (same for 4.0) which delays 
the deletion of the files for a day based on their create time. This means that 
at least snapshots that are in progress are not deleted unless it takes over a 
day to make them. The reason for putting the fix in place is that we've seen 
two production hypervisors collapse in the past two days because of the effects 
of the scavenger removing the files and tapdisk/sparse_dd going bananas and 
hitting something with NFS in the kernel that the kernel didn't like over a 
prolonged period of time. Besides this we're going to figure out what we hit in 
the kernel and hope that the next update cycle contains a patch for it, if not 
we'll have to conjure one up.

Cheers,

Funs

-Original Message-
From: Joris van Lieshout 
Sent: vrijdag 20 september 2013 14:51
To: 'min.c...@citrix.com'; 'sudi...@gmail.com'
Cc: 'Daan Hoogland (daan.hoogl...@gmail.com)'; Funs Kessen; 
'dev@cloudstack.apache.org'; 'Hugo Trippaers'
Subject: FW: (CLOUDSTACK-692) The CleanupSnapshotBackup process on SSVM deletes 
snapshots that are still in the process of being copied to secondary storage

Hi Min and Edison,

I hope you don't mind me addressing you directly. I see that you two have done 
most of the work on the Snapshot parts of CS. 
We've been having production impacting issues due to the bug I tried to 
describe below (and in ticket 692). Yes, it's my first time engaging in the 
community so I hope I've took the right approach. :) Also I've did some digging 
around in the CS 4.0, 4.1 and 4.2 code bases and see that large parts of the 
Snapshot process have been revised in 4.2. The issue that we have been having 
where using the 4.0 and 4.1 code bases and, more particularly, due to "snapshot 
... is not recorded in DB, remove it" in CleanupSnapshotBackupCommand of 
NfsSecondaryStorageResource.java.
Because CleanupSnapshotBackupCommand has been removed in commit 
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=27133fba7daefcea6ddba943efb9c96f23dacef2
 I wonder if therefore this bug has also been solved?

Thanks in advanced.

Kind regards,
Joris van Lieshout

-Original Message-
From: Joris van Lieshout [mailto:jvanliesh...@schubergphilis.com]
Sent: dinsdag 17 september 2013 15:56
To: 'dev@cloudstack.apache.org'
Subject: (CLOUDSTACK-692) The CleanupSnapshotBackup process on SSVM deletes 
snapshots that are still in the process of being copied to secondary storage

Hi there,

I was wondering if anyone can help us with this issue? There seems to be a 
situation where the CleanupSnapshotBackup process deletes vhd files belonging 
to an active BackupSnapshot process. I've created CLOUDSTACK-692 for it and 
logged as much info as possible, including the steps I use to clean the mess up 
after we have hit this. We have seen it happen in CS 4.0 and 4.1.1, and from 
what I have seen in the code it probably also exists in 4.2.
I haven't reproduced the issue in a lab because we are hitting it quite often 
in production and uat so I have all the examples I need. :) But I guess the 
best way to reproduce it is to create a vm with quite some io activity (so 
snapshots will be big), enable hourly snapshot and shorten the 
storage.cleanup.interval global setting so the cleanup process gets trigger 
more frequently.
We are hitting this on XenServer 6.0.2 but if this snapshot cleanup and backup 
process is generally the same across other HVs type I would image this is 
relevant for that as well...

Kind regards,
Joris van Lieshout

RE: Call for 4.3 and 4.2.1 Release Managers!

[Animesh Chaturvedi]

> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Friday, September 20, 2013 12:51 AM
> To: dev
> Subject: Re: Call for 4.3 and 4.2.1 Release Managers!
> 
> H Animesh and the rest,
> 
> I had some consults at home and at Schuberg Philis. The conclusion is
> that it is not wise to take up the task as release manager right now.
> I will be glad to take it up some future iteration.
> 
> sorry to lay this burden back,
> Daan
> 
[Animesh>]  Ok anyone else wants to step up to the plate.

> On Wed, Sep 18, 2013 at 10:24 AM, Daan Hoogland
>  wrote:
> > Community,
> >
> > And especially our friends at Citrix, i am willing but am kind of a
> > dictator in this role. Im an experienced developper but not in such a
> > big oss project. I know i havey style and obsessions that some of you
> > might not like. A fixation on automated tests os one that i know is
> > likely to be accepted. Others will come out of the hat.
> >
> > Thought i had to warm you all,
> > Daan
> >
> > mobile biligual spell checker used
> >
> > Op 18 sep. 2013 07:22 schreef "Animesh Chaturvedi"
> >  het volgende:
> >
> >>
> >>
> >> > -Original Message-
> >> > From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> >> > Sent: Monday, September 16, 2013 10:30 AM
> >> > To: dev@cloudstack.apache.org
> >> > Subject: RE: Call for 4.3 and 4.2.1 Release Managers!
> >> >
> >> >
> >> >
> >> > > -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.
> >> >
> >> [Animesh>] Daan do you want to take up 4.3.0? I have added  a 4.3.0
> >> release page with tentative dates for now. If you don't want to do it
> >> now, I can continue for 4.3.0.
> >> > >
> >> > > 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] Userdata Support for Hyper-V with KVP Data Exchange

[Donal Lafferty]

Let me put this on hold while some technical due diligence is done.  Need to 
verify the KVP support on specific Linux distro used by the system VM.

DL

 
> -Original Message-
> From: Donal Lafferty [mailto:donal.laffe...@citrix.com]
> Sent: 13 September 2013 23:09
> To: dev@cloudstack.apache.org
> Subject: RE: [Proposal] Userdata Support for Hyper-V with KVP Data
> Exchange
> 
> Yep.  I'll recirculate the proposal next week.
> 
> DL
> 
> > -Original Message-
> > From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com]
> > Sent: 13 September 2013 21:16
> > To: dev@cloudstack.apache.org
> > Subject: Re: [Proposal] Userdata Support for Hyper-V with KVP Data
> > Exchange
> >
> > I believe DL is actually referring to boot args, not user/metadata
> >
> > On 9/13/13 12:41 PM, "Darren Shepherd" 
> > wrote:
> >
> > >On 09/13/2013 11:56 AM, Donal Lafferty wrote:
> > >
> > >> Ah, okay, so you're talking about this:
> > >>http://cloudstack.apache.org/docs/en-
> > US/Apache_CloudStack/4.1.1/html/A
> > >>dmi
> > >>n_Guide/user-data-and-meta-data.html
> > >>
> > >
> > >Okay, that leads me back to my original question.  Why is that
> > >hypervisor specific?  That data comes from the VR right?  I know
> > >bootstrapping the VR with the boot args is hypervisor specific, but
> > >why user/metadata?
> > >
> > >Darren
> > >

Re: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fifth round)

[Simon Weller]

So, I'll be testing KVM which requires the new VR, hence why I want to test the 
docs. 

- Original Message -

From: "Animesh Chaturvedi"  
To: dev@cloudstack.apache.org 
Sent: Friday, September 20, 2013 12:24:39 PM 
Subject: RE: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fifth round) 



> -Original Message- 
> From: Simon Weller [mailto:swel...@ena.com] 
> Sent: Friday, September 20, 2013 8:05 AM 
> To: dev@cloudstack.apache.org 
> Subject: Re: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fifth 
> round) 
> 
> Animesh, 
> 
> 
> Are you aware of any proposed upgrade documentation as of yet? I'd 
> really like to try a couple of upgrades to test the procedure. 
> 
> 
> - Si 
[Animesh>]Here is the upgrade steps from RN for ACS 4.1.0 release. It should be 
the same for 4.1.0 to 4.2.0 
http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.1.0/html/Release_Notes/upgrade-instructions.html#upgrade-from-4.0-to-4.1
 

> 
> - Original Message - 
> 
> From: "Animesh Chaturvedi"  
> To: dev@cloudstack.apache.org 
> Sent: Friday, September 20, 2013 12:03:41 AM 
> Subject: RE: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fifth 
> round) 
> 
> 
> 
> > -Original Message- 
> > From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] 
> > Sent: Thursday, September 19, 2013 5:15 PM 
> > To: dev@cloudstack.apache.org 
> > Subject: RE: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fifth 
> > round) 
> > 
> > 
> > 
> > > -Original Message- 
> > > From: Marcus Sorensen [mailto:shadow...@gmail.com] 
> > > Sent: Thursday, September 19, 2013 4:46 PM 
> > > To: dev@cloudstack.apache.org 
> > > Subject: Re: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fifth 
> > > round) 
> > > 
> > > I prefer a respin, as painful as that seems. VPC is a major feature, 
> > > do we really want to release something that we know will break 
> > > anyone who tries to upgrade? I could deal with #1 if we are able to 
> > > include the hotfix script in the packaging, such that the release 
> > > notes can provide dead simple instructions for upgrade (no 'go 
> > > download this script'). I'm just not clear on what we can change and 
> > > what we can't 
> > post-vote. 
> > 
> > [Animesh>] I don't think the release artifacts can be changed so the 
> > script will have to be downloaded. David/Chip/Wido any thoughts on 
> that? 
> > We can have the script available before the release announcement if we 
> > continue with current VOTE. 
> > 
> > > 
> [Animesh>] Only Marcus, Indra and Simon have responded I am prepared to 
> respin tomorrow after VPC testing is complete with fixes from Alena. I 
> would like to stick to 72 hour VOTE including weekend since last time 
> most of the VOTEs were received over weekend. 
> 
> 
> > > On Thu, Sep 19, 2013 at 3:59 PM, Animesh Chaturvedi 
> > >  wrote: 
> > > > 
> > > > 
> > > >> -Original Message- 
> > > >> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] 
> > > >> Sent: Thursday, September 19, 2013 10:43 AM 
> > > >> To: dev@cloudstack.apache.org 
> > > >> Subject: RE: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 
> > > >> (fifth 
> > > >> round) 
> > > >> 
> > > >> 
> > > >> 
> > > >> > -Original Message- 
> > > >> > From: Marcus Sorensen [mailto:shadow...@gmail.com] 
> > > >> > Sent: Thursday, September 19, 2013 9:49 AM 
> > > >> > To: dev@cloudstack.apache.org 
> > > >> > Subject: RE: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 
> > > >> > (fifth 
> > > >> > round) 
> > > >> > 
> > > >> > We do need to ensure that we have the db upgrade fix that was 
> > > >> > mentioned on the other thread, otherwise people going from 4.1 
> > > >> > to 
> > > >> > 4.2 will have their VPCs break. Looks like we are waiting on a 
> > > >> > script. It sounds like the plan will be to provide instructions 
> > > >> > in the release notes. Really wish we would have caught that, 
> > > >> > its not just that we find bugs at RC, but the severity of ones 
> > > >> > we miss is astounding 
> > > >> sometimes. 
> > > >> 
> > > >> [Animesh>] I am also stumped why this was not caught earlier. 
> > > >> Kishan has a fix that is being tested. 
> > > > [Animesh>] So while the fix is being tested we have two options 
> > > > 
> > > > 1. Release 4.2, release note this issue, provide a separate script 
> > > > that would have to be run if someone was using VPC in 4.1 and 
> > > > upgraded to 4.2, fix this issue in 4.2.1 
> > > > 
> > > > 2. Since we have not released 4.2 yet, respin another RC and 
> > > > another round of VOTE. That would be a record 6th RC Vote and 2 
> > > > recalls after successful votes :( 
> > > > 
> > > > Thoughts? 
> > > > 
> > > >> 
> > > >> > On Sep 19, 2013 10:18 AM, "Animesh Chaturvedi" < 
> > > >> > animesh.chaturv...@citrix.com> wrote: 
> > > >> > 
> > > >> > > 
> > > >> > > 
> > > >> > > > -Original Message- 
> > > >> > > > From: Wido den Hollander [mailto:w...@widodh.nl] 
> > > >> > > > Sent: Wedne

RE: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fifth round)

[Animesh Chaturvedi]

Ok it's on the way VPC upgrade has been tested and working now. Just pulled the 
commits into 4.2 and building another RC now



> -Original Message-
> From: Tracy Phillips [mailto:tracp...@mantoso.com]
> Sent: Friday, September 20, 2013 7:55 AM
> To: dev@cloudstack.apache.org
> Subject: Re: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fifth
> round)
> 
> I agree with the respin.
> 
> Cloudstack is still a young open source project and we don't need any
> negative press/tweets/blogs/gossip :)
> 
> 
> On Fri, Sep 20, 2013 at 1:03 AM, Animesh Chaturvedi <
> animesh.chaturv...@citrix.com> wrote:
> 
> >
> >
> > > -Original Message-
> > > From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> > > Sent: Thursday, September 19, 2013 5:15 PM
> > > To: dev@cloudstack.apache.org
> > > Subject: RE: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fifth
> > > round)
> > >
> > >
> > >
> > > > -Original Message-
> > > > From: Marcus Sorensen [mailto:shadow...@gmail.com]
> > > > Sent: Thursday, September 19, 2013 4:46 PM
> > > > To: dev@cloudstack.apache.org
> > > > Subject: Re: [VOTE][RESULTS] Release Apache CloudStack 4.2.0
> > > > (fifth
> > > > round)
> > > >
> > > > I prefer a respin, as painful as that seems. VPC is a major
> > > > feature, do we really want to release something that we know will
> > > > break anyone who tries to upgrade?  I could deal with #1 if we are
> > > > able to include the hotfix script in the packaging, such that the
> > > > release notes can provide dead simple instructions for upgrade (no
> > > > 'go download this script'). I'm just not clear on what we can
> > > > change and what we can't
> > > post-vote.
> > >
> > > [Animesh>] I don't think the  release artifacts can be changed so
> > > the script will have to be downloaded. David/Chip/Wido any thoughts
> on that?
> > > We can have the script available before the release announcement if
> > > we continue with current VOTE.
> > >
> > > >
> > [Animesh>] Only Marcus, Indra and Simon have responded I am prepared
> > to respin tomorrow after VPC testing is complete with fixes from
> > Alena. I would like to stick to 72 hour VOTE including weekend since
> > last time most of the VOTEs were received over weekend.
> >
> >
> > > > On Thu, Sep 19, 2013 at 3:59 PM, Animesh Chaturvedi
> > > >  wrote:
> > > > >
> > > > >
> > > > >> -Original Message-
> > > > >> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> > > > >> Sent: Thursday, September 19, 2013 10:43 AM
> > > > >> To: dev@cloudstack.apache.org
> > > > >> Subject: RE: [VOTE][RESULTS] Release Apache CloudStack 4.2.0
> > > > >> (fifth
> > > > >> round)
> > > > >>
> > > > >>
> > > > >>
> > > > >> > -Original Message-
> > > > >> > From: Marcus Sorensen [mailto:shadow...@gmail.com]
> > > > >> > Sent: Thursday, September 19, 2013 9:49 AM
> > > > >> > To: dev@cloudstack.apache.org
> > > > >> > Subject: RE: [VOTE][RESULTS] Release Apache CloudStack 4.2.0
> > > > >> > (fifth
> > > > >> > round)
> > > > >> >
> > > > >> > We do need to ensure that we have the db upgrade fix that was
> > > > >> > mentioned on the other thread, otherwise people going from
> > > > >> > 4.1 to
> > > > >> > 4.2 will have their VPCs break. Looks like we are waiting on
> > > > >> > a script. It sounds like the plan will be to provide
> > > > >> > instructions in the release notes. Really wish we would have
> > > > >> > caught that, its not just that we find bugs at RC, but the
> > > > >> > severity of ones we miss is astounding
> > > > >> sometimes.
> > > > >>
> > > > >> [Animesh>] I am also stumped why this was not caught earlier.
> > > > >> Kishan has a fix that is being tested.
> > > > > [Animesh>] So while the fix  is being tested we have two options
> > > > >
> > > > > 1. Release 4.2, release note this issue, provide a separate
> > > > > script that would have to be run if someone was using VPC in 4.1
> > > > > and upgraded to 4.2, fix this issue in 4.2.1
> > > > >
> > > > > 2. Since we have not released 4.2 yet, respin another RC and
> > > > > another round of VOTE. That would be a record 6th RC Vote and 2
> > > > > recalls after successful votes :(
> > > > >
> > > > > Thoughts?
> > > > >
> > > > >>
> > > > >> > On Sep 19, 2013 10:18 AM, "Animesh Chaturvedi" <
> > > > >> > animesh.chaturv...@citrix.com> wrote:
> > > > >> >
> > > > >> > >
> > > > >> > >
> > > > >> > > > -Original Message-
> > > > >> > > > From: Wido den Hollander [mailto:w...@widodh.nl]
> > > > >> > > > Sent: Wednesday, September 18, 2013 4:55 PM
> > > > >> > > > To: dev@cloudstack.apache.org
> > > > >> > > > Subject: Re: [VOTE][RESULTS] Release Apache CloudStack
> > > > >> > > > 4.2.0 (fifth
> > > > >> > > > round)
> > > > >> > > >
> > > > >> > > >
> > > > >> > > >
> > > > >> > > > On 09/19/2013 01:28 AM, Animesh Chaturvedi wrote:
> > > > >> > > > >
> > > > >> > > > > The vote has *passed* with the following results
> > > > >> > > > > (binding PMC votes
> > > > >> > > > indi

http://jenkins.cloudstack.org/ is down ?

[Rayees Namathponnan]

RE: Moved the systemvm to its own maven project

[Alex Huang]

Nice!  Can't wait to look at this!

--Alex

> -Original Message-
> From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers
> Sent: Friday, September 20, 2013 3:40 AM
> To: dev@cloudstack.apache.org
> Subject: Moved the systemvm to its own maven project
> 
> Hey all,
> 
> Just a heads-up that i pushed this commit to master:
> 
> commit 6c261042821c5597dab8d6be85dc59c948424e13
> Author: Hugo Trippaers 
> Date:   Fri Sep 20 18:08:20 2013 +0800
> 
> Move the system vm to a separate maven project.
> 
> All (almost) files belonging to the systemvm aer now centralize in the
> systemvm directory. The code for the separate functions is still in the
> services directory. This will make the code easier to understa
> 
> 
> This commit effectively separates the code in the console-proxy from the
> actual building of the systemvm.iso. The systemvm profile (mvn -Psystemvm)
> will now control if the systemvm will be build entirely instead of just
> determining if the iso will be built. For slight speed up in the complete
> compile just leave the systemvm profile disabled.
> 
> I think this will make it more clear for everybody where the systemvm is
> located as its current location in console-proxy was a bit confusing.
> 
> Testing done:
>  * Setting up devcloud with new build and new systemvm.iso
>  * Verified ssvm operation (nfs secondary storage)
>  * Verified  cvm operation
> 
> As with all maven changes don't forget to update the maven configuration in
> your IDE. (For eclipse users, right-click on the project, Maven -> Update
> Project)
> 
> Cheers,
> 
> Hugo

Re: Moved the systemvm to its own maven project

[Darren Shepherd]

I think the build is broken now.  client/pom.xml depends on cloud-systemvm,
so if you don't put -Psystemvm the build breaks.  I think the
cloud-systemvm dep in client/pom.xml needs to be conditional on the
systemvm profile.

Darren


On Fri, Sep 20, 2013 at 11:01 AM, Alex Huang  wrote:

> Nice!  Can't wait to look at this!
>
> --Alex
>
> > -Original Message-
> > From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers
> > Sent: Friday, September 20, 2013 3:40 AM
> > To: dev@cloudstack.apache.org
> > Subject: Moved the systemvm to its own maven project
> >
> > Hey all,
> >
> > Just a heads-up that i pushed this commit to master:
> >
> > commit 6c261042821c5597dab8d6be85dc59c948424e13
> > Author: Hugo Trippaers 
> > Date:   Fri Sep 20 18:08:20 2013 +0800
> >
> > Move the system vm to a separate maven project.
> >
> > All (almost) files belonging to the systemvm aer now centralize in
> the
> > systemvm directory. The code for the separate functions is still in the
> > services directory. This will make the code easier to understa
> >
> >
> > This commit effectively separates the code in the console-proxy from the
> > actual building of the systemvm.iso. The systemvm profile (mvn
> -Psystemvm)
> > will now control if the systemvm will be build entirely instead of just
> > determining if the iso will be built. For slight speed up in the complete
> > compile just leave the systemvm profile disabled.
> >
> > I think this will make it more clear for everybody where the systemvm is
> > located as its current location in console-proxy was a bit confusing.
> >
> > Testing done:
> >  * Setting up devcloud with new build and new systemvm.iso
> >  * Verified ssvm operation (nfs secondary storage)
> >  * Verified  cvm operation
> >
> > As with all maven changes don't forget to update the maven configuration
> in
> > your IDE. (For eclipse users, right-click on the project, Maven -> Update
> > Project)
> >
> > Cheers,
> >
> > Hugo
>

API extract exact name

[Ian Duffy]

Hi,

It possible extract a specific virtualmachine from listvirtualmachines
by giving a name name field?

Basically, I want equality instead of like. I'm having an issue where
by I have a bunch of virtual machines: 'test', 'test2', 'test3'.
Calling listvirtualmachines with a name field supplied results in them
all being returned not sorted by closest matching.

Thanks,
Ian

RE: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fifth round)

[Animesh Chaturvedi]

> -Original Message-
> From: Simon Weller [mailto:swel...@ena.com]
> Sent: Friday, September 20, 2013 8:05 AM
> To: dev@cloudstack.apache.org
> Subject: Re: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fifth
> round)
> 
> Animesh,
> 
> 
> Are you aware of any proposed upgrade documentation as of yet? I'd
> really like to try a couple of upgrades to test the procedure.
> 
> 
> - Si
[Animesh>]Here is the upgrade steps from RN for ACS 4.1.0 release. It should be 
the same for 4.1.0 to 4.2.0 
http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.1.0/html/Release_Notes/upgrade-instructions.html#upgrade-from-4.0-to-4.1

> 
> - Original Message -
> 
> From: "Animesh Chaturvedi" 
> To: dev@cloudstack.apache.org
> Sent: Friday, September 20, 2013 12:03:41 AM
> Subject: RE: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fifth
> round)
> 
> 
> 
> > -Original Message-
> > From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> > Sent: Thursday, September 19, 2013 5:15 PM
> > To: dev@cloudstack.apache.org
> > Subject: RE: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fifth
> > round)
> >
> >
> >
> > > -Original Message-
> > > From: Marcus Sorensen [mailto:shadow...@gmail.com]
> > > Sent: Thursday, September 19, 2013 4:46 PM
> > > To: dev@cloudstack.apache.org
> > > Subject: Re: [VOTE][RESULTS] Release Apache CloudStack 4.2.0 (fifth
> > > round)
> > >
> > > I prefer a respin, as painful as that seems. VPC is a major feature,
> > > do we really want to release something that we know will break
> > > anyone who tries to upgrade? I could deal with #1 if we are able to
> > > include the hotfix script in the packaging, such that the release
> > > notes can provide dead simple instructions for upgrade (no 'go
> > > download this script'). I'm just not clear on what we can change and
> > > what we can't
> > post-vote.
> >
> > [Animesh>] I don't think the release artifacts can be changed so the
> > script will have to be downloaded. David/Chip/Wido any thoughts on
> that?
> > We can have the script available before the release announcement if we
> > continue with current VOTE.
> >
> > >
> [Animesh>] Only Marcus, Indra and Simon have responded I am prepared to
> respin tomorrow after VPC testing is complete with fixes from Alena. I
> would like to stick to 72 hour VOTE including weekend since last time
> most of the VOTEs were received over weekend.
> 
> 
> > > On Thu, Sep 19, 2013 at 3:59 PM, Animesh Chaturvedi
> > >  wrote:
> > > >
> > > >
> > > >> -Original Message-
> > > >> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> > > >> Sent: Thursday, September 19, 2013 10:43 AM
> > > >> To: dev@cloudstack.apache.org
> > > >> Subject: RE: [VOTE][RESULTS] Release Apache CloudStack 4.2.0
> > > >> (fifth
> > > >> round)
> > > >>
> > > >>
> > > >>
> > > >> > -Original Message-
> > > >> > From: Marcus Sorensen [mailto:shadow...@gmail.com]
> > > >> > Sent: Thursday, September 19, 2013 9:49 AM
> > > >> > To: dev@cloudstack.apache.org
> > > >> > Subject: RE: [VOTE][RESULTS] Release Apache CloudStack 4.2.0
> > > >> > (fifth
> > > >> > round)
> > > >> >
> > > >> > We do need to ensure that we have the db upgrade fix that was
> > > >> > mentioned on the other thread, otherwise people going from 4.1
> > > >> > to
> > > >> > 4.2 will have their VPCs break. Looks like we are waiting on a
> > > >> > script. It sounds like the plan will be to provide instructions
> > > >> > in the release notes. Really wish we would have caught that,
> > > >> > its not just that we find bugs at RC, but the severity of ones
> > > >> > we miss is astounding
> > > >> sometimes.
> > > >>
> > > >> [Animesh>] I am also stumped why this was not caught earlier.
> > > >> Kishan has a fix that is being tested.
> > > > [Animesh>] So while the fix is being tested we have two options
> > > >
> > > > 1. Release 4.2, release note this issue, provide a separate script
> > > > that would have to be run if someone was using VPC in 4.1 and
> > > > upgraded to 4.2, fix this issue in 4.2.1
> > > >
> > > > 2. Since we have not released 4.2 yet, respin another RC and
> > > > another round of VOTE. That would be a record 6th RC Vote and 2
> > > > recalls after successful votes :(
> > > >
> > > > Thoughts?
> > > >
> > > >>
> > > >> > On Sep 19, 2013 10:18 AM, "Animesh Chaturvedi" <
> > > >> > animesh.chaturv...@citrix.com> wrote:
> > > >> >
> > > >> > >
> > > >> > >
> > > >> > > > -Original Message-
> > > >> > > > From: Wido den Hollander [mailto:w...@widodh.nl]
> > > >> > > > Sent: Wednesday, September 18, 2013 4:55 PM
> > > >> > > > To: dev@cloudstack.apache.org
> > > >> > > > Subject: Re: [VOTE][RESULTS] Release Apache CloudStack
> > > >> > > > 4.2.0 (fifth
> > > >> > > > round)
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > > >> > > > On 09/19/2013 01:28 AM, Animesh Chaturvedi wrote:
> > > >> > > > >
> > > >> > > > > The vote has *passed* with the following results (binding
> > > >> >

Iptables Configuration

[Michael Phillips]

So I've been having a few issues with my test system which all seem to boil 
down to iptables not being configured correctly on my XEN host. Problems I've 
been having are
1. Template's not able to download - *can be fixed by stopping iptables on XEN 
host
2. System VM's don't deploy and start running - *can be fixed by stopping 
iptables on XEN host
3. Security groups not worling - *been posting in the user list and it seems 
like my XEN host does not have the necessary iptable entries for security 
groups to work properly.
With all these iptables issues, is there a iptables guide posted somewhere that 
outlines the changes needed to make XEN 6.02 + CSP work correctly?
  

[VOTE] Release Apache CloudStack 4.2.0 (sixth round)

[Animesh Chaturvedi]

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: 69c459342c568e2400d57ee88572b301603d8686

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 (Monday 9/23 PST EOD).

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: Managed storage with KVM

[Mike Tutkowski]

You appear to be correct. This is from the MS log (below). Discovery timed
out.

I'm not sure why this would be. My network settings shouldn't have changed
since the last time I tried this.

I am able to ping the KVM host from the MS host and vice versa.

I'm even able to manually kick off a VM on the KVM host and ping from it to
the MS host.

I am using NAT from my Mac OS X host (also running the CS MS) to the VM
running KVM (VMware Fusion).

2013-09-20 19:40:40,141 DEBUG [c.c.h.k.d.LibvirtServerDiscoverer]
(613487991@qtp-1659933291-3:ctx-6b28dc48) Timeout, to wait for the host
connecting to mgt svr, assuming it is failed
2013-09-20 19:40:40,144 WARN  [c.c.r.ResourceManagerImpl]
(613487991@qtp-1659933291-3:ctx-6b28dc48) Unable to find the server
resources at http://192.168.233.10
2013-09-20 19:40:40,145 INFO  [c.c.u.e.CSExceptionErrorCode]
(613487991@qtp-1659933291-3:ctx-6b28dc48) Could not find exception:
com.cloud.exception.DiscoveryException in error code list for exceptions
2013-09-20 19:40:40,147 WARN  [o.a.c.a.c.a.h.AddHostCmd]
(613487991@qtp-1659933291-3:ctx-6b28dc48) Exception:
com.cloud.exception.DiscoveryException: Unable to add the host
at
com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:778)

I do seem to be able to telnet in from my KVM host to the MS host's 8250
port:

mtutkowski@ubuntu:~$ telnet 192.168.233.1 8250
Trying 192.168.233.1...
Connected to 192.168.233.1.
Escape character is '^]'.

Re: Managed storage with KVM

[Mike Tutkowski]

Here's what my /etc/network/interfaces file looks like, if that is of
interest (the 192.168.233.0 network is the NAT network VMware Fusion set
up):

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet manual

auto cloudbr0
iface cloudbr0 inet static
address 192.168.233.10
netmask 255.255.255.0
network 192.168.233.0
broadcast 192.168.233.255
dns-nameservers 8.8.8.8
bridge_ports eth0
bridge_fd 5
bridge_stp off
bridge_maxwait 1
post-up route add default gw 192.168.233.2 metric 1
pre-down route del default gw 192.168.233.2


On Fri, Sep 20, 2013 at 10:08 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> You appear to be correct. This is from the MS log (below). Discovery timed
> out.
>
> I'm not sure why this would be. My network settings shouldn't have changed
> since the last time I tried this.
>
> I am able to ping the KVM host from the MS host and vice versa.
>
> I'm even able to manually kick off a VM on the KVM host and ping from it
> to the MS host.
>
> I am using NAT from my Mac OS X host (also running the CS MS) to the VM
> running KVM (VMware Fusion).
>
> 2013-09-20 19:40:40,141 DEBUG [c.c.h.k.d.LibvirtServerDiscoverer]
> (613487991@qtp-1659933291-3:ctx-6b28dc48) Timeout, to wait for the host
> connecting to mgt svr, assuming it is failed
> 2013-09-20 19:40:40,144 WARN  [c.c.r.ResourceManagerImpl]
> (613487991@qtp-1659933291-3:ctx-6b28dc48) Unable to find the server
> resources at http://192.168.233.10
> 2013-09-20 19:40:40,145 INFO  [c.c.u.e.CSExceptionErrorCode]
> (613487991@qtp-1659933291-3:ctx-6b28dc48) Could not find exception:
> com.cloud.exception.DiscoveryException in error code list for exceptions
> 2013-09-20 19:40:40,147 WARN  [o.a.c.a.c.a.h.AddHostCmd]
> (613487991@qtp-1659933291-3:ctx-6b28dc48) Exception:
> com.cloud.exception.DiscoveryException: Unable to add the host
> at
> com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:778)
>
> I do seem to be able to telnet in from my KVM host to the MS host's 8250
> port:
>
> mtutkowski@ubuntu:~$ telnet 192.168.233.1 8250
> Trying 192.168.233.1...
> Connected to 192.168.233.1.
> Escape character is '^]'.
>



-- 
*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: Managed storage with KVM

[Marcus Sorensen]

The log says your mgmt server is 192.168.233.10? But you tried to telnet to
192.168.233.1? It might be enough to change that in
/etc/cloudstack/agent/agent.properties, but you may want to edit the config
as well to tell it the real ms IP.
On Sep 20, 2013 10:12 PM, "Mike Tutkowski" 
wrote:

> Here's what my /etc/network/interfaces file looks like, if that is of
> interest (the 192.168.233.0 network is the NAT network VMware Fusion set
> up):
>
> auto lo
> iface lo inet loopback
>
> auto eth0
> iface eth0 inet manual
>
> auto cloudbr0
> iface cloudbr0 inet static
> address 192.168.233.10
> netmask 255.255.255.0
> network 192.168.233.0
> broadcast 192.168.233.255
> dns-nameservers 8.8.8.8
> bridge_ports eth0
> bridge_fd 5
> bridge_stp off
> bridge_maxwait 1
> post-up route add default gw 192.168.233.2 metric 1
> pre-down route del default gw 192.168.233.2
>
>
> On Fri, Sep 20, 2013 at 10:08 PM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
> > You appear to be correct. This is from the MS log (below). Discovery
> timed
> > out.
> >
> > I'm not sure why this would be. My network settings shouldn't have
> changed
> > since the last time I tried this.
> >
> > I am able to ping the KVM host from the MS host and vice versa.
> >
> > I'm even able to manually kick off a VM on the KVM host and ping from it
> > to the MS host.
> >
> > I am using NAT from my Mac OS X host (also running the CS MS) to the VM
> > running KVM (VMware Fusion).
> >
> > 2013-09-20 19:40:40,141 DEBUG [c.c.h.k.d.LibvirtServerDiscoverer]
> > (613487991@qtp-1659933291-3:ctx-6b28dc48) Timeout, to wait for the host
> > connecting to mgt svr, assuming it is failed
> > 2013-09-20 19:40:40,144 WARN  [c.c.r.ResourceManagerImpl]
> > (613487991@qtp-1659933291-3:ctx-6b28dc48) Unable to find the server
> > resources at http://192.168.233.10
> > 2013-09-20 19:40:40,145 INFO  [c.c.u.e.CSExceptionErrorCode]
> > (613487991@qtp-1659933291-3:ctx-6b28dc48) Could not find exception:
> > com.cloud.exception.DiscoveryException in error code list for exceptions
> > 2013-09-20 19:40:40,147 WARN  [o.a.c.a.c.a.h.AddHostCmd]
> > (613487991@qtp-1659933291-3:ctx-6b28dc48) Exception:
> > com.cloud.exception.DiscoveryException: Unable to add the host
> > at
> >
> com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:778)
> >
> > I do seem to be able to telnet in from my KVM host to the MS host's 8250
> > port:
> >
> > mtutkowski@ubuntu:~$ telnet 192.168.233.1 8250
> > Trying 192.168.233.1...
> > Connected to 192.168.233.1.
> > Escape character is '^]'.
> >
>
>
>
> --
> *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: Managed storage with KVM

[Mike Tutkowski]

Is it saying that the MS is at the IP address or the KVM host?

The KVM host is at 192.168.233.10.
The MS host is at 192.168.233.1.

I see this for my host Global Settings parameter:
hostThe ip address of management server192.168.233.1


/etc/cloudstack/agent/agent.properties has a host=192.168.233.1 value.


On Fri, Sep 20, 2013 at 10:21 PM, Marcus Sorensen wrote:

> The log says your mgmt server is 192.168.233.10? But you tried to telnet to
> 192.168.233.1? It might be enough to change that in
> /etc/cloudstack/agent/agent.properties, but you may want to edit the config
> as well to tell it the real ms IP.
> On Sep 20, 2013 10:12 PM, "Mike Tutkowski" 
> wrote:
>
> > Here's what my /etc/network/interfaces file looks like, if that is of
> > interest (the 192.168.233.0 network is the NAT network VMware Fusion set
> > up):
> >
> > auto lo
> > iface lo inet loopback
> >
> > auto eth0
> > iface eth0 inet manual
> >
> > auto cloudbr0
> > iface cloudbr0 inet static
> > address 192.168.233.10
> > netmask 255.255.255.0
> > network 192.168.233.0
> > broadcast 192.168.233.255
> > dns-nameservers 8.8.8.8
> > bridge_ports eth0
> > bridge_fd 5
> > bridge_stp off
> > bridge_maxwait 1
> > post-up route add default gw 192.168.233.2 metric 1
> > pre-down route del default gw 192.168.233.2
> >
> >
> > On Fri, Sep 20, 2013 at 10:08 PM, Mike Tutkowski <
> > mike.tutkow...@solidfire.com> wrote:
> >
> > > You appear to be correct. This is from the MS log (below). Discovery
> > timed
> > > out.
> > >
> > > I'm not sure why this would be. My network settings shouldn't have
> > changed
> > > since the last time I tried this.
> > >
> > > I am able to ping the KVM host from the MS host and vice versa.
> > >
> > > I'm even able to manually kick off a VM on the KVM host and ping from
> it
> > > to the MS host.
> > >
> > > I am using NAT from my Mac OS X host (also running the CS MS) to the VM
> > > running KVM (VMware Fusion).
> > >
> > > 2013-09-20 19:40:40,141 DEBUG [c.c.h.k.d.LibvirtServerDiscoverer]
> > > (613487991@qtp-1659933291-3:ctx-6b28dc48) Timeout, to wait for the
> host
> > > connecting to mgt svr, assuming it is failed
> > > 2013-09-20 19:40:40,144 WARN  [c.c.r.ResourceManagerImpl]
> > > (613487991@qtp-1659933291-3:ctx-6b28dc48) Unable to find the server
> > > resources at http://192.168.233.10
> > > 2013-09-20 19:40:40,145 INFO  [c.c.u.e.CSExceptionErrorCode]
> > > (613487991@qtp-1659933291-3:ctx-6b28dc48) Could not find exception:
> > > com.cloud.exception.DiscoveryException in error code list for
> exceptions
> > > 2013-09-20 19:40:40,147 WARN  [o.a.c.a.c.a.h.AddHostCmd]
> > > (613487991@qtp-1659933291-3:ctx-6b28dc48) Exception:
> > > com.cloud.exception.DiscoveryException: Unable to add the host
> > > at
> > >
> >
> com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:778)
> > >
> > > I do seem to be able to telnet in from my KVM host to the MS host's
> 8250
> > > port:
> > >
> > > mtutkowski@ubuntu:~$ telnet 192.168.233.1 8250
> > > Trying 192.168.233.1...
> > > Connected to 192.168.233.1.
> > > Escape character is '^]'.
> > >
> >
> >
> >
> > --
> > *Mike Tutkowski*
> > *Senior CloudStack Developer, SolidFire Inc.*
> > e: mike.tutkow...@solidfire.com
> > o: 303.746.7302
> > Advancing the way the world uses the
> > cloud
> > *™*
> >
>



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

Re: Managed storage with KVM

[Marcus Sorensen]

Sorry, I saw that in the log, I thought it was the agent log for some
reason. Is the agent started? That might be the place to look. There is an
agent log for the agent and one for the setup when it adds the host, both
in /var/log
On Sep 20, 2013 10:42 PM, "Mike Tutkowski" 
wrote:

> Is it saying that the MS is at the IP address or the KVM host?
>
> The KVM host is at 192.168.233.10.
> The MS host is at 192.168.233.1.
>
> I see this for my host Global Settings parameter:
> hostThe ip address of management server192.168.233.1
>
>
> /etc/cloudstack/agent/agent.properties has a host=192.168.233.1 value.
>
>
> On Fri, Sep 20, 2013 at 10:21 PM, Marcus Sorensen  >wrote:
>
> > The log says your mgmt server is 192.168.233.10? But you tried to telnet
> to
> > 192.168.233.1? It might be enough to change that in
> > /etc/cloudstack/agent/agent.properties, but you may want to edit the
> config
> > as well to tell it the real ms IP.
> > On Sep 20, 2013 10:12 PM, "Mike Tutkowski"  >
> > wrote:
> >
> > > Here's what my /etc/network/interfaces file looks like, if that is of
> > > interest (the 192.168.233.0 network is the NAT network VMware Fusion
> set
> > > up):
> > >
> > > auto lo
> > > iface lo inet loopback
> > >
> > > auto eth0
> > > iface eth0 inet manual
> > >
> > > auto cloudbr0
> > > iface cloudbr0 inet static
> > > address 192.168.233.10
> > > netmask 255.255.255.0
> > > network 192.168.233.0
> > > broadcast 192.168.233.255
> > > dns-nameservers 8.8.8.8
> > > bridge_ports eth0
> > > bridge_fd 5
> > > bridge_stp off
> > > bridge_maxwait 1
> > > post-up route add default gw 192.168.233.2 metric 1
> > > pre-down route del default gw 192.168.233.2
> > >
> > >
> > > On Fri, Sep 20, 2013 at 10:08 PM, Mike Tutkowski <
> > > mike.tutkow...@solidfire.com> wrote:
> > >
> > > > You appear to be correct. This is from the MS log (below). Discovery
> > > timed
> > > > out.
> > > >
> > > > I'm not sure why this would be. My network settings shouldn't have
> > > changed
> > > > since the last time I tried this.
> > > >
> > > > I am able to ping the KVM host from the MS host and vice versa.
> > > >
> > > > I'm even able to manually kick off a VM on the KVM host and ping from
> > it
> > > > to the MS host.
> > > >
> > > > I am using NAT from my Mac OS X host (also running the CS MS) to the
> VM
> > > > running KVM (VMware Fusion).
> > > >
> > > > 2013-09-20 19:40:40,141 DEBUG [c.c.h.k.d.LibvirtServerDiscoverer]
> > > > (613487991@qtp-1659933291-3:ctx-6b28dc48) Timeout, to wait for the
> > host
> > > > connecting to mgt svr, assuming it is failed
> > > > 2013-09-20 19:40:40,144 WARN  [c.c.r.ResourceManagerImpl]
> > > > (613487991@qtp-1659933291-3:ctx-6b28dc48) Unable to find the server
> > > > resources at http://192.168.233.10
> > > > 2013-09-20 19:40:40,145 INFO  [c.c.u.e.CSExceptionErrorCode]
> > > > (613487991@qtp-1659933291-3:ctx-6b28dc48) Could not find exception:
> > > > com.cloud.exception.DiscoveryException in error code list for
> > exceptions
> > > > 2013-09-20 19:40:40,147 WARN  [o.a.c.a.c.a.h.AddHostCmd]
> > > > (613487991@qtp-1659933291-3:ctx-6b28dc48) Exception:
> > > > com.cloud.exception.DiscoveryException: Unable to add the host
> > > > at
> > > >
> > >
> >
> com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:778)
> > > >
> > > > I do seem to be able to telnet in from my KVM host to the MS host's
> > 8250
> > > > port:
> > > >
> > > > mtutkowski@ubuntu:~$ telnet 192.168.233.1 8250
> > > > Trying 192.168.233.1...
> > > > Connected to 192.168.233.1.
> > > > Escape character is '^]'.
> > > >
> > >
> > >
> > >
> > > --
> > > *Mike Tutkowski*
> > > *Senior CloudStack Developer, SolidFire Inc.*
> > > e: mike.tutkow...@solidfire.com
> > > o: 303.746.7302
> > > Advancing the way the world uses the
> > > cloud
> > > *™*
> > >
> >
>
>
>
> --
> *Mike Tutkowski*
> *Senior CloudStack Developer, SolidFire Inc.*
> e: mike.tutkow...@solidfire.com
> o: 303.746.7302
> Advancing the way the world uses the
> cloud
> *™*
>

Re: Volunteers to Complete the 4.2 Release Notes

[Indra Pramana]

Hi Radhika,

I have downloaded the PDF document, thank you very much.

I noted that there is no specific upgrade instruction from 4.1.1 to 4.2.0.
What we have there is the generic upgrade instruction from 4.x.x to 4.2.0.

I have actually tried to follow this instruction on my earlier (failed)
upgrade attempt from 4.1.1 to 4.2.0, and found out that some of the steps
are no longer applicable. For example:

Step 6: Changes from /etc/cloud/management/components.xml to
/etc/cloudstack/management/componentContext.xml is no longer required for
upgrade from 4.1.1 to 4.2.0, since we are already using /etc/cloudstack
folder (instead of /etc/cloud folder) on 4.1.1.

Step 8h: Uninstalling old cloud-* packages are not required for upgrade
from 4.1.1 to 4.2.0 (cloud-* packages do not exist).

Step 10: (KVM Only): point a - Manually clean up /var/cache/cloudstack <--
I believe this is supposed to be done on the KVM hosts? There is no
/var/cache/cloudstack folder on our KVM hosts running CloudStack agent
version 4.1.1. I have verified on all my KVM hosts. Is this step required
on the KVM hosts for upgrade from 4.1.1 to 4.2.0?

I found /var/cache/cloudstack folder on my CloudStack management server
though. Is this step supposed to be done on the management server instead
of the KVM hosts? If yes, it's not clearly mentioned.

Step 12: When I tried to run the cloudstack-sysvmadm script to restart the
system VMs, the script failed to run with some error messages.
Unfortunately, I didn't manage to take down the error messages. Is this
step required for upgrade from 4.1.1 to 4.2.0? If for some reason, we are
not able to run the script, are we able to restart the system VMs manually
(say from the CloudStack GUI)?

Looking forward to your reply, thank you.

Cheers.



On Fri, Sep 20, 2013 at 5:45 PM, Radhika Puthiyetath <
radhika.puthiyet...@citrix.com> wrote:

>  Thanks Indra.
>
> ** **
>
> I shall attach the PDF file at
> https://issues.apache.org/jira/browse/CLOUDSTACK-4245.
>
> ** **
>
> ** **
>
> ** **
>
> *From:* Indra Pramana [mailto:in...@sg.or.id]
> *Sent:* Friday, September 20, 2013 12:07 PM
> *To:* Radhika Puthiyetath
> *Cc:* us...@cloudstack.apache.org
>
> *Subject:* Re: Volunteers to Complete the 4.2 Release Notes
>
> ** **
>
> Hi Radhika,
>
> ** **
>
> May I know how can I view the release notes in normal HTML format, instead
> of the original XML format?
>
> ** **
>
> Does it specifically contain migration steps from 4.1.1 to 4.2.0?
>
> ** **
>
> Would like to try again to upgrade my current CloudStack 4.1.1 to 4.2.0,
> provided I can get the detailed instruction on what to do. Last time I
> tried to follow the existing documentation on the .tar.bz2 file (provided
> by Animesh when he started the vote) and some of the steps seem to be not
> applicable anymore, and I might have missed out some other steps which are
> actually required.
>
> ** **
>
> Looking forward to your reply, thank you.
>
> ** **
>
> Cheers.
>
> ** **
>
> ** **
>
> On Thu, Sep 19, 2013 at 2:42 PM, Radhika Puthiyetath <
> radhika.puthiyet...@citrix.com> wrote:
>
> This has been updated. Could someone please validate the API section ?
>
>
> -Original Message-
> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
>
> Sent: Sunday, September 15, 2013 4:16 AM
> To: 
> Cc: dev@cloudstack.apache.org; us...@cloudstack.apache.org
> Subject: Re: Volunteers to Complete the 4.2 Release Notes
>
> I have added a public filters for known issues and fixed issues that we
> can put in release notes. This way the data is dynamic and up to date
>
> Thanks
> Animesh
>
> On Sep 13, 2013, at 8:53 AM, "Radhika Puthiyetath" <
> radhika.puthiyet...@citrix.com> wrote:
>
> > Who is volunteering to provide the list of Fixed issues for the RN?
> >
> > -Original Message-
> > From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> > Sent: Wednesday, August 28, 2013 4:40 AM
> > To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
> > Subject: RE: Volunteers to Complete the 4.2 Release Notes
> >
> > Community help is needed to fix up the release notes, any volunteers
> >
> > Animesh
> >
> >> -Original Message-
> >> From: Radhika Puthiyetath [mailto:radhika.puthiyet...@citrix.com]
> >> Sent: Tuesday, August 13, 2013 1:01 AM
> >> To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
> >> Subject: Volunteers to Complete the 4.2 Release Notes
> >>
> >> Hi,
> >>
> >> Looking for volunteers to help me with the 4.2 Release Notes.
> >>
> >> I have started filling in the new feature section, and checked in to the
> >> 4.2 branch.
> >>
> >> A defect is filed https://issues.apache.org/jira/browse/CLOUDSTACK-4245
> .
> >>
> >> Thanks for the help
> >> -Radhika
>
> ** **
>

Re: Managed storage with KVM

[Mike Tutkowski]

agent.log looks OK to me:

2013-09-20 19:35:39,010 INFO  [cloud.agent.AgentShell] (main:null) Agent
started
2013-09-20 19:35:39,011 INFO  [cloud.agent.AgentShell] (main:null)
Implementation Version is 4.3.0-SNAPSHOT
2013-09-20 19:35:39,015 INFO  [cloud.agent.AgentShell] (main:null)
agent.properties found at /etc/cloudstack/agent/agent.properties
2013-09-20 19:35:39,023 INFO  [cloud.agent.AgentShell] (main:null)
Defaulting to using properties file for storage
2013-09-20 19:35:39,024 INFO  [cloud.agent.AgentShell] (main:null)
Defaulting to the constant time backoff algorithm
2013-09-20 19:35:39,029 INFO  [cloud.utils.LogUtils] (main:null) log4j
configuration found at /etc/cloudstack/agent/log4j-cloud.xml
2013-09-20 19:35:39,163 INFO  [cloud.agent.Agent] (main:null) id is 3
2013-09-20 19:35:39,197 INFO
 [resource.virtualnetwork.VirtualRoutingResource] (main:null)
VirtualRoutingResource _scriptDir to use: scripts/network/domr/kvm

However, I wasn't aware that setup.log was important. This seems to be a
problem, but I'm not sure what it might indicate:

DEBUG:root:execute:sudo /usr/sbin/service cloudstack-agent status
DEBUG:root:Failed to execute: * could not access PID file for
cloudstack-agent
DEBUG:root:execute:sudo /usr/sbin/service cloudstack-agent start


On Fri, Sep 20, 2013 at 10:53 PM, Marcus Sorensen wrote:

> Sorry, I saw that in the log, I thought it was the agent log for some
> reason. Is the agent started? That might be the place to look. There is an
> agent log for the agent and one for the setup when it adds the host, both
> in /var/log
> On Sep 20, 2013 10:42 PM, "Mike Tutkowski" 
> wrote:
>
> > Is it saying that the MS is at the IP address or the KVM host?
> >
> > The KVM host is at 192.168.233.10.
> > The MS host is at 192.168.233.1.
> >
> > I see this for my host Global Settings parameter:
> > hostThe ip address of management server192.168.233.1
> >
> >
> > /etc/cloudstack/agent/agent.properties has a host=192.168.233.1 value.
> >
> >
> > On Fri, Sep 20, 2013 at 10:21 PM, Marcus Sorensen  > >wrote:
> >
> > > The log says your mgmt server is 192.168.233.10? But you tried to
> telnet
> > to
> > > 192.168.233.1? It might be enough to change that in
> > > /etc/cloudstack/agent/agent.properties, but you may want to edit the
> > config
> > > as well to tell it the real ms IP.
> > > On Sep 20, 2013 10:12 PM, "Mike Tutkowski" <
> mike.tutkow...@solidfire.com
> > >
> > > wrote:
> > >
> > > > Here's what my /etc/network/interfaces file looks like, if that is of
> > > > interest (the 192.168.233.0 network is the NAT network VMware Fusion
> > set
> > > > up):
> > > >
> > > > auto lo
> > > > iface lo inet loopback
> > > >
> > > > auto eth0
> > > > iface eth0 inet manual
> > > >
> > > > auto cloudbr0
> > > > iface cloudbr0 inet static
> > > > address 192.168.233.10
> > > > netmask 255.255.255.0
> > > > network 192.168.233.0
> > > > broadcast 192.168.233.255
> > > > dns-nameservers 8.8.8.8
> > > > bridge_ports eth0
> > > > bridge_fd 5
> > > > bridge_stp off
> > > > bridge_maxwait 1
> > > > post-up route add default gw 192.168.233.2 metric 1
> > > > pre-down route del default gw 192.168.233.2
> > > >
> > > >
> > > > On Fri, Sep 20, 2013 at 10:08 PM, Mike Tutkowski <
> > > > mike.tutkow...@solidfire.com> wrote:
> > > >
> > > > > You appear to be correct. This is from the MS log (below).
> Discovery
> > > > timed
> > > > > out.
> > > > >
> > > > > I'm not sure why this would be. My network settings shouldn't have
> > > > changed
> > > > > since the last time I tried this.
> > > > >
> > > > > I am able to ping the KVM host from the MS host and vice versa.
> > > > >
> > > > > I'm even able to manually kick off a VM on the KVM host and ping
> from
> > > it
> > > > > to the MS host.
> > > > >
> > > > > I am using NAT from my Mac OS X host (also running the CS MS) to
> the
> > VM
> > > > > running KVM (VMware Fusion).
> > > > >
> > > > > 2013-09-20 19:40:40,141 DEBUG [c.c.h.k.d.LibvirtServerDiscoverer]
> > > > > (613487991@qtp-1659933291-3:ctx-6b28dc48) Timeout, to wait for the
> > > host
> > > > > connecting to mgt svr, assuming it is failed
> > > > > 2013-09-20 19:40:40,144 WARN  [c.c.r.ResourceManagerImpl]
> > > > > (613487991@qtp-1659933291-3:ctx-6b28dc48) Unable to find the
> server
> > > > > resources at http://192.168.233.10
> > > > > 2013-09-20 19:40:40,145 INFO  [c.c.u.e.CSExceptionErrorCode]
> > > > > (613487991@qtp-1659933291-3:ctx-6b28dc48) Could not find
> exception:
> > > > > com.cloud.exception.DiscoveryException in error code list for
> > > exceptions
> > > > > 2013-09-20 19:40:40,147 WARN  [o.a.c.a.c.a.h.AddHostCmd]
> > > > > (613487991@qtp-1659933291-3:ctx-6b28dc48) Exception:
> > > > > com.cloud.exception.DiscoveryException: Unable to add the host
> > > > > at
> > > > >
> > > >
> > >
> >
> com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:778)
> > > > >
> > > > > I do seem to be able to telnet in from my KVM host to the 

Re: Managed storage with KVM

[Mike Tutkowski]

I get the same error running the command manually:

mtutkowski@ubuntu:/etc/cloudstack/agent$ sudo /usr/sbin/service
cloudstack-agent status
 * could not access PID file for cloudstack-agent


On Fri, Sep 20, 2013 at 11:00 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> agent.log looks OK to me:
>
> 2013-09-20 19:35:39,010 INFO  [cloud.agent.AgentShell] (main:null) Agent
> started
> 2013-09-20 19:35:39,011 INFO  [cloud.agent.AgentShell] (main:null)
> Implementation Version is 4.3.0-SNAPSHOT
> 2013-09-20 19:35:39,015 INFO  [cloud.agent.AgentShell] (main:null)
> agent.properties found at /etc/cloudstack/agent/agent.properties
> 2013-09-20 19:35:39,023 INFO  [cloud.agent.AgentShell] (main:null)
> Defaulting to using properties file for storage
> 2013-09-20 19:35:39,024 INFO  [cloud.agent.AgentShell] (main:null)
> Defaulting to the constant time backoff algorithm
> 2013-09-20 19:35:39,029 INFO  [cloud.utils.LogUtils] (main:null) log4j
> configuration found at /etc/cloudstack/agent/log4j-cloud.xml
> 2013-09-20 19:35:39,163 INFO  [cloud.agent.Agent] (main:null) id is 3
> 2013-09-20 19:35:39,197 INFO
>  [resource.virtualnetwork.VirtualRoutingResource] (main:null)
> VirtualRoutingResource _scriptDir to use: scripts/network/domr/kvm
>
> However, I wasn't aware that setup.log was important. This seems to be a
> problem, but I'm not sure what it might indicate:
>
> DEBUG:root:execute:sudo /usr/sbin/service cloudstack-agent status
> DEBUG:root:Failed to execute: * could not access PID file for
> cloudstack-agent
> DEBUG:root:execute:sudo /usr/sbin/service cloudstack-agent start
>
>
> On Fri, Sep 20, 2013 at 10:53 PM, Marcus Sorensen wrote:
>
>> Sorry, I saw that in the log, I thought it was the agent log for some
>> reason. Is the agent started? That might be the place to look. There is an
>> agent log for the agent and one for the setup when it adds the host, both
>> in /var/log
>> On Sep 20, 2013 10:42 PM, "Mike Tutkowski" 
>> wrote:
>>
>> > Is it saying that the MS is at the IP address or the KVM host?
>> >
>> > The KVM host is at 192.168.233.10.
>> > The MS host is at 192.168.233.1.
>> >
>> > I see this for my host Global Settings parameter:
>> > hostThe ip address of management server192.168.233.1
>> >
>> >
>> > /etc/cloudstack/agent/agent.properties has a host=192.168.233.1 value.
>> >
>> >
>> > On Fri, Sep 20, 2013 at 10:21 PM, Marcus Sorensen > > >wrote:
>> >
>> > > The log says your mgmt server is 192.168.233.10? But you tried to
>> telnet
>> > to
>> > > 192.168.233.1? It might be enough to change that in
>> > > /etc/cloudstack/agent/agent.properties, but you may want to edit the
>> > config
>> > > as well to tell it the real ms IP.
>> > > On Sep 20, 2013 10:12 PM, "Mike Tutkowski" <
>> mike.tutkow...@solidfire.com
>> > >
>> > > wrote:
>> > >
>> > > > Here's what my /etc/network/interfaces file looks like, if that is
>> of
>> > > > interest (the 192.168.233.0 network is the NAT network VMware Fusion
>> > set
>> > > > up):
>> > > >
>> > > > auto lo
>> > > > iface lo inet loopback
>> > > >
>> > > > auto eth0
>> > > > iface eth0 inet manual
>> > > >
>> > > > auto cloudbr0
>> > > > iface cloudbr0 inet static
>> > > > address 192.168.233.10
>> > > > netmask 255.255.255.0
>> > > > network 192.168.233.0
>> > > > broadcast 192.168.233.255
>> > > > dns-nameservers 8.8.8.8
>> > > > bridge_ports eth0
>> > > > bridge_fd 5
>> > > > bridge_stp off
>> > > > bridge_maxwait 1
>> > > > post-up route add default gw 192.168.233.2 metric 1
>> > > > pre-down route del default gw 192.168.233.2
>> > > >
>> > > >
>> > > > On Fri, Sep 20, 2013 at 10:08 PM, Mike Tutkowski <
>> > > > mike.tutkow...@solidfire.com> wrote:
>> > > >
>> > > > > You appear to be correct. This is from the MS log (below).
>> Discovery
>> > > > timed
>> > > > > out.
>> > > > >
>> > > > > I'm not sure why this would be. My network settings shouldn't have
>> > > > changed
>> > > > > since the last time I tried this.
>> > > > >
>> > > > > I am able to ping the KVM host from the MS host and vice versa.
>> > > > >
>> > > > > I'm even able to manually kick off a VM on the KVM host and ping
>> from
>> > > it
>> > > > > to the MS host.
>> > > > >
>> > > > > I am using NAT from my Mac OS X host (also running the CS MS) to
>> the
>> > VM
>> > > > > running KVM (VMware Fusion).
>> > > > >
>> > > > > 2013-09-20 19:40:40,141 DEBUG [c.c.h.k.d.LibvirtServerDiscoverer]
>> > > > > (613487991@qtp-1659933291-3:ctx-6b28dc48) Timeout, to wait for
>> the
>> > > host
>> > > > > connecting to mgt svr, assuming it is failed
>> > > > > 2013-09-20 19:40:40,144 WARN  [c.c.r.ResourceManagerImpl]
>> > > > > (613487991@qtp-1659933291-3:ctx-6b28dc48) Unable to find the
>> server
>> > > > > resources at http://192.168.233.10
>> > > > > 2013-09-20 19:40:40,145 INFO  [c.c.u.e.CSExceptionErrorCode]
>> > > > > (613487991@qtp-1659933291-3:ctx-6b28dc48) Could not find
>> exception:
>> > > > > com.cloud.exception.DiscoveryException in error code 

Re: Managed storage with KVM

[Mike Tutkowski]

When I re-deployed the DEBs, I didn't remove cloudstack-agent first. Would
that be a problem? I just did a sudo apt-get install cloudstack-agent.


On Fri, Sep 20, 2013 at 11:03 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> I get the same error running the command manually:
>
> mtutkowski@ubuntu:/etc/cloudstack/agent$ sudo /usr/sbin/service
> cloudstack-agent status
>  * could not access PID file for cloudstack-agent
>
>
> On Fri, Sep 20, 2013 at 11:00 PM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
>> agent.log looks OK to me:
>>
>> 2013-09-20 19:35:39,010 INFO  [cloud.agent.AgentShell] (main:null) Agent
>> started
>> 2013-09-20 19:35:39,011 INFO  [cloud.agent.AgentShell] (main:null)
>> Implementation Version is 4.3.0-SNAPSHOT
>> 2013-09-20 19:35:39,015 INFO  [cloud.agent.AgentShell] (main:null)
>> agent.properties found at /etc/cloudstack/agent/agent.properties
>> 2013-09-20 19:35:39,023 INFO  [cloud.agent.AgentShell] (main:null)
>> Defaulting to using properties file for storage
>> 2013-09-20 19:35:39,024 INFO  [cloud.agent.AgentShell] (main:null)
>> Defaulting to the constant time backoff algorithm
>> 2013-09-20 19:35:39,029 INFO  [cloud.utils.LogUtils] (main:null) log4j
>> configuration found at /etc/cloudstack/agent/log4j-cloud.xml
>> 2013-09-20 19:35:39,163 INFO  [cloud.agent.Agent] (main:null) id is 3
>> 2013-09-20 19:35:39,197 INFO
>>  [resource.virtualnetwork.VirtualRoutingResource] (main:null)
>> VirtualRoutingResource _scriptDir to use: scripts/network/domr/kvm
>>
>> However, I wasn't aware that setup.log was important. This seems to be a
>> problem, but I'm not sure what it might indicate:
>>
>> DEBUG:root:execute:sudo /usr/sbin/service cloudstack-agent status
>> DEBUG:root:Failed to execute: * could not access PID file for
>> cloudstack-agent
>> DEBUG:root:execute:sudo /usr/sbin/service cloudstack-agent start
>>
>>
>> On Fri, Sep 20, 2013 at 10:53 PM, Marcus Sorensen wrote:
>>
>>> Sorry, I saw that in the log, I thought it was the agent log for some
>>> reason. Is the agent started? That might be the place to look. There is
>>> an
>>> agent log for the agent and one for the setup when it adds the host, both
>>> in /var/log
>>> On Sep 20, 2013 10:42 PM, "Mike Tutkowski" >> >
>>> wrote:
>>>
>>> > Is it saying that the MS is at the IP address or the KVM host?
>>> >
>>> > The KVM host is at 192.168.233.10.
>>> > The MS host is at 192.168.233.1.
>>> >
>>> > I see this for my host Global Settings parameter:
>>> > hostThe ip address of management server192.168.233.1
>>> >
>>> >
>>> > /etc/cloudstack/agent/agent.properties has a host=192.168.233.1 value.
>>> >
>>> >
>>> > On Fri, Sep 20, 2013 at 10:21 PM, Marcus Sorensen >> > >wrote:
>>> >
>>> > > The log says your mgmt server is 192.168.233.10? But you tried to
>>> telnet
>>> > to
>>> > > 192.168.233.1? It might be enough to change that in
>>> > > /etc/cloudstack/agent/agent.properties, but you may want to edit the
>>> > config
>>> > > as well to tell it the real ms IP.
>>> > > On Sep 20, 2013 10:12 PM, "Mike Tutkowski" <
>>> mike.tutkow...@solidfire.com
>>> > >
>>> > > wrote:
>>> > >
>>> > > > Here's what my /etc/network/interfaces file looks like, if that is
>>> of
>>> > > > interest (the 192.168.233.0 network is the NAT network VMware
>>> Fusion
>>> > set
>>> > > > up):
>>> > > >
>>> > > > auto lo
>>> > > > iface lo inet loopback
>>> > > >
>>> > > > auto eth0
>>> > > > iface eth0 inet manual
>>> > > >
>>> > > > auto cloudbr0
>>> > > > iface cloudbr0 inet static
>>> > > > address 192.168.233.10
>>> > > > netmask 255.255.255.0
>>> > > > network 192.168.233.0
>>> > > > broadcast 192.168.233.255
>>> > > > dns-nameservers 8.8.8.8
>>> > > > bridge_ports eth0
>>> > > > bridge_fd 5
>>> > > > bridge_stp off
>>> > > > bridge_maxwait 1
>>> > > > post-up route add default gw 192.168.233.2 metric 1
>>> > > > pre-down route del default gw 192.168.233.2
>>> > > >
>>> > > >
>>> > > > On Fri, Sep 20, 2013 at 10:08 PM, Mike Tutkowski <
>>> > > > mike.tutkow...@solidfire.com> wrote:
>>> > > >
>>> > > > > You appear to be correct. This is from the MS log (below).
>>> Discovery
>>> > > > timed
>>> > > > > out.
>>> > > > >
>>> > > > > I'm not sure why this would be. My network settings shouldn't
>>> have
>>> > > > changed
>>> > > > > since the last time I tried this.
>>> > > > >
>>> > > > > I am able to ping the KVM host from the MS host and vice versa.
>>> > > > >
>>> > > > > I'm even able to manually kick off a VM on the KVM host and ping
>>> from
>>> > > it
>>> > > > > to the MS host.
>>> > > > >
>>> > > > > I am using NAT from my Mac OS X host (also running the CS MS) to
>>> the
>>> > VM
>>> > > > > running KVM (VMware Fusion).
>>> > > > >
>>> > > > > 2013-09-20 19:40:40,141 DEBUG [c.c.h.k.d.LibvirtServerDiscoverer]
>>> > > > > (613487991@qtp-1659933291-3:ctx-6b28dc48) Timeout, to wait for
>>> the
>>> > > host
>>> > > > > connecting to mgt svr, assuming it is failed
>>> > > > > 2013-09-20 19:

Re: [MERGE] changing nonoss to noredist

[Hugo Trippaers]

All,

I've merged the branch to master.

Please beware that the nonoss flag is now gone from master. To build CloudStack 
with the non-redistributable components please use the noredist flag. Please 
adjust your build scripts accordingly.

I've updated the jenkins builds, but testing them is troublesome as all builds 
keep failing due to the libvirt issue.

On Sep 19, 2013, at 2:37 PM, Hugo Trippaers  wrote:

> Hey all,
> 
> As discussed on the mailing list we want to change the name of the nonoss 
> branch to noredist as this better reflects the reason for this separate 
> branch.
> 
> In the branch nonoss-to-noredist i've made the necessary changes to the code. 
> After merging this branch i will also update the wiki and the jenkins jobs. 
> It's not a big change but something that we all must be aware of to avoid 
> problems during compilation.
> 
> Tests done on this branch
> * compile test regular
> * compile test noredist
> * package RPM regular
> * package RPM noredist
> 
> Comments or feedback on this branch? Otherwise i will merge this branch .
> 
> Cheers,
> 
> Hugo

Re: Moved the systemvm to its own maven project

[Hugo Trippaers]

Hey Darren,

Good find. I've moved the dependency to the systemvm profile, including the ant 
tasks to copy the systemvm to the right location.

Cheers,

Hugo

On Sep 21, 2013, at 4:55 AM, Darren Shepherd  
wrote:

> I think the build is broken now.  client/pom.xml depends on cloud-systemvm,
> so if you don't put -Psystemvm the build breaks.  I think the
> cloud-systemvm dep in client/pom.xml needs to be conditional on the
> systemvm profile.
> 
> Darren
> 
> 
> On Fri, Sep 20, 2013 at 11:01 AM, Alex Huang  wrote:
> 
>> Nice!  Can't wait to look at this!
>> 
>> --Alex
>> 
>>> -Original Message-
>>> From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers
>>> Sent: Friday, September 20, 2013 3:40 AM
>>> To: dev@cloudstack.apache.org
>>> Subject: Moved the systemvm to its own maven project
>>> 
>>> Hey all,
>>> 
>>> Just a heads-up that i pushed this commit to master:
>>> 
>>> commit 6c261042821c5597dab8d6be85dc59c948424e13
>>> Author: Hugo Trippaers 
>>> Date:   Fri Sep 20 18:08:20 2013 +0800
>>> 
>>>Move the system vm to a separate maven project.
>>> 
>>>All (almost) files belonging to the systemvm aer now centralize in
>> the
>>> systemvm directory. The code for the separate functions is still in the
>>> services directory. This will make the code easier to understa
>>> 
>>> 
>>> This commit effectively separates the code in the console-proxy from the
>>> actual building of the systemvm.iso. The systemvm profile (mvn
>> -Psystemvm)
>>> will now control if the systemvm will be build entirely instead of just
>>> determining if the iso will be built. For slight speed up in the complete
>>> compile just leave the systemvm profile disabled.
>>> 
>>> I think this will make it more clear for everybody where the systemvm is
>>> located as its current location in console-proxy was a bit confusing.
>>> 
>>> Testing done:
>>> * Setting up devcloud with new build and new systemvm.iso
>>> * Verified ssvm operation (nfs secondary storage)
>>> * Verified  cvm operation
>>> 
>>> As with all maven changes don't forget to update the maven configuration
>> in
>>> your IDE. (For eclipse users, right-click on the project, Maven -> Update
>>> Project)
>>> 
>>> Cheers,
>>> 
>>> Hugo
>> 

Re: [ACS42] Duplicate S3 and Swift Object Storage Features

[Vincent]

Min Chen  writes:

> 
> Agree with Edison on this regarding priority. I can see more influence of 
CloudStack if we can support
> upgrade from NFS to S3.  We didn't say that we are not supporting upgrade 
path for S3 from 4.0 to 4.2, just can
> be prioritized lower than upgrading from NFS to S3 to gain more user base.
> 
> Thanks
> -min
> 
> From: Edison Su mailto:Edison.su@...>>
> Reply-To:
> "dev@..."  cloudstack.apache.org>
> Date: Friday, July 26, 2013 11:02 AM
> To:
> "dev@..."  cloudstack.apache.org>
> Subject: [ACS42] Duplicate S3 and Swift Object Storage Features
> 
> “I see prodded a facility to convert NFS secondary storage to object 
storage as an enhancement where the
> lack of a migration path is a blocking defect.”
> I have different view on this item, regarding the priority. At one hand, 
we have almost all of cloudstack
> users are using NFS as secondary storage, if there is no way to upgrade to 
S3, then all of existing
> CloudStack deployment can’t upgrade to use your Basho CS, or Amazon S3. On 
the other hand, there is tiny
> users are using S3/Swift(S3 in 4.0/4.1 even can’t backup snapshot, and 
nobody reports the issue
> before, so I assume there is zero cloudstack users are using S3 in 
4.0/4.1).
> Then fix the upgrade path  for S3 from 4.0 to 4.2 has little gain for the 
whole CloudStack users(as the user
> base is almost zero), while fix the upgrade path from NFS to S3 will 
benefit the whole community a lot.
> So, which one has the higher priority? Isn’t obvious?
> 
> From: John Burwell [mailto:jburwell@...]
> Sent: Friday, July 26, 2013 7:15 AM
> To: dev@...
> Cc: Min Chen
> Subject: Re: [ACS42] Duplicate S3 and Swift Object Storage Features
> 
> Edison,
> 
> Unfortunately, given the time remaining the 4.2 release cycle, the most 
that can likely be done is to remove
> these global options.  Due to the massive amount of cruft that will be 
created when these global options are
> removed, I am disappointed that a more a comprehensive code removal was 
not performed as part of this
> effort.  I have opened defect CLOUDSTACK-3861 to address the duplicate 
functionality and task
> CLOUDSTACK-3862 to address removal of the dead code post 4.2.0.
> 
> I completely disagree regarding the migration path issue.  As we have 
discussed in the past on the list, we
> have no way of knowing what features are in the use across the community.  
Therefore, migration paths for
> feature replacements must always be provided in order to avoid a scenario 
where users are stranded.  4.1.0
> users employing NFS secondary storage upgrading to 4.2.0 will suffer no 
loss of functionality.  However,
> 4.1.0 users using either S3 or Swift-backed secondary storage will lose 
capability.  I see prodded a
> facility to convert NFS secondary storage to object storage as an 
enhancement where the lack of a
> migration path is a blocking defect.  As such, I have opened defect 
CLOUDSTACK-3360 [2] to address this issue.
> 
> Thanks,
> -John
> 
> [1]: https://issues.apache.org/jira/browse/CLOUDSTACK-3861
> [2]: https://issues.apache.org/jira/browse/CLOUDSTACK-3862
> [3]: https://issues.apache.org/jira/browse/CLOUDSTACK-3860
> 
> On Jul 25, 2013, at 6:08 PM, Edison Su
> mailto:Edison.su@...>> wrote:
> 
> -Original Message-
> From: John Burwell [mailto:jburwell@...]
> Sent: Thursday, July 25, 2013 2:13 PM
> To: dev@...
> Cc: Min Chen
> Subject: Re: [ACS42] Duplicate S3 and Swift Object Storage Features
> 
> Edison,
> 
> The old S3 and Swift-backed secondary storage can still be enabled (via 
global
> options) and configured along side the new object store feature.  Is there 
a
> 
> Do you mean "s3.enabled" and "swift.enabled" in global configuration? This 
two options should be
> removed, and they won't have any effect any more.
> 
> reason why they are still present?  I would have expected the code to have
> been removed.
> 
> The second question is how users utilizing those features will be migrated 
to
> the new object storage approach.
> 
> Haven't have time to take a look at upgrade issue yet. Should be able to 
upgrade from existing S3/Swift into
> 4.2, but I doubt are there any users are using S3/Swift in CloudStack?
> We'd better put our energy on how to upgrade existing NFS secondary 
storage to S3/Swift, which are the most
> users of CloudStack using.
> 
> Thanks,
> -John
> 
> On Jul 25, 2013, at 5:09 PM, Edison Su
> mailto:Edison.su@...>> wrote:
> 
> -Original Message-
> From: John Burwell [mailto:jburwell@...]
> Sent: Thursday, July 25, 2013 2:06 PM
> To: dev@...
> Cc: Edison Su; Min Chen
> Subject: [ACS42] Duplicate S3 and Swift Object Storage Features
> 
> All,
> 
> I have noticed during testing that the old S3 and Swift-backed
> secondary
> 
> What you mean the old s3/swift secondary? Upgrading the old s3 from 4.1
> to 4.2?
> 
> storage featur