RE: Review Request 23192: Adding Readme and run checkbox at the end of the installation. Also installing mysql connector

2014-07-08 Thread Damoder Reddy
Hugo,

 As Rajani mentioned we are not packaging the sources with MSI installer, we 
are telling to installer from where to download the dependencies.

Anyhow my question is, the MSI build is already part of separate build profile 
("buildw") which is not build with default profile. So still we need to move it 
to under noredist profile?

Damoder/

-Original Message-
From: Rajani Karuturi [mailto:rajani.karut...@citrix.com] 
Sent: Wednesday, 9 July 2014 10:45 AM
To: dev@cloudstack.apache.org
Cc: David Nalley; Koushik Das
Subject: Re: Review Request 23192: Adding Readme and run checkbox at the end of 
the installation. Also installing mysql connector

Hi Hugo,
Even in case of windows installer, mysql-connector-java is mentioned in a 
[spec] file. only difference being, it also mentions the download url as 
windows doesn’t have a package repository and doesn’t know where to download 
from.
It will not be part of the installer. The msi only tells where to download the 
mysql connector jar from. It doesn’t include the jar itself.

When the user is installing cloudstack using the msi, the jar will be 
downloaded from the location mentioned.


[spec] https://reviews.apache.org/r/23192/diff/#5

~Rajani



On 08-Jul-2014, at 7:25 pm, Hugo Trippaers 
mailto:h...@trippaers.nl>> wrote:

Rajani,

That is why we renamed nonoss to noredist. It has to do with the policy of the 
Apache Software Foundation regarding compatible licenses [1]. The problem in 
this case is subtle, but there is a difference. The main point in the 
discussion is so-called system dependencies. We know we need java, mysql and 
the mysql-connector-java to be installed before we can install our packages. 
This is what the dependency on mysql-connector-java in the spec file indicates. 
Creating a package containing those source is actually including the items we 
consider is going just a bit further and to a point where we concluded that it 
is not inline with the apache policies. So it is perfectly alright to include a 
popup in the installer that tells the users that he needs to install mysql, 
java etc, but we can’t have an installed in the source that will do that for 
the user as part of the installer.

What David proposes is a the middle ground where we can keep the installer in 
the configured like this in the pom, but it can’t be in that standard build, 
but only in the build that know we can’t redistribute (the noredist build). We 
will never make the artifacts resulting from that build available, but other 
entities can make them available. By specifying noredist on the build command 
we can be reasonably sure that the builder has been informed that distribution 
restrictions might apply on whatever it is he is doing.

Cheers,

Hugo

[1] http://www.apache.org/legal/resolved.html#category-x


On 8 jul. 2014, at 12:57, Rajani Karuturi 
mailto:rajani.karut...@citrix.com>> wrote:

I believe this has nothing to do with nonoss. If I understand it right, nonoss 
modules are required for cloudstack to work with certain 3rd party stuff.

This one is just a helper to create a windows installer. It chose to use a mvn 
command to create the installer instead of shell/bat script. It should work 
with either nonoss or oss modules.
This is very similar to cloud.spec[1] we have which is used to create the rpm 
and which already has mysql-connector-java already listed as required package.

I think the right way would be to create independent git repos for 
deb/rpm/windows installers/packages.

In its current state, I don’t see it any different from other helper installer 
scripts we already have.

[1] 
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=packaging/centos63/cloud.spec;hb=HEAD

~Rajani



On 08-Jul-2014, at 9:56 am, Damoder Reddy 
mailto:damoder.re...@citrix.com>>
 wrote:

Ok,

To clarify the windows MSI will not build in the default profile. I have 
enabled a new profile "buildw" to build windows MSI installer which explicitly 
we need to pass similar to nonoss?

Is that sufficient to make it nonoss or still we need to move it under nonoss 
profile explicitly?

Thanks
Damoder/

-Original Message-
From: David Nalley [mailto:da...@gnsa.us]
Sent: Thursday, 3 July 2014 9:58 PM
To: 
dev@cloudstack.apache.org
Cc: Damoder Reddy; Koushik Das
Subject: Re: Review Request 23192: Adding Readme and run checkbox at the end of 
the installation. Also installing mysql connector

On Thu, Jul 3, 2014 at 12:08 PM, Chip Childers 
mailto:chipchild...@apache.org>>
 wrote:
On Thu, Jul 03, 2014 at 03:14:30PM +, Leo Simons wrote:
It looks like that maven pom on windows _by default_ downloads and installs a 
variety of non-apache-license (and/or non-mit/bsd/variant
license) software. That shouldnąt really happen. The principle is one of łleast 
surprise˛: As a user or developer who does not RTFM, f

Re: [DISCUSS][PROPOSAL] git workflow

2014-07-08 Thread Rajani Karuturi
In my first email, I mentioned a youtube url[1] which is a google tech talk by  
Laura Wingerd [2] of Perforce Software
I recommend watching it as well. (its a 55 min video).

[1] https://www.youtube.com/watch?v=AJ-CpGsCpM0
[2] http://www.perforce.com/blog/author/lwingerd

~Rajani



On 09-Jul-2014, at 3:52 am, Sebastien Goasguen 
mailto:run...@gmail.com>> wrote:

This is also a good read, against cherry-picking (back to Rajani's original 
point):

http://www.draconianoverlord.com/2013/09/07/no-cherry-picking.html

(even wondering if Rohit did not send this to the list already…)

-sebastien



Re: Review Request 23192: Adding Readme and run checkbox at the end of the installation. Also installing mysql connector

2014-07-08 Thread Rajani Karuturi
Hi Hugo,
Even in case of windows installer, mysql-connector-java is mentioned in a 
[spec] file. only difference being, it also mentions the download url as 
windows doesn’t have a package repository and doesn’t know where to download 
from.
It will not be part of the installer. The msi only tells where to download the 
mysql connector jar from. It doesn’t include the jar itself.

When the user is installing cloudstack using the msi, the jar will be 
downloaded from the location mentioned.


[spec] https://reviews.apache.org/r/23192/diff/#5

~Rajani



On 08-Jul-2014, at 7:25 pm, Hugo Trippaers 
mailto:h...@trippaers.nl>> wrote:

Rajani,

That is why we renamed nonoss to noredist. It has to do with the policy of the 
Apache Software Foundation regarding compatible licenses [1]. The problem in 
this case is subtle, but there is a difference. The main point in the 
discussion is so-called system dependencies. We know we need java, mysql and 
the mysql-connector-java to be installed before we can install our packages. 
This is what the dependency on mysql-connector-java in the spec file indicates. 
Creating a package containing those source is actually including the items we 
consider is going just a bit further and to a point where we concluded that it 
is not inline with the apache policies. So it is perfectly alright to include a 
popup in the installer that tells the users that he needs to install mysql, 
java etc, but we can’t have an installed in the source that will do that for 
the user as part of the installer.

What David proposes is a the middle ground where we can keep the installer in 
the configured like this in the pom, but it can’t be in that standard build, 
but only in the build that know we can’t redistribute (the noredist build). We 
will never make the artifacts resulting from that build available, but other 
entities can make them available. By specifying noredist on the build command 
we can be reasonably sure that the builder has been informed that distribution 
restrictions might apply on whatever it is he is doing.

Cheers,

Hugo

[1] http://www.apache.org/legal/resolved.html#category-x


On 8 jul. 2014, at 12:57, Rajani Karuturi 
mailto:rajani.karut...@citrix.com>> wrote:

I believe this has nothing to do with nonoss. If I understand it right, nonoss 
modules are required for cloudstack to work with certain 3rd party stuff.

This one is just a helper to create a windows installer. It chose to use a mvn 
command to create the installer instead of shell/bat script. It should work 
with either nonoss or oss modules.
This is very similar to cloud.spec[1] we have which is used to create the rpm 
and which already has mysql-connector-java already listed as required package.

I think the right way would be to create independent git repos for 
deb/rpm/windows installers/packages.

In its current state, I don’t see it any different from other helper installer 
scripts we already have.

[1] 
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=packaging/centos63/cloud.spec;hb=HEAD

~Rajani



On 08-Jul-2014, at 9:56 am, Damoder Reddy 
mailto:damoder.re...@citrix.com>>
 wrote:

Ok,

To clarify the windows MSI will not build in the default profile. I have 
enabled a new profile "buildw" to build windows MSI installer which explicitly 
we need to pass similar to nonoss?

Is that sufficient to make it nonoss or still we need to move it under nonoss 
profile explicitly?

Thanks
Damoder/

-Original Message-
From: David Nalley [mailto:da...@gnsa.us]
Sent: Thursday, 3 July 2014 9:58 PM
To: 
dev@cloudstack.apache.org
Cc: Damoder Reddy; Koushik Das
Subject: Re: Review Request 23192: Adding Readme and run checkbox at the end of 
the installation. Also installing mysql connector

On Thu, Jul 3, 2014 at 12:08 PM, Chip Childers 
mailto:chipchild...@apache.org>>
 wrote:
On Thu, Jul 03, 2014 at 03:14:30PM +, Leo Simons wrote:
It looks like that maven pom on windows _by default_ downloads and
installs a variety of non-apache-license (and/or non-mit/bsd/variant
license) software. That shouldnąt really happen. The principle is one
of łleast surprise˛: As a user or developer who does not RTFM,
following the default commands/tools/etc, you should end up with a
more-or-less apache-licensed build result (*) that you can
redistribute the result under.

+1


But apache policy is that it is acceptable to provide scripts/build
tools/assistance to help those same users/developers do things that
they want to do. As long as they understand the legal situation they end up in.

I would recommend adding a "nonoss" maven profile that the
developer/user has to explicitly select in order to do those
downloads. As long as that option is described clearly, thatąs then
ok. See

http://svn.apache.org/repos/asf/apr/apr/trunk/README

for an example of how to point out the 

Re: Review Request 23314: Plugin specific code for the Brocade Network Plugin

2014-07-08 Thread Ritu Sabharwal


> On July 8, 2014, 9:29 a.m., Hugo Trippaers wrote:
> > Thanks for make this a separate review, much easier to read.
> > 
> > The licenses are not added to all files and in some files they appear not 
> > to be complete. A good trick to solve this is to include the 
> > license-maven-plugin in the build section. See 
> > plugins/network-elements/nicira-nvp/pom.xml for an example.
> > 
> > Also the plugin doesn't contain any tests. We need unit tests or functional 
> > tests (and preferably both) to validate that this plugin works and keeps on 
> > working in future versions of CloudStack. It would be great if you could 
> > supply unit tests to validate this inner workings of this module and marvin 
> > based integration tests that we can run to see if this work with the 
> > intended hardware.
> > 
> > The last general point is that we would also need documentation on this 
> > plugin so administrators will know how to use this.
> 
> Ritu  Sabharwal wrote:
> Thanks for reviewing the code.
> 
> I have fixed the license in all the files.
> 
> I am working on writing the unit tests for the plugin.
> 
> I am working on providing the documentation on using the plugin.
> 
> I have tested the plugin with the simulator and see the configurations on 
> Brocade switches happening. Currently, I am setting up a real hardware setup 
> with Vmware hypervisor and Brocade switches so test the connectivity between 
> spawned VMs.
> 
> Can I continue writing the unit tests and marvin integration tests and 
> documentation after the July 19 date so that this plugin makes to 4.5 feature 
> freeze date.
> 
> I have updated the diffs with the changes for the license and other 
> comments.

I am planning to include the following in the documentation:
 - Brocade switch setup
 - Connections to the Hypervisor hosts
 - the flow to use the plugin from UI


- Ritu


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


On July 8, 2014, 6:49 p.m., Ritu  Sabharwal wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/23314/
> ---
> 
> (Updated July 8, 2014, 6:49 p.m.)
> 
> 
> Review request for cloudstack.
> 
> 
> Bugs: CLOUDSTACK-6823
> https://issues.apache.org/jira/browse/CLOUDSTACK-6823
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Plugin specific code.
> 
> 
> Diffs
> -
> 
>   plugins/network-elements/brocade-vcs/pom.xml PRE-CREATION 
>   plugins/network-elements/brocade-vcs/resources/BrocadeInterfaceSchema.xsd 
> PRE-CREATION 
>   plugins/network-elements/brocade-vcs/resources/BrocadePortProfileSchema.xsd 
> PRE-CREATION 
>   plugins/network-elements/brocade-vcs/resources/BrocadeShowVcsSchema.xsd 
> PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/resources/META-INF/cloudstack/vcs/module.properties
>  PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/resources/META-INF/cloudstack/vcs/spring-vcs-context.xml
>  PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/src/com/cloud/agent/api/AssociateMacToNetworkAnswer.java
>  PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/src/com/cloud/agent/api/AssociateMacToNetworkCommand.java
>  PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/src/com/cloud/agent/api/CreateNetworkAnswer.java
>  PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/src/com/cloud/agent/api/CreateNetworkCommand.java
>  PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/src/com/cloud/agent/api/DeleteNetworkAnswer.java
>  PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/src/com/cloud/agent/api/DeleteNetworkCommand.java
>  PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/src/com/cloud/agent/api/DisassociateMacFromNetworkAnswer.java
>  PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/src/com/cloud/agent/api/DisassociateMacFromNetworkCommand.java
>  PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/src/com/cloud/agent/api/StartupBrocadeVcsCommand.java
>  PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/src/com/cloud/network/BrocadeVcsNetworkHostMappingVO.java
>  PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/src/com/cloud/network/brocade/BrocadeVcsApi.java
>  PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/src/com/cloud/network/brocade/BrocadeVcsApiException.java
>  PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/src/com/cloud/network/brocade/Cache.java 
> PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/src/com/cloud/network/brocade/CacheManager.java
>  PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/src/com/cloud/network/brocade/Constants.java
>  PRE-CREATI

[Help] Help for setting up Vmware Cluster in CloudStack...

2014-07-08 Thread Ritu Sabharwal
Hi Ilya,

I am trying to add VMWare DC for the first time in CloudStack management server 
and need help in doing so. I am trying to test the Brocade Network Plugin 
functionality. The Jira id is : 
https://issues.apache.org/jira/browse/CLOUDSTACK-6823

I am following the Tutorial: 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Advanced+Network+Tutorial+-+Step+by+Step

My Network setup:


1.   2 ESXi hosts 4.1.0 hosts.

2.   vCenter 5.0

Network layout:

vSwitch0: For Management Network
vSwitch0: for Guest Network

vSwitch0 is assigned 1 Physical Nic. This Nic is connected to Brocade VDX 
switch.


My test includes:

 *   Create an isolated network; verify that the port-profile is created on the 
Brocade switch.
 *   Attach a VM to the network; verify that the VMs MAC address is associated 
with the port profile of the network on the Brocade switch.
 *   Add VMs to the same guest network but on different hosts and verify 
connectivity.
 *   Check the availability of the switch by using the CloudStack API: 
http://:8096/client/api?command=listHosts&type=L2Networking.
 This should list the switch with its availability status.
 *   Delete VMs for an isolated network; verify that the VMs MAC address is 
disassociated with the port profile of the network on the Brocade switch.
 *   Delete the isolated network; verify that the port-profile is deleted from 
the Brocade switch.

I have few questions:

1.   Where do I download the system vm template for vmware. I am using 
master CS codebase, I don't have the script 
/usr/lib64/cloud/common/scripts/storage/secondary/cloud-install-sys-tmplt

2.   Since I am testing L2 connectivity b/w VMs using Brocade switches by 
configuring the VLANs( by creating port-profiles) for the network on the 
switches, do I need to assign a IP range for Public network and storage network?

3.   In the tutorial, there are 2 portgroups for VMs on Managemnt Network 
and Development Network? What are these 2 types of VMs?

4.   For primary storage, do I give the datastore attached to the 
hypervisor hosts?


Any help is appreciated.

Thanks & Regards,
Ritu S.


RE: [HELP] How to build CS to enable VMware support in CloudStack..

2014-07-08 Thread Ritu Sabharwal
Thanks Hugo, I was able to build Cloudstack.

I have some more questions on Vmware cluster setup for CloudStack. Sent that in 
a  separate email.

Thanks & Regards,
Ritu S.

-Original Message-
From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers
Sent: Tuesday, July 08, 2014 1:52 PM
To: dev@cloudstack.apache.org
Subject: Re: [HELP] How to build CS to enable VMware support in CloudStack..

Ritu.

If you wan to build only the vmware dependencies , just enable the profile 
vmware

So the command should be: mvm -P vmware,systemvm install.

That would build only the vmware dependencies. Make sure the dependencies are 
in the deps folder and added to the local maven repository. The commands to do 
that are in the install-non-oss.sh script in the deps directory.

The noredist flag is just a convenience flag that enables all plugins with 
distribution restrictions, no need to use it to just build vmware support.

Cheers,

Hugo


On 8 jul. 2014, at 22:03, Ritu Sabharwal  wrote:

> Hi,
> 
> I am trying to add VMWare DC for the first time in CloudStack management 
> server and need help in doing so. I downloaded the vim25.jar and apputils.jar 
> from VSphere Management SDK and copied them to deps folder.
> 
> When I a tryingto build cloudStack from source using the command mvn install  
> -Dnoredist , it is failing and looking for dependencies for NetApp Plugin.
> 
> [ERROR] Failed to execute goal on project cloud-plugin-netapp: Could not 
> resolve dependencies for project 
> org.apache.cloudstack:cloud-plugin-netapp:jar:4.5.0-SNAPSHOT: Failure to find 
> com.cloud.com.netapp:manageontap:jar:4.0 in 
> http://repo.maven.apache.org/maven2 was cached in the local repository, 
> resolution will not be reattempted until the update interval of central has 
> elapsed or updates are forced -> [Help 1]
> 
> 
> How can I just build for enabling VMware support and no other opensource 
> dependency?
> 
> Help in this regard is appreciated.
> 
> Thanks & Regards,
> Ritu S.
> 



Re: [DISCUSS][PROPOSAL] git workflow

2014-07-08 Thread Sebastien Goasguen

On Jul 8, 2014, at 5:40 PM, Sebastien Goasguen  wrote:

> 
> On Jul 8, 2014, at 4:13 PM, Rohit Yadav  wrote:
> 
>> Hi Chip,
>> 
>> Chip Childers wrote:
>>> Let me try that again, this time with content!
>>> 
>>> I've dropped private@, since this doesn't belong there.
>>> 
>>> On Tue, Jul 8, 2014 at 3:30 PM, Rohit Yadav  
>>> wrote:
 Hi,
 
 
 Daan Hoogland wrote:
> I do not see why the PMC should drive defining the
> standard. This is something that should be carried and cherished by
> all developers.
 
 In my experience when something is everyone's responsibility, eventually
 no one is responsible for it.
 
 I think the PMC should drive it because IMHO the PMC comprises of our
 project management folks who have decision making powers and are
 officially responsible for the project as recognized by the ASF [1].
 
 Therefore, I'm requesting our PMC to come up with a convention along
 with committers/developers on this issue and enforce it using some
 tooling etc.
 
 [1] http://www.apache.org/dev/pmc.htm
>>> 
>>> Everyone here is part of the community, and everyone deserves a say in
>>> how this is done.  If you're suggesting that PMC members should be
>>> involved in this discussion, agreed!  But should should committers and
>>> contributors!
>> 
>> Thanks Chip -- I'm with you on this.
>> 
>> I'm trying to say is -- shared responsibility is tricky, in most cases
>> no one would be responsible eventually, *unless*…
>> 
> 
> That's really a bar discussion :).
> 
> At Apache we govern by consensus. Any technical decisions (especially one 
> like this), needs to be agreed upon by the community as a whole.
> The agreement will happen through discussion on the dev list. 
> 
> For us to change, we need people (who believe that what we are doing 
> currently is wrong) to step up,  explain the issues and make a proposal.
> Then by iterating and discussing the proposal we will reach consensus.
> 
> At least that's how I view things.
> 
> I re-opened the thread because no-one picked it up, and as you say it's a 
> shame.
> 
> IMHO our development methodology is totally broken and this is best shown by 
> our inability to release on-time.
> 
> I am interested to take on the 4.5 or 4.6 RM duties if we agree to change our 
> workflow significantly.
> 
> Personally, I would like to freeze master and make the development happen 
> somewhere else.
> 
> Basically master should be our releasable branch and once we merge things in 
> master we end up with working releases.
> I would go further and actually propose that only the RM gets to merge in 
> master.
> 
> I think if we started from a working release tag it would mean that we would 
> never miss a release on time. Only the scope of the features would be 
> affected.
> 
> Until we have a proper review/test/commit CI setup we should not allow 
> committing to master.
> 
> I am still thinking through this, but once I have a clear idea, I plan to 
> make a proposal by writing a new workflow on the wiki.
> 
> ideas, thoughts, flames ?
> 
> -sebastien
> 

This is also a good read, against cherry-picking (back to Rajani's original 
point):

http://www.draconianoverlord.com/2013/09/07/no-cherry-picking.html

(even wondering if Rohit did not send this to the list already…)

-sebastien


> 
>> Regards,
>> Rohit Yadav
>> Software Architect, ShapeBlue
>> M. +91 88 262 30892 | rohit.ya...@shapeblue.com
>> Blog: bhaisaab.org | Twitter: @_bhaisaab
>> Find out more about ShapeBlue and our range of CloudStack related services
>> 
>> IaaS Cloud Design & Build
>> CSForge – rapid IaaS deployment framework
>> CloudStack Consulting
>> CloudStack Infrastructure 
>> Support
>> CloudStack Bootcamp Training 
>> Courses
>> 
>> This email and any attachments to it may be confidential and are intended 
>> solely for the use of the individual to whom it is addressed. Any views or 
>> opinions expressed are solely those of the author and do not necessarily 
>> represent those of Shape Blue Ltd or related companies. If you are not the 
>> intended recipient of this email, you must neither take any action based 
>> upon its contents, nor copy or show it to anyone. Please contact the sender 
>> if you believe you have received this email in error. Shape Blue Ltd is a 
>> company incorporated in England & Wales. ShapeBlue Services India LLP is a 
>> company incorporated in India and is operated under license from Shape Blue 
>> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil 
>> and is operated under license from Shape Blue Ltd. ShapeBlue is a registered 
>> trademark.
> 



Re: [DISCUSS][PROPOSAL] git workflow

2014-07-08 Thread Sebastien Goasguen

On Jul 8, 2014, at 2:20 PM, Nate Gordon  wrote:

> As someone who has worked with a number of different version control
> systems (and have far more love for git than any other), I'm curious as to
> why we would want to fight what I've always seen as the core feature of
> git. Branching and merging. The gitflow model is incredibly useful for
> keeping track of a number of different development paths concurrently.
> Branches remained organized and have a clear destination and workflow that
> they need to go through as part of the merging process. We use it
> internally (on a much smaller team) with great success. And with the
> difficulties I've seen on the mailing list around the -forward branches and
> cherry-picking,I'm curious as to why this is the preferred method.

I don't think it's the preferred method.
I see it as 'the method currently used'.

I think we need to change.

> From
> everything I've read about git and cherry-picking, it is a copy of the
> commit, not a reference to the original commit. This makes it hard to track
> down an individual change to find the original source.
> 
> Thanks,
> 
> -Nate
> 
> 
> On Tue, Jul 8, 2014 at 11:04 AM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
> 
>> Thanks for bringing this up again, Sebastien.
>> 
>> I've had http://nvie.com/posts/a-successful-git-branching-model/ up in
>> Chrome since you sent that link and been reading through it a bit here and
>> there, but have just been too busy as of late to give it a bunch of
>> thought.
>> 
>> I agree, though, that we should really think about moving to another model
>> of using Git as it is not un-common for master to be broken, which leads to
>> a lot of lost development time for many people.
>> 
>> 
>> On Mon, Jun 30, 2014 at 4:09 PM, Sebastien Goasguen 
>> wrote:
>> 
>>> I would like to re-start this discussion.
>>> 
>>> Rajani made some good points and someone mentioned Gitflow:
>>> 
>>> http://nvie.com/posts/a-successful-git-branching-model/
>>> 
>>> Thinking about our release procedure, we clearly need more tests and a
>> CI.
>>> However it looks like this is going to take some time.
>>> 
>>> In the meantime I think there is nothing preventing us from agreeing to
>>> 'git practices', we don't need tests or new infra, we just need to agree
>> on
>>> the git workflow.
>>> 
>>> Right now Master is really a development branch, we should make it a
>>> stable branch for production with very few commits.
>>> This does not mean that we would release less, in contrary this would
>>> ensure that a commit to master means it's a production release.
>>> 
>>> In addition gitflow [1] does not do cherry-picks (gets back to Rajani's
>>> point) everything is based on merges.
>>> 
>>> I am of the opinion that git flow provides a nice process. It basically
>>> freezes master. Development happens in a 'develop' branch, releases
>>> branches are branched off of that and merged into master and back into
>>> develop….etc
>>> 
>>> Please read [1] it's a good read.
>>> 
>>> And let's discuss,
>>> 
>>> [1] http://nvie.com/posts/a-successful-git-branching-model/
>>> 
>>> -Sebastien
>>> 
>>> On Jun 2, 2014, at 11:58 PM, Rajani Karuturi >> 
>>> wrote:
>>> 
 There is also the problem of cherry-picking.
 As a contributor, I always endup creating multiple patches for each
>>> branch as they don’t cleanly apply on the upward branches. which means
>>> distinct commits for each branch and I don’t easily know which all
>> branches
>>> my commit exists unless I do grep.
 if we follow merging strategy properly, apart from the first merge of
>>> the branch, everything else on top of it should be a painless merge.
 
 
 
 ~Rajani
 
 
 
 On 02-Jun-2014, at 10:51 pm, Marcus  wrote:
 
> I think many of the bullet points are what we are currently doing
> (guidelines for commit comments, feature branches need to stay in sync
>>> with
> master, no back-merging). I also think that much of what we do now is
>>> done
> the way it is simply because there *are* vast changes between
>> versions.
> Classes are getting shuffled around and changed all the time. If its
> feasible to merge branch fixes to master, that's fine, but some quick
>>> tests
> seem to indicate that this will be messy getting started.
> 
> That leaves us with how we do releases. I'm fine with having single
> branches for major releases(4.3) and tagging the commits where each
> incremental release (4.3.x) is done. I'm trying to remember why we
>> went
> with the -forward, I'm sure it's in the mailing list somewhere, but
>> one
>>> of
> the nice things it provides is the ability for the release manager to
> control what changes are made during code freeze while giving people a
> place to stage fixes (though admittedly this is not always followed).
> Without -forward, would the flow be for each dev to have their own
>> repo
>>> and
> issue pull requests for bugfix

Re: [DISCUSS][PROPOSAL] git workflow

2014-07-08 Thread Sebastien Goasguen

On Jul 8, 2014, at 4:13 PM, Rohit Yadav  wrote:

> Hi Chip,
> 
> Chip Childers wrote:
>> Let me try that again, this time with content!
>> 
>> I've dropped private@, since this doesn't belong there.
>> 
>> On Tue, Jul 8, 2014 at 3:30 PM, Rohit Yadav  
>> wrote:
>>> Hi,
>>> 
>>> 
>>> Daan Hoogland wrote:
 I do not see why the PMC should drive defining the
 standard. This is something that should be carried and cherished by
 all developers.
>>> 
>>> In my experience when something is everyone's responsibility, eventually
>>> no one is responsible for it.
>>> 
>>> I think the PMC should drive it because IMHO the PMC comprises of our
>>> project management folks who have decision making powers and are
>>> officially responsible for the project as recognized by the ASF [1].
>>> 
>>> Therefore, I'm requesting our PMC to come up with a convention along
>>> with committers/developers on this issue and enforce it using some
>>> tooling etc.
>>> 
>>> [1] http://www.apache.org/dev/pmc.htm
>> 
>> Everyone here is part of the community, and everyone deserves a say in
>> how this is done.  If you're suggesting that PMC members should be
>> involved in this discussion, agreed!  But should should committers and
>> contributors!
> 
> Thanks Chip -- I'm with you on this.
> 
> I'm trying to say is -- shared responsibility is tricky, in most cases
> no one would be responsible eventually, *unless*…
> 

That's really a bar discussion :).

At Apache we govern by consensus. Any technical decisions (especially one like 
this), needs to be agreed upon by the community as a whole.
The agreement will happen through discussion on the dev list. 

For us to change, we need people (who believe that what we are doing currently 
is wrong) to step up,  explain the issues and make a proposal.
Then by iterating and discussing the proposal we will reach consensus.

At least that's how I view things.

I re-opened the thread because no-one picked it up, and as you say it's a shame.

IMHO our development methodology is totally broken and this is best shown by 
our inability to release on-time.

I am interested to take on the 4.5 or 4.6 RM duties if we agree to change our 
workflow significantly.

Personally, I would like to freeze master and make the development happen 
somewhere else.

Basically master should be our releasable branch and once we merge things in 
master we end up with working releases.
I would go further and actually propose that only the RM gets to merge in 
master.

I think if we started from a working release tag it would mean that we would 
never miss a release on time. Only the scope of the features would be affected.

Until we have a proper review/test/commit CI setup we should not allow 
committing to master.

I am still thinking through this, but once I have a clear idea, I plan to make 
a proposal by writing a new workflow on the wiki.

ideas, thoughts, flames ?

-sebastien


> Regards,
> Rohit Yadav
> Software Architect, ShapeBlue
> M. +91 88 262 30892 | rohit.ya...@shapeblue.com
> Blog: bhaisaab.org | Twitter: @_bhaisaab
> Find out more about ShapeBlue and our range of CloudStack related services
> 
> IaaS Cloud Design & Build
> CSForge – rapid IaaS deployment framework
> CloudStack Consulting
> CloudStack Infrastructure 
> Support
> CloudStack Bootcamp Training 
> Courses
> 
> This email and any attachments to it may be confidential and are intended 
> solely for the use of the individual to whom it is addressed. Any views or 
> opinions expressed are solely those of the author and do not necessarily 
> represent those of Shape Blue Ltd or related companies. If you are not the 
> intended recipient of this email, you must neither take any action based upon 
> its contents, nor copy or show it to anyone. Please contact the sender if you 
> believe you have received this email in error. Shape Blue Ltd is a company 
> incorporated in England & Wales. ShapeBlue Services India LLP is a company 
> incorporated in India and is operated under license from Shape Blue Ltd. 
> Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
> operated under license from Shape Blue Ltd. ShapeBlue is a registered 
> trademark.



[CASE STUDY] GreenQloud Accelerates the Market Adoption of a Cleaner Cloud and Offers a Full Cloud Infrastructure Stack Built on Apache CloudStack

2014-07-08 Thread Karen Vuong
Hi all,



A new case study has been published, titled, GreenQloud Accelerates the
Market Adoption of a Cleaner Cloud and Offers a Full Cloud Infrastructure
Stack Built on Apache CloudStack.



Click-to-tweet - http://ctt.ec/cd29Q: [CASE STUDY] Built on #CloudStack,
#GreenQloud accelerates the market adoption of a cleaner cloud -
clds.co/1oh8HPv #opensource #cloud



Thanks,



Karen


Re: Review Request 23098: Updated Marvin code to support more properties.

2014-07-08 Thread Mike Tutkowski

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

Ship it!


Ship It!

- Mike Tutkowski


On July 8, 2014, 2:51 p.m., Vania Xu wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/23098/
> ---
> 
> (Updated July 8, 2014, 2:51 p.m.)
> 
> 
> Review request for cloudstack and Mike Tutkowski.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Building automated integration tests that needed additional properties added 
> to Marvin code. 
> 
> 
> Diffs
> -
> 
>   tools/marvin/marvin/lib/base.py 2ef6f82 
> 
> Diff: https://reviews.apache.org/r/23098/diff/
> 
> 
> Testing
> ---
> 
> Ran new code against my integration tests, and it was successful. 
> 
> 
> Thanks,
> 
> Vania Xu
> 
>



Re: [HELP] How to build CS to enable VMware support in CloudStack..

2014-07-08 Thread Hugo Trippaers

On 8 jul. 2014, at 22:35, Amogh Vasekar  wrote:

> Hi,
> 
> Unfortunately, you need to download and install the manageontop jar too
> 

You can enable every noredist plugin by itself, the noredist flag is just a 
handy shortcut to enable all of them for developers.

> Thanks,
> Amogh
> 
> On 7/8/14 1:03 PM, "Ritu Sabharwal"  wrote:
> 
>> Hi,
>> 
>> I am trying to add VMWare DC for the first time in CloudStack management
>> server and need help in doing so. I downloaded the vim25.jar and
>> apputils.jar from VSphere Management SDK and copied them to deps folder.
>> 
>> When I a tryingto build cloudStack from source using the command mvn
>> install  -Dnoredist , it is failing and looking for dependencies for
>> NetApp Plugin.
>> 
>> [ERROR] Failed to execute goal on project cloud-plugin-netapp: Could not
>> resolve dependencies for project
>> org.apache.cloudstack:cloud-plugin-netapp:jar:4.5.0-SNAPSHOT: Failure to
>> find com.cloud.com.netapp:manageontap:jar:4.0 in
>> http://repo.maven.apache.org/maven2 was cached in the local repository,
>> resolution will not be reattempted until the update interval of central
>> has elapsed or updates are forced -> [Help 1]
>> 
>> 
>> How can I just build for enabling VMware support and no other opensource
>> dependency?
>> 
>> Help in this regard is appreciated.
>> 
>> Thanks & Regards,
>> Ritu S.
>> 
> 



Re: [HELP] How to build CS to enable VMware support in CloudStack..

2014-07-08 Thread Hugo Trippaers
Ritu.

If you wan to build only the vmware dependencies , just enable the profile 
vmware

So the command should be: mvm -P vmware,systemvm install.

That would build only the vmware dependencies. Make sure the dependencies are 
in the deps folder and added to the local maven repository. The commands to do 
that are in the install-non-oss.sh script in the deps directory.

The noredist flag is just a convenience flag that enables all plugins with 
distribution restrictions, no need to use it to just build vmware support.

Cheers,

Hugo


On 8 jul. 2014, at 22:03, Ritu Sabharwal  wrote:

> Hi,
> 
> I am trying to add VMWare DC for the first time in CloudStack management 
> server and need help in doing so. I downloaded the vim25.jar and apputils.jar 
> from VSphere Management SDK and copied them to deps folder.
> 
> When I a tryingto build cloudStack from source using the command mvn install  
> -Dnoredist , it is failing and looking for dependencies for NetApp Plugin.
> 
> [ERROR] Failed to execute goal on project cloud-plugin-netapp: Could not 
> resolve dependencies for project 
> org.apache.cloudstack:cloud-plugin-netapp:jar:4.5.0-SNAPSHOT: Failure to find 
> com.cloud.com.netapp:manageontap:jar:4.0 in 
> http://repo.maven.apache.org/maven2 was cached in the local repository, 
> resolution will not be reattempted until the update interval of central has 
> elapsed or updates are forced -> [Help 1]
> 
> 
> How can I just build for enabling VMware support and no other opensource 
> dependency?
> 
> Help in this regard is appreciated.
> 
> Thanks & Regards,
> Ritu S.
> 



Re: Review Request 23098: Updated Marvin code to support more properties.

2014-07-08 Thread Vania Xu

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

(Updated July 8, 2014, 8:51 p.m.)


Review request for cloudstack and Mike Tutkowski.


Changes
---

Here's the updated diff. 


Repository: cloudstack-git


Description
---

Building automated integration tests that needed additional properties added to 
Marvin code. 


Diffs (updated)
-

  tools/marvin/marvin/lib/base.py 2ef6f82 

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


Testing
---

Ran new code against my integration tests, and it was successful. 


Thanks,

Vania Xu



Re: Review Request 23098: Updated Marvin code to support more properties.

2014-07-08 Thread Vania Xu


> On July 8, 2014, 8:50 p.m., Mike Tutkowski wrote:
> > It looks like the base.py file has been relocated for the 4.5 release.
> > 
> > Can you please regenerate your diff using the 4.5 branch?
> > 
> > Thanks!

I'll go ahead and upload a new diff. 


- Vania


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


On June 26, 2014, 11:13 p.m., Vania Xu wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/23098/
> ---
> 
> (Updated June 26, 2014, 11:13 p.m.)
> 
> 
> Review request for cloudstack and Mike Tutkowski.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Building automated integration tests that needed additional properties added 
> to Marvin code. 
> 
> 
> Diffs
> -
> 
>   tools/marvin/marvin/integration/lib/base.py 95b7fe9 
> 
> Diff: https://reviews.apache.org/r/23098/diff/
> 
> 
> Testing
> ---
> 
> Ran new code against my integration tests, and it was successful. 
> 
> 
> Thanks,
> 
> Vania Xu
> 
>



Re: Review Request 23098: Updated Marvin code to support more properties.

2014-07-08 Thread Mike Tutkowski

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


It looks like the base.py file has been relocated for the 4.5 release.

Can you please regenerate your diff using the 4.5 branch?

Thanks!

- Mike Tutkowski


On June 26, 2014, 5:13 p.m., Vania Xu wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/23098/
> ---
> 
> (Updated June 26, 2014, 5:13 p.m.)
> 
> 
> Review request for cloudstack and Mike Tutkowski.
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Building automated integration tests that needed additional properties added 
> to Marvin code. 
> 
> 
> Diffs
> -
> 
>   tools/marvin/marvin/integration/lib/base.py 95b7fe9 
> 
> Diff: https://reviews.apache.org/r/23098/diff/
> 
> 
> Testing
> ---
> 
> Ran new code against my integration tests, and it was successful. 
> 
> 
> Thanks,
> 
> Vania Xu
> 
>



Re: [HELP] How to build CS to enable VMware support in CloudStack..

2014-07-08 Thread Amogh Vasekar
Hi,

Unfortunately, you need to download and install the manageontop jar too

Thanks,
Amogh

On 7/8/14 1:03 PM, "Ritu Sabharwal"  wrote:

>Hi,
>
>I am trying to add VMWare DC for the first time in CloudStack management
>server and need help in doing so. I downloaded the vim25.jar and
>apputils.jar from VSphere Management SDK and copied them to deps folder.
>
>When I a tryingto build cloudStack from source using the command mvn
>install  -Dnoredist , it is failing and looking for dependencies for
>NetApp Plugin.
>
>[ERROR] Failed to execute goal on project cloud-plugin-netapp: Could not
>resolve dependencies for project
>org.apache.cloudstack:cloud-plugin-netapp:jar:4.5.0-SNAPSHOT: Failure to
>find com.cloud.com.netapp:manageontap:jar:4.0 in
>http://repo.maven.apache.org/maven2 was cached in the local repository,
>resolution will not be reattempted until the update interval of central
>has elapsed or updates are forced -> [Help 1]
>
>
>How can I just build for enabling VMware support and no other opensource
>dependency?
>
>Help in this regard is appreciated.
>
>Thanks & Regards,
>Ritu S.
>



Re: [HELP] How to build CS to enable VMware support in CloudStack..

2014-07-08 Thread Mike Tutkowski
Check out the Dependencies instructions here:

https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack


On Tue, Jul 8, 2014 at 2:03 PM, Ritu Sabharwal  wrote:

> Hi,
>
> I am trying to add VMWare DC for the first time in CloudStack management
> server and need help in doing so. I downloaded the vim25.jar and
> apputils.jar from VSphere Management SDK and copied them to deps folder.
>
> When I a tryingto build cloudStack from source using the command mvn
> install  -Dnoredist , it is failing and looking for dependencies for NetApp
> Plugin.
>
> [ERROR] Failed to execute goal on project cloud-plugin-netapp: Could not
> resolve dependencies for project
> org.apache.cloudstack:cloud-plugin-netapp:jar:4.5.0-SNAPSHOT: Failure to
> find com.cloud.com.netapp:manageontap:jar:4.0 in
> http://repo.maven.apache.org/maven2 was cached in the local repository,
> resolution will not be reattempted until the update interval of central has
> elapsed or updates are forced -> [Help 1]
>
>
> How can I just build for enabling VMware support and no other opensource
> dependency?
>
> Help in this regard is appreciated.
>
> Thanks & Regards,
> Ritu S.
>
>


-- 
*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: [HELP] How to build CS to enable VMware support in CloudStack..

2014-07-08 Thread Mike Tutkowski
Here:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack#HowtobuildCloudStack-Dependencies


On Tue, Jul 8, 2014 at 2:16 PM, Mike Tutkowski  wrote:

> Check out the Dependencies instructions here:
>
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack
>
>
> On Tue, Jul 8, 2014 at 2:03 PM, Ritu Sabharwal 
> wrote:
>
>> Hi,
>>
>> I am trying to add VMWare DC for the first time in CloudStack management
>> server and need help in doing so. I downloaded the vim25.jar and
>> apputils.jar from VSphere Management SDK and copied them to deps folder.
>>
>> When I a tryingto build cloudStack from source using the command mvn
>> install  -Dnoredist , it is failing and looking for dependencies for NetApp
>> Plugin.
>>
>> [ERROR] Failed to execute goal on project cloud-plugin-netapp: Could not
>> resolve dependencies for project
>> org.apache.cloudstack:cloud-plugin-netapp:jar:4.5.0-SNAPSHOT: Failure to
>> find com.cloud.com.netapp:manageontap:jar:4.0 in
>> http://repo.maven.apache.org/maven2 was cached in the local repository,
>> resolution will not be reattempted until the update interval of central has
>> elapsed or updates are forced -> [Help 1]
>>
>>
>> How can I just build for enabling VMware support and no other opensource
>> dependency?
>>
>> Help in this regard is appreciated.
>>
>> Thanks & Regards,
>> Ritu S.
>>
>>
>
>
> --
> *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: [DISCUSS][PROPOSAL] git workflow

2014-07-08 Thread Rohit Yadav

Hi Chip,

Chip Childers wrote:

Let me try that again, this time with content!

I've dropped private@, since this doesn't belong there.

On Tue, Jul 8, 2014 at 3:30 PM, Rohit Yadav  wrote:

Hi,


Daan Hoogland wrote:

I do not see why the PMC should drive defining the
standard. This is something that should be carried and cherished by
all developers.


In my experience when something is everyone's responsibility, eventually
no one is responsible for it.

I think the PMC should drive it because IMHO the PMC comprises of our
project management folks who have decision making powers and are
officially responsible for the project as recognized by the ASF [1].

Therefore, I'm requesting our PMC to come up with a convention along
with committers/developers on this issue and enforce it using some
tooling etc.

[1] http://www.apache.org/dev/pmc.htm


Everyone here is part of the community, and everyone deserves a say in
how this is done.  If you're suggesting that PMC members should be
involved in this discussion, agreed!  But should should committers and
contributors!


Thanks Chip -- I'm with you on this.

I'm trying to say is -- shared responsibility is tricky, in most cases
no one would be responsible eventually, *unless*...

Regards,
Rohit Yadav
Software Architect, ShapeBlue
M. +91 88 262 30892 | rohit.ya...@shapeblue.com
Blog: bhaisaab.org | Twitter: @_bhaisaab
Find out more about ShapeBlue and our range of CloudStack related services

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

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


RE: Timeout error while brining up VM console from UI for testing Brocade Network Plugin: CLOUDSTACK-6823

2014-07-08 Thread Ritu Sabharwal
Thanks Amogh for the reply.

So for testing the ping across VMs , I need to setup real hardware. I am trying 
to add a VMware Cluster with ESXi hosts connected to Brocade VDX switches.

I am facing issues in setting up the VMWare support in CS.

I downloaded the vim25.jar and apputils.jar from VSphere Management SDK and 
copied them to deps folder.

When I am trying to build cloudStack from source using the command mvn install  
-Dnoredist , it is failing and looking for dependencies for NetApp Plugin.

[ERROR] Failed to execute goal on project cloud-plugin-netapp: Could not 
resolve dependencies for project 
org.apache.cloudstack:cloud-plugin-netapp:jar:4.5.0-SNAPSHOT: Failure to find 
com.cloud.com.netapp:manageontap:jar:4.0 in http://repo.maven.apache.org/maven2 
was cached in the local repository, resolution will not be reattempted until 
the update interval of central has elapsed or updates are forced -> [Help 1]

How can I just build for enabling VMware support and no other opensource 
dependency?

Thanks & Regards,
Ritu S.

-Original Message-
From: Amogh Vasekar [mailto:amogh.vase...@citrix.com] 
Sent: Tuesday, July 08, 2014 11:22 AM
To: dev@cloudstack.apache.org; Hugo Trippaers
Subject: Re: Timeout error while brining up VM console from UI for testing 
Brocade Network Plugin: CLOUDSTACK-6823

Hi,

AFAIK, since the simulator does not actually have any H/W or real VM, I don't 
think console access is available.

Thanks,
Amogh

On 7/7/14 4:00 PM, "Ritu Sabharwal"  wrote:

>Hi,
>
>I have tested the plugin functionality with the Simulator by creating 
>the datacenter with the marvin script and configuring the Brocade VDX 
>switches.
>
>The Brocade VDX switches are configured with the port-profiles and 
>interfaces at appropriate lifecycles of VMs.
>
>I can see the VMs coming up and running. I need to bring up the console 
>for the VMs to test the ping across the VMs.
>
>In the CloudStack UI, when I click the console button for a VM, I don't 
>get the console but see a timeout message.
>
>Thanks & Regards,
>Ritu S.



[HELP] How to build CS to enable VMware support in CloudStack..

2014-07-08 Thread Ritu Sabharwal
Hi,

I am trying to add VMWare DC for the first time in CloudStack management server 
and need help in doing so. I downloaded the vim25.jar and apputils.jar from 
VSphere Management SDK and copied them to deps folder.

When I a tryingto build cloudStack from source using the command mvn install  
-Dnoredist , it is failing and looking for dependencies for NetApp Plugin.

[ERROR] Failed to execute goal on project cloud-plugin-netapp: Could not 
resolve dependencies for project 
org.apache.cloudstack:cloud-plugin-netapp:jar:4.5.0-SNAPSHOT: Failure to find 
com.cloud.com.netapp:manageontap:jar:4.0 in http://repo.maven.apache.org/maven2 
was cached in the local repository, resolution will not be reattempted until 
the update interval of central has elapsed or updates are forced -> [Help 1]


How can I just build for enabling VMware support and no other opensource 
dependency?

Help in this regard is appreciated.

Thanks & Regards,
Ritu S.



Re: [DISCUSS][PROPOSAL] git workflow

2014-07-08 Thread Chip Childers
Let me try that again, this time with content!

I've dropped private@, since this doesn't belong there.

On Tue, Jul 8, 2014 at 3:30 PM, Rohit Yadav  wrote:
> Hi,
>
>
> Daan Hoogland wrote:
>>
>> I do not see why the PMC should drive defining the
>> standard. This is something that should be carried and cherished by
>> all developers.
>
>
> In my experience when something is everyone's responsibility, eventually
> no one is responsible for it.
>
> I think the PMC should drive it because IMHO the PMC comprises of our
> project management folks who have decision making powers and are
> officially responsible for the project as recognized by the ASF [1].
>
> Therefore, I'm requesting our PMC to come up with a convention along
> with committers/developers on this issue and enforce it using some
> tooling etc.
>
> [1] http://www.apache.org/dev/pmc.htm

Everyone here is part of the community, and everyone deserves a say in
how this is done.  If you're suggesting that PMC members should be
involved in this discussion, agreed!  But should should committers and
contributors!


Re: [DISCUSS][PROPOSAL] git workflow

2014-07-08 Thread Chip Childers
On Tue, Jul 8, 2014 at 3:30 PM, Rohit Yadav  wrote:
> Hi,
>
>
> Daan Hoogland wrote:
>>
>> I do not see why the PMC should drive defining the
>> standard. This is something that should be carried and cherished by
>> all developers.
>
>
> In my experience when something is everyone's responsibility, eventually
> no one is responsible for it.
>
> I think the PMC should drive it because IMHO the PMC comprises of our
> project management folks who have decision making powers and are
> officially responsible for the project as recognized by the ASF [1].
>
> Therefore, I'm requesting our PMC to come up with a convention along
> with committers/developers on this issue and enforce it using some
> tooling etc.
>
> [1] http://www.apache.org/dev/pmc.htm
>
> Regards,
> Rohit Yadav
> Software Architect, ShapeBlue
> M. +91 88 262 30892 | rohit.ya...@shapeblue.com
> Blog: bhaisaab.org | Twitter: @_bhaisaab
> Find out more about ShapeBlue and our range of CloudStack related services
>
> IaaS Cloud Design &
> Build
> CSForge – rapid IaaS deployment framework
> CloudStack Consulting
> CloudStack Infrastructure
> Support
> CloudStack Bootcamp Training
> Courses
>
> This email and any attachments to it may be confidential and are intended
> solely for the use of the individual to whom it is addressed. Any views or
> opinions expressed are solely those of the author and do not necessarily
> represent those of Shape Blue Ltd or related companies. If you are not the
> intended recipient of this email, you must neither take any action based
> upon its contents, nor copy or show it to anyone. Please contact the sender
> if you believe you have received this email in error. Shape Blue Ltd is a
> company incorporated in England & Wales. ShapeBlue Services India LLP is a
> company incorporated in India and is operated under license from Shape Blue
> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil
> and is operated under license from Shape Blue Ltd. ShapeBlue is a registered
> trademark.


Re: [DISCUSS][PROPOSAL] git workflow

2014-07-08 Thread Rohit Yadav

Hi,

Daan Hoogland wrote:

I do not see why the PMC should drive defining the
standard. This is something that should be carried and cherished by
all developers.


In my experience when something is everyone's responsibility, eventually
no one is responsible for it.

I think the PMC should drive it because IMHO the PMC comprises of our
project management folks who have decision making powers and are
officially responsible for the project as recognized by the ASF [1].

Therefore, I'm requesting our PMC to come up with a convention along
with committers/developers on this issue and enforce it using some
tooling etc.

[1] http://www.apache.org/dev/pmc.htm

Regards,
Rohit Yadav
Software Architect, ShapeBlue
M. +91 88 262 30892 | rohit.ya...@shapeblue.com
Blog: bhaisaab.org | Twitter: @_bhaisaab
Find out more about ShapeBlue and our range of CloudStack related services

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

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


Re: Testing a Cloudstack Virtual Router (SystemVM).

2014-07-08 Thread Rohit Yadav

Hi,

Karl Harris wrote:


Since cloud-early-config.sh is "hypervisor aware", at least for those that

do not populate /proc/cmdline directly,  did you test each hypervisor
manually?


Unfortunately yes, I used to do it only for Xen and KVM only.

Regards.



Regards.



Thanks,

Karl

  Find out more about ShapeBlue and our range of CloudStack related

services

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

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






--
Rohit Yadav
Software Architect, ShapeBlue
M. +91 88 262 30892 | rohit.ya...@shapeblue.com
Blog: bhaisaab.org | Twitter: @_bhaisaab
Find out more about ShapeBlue and our range of CloudStack related services

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

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


Re: Review Request 23282: CLOUDSTACK-6845 : First Code drop for NuageVsp Network plugin

2014-07-08 Thread Suresh Ramamurthy
Hi Hugo,

Thanks for reviewing NuageVsp plugin and supporting us.

I have update the comments with my response.

Thanks,
Suresh


On Tue, Jul 8, 2014 at 3:07 AM, Hugo Trippaers <
htrippa...@schubergphilis.com> wrote:

>This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/23282/
>
> Hey Suresh,
>
> Great to see this review, happy to help integrate the NuageVsp code into 
> CloudStack. I did an initial review an put my first feedback in the line 
> comments. I haven't tested functionality or tried to apply the patch yet, but 
> will do that after you had a chance to review these comments.
>
> Cheers,
>
> Hugo
>
>
>client/tomcatconf/log4j-cloud.xml.in
>  
> (Diff
> revision 1)
>
> 66
>
> class="org.apache.log4j.rolling.RollingFileAppender">
>
>   Why do you introduce a new logfile specific for Nuage? Isn't is easier for 
> admins if all cloudstack related messages appear in the already existing 
> logfile that admins are familiar with?
>
>
>
> plugins/network-elements/nuage-vsp/resources/META-INF/cloudstack/vsp/vsp-defaults.ini
>  (Diff
> revision 1)
>
> 1
>
> #This property file contains the default values to be set for the entities 
> that are
>
>   Missing Apache License Header
>
>
>
> plugins/network-elements/nuage-vsp/resources/META-INF/cloudstack/vsp/vsp-defaults.ini
>  (Diff
> revision 1)
>
> 4
>
> noOfSyncThreads=5
>
>   Why introduce another configuration file? CloudStack provides options to 
> set configuration using either network service provides or global 
> configuration.
>
>
>
> plugins/network-elements/nuage-vsp/resources/META-INF/cloudstack/vsp/vsp-defaults.ini
>  
> (Diff
> revision 1)
>
> 10
>
> nuagePluginClientJarLocation=/usr/share/cloudstack-management/webapps/client/WEB-INF/lib
>
>   Please do not make any assumptions on the locations of jar files. That is 
> up to the people doing the packaging and might vary from distribution to 
> distribution. Expect everything to be available using the web app class 
> loader.
>
>
>
> plugins/network-elements/nuage-vsp/src/com/cloud/network/resource/NuageVspResource.java
>  
> (Diff
> revision 1)
>
> 95
>
> private static final String NUAGE_PLUGIN_CLIENT_JAR_LOCATION = 
> "/usr/share/cloudstack-management/webapps/client/WEB-INF/lib";
>
>   Don't depend on file locations as they will change. Use the java class 
> loader to load any libraries.
>
>
>
> plugins/network-elements/nuage-vsp/src/com/cloud/network/resource/NuageVspResource.java
>  
> (Diff
> revision 1)
>
> 196
>
> private  extends NuageVspSyncClient, D extends NuageVspGuruClient> void 
> loadNuageClient() throws Exception {
>
>   I'm not really agreeing with this method of loading the client. The client 
> should be loaded using the classloader.
>
> Is the library available from maven central or is distribution restricted? If 
> the latter case we need to move this plugin and the dependency on the library 
> to the noredist build.
>
>
>
> plugins/network-elements/nuage-vsp/test/com/cloud/network/element/NuageVspElementTest.java
>  
> (Diff
> revision 1)
>
> 103
>
> // NVP provider does not provide Connectivity for this network
>
>   copy-paste error ;-)
>
>
>server/src/com/cloud/network/vpc/VpcManagerImpl.java
>  
> (Diff
> revision 1)
>
> public void doInTransactionWithoutResult(TransactionStatus status) {
>
>1394
>
> if (vpcElements != null && vpcElements.size() < 3) {
>
>   Depending on a size here looks like a bug waiting to happen when somebody 
> adds an element. Is there another way to solve this?
>
>
>setup/db/create-schema.sql
>  
> (Diff
> revision 1)
>
> 149
>
> DROP TABLE IF EXISTS `cloud`.`external_nuage_vsp_devices`;
>
>   Modifying create-schema.sql is not allowed. Please make all necessary 
> database changes in the upgrade scripts for the current master branch.
>
>
> - Hugo Trippaers
>
> On July 7th, 2014, 6 p.m. UTC, Suresh Ramamurthy wrote:
>   Review request for cloudstack and Hugo Trippaers.
> By Suresh Ramamurthy.
>
> *Updated July 7, 2014, 6 p.m.*
>  *Bugs: * CLOUDSTACK-6845
> 
>  *Repository: * cloudstack-git
> Description
>
> This is first code drop for NuageVsp Network plugin support that will bring 
> the Nuage VSP network virtualization technology to CloudStack.
>
> We need a

Re: Review Request 23282: CLOUDSTACK-6845 : First Code drop for NuageVsp Network plugin

2014-07-08 Thread Suresh Ramamurthy


> On July 8, 2014, 10:07 a.m., Hugo Trippaers wrote:
> > client/tomcatconf/log4j-cloud.xml.in, line 66
> > 
> >
> > Why do you introduce a new logfile specific for Nuage? Isn't is easier 
> > for admins if all cloudstack related messages appear in the already 
> > existing logfile that admins are familiar with?

Sure, I will remove our logger.


> On July 8, 2014, 10:07 a.m., Hugo Trippaers wrote:
> > plugins/network-elements/nuage-vsp/resources/META-INF/cloudstack/vsp/vsp-defaults.ini,
> >  line 1
> > 
> >
> > Missing Apache License Header

Accepted, I will add the header. Sorry, I missed it.


> On July 8, 2014, 10:07 a.m., Hugo Trippaers wrote:
> > plugins/network-elements/nuage-vsp/resources/META-INF/cloudstack/vsp/vsp-defaults.ini,
> >  line 4
> > 
> >
> > Why introduce another configuration file? CloudStack provides options 
> > to set configuration using either network service provides or global 
> > configuration.

noOfSyncThreads=5
syncUpIntervalInMinutes=480

Both the above configurations are for NuageVsp plugin sync behavior. So, I will 
add them to Global configuration.


> On July 8, 2014, 10:07 a.m., Hugo Trippaers wrote:
> > plugins/network-elements/nuage-vsp/src/com/cloud/network/resource/NuageVspResource.java,
> >  line 95
> > 
> >
> > Don't depend on file locations as they will change. Use the java class 
> > loader to load any libraries.

Could you please at my comments for dynamic class loader...


> On July 8, 2014, 10:07 a.m., Hugo Trippaers wrote:
> > plugins/network-elements/nuage-vsp/resources/META-INF/cloudstack/vsp/vsp-defaults.ini,
> >  line 10
> > 
> >
> > Please do not make any assumptions on the locations of jar files. That 
> > is up to the people doing the packaging and might vary from distribution to 
> > distribution. Expect everything to be available using the web app class 
> > loader.

Could you please at my comments for dynamic class loader...


> On July 8, 2014, 10:07 a.m., Hugo Trippaers wrote:
> > plugins/network-elements/nuage-vsp/src/com/cloud/network/resource/NuageVspResource.java,
> >  line 196
> > 
> >
> > I'm not really agreeing with this method of loading the client. The 
> > client should be loaded using the classloader.
> > 
> > Is the library available from maven central or is distribution 
> > restricted? If the latter case we need to move this plugin and the 
> > dependency on the library to the noredist build.

Yes, NuageVsp plugin client library is distribution restricted. I had some 
design question regarding dropping the library and loading it dynamically. 
Please find below our requirement'

1) We wanted to drop our NuageVsp plugin client after installing CloudStack. 
2) We wanted to create an NuageVsp plugin Client RPM and then install the RPM 
that copies in a location. The location could be some other location that 
NuageVsp Plugin client chooses.
   In this case I thought of copying it under 
/usr/share/cloudstack-management/webapps/client/WEB-INF/lib but it could be 
different location
3) Then restart CloudStack.
4) When NuageVsp Device is added, then the class files will be dynamically 
loaded and things will work seamlessly

Advantages of above approach:

1) Cloudstack build does not have any dependency on our jar files. This is 
because, we do not have any reference of NuageVsp Plugin client code 
   and the client classes are loaded dynamically
2) There is no maven central dependency
3) Version Upgrade of NuageVsp Plugin client does not depend on Cloudstack 
version. We will just uninstall our RPM and re-install the new version of 
NuageVsp Plugin client code and restart CloudStack

Hugo, above was our suggestion. Is it okay to follow the above approach of 
loading the Plugin Client files? 

If the above approach is not acceptable then we are open to follow the noredist 
build approach. If we are following the noredist build approach then I just 
want to clarify the procedure to be
followed to use NuageVsp Plugin

1) User needs to download NuageVsp Plugin client jar file
2) Copy the jar under deps folder
3) Run install-non-oss.sh
4) Build RPM using -p NOREDIST option

Could you please let me know details of the forum where we can have design 
discussions?

I know, I am asking too many question :)

Thanks reviewing and supporting us.


> On July 8, 2014, 10:07 a.m., Hugo Trippaers wrote:
> > plugins/network-elements/nuage-vsp/test/com/cloud/network/element/NuageVspElementTest.java,
> >  line 103
> > 
> >

Re: [DB-CHANGE]

2014-07-08 Thread Daan Hoogland
please note that similar work was done by Alex:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Mailing+List+Guidelines
We should unify this.

On Tue, Jul 8, 2014 at 6:52 PM, Alena Prokharchyk
 wrote:
> Yes! :) Thank you and Daan who added the page.
>
> -Alena.
>
> From: Mike Tutkowski 
> mailto:mike.tutkow...@solidfire.com>>
> Date: Tuesday, July 8, 2014 at 9:45 AM
> To: Alena Prokharchyk 
> mailto:alena.prokharc...@citrix.com>>
> Cc: "dev@cloudstack.apache.org" 
> mailto:dev@cloudstack.apache.org>>
> Subject: Re: [DB-CHANGE]
>
> I think this is what you are asking for:
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/mail+tags+to+use+to+help+each+other
>
>
> On Tue, Jul 8, 2014 at 10:38 AM, Alena Prokharchyk 
> mailto:alena.prokharc...@citrix.com>> wrote:
> Thank you, Mike!
>
> Do you know if this information is on the wiki somewhere? It would be
> helpful to gather all the tags in some place central, so we all know what
> to put in the subject for diff kinds of updates/requests.
>
> -alena.
>
> On 7/7/14, 9:11 PM, "Mike Tutkowski" 
> mailto:mike.tutkow...@solidfire.com>> wrote:
>
>>Thanks, Alena!
>>
>>For those of you who may be new to the [DB-CHANGE] tag, the idea, as the
>>tag implies, is that a developer has changed the schema of the DB. In an
>>effort to help you not to have an issue after fetching his/her change, the
>>developer is telling you how you can alter your DB so you don't have to
>>completely scratch your existing cloud (due to an incompatibility between
>>the code and the DB) and create it from scratch again.
>>
>>This typically happens on the master branch as that branch is the most
>>susceptible to these kinds of changes during development and there is no
>>script that we maintain to upgrade a DB of the same [major.minor] version.
>>
>>
>>On Mon, Jul 7, 2014 at 5:36 PM, Alena Prokharchyk <
>>alena.prokharc...@citrix.com> wrote:
>>
>>> Please run these mysql statements after getting commit
>>> 5a96d8ef5cbc88df366016ae9dd7ee46e4ca417a on master branch:
>>>
>>> ALTER TABLE `cloud`.`user` ADD COLUMN domain_id bigint(20) unsigned
>>> DEFAULT NULL;
>>> ALTER TABLE `cloud`.`user` ADD CONSTRAINT `fk_user__domain_id` FOREIGN
>>>KEY
>>> `fk_user__domain_id`(`domain_id`) REFERENCES `domain`(`id`) ON DELETE
>>> CASCADE;
>>> UPDATE `cloud`.`user` SET `cloud`.`user`.domain_id=(SELECT
>>> `cloud`.`account`.domain_id   FROM `cloud`.`account`   WHERE
>>> `cloud`.`account`.id=`cloud`.`user`.account_id) where id > 0;
>>> ALTER TABLE `cloud`.`user` ADD UNIQUE KEY `username_domain_id`
>>> (`username`,`domain_id`);
>>>
>>>
>>> -alena.
>>>
>>
>>
>>
>>--
>>*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™



-- 
Daan


Re: Review Request 23314: Plugin specific code for the Brocade Network Plugin

2014-07-08 Thread Ritu Sabharwal

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

(Updated July 8, 2014, 6:49 p.m.)


Review request for cloudstack.


Changes
---

Thanks for reviewing the code.

I have fixed the license in all the files.

I am working on writing the unit tests for the plugin.

I am working on providing the documentation on using the plugin.

I have tested the plugin with the simulator and see the configurations on 
Brocade switches happening. Currently, I am setting up a real hardware setup 
with Vmware hypervisor and Brocade switches so test the connectivity between 
spawned VMs.

Can I continue writing the unit tests and marvin integration tests and 
documentation after the July 19 date so that this plugin makes to 4.5 feature 
freeze date.

I have updated the diffs with the changes for the license and other comments.


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


Repository: cloudstack-git


Description
---

Plugin specific code.


Diffs (updated)
-

  plugins/network-elements/brocade-vcs/pom.xml PRE-CREATION 
  plugins/network-elements/brocade-vcs/resources/BrocadeInterfaceSchema.xsd 
PRE-CREATION 
  plugins/network-elements/brocade-vcs/resources/BrocadePortProfileSchema.xsd 
PRE-CREATION 
  plugins/network-elements/brocade-vcs/resources/BrocadeShowVcsSchema.xsd 
PRE-CREATION 
  
plugins/network-elements/brocade-vcs/resources/META-INF/cloudstack/vcs/module.properties
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/resources/META-INF/cloudstack/vcs/spring-vcs-context.xml
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/agent/api/AssociateMacToNetworkAnswer.java
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/agent/api/AssociateMacToNetworkCommand.java
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/agent/api/CreateNetworkAnswer.java
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/agent/api/CreateNetworkCommand.java
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/agent/api/DeleteNetworkAnswer.java
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/agent/api/DeleteNetworkCommand.java
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/agent/api/DisassociateMacFromNetworkAnswer.java
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/agent/api/DisassociateMacFromNetworkCommand.java
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/agent/api/StartupBrocadeVcsCommand.java
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/network/BrocadeVcsNetworkHostMappingVO.java
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/network/brocade/BrocadeVcsApi.java
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/network/brocade/BrocadeVcsApiException.java
 PRE-CREATION 
  plugins/network-elements/brocade-vcs/src/com/cloud/network/brocade/Cache.java 
PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/network/brocade/CacheManager.java
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/network/brocade/Constants.java
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/network/brocade/Switch.java 
PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/network/dao/BrocadeVcsNetworkHostMappingDao.java
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/network/dao/BrocadeVcsNetworkHostMappingDaoImpl.java
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/network/element/BrocadeVcsElement.java
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/network/guru/BrocadeVcsGuestNetworkGuru.java
 PRE-CREATION 
  
plugins/network-elements/brocade-vcs/src/com/cloud/network/resource/BrocadeVcsResource.java
 PRE-CREATION 

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


Testing
---


Thanks,

Ritu  Sabharwal



Re: Review Request 23314: Plugin specific code for the Brocade Network Plugin

2014-07-08 Thread Ritu Sabharwal


> On July 8, 2014, 9:29 a.m., Hugo Trippaers wrote:
> > Thanks for make this a separate review, much easier to read.
> > 
> > The licenses are not added to all files and in some files they appear not 
> > to be complete. A good trick to solve this is to include the 
> > license-maven-plugin in the build section. See 
> > plugins/network-elements/nicira-nvp/pom.xml for an example.
> > 
> > Also the plugin doesn't contain any tests. We need unit tests or functional 
> > tests (and preferably both) to validate that this plugin works and keeps on 
> > working in future versions of CloudStack. It would be great if you could 
> > supply unit tests to validate this inner workings of this module and marvin 
> > based integration tests that we can run to see if this work with the 
> > intended hardware.
> > 
> > The last general point is that we would also need documentation on this 
> > plugin so administrators will know how to use this.

Thanks for reviewing the code.

I have fixed the license in all the files.

I am working on writing the unit tests for the plugin.

I am working on providing the documentation on using the plugin.

I have tested the plugin with the simulator and see the configurations on 
Brocade switches happening. Currently, I am setting up a real hardware setup 
with Vmware hypervisor and Brocade switches so test the connectivity between 
spawned VMs.

Can I continue writing the unit tests and marvin integration tests and 
documentation after the July 19 date so that this plugin makes to 4.5 feature 
freeze date.

I have updated the diffs with the changes for the license and other comments.


> On July 8, 2014, 9:29 a.m., Hugo Trippaers wrote:
> > plugins/network-elements/brocade-vcs/src/com/cloud/network/guru/BrocadeVcsGuestNetworkGuru.java,
> >  line 303
> > 
> >
> > This TODO is fixed right?

This is fixed. Just the comment was there.


> On July 8, 2014, 9:29 a.m., Hugo Trippaers wrote:
> > plugins/network-elements/brocade-vcs/src/com/cloud/network/guru/BrocadeVcsGuestNetworkGuru.java,
> >  line 106
> > 
> >
> > Please remove commented code.

Removed the commented code.


> On July 8, 2014, 9:29 a.m., Hugo Trippaers wrote:
> > plugins/network-elements/brocade-vcs/src/com/cloud/network/brocade/CacheManager.java,
> >  line 50
> > 
> >
> > You should get all properties from the CloudStack configuration 
> > mechanism. Either via the global config or via the settings on the network 
> > service provider configuration (preferred)

The Brocade network gear details are read from config file for now because of 
the time constraint to meet the 4.5 timelines. I plan to enhance this and get 
these values from network service provider configuration for future versions.


> On July 8, 2014, 9:29 a.m., Hugo Trippaers wrote:
> > plugins/network-elements/brocade-vcs/src/com/cloud/network/brocade/CacheManager.java,
> >  line 86
> > 
> >
> > This looks like something that should be persisted in the cloudstack 
> > database instead of stored outside cloudstack.

The Brocade network gear mapping details are read from config file for now 
because of the time constraint to meet the 4.5 timelines. I plan to enhance 
this and get these values from network service provider configuration for 
future versions and persist it DB.


- Ritu


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


On July 8, 2014, 6:49 p.m., Ritu  Sabharwal wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/23314/
> ---
> 
> (Updated July 8, 2014, 6:49 p.m.)
> 
> 
> Review request for cloudstack.
> 
> 
> Bugs: CLOUDSTACK-6823
> https://issues.apache.org/jira/browse/CLOUDSTACK-6823
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Plugin specific code.
> 
> 
> Diffs
> -
> 
>   plugins/network-elements/brocade-vcs/pom.xml PRE-CREATION 
>   plugins/network-elements/brocade-vcs/resources/BrocadeInterfaceSchema.xsd 
> PRE-CREATION 
>   plugins/network-elements/brocade-vcs/resources/BrocadePortProfileSchema.xsd 
> PRE-CREATION 
>   plugins/network-elements/brocade-vcs/resources/BrocadeShowVcsSchema.xsd 
> PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/resources/META-INF/cloudstack/vcs/module.properties
>  PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/resources/META-INF/cloudstack/vcs/spring-vcs-context.xml
>  PRE-CREATION 
>   
> plugins/network-ele

Re: Timeout error while brining up VM console from UI for testing Brocade Network Plugin: CLOUDSTACK-6823

2014-07-08 Thread Amogh Vasekar
Hi,

AFAIK, since the simulator does not actually have any H/W or real VM, I
don't think console access is available.

Thanks,
Amogh

On 7/7/14 4:00 PM, "Ritu Sabharwal"  wrote:

>Hi,
>
>I have tested the plugin functionality with the Simulator by creating the
>datacenter with the marvin script and configuring the Brocade VDX
>switches.
>
>The Brocade VDX switches are configured with the port-profiles and
>interfaces at appropriate lifecycles of VMs.
>
>I can see the VMs coming up and running. I need to bring up the console
>for the VMs to test the ping across the VMs.
>
>In the CloudStack UI, when I click the console button for a VM, I don't
>get the console but see a timeout message.
>
>Thanks & Regards,
>Ritu S.



Re: [DISCUSS][PROPOSAL] git workflow

2014-07-08 Thread Nate Gordon
As someone who has worked with a number of different version control
systems (and have far more love for git than any other), I'm curious as to
why we would want to fight what I've always seen as the core feature of
git. Branching and merging. The gitflow model is incredibly useful for
keeping track of a number of different development paths concurrently.
Branches remained organized and have a clear destination and workflow that
they need to go through as part of the merging process. We use it
internally (on a much smaller team) with great success. And with the
difficulties I've seen on the mailing list around the -forward branches and
cherry-picking, I'm curious as to why this is the preferred method. From
everything I've read about git and cherry-picking, it is a copy of the
commit, not a reference to the original commit. This makes it hard to track
down an individual change to find the original source.

Thanks,

-Nate


On Tue, Jul 8, 2014 at 11:04 AM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> Thanks for bringing this up again, Sebastien.
>
> I've had http://nvie.com/posts/a-successful-git-branching-model/ up in
> Chrome since you sent that link and been reading through it a bit here and
> there, but have just been too busy as of late to give it a bunch of
> thought.
>
> I agree, though, that we should really think about moving to another model
> of using Git as it is not un-common for master to be broken, which leads to
> a lot of lost development time for many people.
>
>
> On Mon, Jun 30, 2014 at 4:09 PM, Sebastien Goasguen 
> wrote:
>
> > I would like to re-start this discussion.
> >
> > Rajani made some good points and someone mentioned Gitflow:
> >
> > http://nvie.com/posts/a-successful-git-branching-model/
> >
> > Thinking about our release procedure, we clearly need more tests and a
> CI.
> > However it looks like this is going to take some time.
> >
> > In the meantime I think there is nothing preventing us from agreeing to
> > 'git practices', we don't need tests or new infra, we just need to agree
> on
> > the git workflow.
> >
> > Right now Master is really a development branch, we should make it a
> > stable branch for production with very few commits.
> > This does not mean that we would release less, in contrary this would
> > ensure that a commit to master means it's a production release.
> >
> > In addition gitflow [1] does not do cherry-picks (gets back to Rajani's
> > point) everything is based on merges.
> >
> > I am of the opinion that git flow provides a nice process. It basically
> > freezes master. Development happens in a 'develop' branch, releases
> > branches are branched off of that and merged into master and back into
> > develop….etc
> >
> > Please read [1] it's a good read.
> >
> > And let's discuss,
> >
> > [1] http://nvie.com/posts/a-successful-git-branching-model/
> >
> > -Sebastien
> >
> > On Jun 2, 2014, at 11:58 PM, Rajani Karuturi  >
> > wrote:
> >
> > > There is also the problem of cherry-picking.
> > > As a contributor, I always endup creating multiple patches for each
> > branch as they don’t cleanly apply on the upward branches. which means
> > distinct commits for each branch and I don’t easily know which all
> branches
> > my commit exists unless I do grep.
> > > if we follow merging strategy properly, apart from the first merge of
> > the branch, everything else on top of it should be a painless merge.
> > >
> > >
> > >
> > > ~Rajani
> > >
> > >
> > >
> > > On 02-Jun-2014, at 10:51 pm, Marcus  wrote:
> > >
> > >> I think many of the bullet points are what we are currently doing
> > >> (guidelines for commit comments, feature branches need to stay in sync
> > with
> > >> master, no back-merging). I also think that much of what we do now is
> > done
> > >> the way it is simply because there *are* vast changes between
> versions.
> > >> Classes are getting shuffled around and changed all the time. If its
> > >> feasible to merge branch fixes to master, that's fine, but some quick
> > tests
> > >> seem to indicate that this will be messy getting started.
> > >>
> > >> That leaves us with how we do releases. I'm fine with having single
> > >> branches for major releases(4.3) and tagging the commits where each
> > >> incremental release (4.3.x) is done. I'm trying to remember why we
> went
> > >> with the -forward, I'm sure it's in the mailing list somewhere, but
> one
> > of
> > >> the nice things it provides is the ability for the release manager to
> > >> control what changes are made during code freeze while giving people a
> > >> place to stage fixes (though admittedly this is not always followed).
> > >> Without -forward, would the flow be for each dev to have their own
> repo
> > and
> > >> issue pull requests for bugfixes?
> > >>
> > >>
> > >> On Mon, Jun 2, 2014 at 3:17 AM, Rajani Karuturi <
> > rajani.karut...@citrix.com>
> > >> wrote:
> > >>
> > >>> Any other suggestions/objections/comments??
> > >>> Can we discuss this in detail and agree

Re: [ACS4.5] Can't access volumes on storage tab in GUI

2014-07-08 Thread Mike Tutkowski
Just a follow up to this:

I updated my codebase, rebuilt my cloud from scratch, and now it seems that
all of my disks/volumes (both root and data) show up on the Storage tab as
I spin up VMs and attach data disks to them.


On Sun, Jul 6, 2014 at 12:25 AM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:

> Interesting...one of my three ROOT disks shows up at the time being.
>
>
> On Sun, Jul 6, 2014 at 12:17 AM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
>> I noticed tonight that the Storage tab no longer shows me ROOT
>> volumes...just DATADISK ones.
>>
>> Possibly related to the issue that was being discussed in this thread?
>>
>>
>> On Tue, Jul 1, 2014 at 6:18 PM, Mike Tutkowski <
>> mike.tutkow...@solidfire.com> wrote:
>>
>>> Actually, this is a good opportunity to remind devs in general that if
>>> you make a change to a schema-upgrade file for a release and you are not on
>>> master that you should take a peek at the schema-upgrade file on master to
>>> see if it needs to be updated, as well.
>>>
>>> In this case, it would have been OK (nothing to do on master) had the
>>> volume_view not been modified going from 4.4 to 4.5, but it had been (so
>>> modifications to volume_view going from 4.3 to 4.4 needed to be carried
>>> forward going from 4.4 to 4.5).
>>>
>>> Thanks!
>>>
>>>
>>> On Tue, Jul 1, 2014 at 6:10 PM, Mike Tutkowski <
>>> mike.tutkow...@solidfire.com> wrote:
>>>
 Thanks!


 On Tue, Jul 1, 2014 at 4:26 PM, Yoshikazu Nojima 
 wrote:

> Hi all,
> I pushed a commit to fix this issue.
> I confirmed listVolumes doesn't throw an error now in my environment.
>
> Commit 890e71cb5c2f80b09cd4db7947d94e325d7bd182 in cloudstack's branch
> refs/heads/master from Yoshikazu Nojima
> [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=890e71c ]
>
> CLOUDSTACK-7032 bugfix: listVolumes throws an error
>
> Since schema change made on 4.4 is not applied to the upgrade script
> from 4.4 to 4.5, listVolumes api throws an error.
> This commit fix the issue.
>
>
> 2014-07-01 14:06 GMT-06:00 Mike Tutkowski <
> mike.tutkow...@solidfire.com>:
> > Somehow I didn't see that aliasing going on there.
> >
> >
> > On Tue, Jul 1, 2014 at 2:05 PM, Mike Tutkowski <
> mike.tutkow...@solidfire.com
> >> wrote:
> >
> >> Ah, yes, good point.
> >>
> >>
> >> On Tue, Jul 1, 2014 at 2:02 PM, Yoshikazu Nojima 
> wrote:
> >>
> >>> Hi Mike,
> >>> I suppose "iso" is an alias for "vm_template".
> >>> See the left join syntax you refered.
> >>>
> >>> >left join
> >>> >`cloud`.`vm_template` iso ON iso.id = volumes.iso_id
> >>>
> >>>
> >>> Regards,
> >>> Noji
> >>>
> >>> 2014-07-01 12:19 GMT-06:00 Mike Tutkowski <
> mike.tutkow...@solidfire.com>:
> >>> > This diff shows some of the problem:
> >>> >
> >>> > http://i.imgur.com/PW7lqbs.png
> >>> >
> >>> > Six fields have been removed from the volume_view and five of
> those six
> >>> are
> >>> > still in use.
> >>> >
> >>> > It is not a simple matter of adding them back in, however,
> because the
> >>> iso
> >>> > table that used to be used is no longer present in 4.5.
> >>> >
> >>> > That being the case, we need to figure out where to get this
> data from
> >>> in
> >>> > 4.5. I don't have a lot of context, though, on why the iso table
> doesn't
> >>> > exist anymore.
> >>> >
> >>> > Thoughts?
> >>> >
> >>> >
> >>> > On Mon, Jun 30, 2014 at 11:12 PM, Mike Tutkowski <
> >>> > mike.tutkow...@solidfire.com> wrote:
> >>> >
> >>> >> Upon further consideration, I forgot that we drop and re-create
> views
> >>> in
> >>> >> the SQL - if need be - from release to release.
> >>> >>
> >>> >> It looks like a new version of the volume_view went into 4.5
> with
> >>> >> 11f5bdd78de4121331b07995800f6e9e7c22f2c0, which is from Review
> Request
> >>> >> 19446.
> >>> >>
> >>> >> It appears volume_view is missing several columns.
> >>> >>
> >>> >>
> >>> >> On Mon, Jun 30, 2014 at 10:30 PM, Mike Tutkowski <
> >>> >> mike.tutkow...@solidfire.com> wrote:
> >>> >>
> >>> >>> Actually, in looking at "git blame", it appears this view has
> never
> >>> had
> >>> >>> those two columns.
> >>> >>>
> >>> >>> I think the intent, however, is that those two columns exist
> in the
> >>> view.
> >>> >>>
> >>> >>> I'm adding them in my sandbox and testing this out now.
> >>> >>>
> >>> >>>
> >>> >>> On Mon, Jun 30, 2014 at 10:11 PM, Mike Tutkowski <
> >>> >>> mike.tutkow...@solidfire.com> wrote:
> >>> >>>
> >>>  I looked into this a bit more.
> >>> 
> >>>  It appears that the "volume_view" no longer has the following
> two
> 

Re: Review Request 23169: CLOUDSTACK-7010: Add domain to createZones in marvin

2014-07-08 Thread ASF Subversion and Git Services

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


Commit 63ba1ddfb9ddfb47c7e0c564fea3ad8edf2bd19a in cloudstack's branch 
refs/heads/master from John Dilley
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=63ba1dd ]

CLOUDSTACK-7010: Add domain to createZones in marvin


- ASF Subversion and Git Services


On July 8, 2014, 9:48 a.m., John Dilley wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/23169/
> ---
> 
> (Updated July 8, 2014, 9:48 a.m.)
> 
> 
> Review request for cloudstack and Santhosh Edukulla.
> 
> 
> Bugs: CLOUDSTACK-7010
> https://issues.apache.org/jira/browse/CLOUDSTACK-7010
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Add domain to createZones in deployDataCenter
> 
> 
> Diffs
> -
> 
>   tools/marvin/marvin/configGenerator.py 8d9 
>   tools/marvin/marvin/deployDataCenter.py c097238 
> 
> Diff: https://reviews.apache.org/r/23169/diff/
> 
> 
> Testing
> ---
> 
> Tested deployDataCenter, both with and without specifying a domain
> 
> 
> Thanks,
> 
> John Dilley
> 
>



Re: [DB-CHANGE]

2014-07-08 Thread Alena Prokharchyk
Yes! :) Thank you and Daan who added the page.

-Alena.

From: Mike Tutkowski 
mailto:mike.tutkow...@solidfire.com>>
Date: Tuesday, July 8, 2014 at 9:45 AM
To: Alena Prokharchyk 
mailto:alena.prokharc...@citrix.com>>
Cc: "dev@cloudstack.apache.org" 
mailto:dev@cloudstack.apache.org>>
Subject: Re: [DB-CHANGE]

I think this is what you are asking for:

https://cwiki.apache.org/confluence/display/CLOUDSTACK/mail+tags+to+use+to+help+each+other


On Tue, Jul 8, 2014 at 10:38 AM, Alena Prokharchyk 
mailto:alena.prokharc...@citrix.com>> wrote:
Thank you, Mike!

Do you know if this information is on the wiki somewhere? It would be
helpful to gather all the tags in some place central, so we all know what
to put in the subject for diff kinds of updates/requests.

-alena.

On 7/7/14, 9:11 PM, "Mike Tutkowski" 
mailto:mike.tutkow...@solidfire.com>> wrote:

>Thanks, Alena!
>
>For those of you who may be new to the [DB-CHANGE] tag, the idea, as the
>tag implies, is that a developer has changed the schema of the DB. In an
>effort to help you not to have an issue after fetching his/her change, the
>developer is telling you how you can alter your DB so you don't have to
>completely scratch your existing cloud (due to an incompatibility between
>the code and the DB) and create it from scratch again.
>
>This typically happens on the master branch as that branch is the most
>susceptible to these kinds of changes during development and there is no
>script that we maintain to upgrade a DB of the same [major.minor] version.
>
>
>On Mon, Jul 7, 2014 at 5:36 PM, Alena Prokharchyk <
>alena.prokharc...@citrix.com> wrote:
>
>> Please run these mysql statements after getting commit
>> 5a96d8ef5cbc88df366016ae9dd7ee46e4ca417a on master branch:
>>
>> ALTER TABLE `cloud`.`user` ADD COLUMN domain_id bigint(20) unsigned
>> DEFAULT NULL;
>> ALTER TABLE `cloud`.`user` ADD CONSTRAINT `fk_user__domain_id` FOREIGN
>>KEY
>> `fk_user__domain_id`(`domain_id`) REFERENCES `domain`(`id`) ON DELETE
>> CASCADE;
>> UPDATE `cloud`.`user` SET `cloud`.`user`.domain_id=(SELECT
>> `cloud`.`account`.domain_id   FROM `cloud`.`account`   WHERE
>> `cloud`.`account`.id=`cloud`.`user`.account_id) where id > 0;
>> ALTER TABLE `cloud`.`user` ADD UNIQUE KEY `username_domain_id`
>> (`username`,`domain_id`);
>>
>>
>> -alena.
>>
>
>
>
>--
>*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: [DB-CHANGE]

2014-07-08 Thread Mike Tutkowski
I think this is what you are asking for:

https://cwiki.apache.org/confluence/display/CLOUDSTACK/mail+tags+to+use+to+help+each+other


On Tue, Jul 8, 2014 at 10:38 AM, Alena Prokharchyk <
alena.prokharc...@citrix.com> wrote:

> Thank you, Mike!
>
> Do you know if this information is on the wiki somewhere? It would be
> helpful to gather all the tags in some place central, so we all know what
> to put in the subject for diff kinds of updates/requests.
>
> -alena.
>
> On 7/7/14, 9:11 PM, "Mike Tutkowski"  wrote:
>
> >Thanks, Alena!
> >
> >For those of you who may be new to the [DB-CHANGE] tag, the idea, as the
> >tag implies, is that a developer has changed the schema of the DB. In an
> >effort to help you not to have an issue after fetching his/her change, the
> >developer is telling you how you can alter your DB so you don't have to
> >completely scratch your existing cloud (due to an incompatibility between
> >the code and the DB) and create it from scratch again.
> >
> >This typically happens on the master branch as that branch is the most
> >susceptible to these kinds of changes during development and there is no
> >script that we maintain to upgrade a DB of the same [major.minor] version.
> >
> >
> >On Mon, Jul 7, 2014 at 5:36 PM, Alena Prokharchyk <
> >alena.prokharc...@citrix.com> wrote:
> >
> >> Please run these mysql statements after getting commit
> >> 5a96d8ef5cbc88df366016ae9dd7ee46e4ca417a on master branch:
> >>
> >> ALTER TABLE `cloud`.`user` ADD COLUMN domain_id bigint(20) unsigned
> >> DEFAULT NULL;
> >> ALTER TABLE `cloud`.`user` ADD CONSTRAINT `fk_user__domain_id` FOREIGN
> >>KEY
> >> `fk_user__domain_id`(`domain_id`) REFERENCES `domain`(`id`) ON DELETE
> >> CASCADE;
> >> UPDATE `cloud`.`user` SET `cloud`.`user`.domain_id=(SELECT
> >> `cloud`.`account`.domain_id   FROM `cloud`.`account`   WHERE
> >> `cloud`.`account`.id=`cloud`.`user`.account_id) where id > 0;
> >> ALTER TABLE `cloud`.`user` ADD UNIQUE KEY `username_domain_id`
> >> (`username`,`domain_id`);
> >>
> >>
> >> -alena.
> >>
> >
> >
> >
> >--
> >*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: [DB-CHANGE]

2014-07-08 Thread Alena Prokharchyk
Thank you, Mike!

Do you know if this information is on the wiki somewhere? It would be
helpful to gather all the tags in some place central, so we all know what
to put in the subject for diff kinds of updates/requests.

-alena.

On 7/7/14, 9:11 PM, "Mike Tutkowski"  wrote:

>Thanks, Alena!
>
>For those of you who may be new to the [DB-CHANGE] tag, the idea, as the
>tag implies, is that a developer has changed the schema of the DB. In an
>effort to help you not to have an issue after fetching his/her change, the
>developer is telling you how you can alter your DB so you don't have to
>completely scratch your existing cloud (due to an incompatibility between
>the code and the DB) and create it from scratch again.
>
>This typically happens on the master branch as that branch is the most
>susceptible to these kinds of changes during development and there is no
>script that we maintain to upgrade a DB of the same [major.minor] version.
>
>
>On Mon, Jul 7, 2014 at 5:36 PM, Alena Prokharchyk <
>alena.prokharc...@citrix.com> wrote:
>
>> Please run these mysql statements after getting commit
>> 5a96d8ef5cbc88df366016ae9dd7ee46e4ca417a on master branch:
>>
>> ALTER TABLE `cloud`.`user` ADD COLUMN domain_id bigint(20) unsigned
>> DEFAULT NULL;
>> ALTER TABLE `cloud`.`user` ADD CONSTRAINT `fk_user__domain_id` FOREIGN
>>KEY
>> `fk_user__domain_id`(`domain_id`) REFERENCES `domain`(`id`) ON DELETE
>> CASCADE;
>> UPDATE `cloud`.`user` SET `cloud`.`user`.domain_id=(SELECT
>> `cloud`.`account`.domain_id   FROM `cloud`.`account`   WHERE
>> `cloud`.`account`.id=`cloud`.`user`.account_id) where id > 0;
>> ALTER TABLE `cloud`.`user` ADD UNIQUE KEY `username_domain_id`
>> (`username`,`domain_id`);
>>
>>
>> -alena.
>>
>
>
>
>-- 
>*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: [DISCUSS][PROPOSAL] git workflow

2014-07-08 Thread Mike Tutkowski
Thanks for bringing this up again, Sebastien.

I've had http://nvie.com/posts/a-successful-git-branching-model/ up in
Chrome since you sent that link and been reading through it a bit here and
there, but have just been too busy as of late to give it a bunch of thought.

I agree, though, that we should really think about moving to another model
of using Git as it is not un-common for master to be broken, which leads to
a lot of lost development time for many people.


On Mon, Jun 30, 2014 at 4:09 PM, Sebastien Goasguen 
wrote:

> I would like to re-start this discussion.
>
> Rajani made some good points and someone mentioned Gitflow:
>
> http://nvie.com/posts/a-successful-git-branching-model/
>
> Thinking about our release procedure, we clearly need more tests and a CI.
> However it looks like this is going to take some time.
>
> In the meantime I think there is nothing preventing us from agreeing to
> 'git practices', we don't need tests or new infra, we just need to agree on
> the git workflow.
>
> Right now Master is really a development branch, we should make it a
> stable branch for production with very few commits.
> This does not mean that we would release less, in contrary this would
> ensure that a commit to master means it's a production release.
>
> In addition gitflow [1] does not do cherry-picks (gets back to Rajani's
> point) everything is based on merges.
>
> I am of the opinion that git flow provides a nice process. It basically
> freezes master. Development happens in a 'develop' branch, releases
> branches are branched off of that and merged into master and back into
> develop….etc
>
> Please read [1] it's a good read.
>
> And let's discuss,
>
> [1] http://nvie.com/posts/a-successful-git-branching-model/
>
> -Sebastien
>
> On Jun 2, 2014, at 11:58 PM, Rajani Karuturi 
> wrote:
>
> > There is also the problem of cherry-picking.
> > As a contributor, I always endup creating multiple patches for each
> branch as they don’t cleanly apply on the upward branches. which means
> distinct commits for each branch and I don’t easily know which all branches
> my commit exists unless I do grep.
> > if we follow merging strategy properly, apart from the first merge of
> the branch, everything else on top of it should be a painless merge.
> >
> >
> >
> > ~Rajani
> >
> >
> >
> > On 02-Jun-2014, at 10:51 pm, Marcus  wrote:
> >
> >> I think many of the bullet points are what we are currently doing
> >> (guidelines for commit comments, feature branches need to stay in sync
> with
> >> master, no back-merging). I also think that much of what we do now is
> done
> >> the way it is simply because there *are* vast changes between versions.
> >> Classes are getting shuffled around and changed all the time. If its
> >> feasible to merge branch fixes to master, that's fine, but some quick
> tests
> >> seem to indicate that this will be messy getting started.
> >>
> >> That leaves us with how we do releases. I'm fine with having single
> >> branches for major releases(4.3) and tagging the commits where each
> >> incremental release (4.3.x) is done. I'm trying to remember why we went
> >> with the -forward, I'm sure it's in the mailing list somewhere, but one
> of
> >> the nice things it provides is the ability for the release manager to
> >> control what changes are made during code freeze while giving people a
> >> place to stage fixes (though admittedly this is not always followed).
> >> Without -forward, would the flow be for each dev to have their own repo
> and
> >> issue pull requests for bugfixes?
> >>
> >>
> >> On Mon, Jun 2, 2014 at 3:17 AM, Rajani Karuturi <
> rajani.karut...@citrix.com>
> >> wrote:
> >>
> >>> Any other suggestions/objections/comments??
> >>> Can we discuss this in detail and agree to a process??
> >>>
> >>>
> >>> ~Rajani
> >>>
> >>>
> >>>
> >>> On 02-Jun-2014, at 9:32 am, Rajani Karuturi <
> rajani.karut...@citrix.com>
> >>> wrote:
> >>>
>  Yes as mike said, if its a one-off case we can do a empty merge(merge
> -s
> >>> ours) for it and git will assume its merged but will not bring in any
> >>> changes.
> 
>  If the branches diverged a lot, for example after a major rewrite, we
> >>> could stop merging to that branch and above and make the fix manually.
> 
> 
>  ~Rajani
> 
> 
> 
>  On 30-May-2014, at 11:26 pm, Mike Tutkowski <
> >>> mike.tutkow...@solidfire.com> wrote:
> 
> > Yep, that's what I was referring to in that a particular fix for an
> old
> > release may not apply to newer versions. That does happen.
> >
> > We used to mark those as "don't need to merge to branch x" in SVN and
> >>> then
> > you handed it however made sense on the applicable branch(es).
> >
> >
> > On Fri, May 30, 2014 at 11:53 AM, Stephen Turner <
> >>> stephen.tur...@citrix.com>
> > wrote:
> >
> >> What happens if a fix isn't relevant for newer versions, or has to
> be
> >> rewritten for newer versions because the code 

Re: Review Request 23192: Adding Readme and run checkbox at the end of the installation. Also installing mysql connector

2014-07-08 Thread Hugo Trippaers
Rajani,

That is why we renamed nonoss to noredist. It has to do with the policy of the 
Apache Software Foundation regarding compatible licenses [1]. The problem in 
this case is subtle, but there is a difference. The main point in the 
discussion is so-called system dependencies. We know we need java, mysql and 
the mysql-connector-java to be installed before we can install our packages. 
This is what the dependency on mysql-connector-java in the spec file indicates. 
Creating a package containing those source is actually including the items we 
consider is going just a bit further and to a point where we concluded that it 
is not inline with the apache policies. So it is perfectly alright to include a 
popup in the installer that tells the users that he needs to install mysql, 
java etc, but we can’t have an installed in the source that will do that for 
the user as part of the installer.

What David proposes is a the middle ground where we can keep the installer in 
the configured like this in the pom, but it can’t be in that standard build, 
but only in the build that know we can’t redistribute (the noredist build). We 
will never make the artifacts resulting from that build available, but other 
entities can make them available. By specifying noredist on the build command 
we can be reasonably sure that the builder has been informed that distribution 
restrictions might apply on whatever it is he is doing.

Cheers,

Hugo

[1] http://www.apache.org/legal/resolved.html#category-x


On 8 jul. 2014, at 12:57, Rajani Karuturi  wrote:

> I believe this has nothing to do with nonoss. If I understand it right, 
> nonoss modules are required for cloudstack to work with certain 3rd party 
> stuff.
> 
> This one is just a helper to create a windows installer. It chose to use a 
> mvn command to create the installer instead of shell/bat script. It should 
> work with either nonoss or oss modules.
> This is very similar to cloud.spec[1] we have which is used to create the rpm 
> and which already has mysql-connector-java already listed as required package.
> 
> I think the right way would be to create independent git repos for 
> deb/rpm/windows installers/packages.
> 
> In its current state, I don’t see it any different from other helper 
> installer scripts we already have.
> 
> [1] 
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=packaging/centos63/cloud.spec;hb=HEAD
> 
> ~Rajani
> 
> 
> 
> On 08-Jul-2014, at 9:56 am, Damoder Reddy 
> mailto:damoder.re...@citrix.com>> wrote:
> 
> Ok,
> 
> To clarify the windows MSI will not build in the default profile. I have 
> enabled a new profile "buildw" to build windows MSI installer which 
> explicitly we need to pass similar to nonoss?
> 
> Is that sufficient to make it nonoss or still we need to move it under nonoss 
> profile explicitly?
> 
> Thanks
> Damoder/
> 
> -Original Message-
> From: David Nalley [mailto:da...@gnsa.us]
> Sent: Thursday, 3 July 2014 9:58 PM
> To: dev@cloudstack.apache.org
> Cc: Damoder Reddy; Koushik Das
> Subject: Re: Review Request 23192: Adding Readme and run checkbox at the end 
> of the installation. Also installing mysql connector
> 
> On Thu, Jul 3, 2014 at 12:08 PM, Chip Childers 
> mailto:chipchild...@apache.org>> wrote:
> On Thu, Jul 03, 2014 at 03:14:30PM +, Leo Simons wrote:
> It looks like that maven pom on windows _by default_ downloads and
> installs a variety of non-apache-license (and/or non-mit/bsd/variant
> license) software. That shouldnąt really happen. The principle is one
> of łleast surprise˛: As a user or developer who does not RTFM,
> following the default commands/tools/etc, you should end up with a
> more-or-less apache-licensed build result (*) that you can
> redistribute the result under.
> 
> +1
> 
> 
> But apache policy is that it is acceptable to provide scripts/build
> tools/assistance to help those same users/developers do things that
> they want to do. As long as they understand the legal situation they end up 
> in.
> 
> I would recommend adding a "nonoss" maven profile that the
> developer/user has to explicitly select in order to do those
> downloads. As long as that option is described clearly, thatąs then
> ok. See
> 
> http://svn.apache.org/repos/asf/apr/apr/trunk/README
> 
> for an example of how to point out the license situation.
> 
> We already have the nonoss profile, so this is a pretty good fix for
> the windows build issues noted above IMO.
> 
> Damoder/Koushik - please make this change.
> 
> 
> Something similar is true by the way (IMHO, but as a project
> cloudstack can definitely decide differently), for a possible MSI
> script. Making an MSI script that prompts the user whether to
> download mysql at the point of install, **clearly pointing out the
> license situation** if they choose to do so, seems reasonable, and I
> personally would not object to shipping _that_ kind of script as part of an 
> apache source release

Re: Testing a Cloudstack Virtual Router (SystemVM).

2014-07-08 Thread Karl Harris
On Tue, Jul 8, 2014 at 5:04 AM, Rohit Yadav 
wrote:

> Hi Karl,
>
>
> Karl Harris wrote:
>
>> What is the current framework used to test a Cloudstack Virtual Router
>> (SystemVM) in isolation aka without Management Server if any?
>>
>
> AFAIK we don't have any such testing/automation framework within Apache
> CloudStack.
>
>
>  I'd like to call a SystemVM script with a set of configuration parameters
>> (changes for VPCVrr, etc.) and observe the changes to the virtual routers
>> configuration.
>>
>> Since I will eventually need the ethernet connections to be added and
>> deleted I would like to aviod using ethernet to make the connection to the
>> SystemVM image. Ideally I don't want to change the SystemVM image from
>> what
>> is build by tools/appliance/build.sh.
>>
>>
> The SystemVM image and the agent is tightly coupled with CloudStack, you
> may have to change things in the build script (if you intend to
> add/remove/modify packages, files and contents).
>
>
>  How was this testing done in the past?
>>
>
> In the past, I would create a systemvm template, have CloudStack
> management to use it to boot up SSVMs, VRs etc. and ssh into them from
> their respective hosts on their link local IP. Then, I would change the
> internal state of the VM and check with management server to test things
> and see if it would fix the state itself, execute platform apis etc.
>
> There is/was no automation framework to do the testing so it was mostly
> manually. Any work in this regard would be great.
>
> Since cloud-early-config.sh is "hypervisor aware", at least for those that
do not populate /proc/cmdline directly,  did you test each hypervisor
manually?

Regards.
>
>
>> Thanks,
>>
>> Karl
>>
>>  Find out more about ShapeBlue and our range of CloudStack related
> services
>
> IaaS Cloud Design & Build iaas-cloud-design-and-build//>
> CSForge – rapid IaaS deployment framework
> CloudStack Consulting
> CloudStack Infrastructure Support cloudstack-infrastructure-support/>
> CloudStack Bootcamp Training Courses cloudstack-training/>
>
> This email and any attachments to it may be confidential and are intended
> solely for the use of the individual to whom it is addressed. Any views or
> opinions expressed are solely those of the author and do not necessarily
> represent those of Shape Blue Ltd or related companies. If you are not the
> intended recipient of this email, you must neither take any action based
> upon its contents, nor copy or show it to anyone. Please contact the sender
> if you believe you have received this email in error. Shape Blue Ltd is a
> company incorporated in England & Wales. ShapeBlue Services India LLP is a
> company incorporated in India and is operated under license from Shape Blue
> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil
> and is operated under license from Shape Blue Ltd. ShapeBlue is a
> registered trademark.
>
>


Re: Testing a Cloudstack Virtual Router (SystemVM).

2014-07-08 Thread Karl Harris
Sorry for the duplicate questions!

Most were answered in you previous response!

Thanks Rohit!

On Tuesday, July 8, 2014, Karl Harris  wrote:

> How is the unit testing accomplished for changes to the
> configuration/startup scripts? I can obviously run the scripts in a
> different Debian build!
> Im trying to build something that can be tested easily without many
> changes to the baseline System VM image.
>
> The current System VM build runs under vbox freestanding but has no net
> work unless parameter are passed to it via Grub/proc/cmdline which is used
> by cloud-early-config.sh to set up the network.
>
> How was the unit testing done in the past?
>
> Or was iit ntegration testing only?
>
>
> On Tuesday, July 8, 2014, Rohit Yadav  > wrote:
>
>> Hi Karl,
>>
>> Karl Harris wrote:
>>
>>> What is the current framework used to test a Cloudstack Virtual Router
>>> (SystemVM) in isolation aka without Management Server if any?
>>>
>>
>> AFAIK we don't have any such testing/automation framework within Apache
>> CloudStack.
>>
>>  I'd like to call a SystemVM script with a set of configuration parameters
>>> (changes for VPCVrr, etc.) and observe the changes to the virtual routers
>>> configuration.
>>>
>>> Since I will eventually need the ethernet connections to be added and
>>> deleted I would like to aviod using ethernet to make the connection to
>>> the
>>> SystemVM image. Ideally I don't want to change the SystemVM image from
>>> what
>>> is build by tools/appliance/build.sh.
>>>
>>>
>> The SystemVM image and the agent is tightly coupled with CloudStack, you
>> may have to change things in the build script (if you intend to
>> add/remove/modify packages, files and contents).
>>
>>  How was this testing done in the past?
>>>
>>
>> In the past, I would create a systemvm template, have CloudStack
>> management to use it to boot up SSVMs, VRs etc. and ssh into them from
>> their respective hosts on their link local IP. Then, I would change the
>> internal state of the VM and check with management server to test things
>> and see if it would fix the state itself, execute platform apis etc.
>>
>> There is/was no automation framework to do the testing so it was mostly
>> manually. Any work in this regard would be great.
>>
>> Regards.
>>
>>
>>> Thanks,
>>>
>>> Karl
>>>
>>>  Find out more about ShapeBlue and our range of CloudStack related
>> services
>>
>> IaaS Cloud Design & Build> iaas-cloud-design-and-build//>
>> CSForge – rapid IaaS deployment framework
>> CloudStack Consulting
>> CloudStack Infrastructure Support> cloudstack-infrastructure-support/>
>> CloudStack Bootcamp Training Courses> cloudstack-training/>
>>
>> This email and any attachments to it may be confidential and are intended
>> solely for the use of the individual to whom it is addressed. Any views or
>> opinions expressed are solely those of the author and do not necessarily
>> represent those of Shape Blue Ltd or related companies. If you are not the
>> intended recipient of this email, you must neither take any action based
>> upon its contents, nor copy or show it to anyone. Please contact the sender
>> if you believe you have received this email in error. Shape Blue Ltd is a
>> company incorporated in England & Wales. ShapeBlue Services India LLP is a
>> company incorporated in India and is operated under license from Shape Blue
>> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil
>> and is operated under license from Shape Blue Ltd. ShapeBlue is a
>> registered trademark.
>>
>>


Re: Testing a Cloudstack Virtual Router (SystemVM).

2014-07-08 Thread Karl Harris
How is the unit testing accomplished for changes to the
configuration/startup scripts? I can obviously run the scripts in a
different Debian build!
Im trying to build something that can be tested easily without many changes
to the baseline System VM image.

The current System VM build runs under vbox freestanding but has no net
work unless parameter are passed to it via Grub/proc/cmdline which is used
by cloud-early-config.sh to set up the network.

How was the unit testing done in the past?

Or was iit ntegration testing only?


On Tuesday, July 8, 2014, Rohit Yadav  wrote:

> Hi Karl,
>
> Karl Harris wrote:
>
>> What is the current framework used to test a Cloudstack Virtual Router
>> (SystemVM) in isolation aka without Management Server if any?
>>
>
> AFAIK we don't have any such testing/automation framework within Apache
> CloudStack.
>
>  I'd like to call a SystemVM script with a set of configuration parameters
>> (changes for VPCVrr, etc.) and observe the changes to the virtual routers
>> configuration.
>>
>> Since I will eventually need the ethernet connections to be added and
>> deleted I would like to aviod using ethernet to make the connection to the
>> SystemVM image. Ideally I don't want to change the SystemVM image from
>> what
>> is build by tools/appliance/build.sh.
>>
>>
> The SystemVM image and the agent is tightly coupled with CloudStack, you
> may have to change things in the build script (if you intend to
> add/remove/modify packages, files and contents).
>
>  How was this testing done in the past?
>>
>
> In the past, I would create a systemvm template, have CloudStack
> management to use it to boot up SSVMs, VRs etc. and ssh into them from
> their respective hosts on their link local IP. Then, I would change the
> internal state of the VM and check with management server to test things
> and see if it would fix the state itself, execute platform apis etc.
>
> There is/was no automation framework to do the testing so it was mostly
> manually. Any work in this regard would be great.
>
> Regards.
>
>
>> Thanks,
>>
>> Karl
>>
>>  Find out more about ShapeBlue and our range of CloudStack related
> services
>
> IaaS Cloud Design & Build iaas-cloud-design-and-build//>
> CSForge – rapid IaaS deployment framework
> CloudStack Consulting
> CloudStack Infrastructure Support cloudstack-infrastructure-support/>
> CloudStack Bootcamp Training Courses cloudstack-training/>
>
> This email and any attachments to it may be confidential and are intended
> solely for the use of the individual to whom it is addressed. Any views or
> opinions expressed are solely those of the author and do not necessarily
> represent those of Shape Blue Ltd or related companies. If you are not the
> intended recipient of this email, you must neither take any action based
> upon its contents, nor copy or show it to anyone. Please contact the sender
> if you believe you have received this email in error. Shape Blue Ltd is a
> company incorporated in England & Wales. ShapeBlue Services India LLP is a
> company incorporated in India and is operated under license from Shape Blue
> Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil
> and is operated under license from Shape Blue Ltd. ShapeBlue is a
> registered trademark.
>
>


Re: Review Request 23192: Adding Readme and run checkbox at the end of the installation. Also installing mysql connector

2014-07-08 Thread Rajani Karuturi
I believe this has nothing to do with nonoss. If I understand it right, nonoss 
modules are required for cloudstack to work with certain 3rd party stuff.

This one is just a helper to create a windows installer. It chose to use a mvn 
command to create the installer instead of shell/bat script. It should work 
with either nonoss or oss modules.
This is very similar to cloud.spec[1] we have which is used to create the rpm 
and which already has mysql-connector-java already listed as required package.

I think the right way would be to create independent git repos for 
deb/rpm/windows installers/packages.

In its current state, I don’t see it any different from other helper installer 
scripts we already have.

[1] 
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=blob_plain;f=packaging/centos63/cloud.spec;hb=HEAD

~Rajani



On 08-Jul-2014, at 9:56 am, Damoder Reddy 
mailto:damoder.re...@citrix.com>> wrote:

Ok,

To clarify the windows MSI will not build in the default profile. I have 
enabled a new profile "buildw" to build windows MSI installer which explicitly 
we need to pass similar to nonoss?

Is that sufficient to make it nonoss or still we need to move it under nonoss 
profile explicitly?

Thanks
Damoder/

-Original Message-
From: David Nalley [mailto:da...@gnsa.us]
Sent: Thursday, 3 July 2014 9:58 PM
To: dev@cloudstack.apache.org
Cc: Damoder Reddy; Koushik Das
Subject: Re: Review Request 23192: Adding Readme and run checkbox at the end of 
the installation. Also installing mysql connector

On Thu, Jul 3, 2014 at 12:08 PM, Chip Childers 
mailto:chipchild...@apache.org>> wrote:
On Thu, Jul 03, 2014 at 03:14:30PM +, Leo Simons wrote:
It looks like that maven pom on windows _by default_ downloads and
installs a variety of non-apache-license (and/or non-mit/bsd/variant
license) software. That shouldnąt really happen. The principle is one
of łleast surprise˛: As a user or developer who does not RTFM,
following the default commands/tools/etc, you should end up with a
more-or-less apache-licensed build result (*) that you can
redistribute the result under.

+1


But apache policy is that it is acceptable to provide scripts/build
tools/assistance to help those same users/developers do things that
they want to do. As long as they understand the legal situation they end up in.

I would recommend adding a "nonoss" maven profile that the
developer/user has to explicitly select in order to do those
downloads. As long as that option is described clearly, thatąs then
ok. See

 http://svn.apache.org/repos/asf/apr/apr/trunk/README

for an example of how to point out the license situation.

We already have the nonoss profile, so this is a pretty good fix for
the windows build issues noted above IMO.

Damoder/Koushik - please make this change.


Something similar is true by the way (IMHO, but as a project
cloudstack can definitely decide differently), for a possible MSI
script. Making an MSI script that prompts the user whether to
download mysql at the point of install, **clearly pointing out the
license situation** if they choose to do so, seems reasonable, and I
personally would not object to shipping _that_ kind of script as part of an 
apache source release.


+1 - that's a reasonable approach as well.  Damoder / Koushik - what
+do
you think about this approach?


I like this approach. We have a number of things that aren't in the 'default' 
build because of policy reasons. This is just another of them.



Finally, the _spirit_ behind the apache policies is that there should
be an option to use cloudstack with a license-compatible database
(say, postgres), even if most users will use mysql (just like most
people that use dbm with httpd will use berkely dbm, but you _can_
use something else). Itąs perhaps unfortunate that this isnąt
supported, but thatąs not apache policy, and given the license
situation of other system dependencies, I can imagine no-one here wants to make 
it a priority.

Yeah, that would be nice...  but somebody would have to decide that
they want to do that.



cheers,


Leo

PS: IANAL, but, a lot of this discussion is a bit beyond legal, and
is about choice/policy, and the policy is supposed to be based on
common sense much more than license stuff tends to be :)

Agreed - this is about policy not legality.




Re: [DISCUSS][PROPOSAL] git workflow

2014-07-08 Thread Daan Hoogland
Rohit, I agree with most and I am glad to see you prefer cherry-pick
over merges. I do not see why the PMC should drive defining the
standard. This is something that should be carried and cherished by
all developers.

On Tue, Jul 8, 2014 at 9:51 AM, Rohit Yadav  wrote:
> Hi,
>
>
> On Tue, Jul 1, 2014 at 3:39 AM, Sebastien Goasguen  wrote:
>
>> I would like to re-start this discussion.
>>
>
> Such a shame, this is not getting any attention.
>
>
>>
>> Rajani made some good points and someone mentioned Gitflow:
>>
>> http://nvie.com/posts/a-successful-git-branching-model/
>>
>> Thinking about our release procedure, we clearly need more tests and a CI.
>> However it looks like this is going to take some time.
>>
>
> I think too that this is going to take time, meanwhile a great way would be
> to self police?
>
> I would encourage every committer at least to learn to use git, handle git
> mess-ups, have a knowledge about various ACS 4.x branches, favour squashed
> commits and cherry-picking over branch merges, rebase on target branch
> (master) regularly, build often with unit tests before pushing to master
> (at least), test patches on local before merging them on master and other
> branches.
>
> @PMC: suggestion -- help drive defining a convention on committer workflow
> (refer nvie etc.), make it a requirement for all the committers (future and
> present) to learn/know (basic/novice) git, have knowledge about various ACS
> branches and release processes.
>
> Comments, suggestions?
>
> Regards.
>
>
>>
>> In the meantime I think there is nothing preventing us from agreeing to
>> 'git practices', we don't need tests or new infra, we just need to agree on
>> the git workflow.
>>
>> Right now Master is really a development branch, we should make it a
>> stable branch for production with very few commits.
>> This does not mean that we would release less, in contrary this would
>> ensure that a commit to master means it's a production release.
>>
>> In addition gitflow [1] does not do cherry-picks (gets back to Rajani's
>> point) everything is based on merges.
>>
>> I am of the opinion that git flow provides a nice process. It basically
>> freezes master. Development happens in a 'develop' branch, releases
>> branches are branched off of that and merged into master and back into
>> developetc
>>
>> Please read [1] it's a good read.
>>
>> And let's discuss,
>>
>> [1] http://nvie.com/posts/a-successful-git-branching-model/
>>
>> -Sebastien
>>
>> On Jun 2, 2014, at 11:58 PM, Rajani Karuturi 
>> wrote:
>>
>> > There is also the problem of cherry-picking.
>> > As a contributor, I always endup creating multiple patches for each
>> branch as they don't cleanly apply on the upward branches. which means
>> distinct commits for each branch and I don't easily know which all branches
>> my commit exists unless I do grep.
>> > if we follow merging strategy properly, apart from the first merge of
>> the branch, everything else on top of it should be a painless merge.
>> >
>> >
>> >
>> > ~Rajani
>> >
>> >
>> >
>> > On 02-Jun-2014, at 10:51 pm, Marcus  wrote:
>> >
>> >> I think many of the bullet points are what we are currently doing
>> >> (guidelines for commit comments, feature branches need to stay in sync
>> with
>> >> master, no back-merging). I also think that much of what we do now is
>> done
>> >> the way it is simply because there *are* vast changes between versions.
>> >> Classes are getting shuffled around and changed all the time. If its
>> >> feasible to merge branch fixes to master, that's fine, but some quick
>> tests
>> >> seem to indicate that this will be messy getting started.
>> >>
>> >> That leaves us with how we do releases. I'm fine with having single
>> >> branches for major releases(4.3) and tagging the commits where each
>> >> incremental release (4.3.x) is done. I'm trying to remember why we went
>> >> with the -forward, I'm sure it's in the mailing list somewhere, but one
>> of
>> >> the nice things it provides is the ability for the release manager to
>> >> control what changes are made during code freeze while giving people a
>> >> place to stage fixes (though admittedly this is not always followed).
>> >> Without -forward, would the flow be for each dev to have their own repo
>> and
>> >> issue pull requests for bugfixes?
>> >>
>> >>
>> >> On Mon, Jun 2, 2014 at 3:17 AM, Rajani Karuturi <
>> rajani.karut...@citrix.com>
>> >> wrote:
>> >>
>> >>> Any other suggestions/objections/comments??
>> >>> Can we discuss this in detail and agree to a process??
>> >>>
>> >>>
>> >>> ~Rajani
>> >>>
>> >>>
>> >>>
>> >>> On 02-Jun-2014, at 9:32 am, Rajani Karuturi <
>> rajani.karut...@citrix.com>
>> >>> wrote:
>> >>>
>>  Yes as mike said, if its a one-off case we can do a empty merge(merge
>> -s
>> >>> ours) for it and git will assume its merged but will not bring in any
>> >>> changes.
>> 
>>  If the branches diverged a lot, for example after a major rewrite, we
>> >>> could stop merging to that bra

Re: Review Request 23282: CLOUDSTACK-6845 : First Code drop for NuageVsp Network plugin

2014-07-08 Thread Hugo Trippaers

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


Hey Suresh,

Great to see this review, happy to help integrate the NuageVsp code into 
CloudStack. I did an initial review an put my first feedback in the line 
comments. I haven't tested functionality or tried to apply the patch yet, but 
will do that after you had a chance to review these comments.

Cheers,

Hugo


client/tomcatconf/log4j-cloud.xml.in


Why do you introduce a new logfile specific for Nuage? Isn't is easier for 
admins if all cloudstack related messages appear in the already existing 
logfile that admins are familiar with?



plugins/network-elements/nuage-vsp/resources/META-INF/cloudstack/vsp/vsp-defaults.ini


Missing Apache License Header



plugins/network-elements/nuage-vsp/resources/META-INF/cloudstack/vsp/vsp-defaults.ini


Why introduce another configuration file? CloudStack provides options to 
set configuration using either network service provides or global 
configuration. 



plugins/network-elements/nuage-vsp/resources/META-INF/cloudstack/vsp/vsp-defaults.ini


Please do not make any assumptions on the locations of jar files. That is 
up to the people doing the packaging and might vary from distribution to 
distribution. Expect everything to be available using the web app class loader.



plugins/network-elements/nuage-vsp/src/com/cloud/network/resource/NuageVspResource.java


Don't depend on file locations as they will change. Use the java class 
loader to load any libraries.



plugins/network-elements/nuage-vsp/src/com/cloud/network/resource/NuageVspResource.java


I'm not really agreeing with this method of loading the client. The client 
should be loaded using the classloader.

Is the library available from maven central or is distribution restricted? 
If the latter case we need to move this plugin and the dependency on the 
library to the noredist build.



plugins/network-elements/nuage-vsp/test/com/cloud/network/element/NuageVspElementTest.java


copy-paste error ;-)



server/src/com/cloud/network/vpc/VpcManagerImpl.java


Depending on a size here looks like a bug waiting to happen when somebody 
adds an element. Is there another way to solve this?



setup/db/create-schema.sql


Modifying create-schema.sql is not allowed. Please make all necessary 
database changes in the upgrade scripts for the current master branch.


- Hugo Trippaers


On July 7, 2014, 6 p.m., Suresh Ramamurthy wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/23282/
> ---
> 
> (Updated July 7, 2014, 6 p.m.)
> 
> 
> Review request for cloudstack and Hugo Trippaers.
> 
> 
> Bugs: CLOUDSTACK-6845
> https://issues.apache.org/jira/browse/CLOUDSTACK-6845
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> This is first code drop for NuageVsp Network plugin support that will bring 
> the Nuage VSP network virtualization technology to CloudStack.
> 
> We need a new branch to checkin the fixes once the review is done. Please 
> create a new branch for NuageVsp plugin.
> 
> 
> Diffs
> -
> 
>   api/src/com/cloud/event/EventTypes.java 5b9ea5c 
>   api/src/com/cloud/network/Network.java 885bffe 
>   api/src/com/cloud/network/Networks.java 1e4d229 
>   api/src/com/cloud/network/PhysicalNetwork.java 8cc214e 
>   build/replace.properties 265f335 
>   client/WEB-INF/classes/resources/messages.properties b192cb0 
>   client/WEB-INF/classes/resources/messages_zh_CN.properties 1ec4e95 
>   client/pom.xml 29fef4f 
>   client/tomcatconf/commands.properties.in b9ac27b 
>   client/tomcatconf/log4j-cloud.xml.in 08021f2 
>   packaging/debian/replace.properties 5a0bd58 
>   
> plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/OvsVifDriver.java
>  8e4c710 
>   
> plugins/hypervisors/vmware/src/com/cloud/hypervisor/vmware/resource/VmwareResource.java
>  5b49e5b 
>   
> plugins/hypervisors/xenserver/src/com/cloud/hypervisor/xenserver/resource/CitrixResourceBase.java
>  a9840bd 
>   plugins/network-elements/nuage-vsp/pom.xml PRE-CREATION 
>   
> plugins/network-elements/nuage-vsp/resources/META-INF/cloudstack/vsp/module.properties
>  PRE-CREATION 
>   
> plugins/network-elements/nuage-vsp/resources/META-INF/cl

Re: Review Request 23169: CLOUDSTACK-7010: Add domain to createZones in marvin

2014-07-08 Thread John Dilley

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

(Updated July 8, 2014, 9:48 a.m.)


Review request for cloudstack and Santhosh Edukulla.


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


Repository: cloudstack-git


Description
---

Add domain to createZones in deployDataCenter


Diffs
-

  tools/marvin/marvin/configGenerator.py 8d9 
  tools/marvin/marvin/deployDataCenter.py c097238 

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


Testing
---

Tested deployDataCenter, both with and without specifying a domain


Thanks,

John Dilley



Re: Review Request 23169: CLOUDSTACK-7010: Add domain to createZones in marvin

2014-07-08 Thread John Dilley


> On July 1, 2014, 3 p.m., Santhosh Edukulla wrote:
> > tools/marvin/marvin/configGenerator.py, line 91
> > 
> >
> > Does cfg, files used has these option of domain?
> > 
> > As well, please test it on both 4.4-forward and master, if it need to 
> > go to both?
> 
> John Dilley wrote:
> > Does cfg, files used has these option of domain?
> 
> Hi Santhosh,
> 
> Not quite sure what you mean here - can you clarify?
> 
> Thanks,
> 
> John
> 
> Santhosh Edukulla wrote:
> I mean, does cfg file say advanced.cfg requires this flag, as well, what 
> if zone.domain is None, does createZone command leads to any issue?
> 
> John Dilley wrote:
> No problem if zone.domain is not specified - createZone will behave as 
> before, not specifying a domain (and will default to cs.internal)
> 
> Santhosh Edukulla wrote:
> Ok, can you please mention the bugid, and related branches information 
> for this review submission?

Added above.


- John


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


On July 8, 2014, 9:48 a.m., John Dilley wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/23169/
> ---
> 
> (Updated July 8, 2014, 9:48 a.m.)
> 
> 
> Review request for cloudstack and Santhosh Edukulla.
> 
> 
> Bugs: CLOUDSTACK-7010
> https://issues.apache.org/jira/browse/CLOUDSTACK-7010
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Add domain to createZones in deployDataCenter
> 
> 
> Diffs
> -
> 
>   tools/marvin/marvin/configGenerator.py 8d9 
>   tools/marvin/marvin/deployDataCenter.py c097238 
> 
> Diff: https://reviews.apache.org/r/23169/diff/
> 
> 
> Testing
> ---
> 
> Tested deployDataCenter, both with and without specifying a domain
> 
> 
> Thanks,
> 
> John Dilley
> 
>



Re: Review Request 22863: CLOUDSTACK-6823 : First code drop for Brocade Network plugin to orchestrate Brocade VDX switches for L2 connectivity.

2014-07-08 Thread Ritu Sabharwal

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

(Updated July 8, 2014, 9:30 a.m.)


Review request for cloudstack and Hugo Trippaers.


Changes
---

Add the dependency on the plugin code


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


Repository: cloudstack-git


Description
---

First code drop for Brocade Network plugin to orchestrate Brocade VDX switches 
for L2 connectivity. Please create a new branch for Brocade plugin.


Diffs
-

  api/src/com/cloud/network/Network.java 885bffe 
  api/src/com/cloud/network/Networks.java 1e4d229 
  api/src/com/cloud/network/PhysicalNetwork.java 8cc214e 
  client/pom.xml 29fef4f 
  plugins/pom.xml b5e6a61 
  setup/db/db/schema-440to450.sql 77445a9 
  ui/scripts/system.js 9a98a5c 

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


Testing
---

•   Create an isolated network; verify that the port-profile is created on 
the Brocade switch.
•   Attach a VM to the network; verify that the VMs MAC address is 
associated with the port profile of the network on the Brocade switch.
•   Delete VMs for an isolated network; verify that the VMs MAC address is 
disassociated with the port profile of the network on the Brocade switch.
•   Delete the isolated network; verify that the port-profile is deleted 
from the Brocade switch.


File Attachments


Diff for the existing cloudstack code
  
https://reviews.apache.org/media/uploaded/files/2014/06/23/8fc3cfb1-7a21-4714-98f3-6514cf54ba84__diff
Patch file for Brocade functionality code
  
https://reviews.apache.org/media/uploaded/files/2014/06/26/92bb0014-a7b7-4f0b-97c9-018d615b658a__brocade-vcs.patch


Thanks,

Ritu  Sabharwal



Re: Review Request 23314: Plugin specific code for the Brocade Network Plugin

2014-07-08 Thread Hugo Trippaers

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


Thanks for make this a separate review, much easier to read.

The licenses are not added to all files and in some files they appear not to be 
complete. A good trick to solve this is to include the license-maven-plugin in 
the build section. See plugins/network-elements/nicira-nvp/pom.xml for an 
example.

Also the plugin doesn't contain any tests. We need unit tests or functional 
tests (and preferably both) to validate that this plugin works and keeps on 
working in future versions of CloudStack. It would be great if you could supply 
unit tests to validate this inner workings of this module and marvin based 
integration tests that we can run to see if this work with the intended 
hardware.

The last general point is that we would also need documentation on this plugin 
so administrators will know how to use this.


plugins/network-elements/brocade-vcs/src/com/cloud/network/brocade/CacheManager.java


You should get all properties from the CloudStack configuration mechanism. 
Either via the global config or via the settings on the network service 
provider configuration (preferred)



plugins/network-elements/brocade-vcs/src/com/cloud/network/brocade/CacheManager.java


This looks like something that should be persisted in the cloudstack 
database instead of stored outside cloudstack.



plugins/network-elements/brocade-vcs/src/com/cloud/network/guru/BrocadeVcsGuestNetworkGuru.java


Please remove commented code.



plugins/network-elements/brocade-vcs/src/com/cloud/network/guru/BrocadeVcsGuestNetworkGuru.java


This TODO is fixed right?


- Hugo Trippaers


On July 7, 2014, 7:08 p.m., Ritu  Sabharwal wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/23314/
> ---
> 
> (Updated July 7, 2014, 7:08 p.m.)
> 
> 
> Review request for cloudstack.
> 
> 
> Bugs: CLOUDSTACK-6823
> https://issues.apache.org/jira/browse/CLOUDSTACK-6823
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> Plugin specific code.
> 
> 
> Diffs
> -
> 
>   plugins/network-elements/brocade-vcs/pom.xml PRE-CREATION 
>   plugins/network-elements/brocade-vcs/resources/BrocadeInterfaceSchema.xsd 
> PRE-CREATION 
>   plugins/network-elements/brocade-vcs/resources/BrocadePortProfileSchema.xsd 
> PRE-CREATION 
>   plugins/network-elements/brocade-vcs/resources/BrocadeShowVcsSchema.xsd 
> PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/resources/META-INF/cloudstack/vcs/module.properties
>  PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/resources/META-INF/cloudstack/vcs/spring-vcs-context.xml
>  PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/src/com/cloud/agent/api/AssociateMacToNetworkAnswer.java
>  PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/src/com/cloud/agent/api/AssociateMacToNetworkCommand.java
>  PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/src/com/cloud/agent/api/CreateNetworkAnswer.java
>  PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/src/com/cloud/agent/api/CreateNetworkCommand.java
>  PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/src/com/cloud/agent/api/DeleteNetworkAnswer.java
>  PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/src/com/cloud/agent/api/DeleteNetworkCommand.java
>  PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/src/com/cloud/agent/api/DisassociateMacFromNetworkAnswer.java
>  PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/src/com/cloud/agent/api/DisassociateMacFromNetworkCommand.java
>  PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/src/com/cloud/agent/api/StartupBrocadeVcsCommand.java
>  PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/src/com/cloud/network/BrocadeVcsNetworkHostMappingVO.java
>  PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/src/com/cloud/network/brocade/BrocadeVcsApi.java
>  PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/src/com/cloud/network/brocade/BrocadeVcsApiException.java
>  PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/src/com/cloud/network/brocade/Cache.java 
> PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/src/com/cloud/network/brocade/CacheManager.java
>  PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/src/com/cloud/network/brocade/Constants.java
>  PRE-CREATION 
>   
> plugins/network-elements/brocade-vcs/src/com/cloud/network/brocade/Switch.java
>  PRE-CREATION 
>   
> plugins

Re: Review Request 22927: Bugfix CLOUDSTACK-6261: remove the forceful timeout setting when login to NetScaler.

2014-07-08 Thread Sujaya Maiyya

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

(Updated July 8, 2014, 9:28 a.m.)


Review request for cloudstack, Murali Reddy and Rajesh Battala.


Changes
---

The whitespace errors in the patch are fixed.


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


Repository: cloudstack-git


Description
---

The NetScaler Resource forces a idle timeout of 100,000 seconds during login. 
It is best to leave it to the system default which is 30 mins. The timeout has 
been removed from NetscalerResource in order to support login for Netscaler 
10.5 devices.


Diffs (updated)
-

  
plugins/network-elements/netscaler/src/com/cloud/network/resource/NetscalerResource.java
 ff51ef9 

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


Testing
---

Timeout was removed and login to the Netscaler devices with the default timeout 
of 30 minutes was successful. It was tested for Netscaler builds 10.1 and 10.5.


Thanks,

Sujaya Maiyya



Re: Ubuntu noredist

2014-07-08 Thread Wido den Hollander

On 07/07/2014 09:13 AM, Hugo Trippaers wrote:

Hey Wido,

This is particular ticket is about the mysql Ha module. It is part of the 
noredist build as we have a build time dependency on the mysql connector. The 
module also needs to be installed in a specific location in order to be loaded 
by the tomcat system class loader instead of the web app class loader.



Ok, I have no clue what that MySQL module does. So I'm not sure how to 
implement this on Ubuntu.


Wido


Cheers,

Hugo


On 7 jul. 2014, at 07:32, Wido den Hollander  wrote:




On 07/04/2014 08:48 PM, Wido den Hollander wrote:



On 07/04/2014 03:36 PM, Sebastien Goasguen wrote:

Hi,

To fix: http://issues.apache.org/jira/browse/CLOUDSTACK-6892 on ubuntu
we need a noredist build.

anyone using Ubuntu out there, could check out the fix that was done
for CentOS and provide a patch for Ubuntu ?


I'll see if I can come up with a patch over the weekend!



Ah, so this is about a noredist package for the MySQL connector and there is no 
'noredist' architecture at all in the Debian packages.

Currently the Debian packages simply depend on libmysql-java, so shouldn't that 
be sufficient?

Wido


Wido



thanks,

-Sebastien








Re: Testing a Cloudstack Virtual Router (SystemVM).

2014-07-08 Thread Rohit Yadav

Hi Karl,

Karl Harris wrote:

What is the current framework used to test a Cloudstack Virtual Router
(SystemVM) in isolation aka without Management Server if any?


AFAIK we don't have any such testing/automation framework within Apache 
CloudStack.


I'd like to call a SystemVM script with a set of configuration parameters
(changes for VPCVrr, etc.) and observe the changes to the virtual routers
configuration.

Since I will eventually need the ethernet connections to be added and
deleted I would like to aviod using ethernet to make the connection to the
SystemVM image. Ideally I don't want to change the SystemVM image from what
is build by tools/appliance/build.sh.



The SystemVM image and the agent is tightly coupled with CloudStack, you may 
have to change things in the build script (if you intend to add/remove/modify 
packages, files and contents).


How was this testing done in the past?


In the past, I would create a systemvm template, have CloudStack management to 
use it to boot up SSVMs, VRs etc. and ssh into them from their respective hosts 
on their link local IP. Then, I would change the internal state of the VM and 
check with management server to test things and see if it would fix the state 
itself, execute platform apis etc.

There is/was no automation framework to do the testing so it was mostly 
manually. Any work in this regard would be great.

Regards.



Thanks,

Karl


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

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

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


Re: [DISCUSS][PROPOSAL] git workflow

2014-07-08 Thread Rohit Yadav
Hi,


On Tue, Jul 1, 2014 at 3:39 AM, Sebastien Goasguen  wrote:

> I would like to re-start this discussion.
>

Such a shame, this is not getting any attention.


>
> Rajani made some good points and someone mentioned Gitflow:
>
> http://nvie.com/posts/a-successful-git-branching-model/
>
> Thinking about our release procedure, we clearly need more tests and a CI.
> However it looks like this is going to take some time.
>

I think too that this is going to take time, meanwhile a great way would be
to self police?

I would encourage every committer at least to learn to use git, handle git
mess-ups, have a knowledge about various ACS 4.x branches, favour squashed
commits and cherry-picking over branch merges, rebase on target branch
(master) regularly, build often with unit tests before pushing to master
(at least), test patches on local before merging them on master and other
branches.

@PMC: suggestion -- help drive defining a convention on committer workflow
(refer nvie etc.), make it a requirement for all the committers (future and
present) to learn/know (basic/novice) git, have knowledge about various ACS
branches and release processes.

Comments, suggestions?

Regards.


>
> In the meantime I think there is nothing preventing us from agreeing to
> 'git practices', we don't need tests or new infra, we just need to agree on
> the git workflow.
>
> Right now Master is really a development branch, we should make it a
> stable branch for production with very few commits.
> This does not mean that we would release less, in contrary this would
> ensure that a commit to master means it's a production release.
>
> In addition gitflow [1] does not do cherry-picks (gets back to Rajani's
> point) everything is based on merges.
>
> I am of the opinion that git flow provides a nice process. It basically
> freezes master. Development happens in a 'develop' branch, releases
> branches are branched off of that and merged into master and back into
> developetc
>
> Please read [1] it's a good read.
>
> And let's discuss,
>
> [1] http://nvie.com/posts/a-successful-git-branching-model/
>
> -Sebastien
>
> On Jun 2, 2014, at 11:58 PM, Rajani Karuturi 
> wrote:
>
> > There is also the problem of cherry-picking.
> > As a contributor, I always endup creating multiple patches for each
> branch as they don't cleanly apply on the upward branches. which means
> distinct commits for each branch and I don't easily know which all branches
> my commit exists unless I do grep.
> > if we follow merging strategy properly, apart from the first merge of
> the branch, everything else on top of it should be a painless merge.
> >
> >
> >
> > ~Rajani
> >
> >
> >
> > On 02-Jun-2014, at 10:51 pm, Marcus  wrote:
> >
> >> I think many of the bullet points are what we are currently doing
> >> (guidelines for commit comments, feature branches need to stay in sync
> with
> >> master, no back-merging). I also think that much of what we do now is
> done
> >> the way it is simply because there *are* vast changes between versions.
> >> Classes are getting shuffled around and changed all the time. If its
> >> feasible to merge branch fixes to master, that's fine, but some quick
> tests
> >> seem to indicate that this will be messy getting started.
> >>
> >> That leaves us with how we do releases. I'm fine with having single
> >> branches for major releases(4.3) and tagging the commits where each
> >> incremental release (4.3.x) is done. I'm trying to remember why we went
> >> with the -forward, I'm sure it's in the mailing list somewhere, but one
> of
> >> the nice things it provides is the ability for the release manager to
> >> control what changes are made during code freeze while giving people a
> >> place to stage fixes (though admittedly this is not always followed).
> >> Without -forward, would the flow be for each dev to have their own repo
> and
> >> issue pull requests for bugfixes?
> >>
> >>
> >> On Mon, Jun 2, 2014 at 3:17 AM, Rajani Karuturi <
> rajani.karut...@citrix.com>
> >> wrote:
> >>
> >>> Any other suggestions/objections/comments??
> >>> Can we discuss this in detail and agree to a process??
> >>>
> >>>
> >>> ~Rajani
> >>>
> >>>
> >>>
> >>> On 02-Jun-2014, at 9:32 am, Rajani Karuturi <
> rajani.karut...@citrix.com>
> >>> wrote:
> >>>
>  Yes as mike said, if its a one-off case we can do a empty merge(merge
> -s
> >>> ours) for it and git will assume its merged but will not bring in any
> >>> changes.
> 
>  If the branches diverged a lot, for example after a major rewrite, we
> >>> could stop merging to that branch and above and make the fix manually.
> 
> 
>  ~Rajani
> 
> 
> 
>  On 30-May-2014, at 11:26 pm, Mike Tutkowski <
> >>> mike.tutkow...@solidfire.com> wrote:
> 
> > Yep, that's what I was referring to in that a particular fix for an
> old
> > release may not apply to newer versions. That does happen.
> >
> > We used to mark those as "don't need to merge to branch x" i