SDN compat matrix

2013-11-17 Thread Hugo Trippaers 
Hey guys,

I’m building the compatibility matrix for our SDN plugins to use in my 
presentation for CCCEU13. I think i got everything in there, but would like to 
check it against your combined knowledge:

GRE isolation
supports L2 isolation
XenServer supported since pre ACS
KVM supported since pre ACS
(not taking son extensions branch into account yet)
VXLAN
supports L2 isolation
KVM supported since master (4.3)
Nicira NVP
supports L2 isolation
supports L3 NAT function since 4.1
supports VPC networks
XenServer supported since 4.0
KVM supported since 4.1
VMware supported since 4.2
Midokura
supports L2 isolation
supports L3 NAT, DHCP, Firewall
supports VPC networks
KVM supported since 4.2
Stratosphere
supports L2 isolation
KVM supported since 4.2
Contrail
supports L2 isolation
supports L3 NAT, DHCP
Xenserver supported since master
KVM supported since master


Anything i forgot here?

Cheers,

Hugo

Re: SDN compat matrix

2013-11-17 Thread David Nalley 
Big switch?
On Nov 17, 2013 5:41 AM, "Hugo Trippaers"  wrote:

> Hey guys,
>
> I’m building the compatibility matrix for our SDN plugins to use in my
> presentation for CCCEU13. I think i got everything in there, but would like
> to check it against your combined knowledge:
>
> GRE isolation
> supports L2 isolation
> XenServer supported since pre ACS
> KVM supported since pre ACS
> (not taking son extensions branch into account yet)
> VXLAN
> supports L2 isolation
> KVM supported since master (4.3)
> Nicira NVP
> supports L2 isolation
> supports L3 NAT function since 4.1
> supports VPC networks
> XenServer supported since 4.0
> KVM supported since 4.1
> VMware supported since 4.2
> Midokura
> supports L2 isolation
> supports L3 NAT, DHCP, Firewall
> supports VPC networks
> KVM supported since 4.2
> Stratosphere
> supports L2 isolation
> KVM supported since 4.2
> Contrail
> supports L2 isolation
> supports L3 NAT, DHCP
> Xenserver supported since master
> KVM supported since master
>
>
> Anything i forgot here?
>
> Cheers,
>
> Hugo

Re: SDN compat matrix

2013-11-17 Thread David Nalley 
Bah autocorrect Bigswitch
On Nov 17, 2013 9:50 AM, "David Nalley"  wrote:

> Big switch?
> On Nov 17, 2013 5:41 AM, "Hugo Trippaers"  wrote:
>
>> Hey guys,
>>
>> I’m building the compatibility matrix for our SDN plugins to use in my
>> presentation for CCCEU13. I think i got everything in there, but would like
>> to check it against your combined knowledge:
>>
>> GRE isolation
>> supports L2 isolation
>> XenServer supported since pre ACS
>> KVM supported since pre ACS
>> (not taking son extensions branch into account yet)
>> VXLAN
>> supports L2 isolation
>> KVM supported since master (4.3)
>> Nicira NVP
>> supports L2 isolation
>> supports L3 NAT function since 4.1
>> supports VPC networks
>> XenServer supported since 4.0
>> KVM supported since 4.1
>> VMware supported since 4.2
>> Midokura
>> supports L2 isolation
>> supports L3 NAT, DHCP, Firewall
>> supports VPC networks
>> KVM supported since 4.2
>> Stratosphere
>> supports L2 isolation
>> KVM supported since 4.2
>> Contrail
>> supports L2 isolation
>> supports L3 NAT, DHCP
>> Xenserver supported since master
>> KVM supported since master
>>
>>
>> Anything i forgot here?
>>
>> Cheers,
>>
>> Hugo
>
>

Re: SDN compat matrix

2013-11-17 Thread Chiradeep Vittal 
Also BigSwitch VNS 4.2

--
Chiradeep

> On Nov 17, 2013, at 2:40 AM, "Hugo Trippaers"  wrote:
> 
> Hey guys,
> 
> I’m building the compatibility matrix for our SDN plugins to use in my 
> presentation for CCCEU13. I think i got everything in there, but would like 
> to check it against your combined knowledge:
> 
> GRE isolation
>supports L2 isolation
>XenServer supported since pre ACS
>KVM supported since pre ACS
>(not taking son extensions branch into account yet)
> VXLAN
>supports L2 isolation
>KVM supported since master (4.3)
> Nicira NVP
>supports L2 isolation
>supports L3 NAT function since 4.1
>supports VPC networks
>XenServer supported since 4.0
>KVM supported since 4.1
>VMware supported since 4.2
> Midokura
>supports L2 isolation
>supports L3 NAT, DHCP, Firewall
>supports VPC networks
>KVM supported since 4.2
> Stratosphere
>supports L2 isolation
>KVM supported since 4.2
> Contrail
>supports L2 isolation
>supports L3 NAT, DHCP
>Xenserver supported since master
>KVM supported since master
> 
> 
> Anything i forgot here?
> 
> Cheers,
> 
> Hugo

Re: [DOC] 4.2.0 Templates

2013-11-17 Thread Marty Sweet 
Hi Sebastien,

Thanks for looking at this, what repo should I be committing to/pulling
from? I can't find anything solid on confluence.

Marty


On Fri, Nov 8, 2013 at 9:15 AM, Sebastien Goasguen  wrote:

>
> On Oct 27, 2013, at 7:02 AM, Marty Sweet  wrote:
>
> > Hi,
> >
> > Is there any update on this?
> > My commit
> >
> https://github.com/apache/cloudstack/commit/f5e7f46dadda741f10e5b674d0578ade9ba719d7
> > made
> > it into the 4.2.0 docs but
> >
> https://github.com/apache/cloudstack/commit/922ef76224d4a8534f67f47b97cf664e5c65ecba
> > hasn't,
> > I have gone to use this several times just to remember it's not there :)
>
> Marty, I commented on your patch:
> https://reviews.apache.org/r/13745/
>
> Seems to me your patch was lost somehow in the move to the new repo.
>
> Can you also make sure that you have your author info in there, otherwise
> we loose the authorship info.
> Just use git config to set your name and email in your patch.
>
> thanks,
>
> -sebastien
>
> >
> > Thanks,
> > Marty
> >
> >
> > On Thu, Oct 10, 2013 at 10:05 AM, Daan Hoogland  >wrote:
> >
> >> Marty,
> >>
> >> As I understand the master branch for docs will be filled as work on
> >> it starts. the ones in the 4.2 branch are the current ones.
> >>
> >> btw commits get hidden, rarely lost :p
> >>
> >> regards,
> >>
> >> On Thu, Oct 10, 2013 at 8:29 AM, Marty Sweet 
> wrote:
> >>> Where will the docs commited to the master become available? This
> >> probably
> >>> isn't the only case where commits have been lost?
> >>>
> >>> https://reviews.apache.org/r/13745/
> >>>
> >>>
> >>>
> >>> On Thu, Oct 10, 2013 at 1:17 AM, Radhika Puthiyetath <
> >>> radhika.puthiyet...@citrix.com> wrote:
> >>>
>  4.2 docs are from 4.2 branch.
> 
>  -Original Message-
>  From: Marty Sweet [mailto:msweet@gmail.com]
>  Sent: Thursday, October 10, 2013 3:27 AM
>  To: dev@cloudstack.apache.org
>  Subject: Re: [DOC] 4.2.0 Templates
> 
>  Hi Daan,
> 
>  Yeah the doc directory in the repo commited to master, where is the
>  current
> 
> >>
> http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/Admin_Guide/working-with-templates.html
>  being
>  built from?
> 
>  Marty
> 
> 
>  On Wed, Oct 9, 2013 at 8:55 PM, Daan Hoogland <
> daan.hoogl...@gmail.com
> > wrote:
> 
> > Marty,
> >
> > I am not sure what you mean. Do you mean the doc dir in the repo? I
> > think you need to look in
> > https://git-wip-us.apache.org/repos/asf/cloudstack-docs.git for the
> > 4.2 docs.
> >
> > regards,
> > Daan
> >
> > On Sun, Oct 6, 2013 at 10:51 PM, Marty Sweet 
>  wrote:
> >> Hi guys,
> >>
> >> I created a document for creating Linux documentation for the 4.2.0
> >> release. Checking the documentation it seems that it is not there?
> >> Is
> > there
> >> any reason for this?
> >>
> >>
> >
> >> http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/A
> > dmin_Guide/working-with-templates.html
> >>
> >>
> >
> >> https://github.com/apache/cloudstack/commit/922ef76224d4a8534f67f47b97
> > cf664e5c65ecba
> >> https://issues.apache.org/jira/browse/CLOUDSTACK-4329
> >>
> >> Thanks,
> >> Marty
> >
> 
> >>
>
>

Re: [DOC] 4.2.0 Templates

2013-11-17 Thread Marty Sweet 
Jumped the gun! Is this the correct one:
https://github.com/apache/cloudstack-docs ?

4.2 or master?

Marty


On Sun, Nov 17, 2013 at 3:56 PM, Marty Sweet  wrote:

> Hi Sebastien,
>
> Thanks for looking at this, what repo should I be committing to/pulling
> from? I can't find anything solid on confluence.
>
> Marty
>
>
> On Fri, Nov 8, 2013 at 9:15 AM, Sebastien Goasguen wrote:
>
>>
>> On Oct 27, 2013, at 7:02 AM, Marty Sweet  wrote:
>>
>> > Hi,
>> >
>> > Is there any update on this?
>> > My commit
>> >
>> https://github.com/apache/cloudstack/commit/f5e7f46dadda741f10e5b674d0578ade9ba719d7
>> > made
>> > it into the 4.2.0 docs but
>> >
>> https://github.com/apache/cloudstack/commit/922ef76224d4a8534f67f47b97cf664e5c65ecba
>> > hasn't,
>> > I have gone to use this several times just to remember it's not there :)
>>
>> Marty, I commented on your patch:
>> https://reviews.apache.org/r/13745/
>>
>> Seems to me your patch was lost somehow in the move to the new repo.
>>
>> Can you also make sure that you have your author info in there, otherwise
>> we loose the authorship info.
>> Just use git config to set your name and email in your patch.
>>
>> thanks,
>>
>> -sebastien
>>
>> >
>> > Thanks,
>> > Marty
>> >
>> >
>> > On Thu, Oct 10, 2013 at 10:05 AM, Daan Hoogland <
>> daan.hoogl...@gmail.com>wrote:
>> >
>> >> Marty,
>> >>
>> >> As I understand the master branch for docs will be filled as work on
>> >> it starts. the ones in the 4.2 branch are the current ones.
>> >>
>> >> btw commits get hidden, rarely lost :p
>> >>
>> >> regards,
>> >>
>> >> On Thu, Oct 10, 2013 at 8:29 AM, Marty Sweet 
>> wrote:
>> >>> Where will the docs commited to the master become available? This
>> >> probably
>> >>> isn't the only case where commits have been lost?
>> >>>
>> >>> https://reviews.apache.org/r/13745/
>> >>>
>> >>>
>> >>>
>> >>> On Thu, Oct 10, 2013 at 1:17 AM, Radhika Puthiyetath <
>> >>> radhika.puthiyet...@citrix.com> wrote:
>> >>>
>>  4.2 docs are from 4.2 branch.
>> 
>>  -Original Message-
>>  From: Marty Sweet [mailto:msweet@gmail.com]
>>  Sent: Thursday, October 10, 2013 3:27 AM
>>  To: dev@cloudstack.apache.org
>>  Subject: Re: [DOC] 4.2.0 Templates
>> 
>>  Hi Daan,
>> 
>>  Yeah the doc directory in the repo commited to master, where is the
>>  current
>> 
>> >>
>> http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/Admin_Guide/working-with-templates.html
>>  being
>>  built from?
>> 
>>  Marty
>> 
>> 
>>  On Wed, Oct 9, 2013 at 8:55 PM, Daan Hoogland <
>> daan.hoogl...@gmail.com
>> > wrote:
>> 
>> > Marty,
>> >
>> > I am not sure what you mean. Do you mean the doc dir in the repo? I
>> > think you need to look in
>> > https://git-wip-us.apache.org/repos/asf/cloudstack-docs.git for the
>> > 4.2 docs.
>> >
>> > regards,
>> > Daan
>> >
>> > On Sun, Oct 6, 2013 at 10:51 PM, Marty Sweet 
>>  wrote:
>> >> Hi guys,
>> >>
>> >> I created a document for creating Linux documentation for the 4.2.0
>> >> release. Checking the documentation it seems that it is not there?
>> >> Is
>> > there
>> >> any reason for this?
>> >>
>> >>
>> >
>> >> http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/A
>> > dmin_Guide/working-with-templates.html
>> >>
>> >>
>> >
>> >> https://github.com/apache/cloudstack/commit/922ef76224d4a8534f67f47b97
>> > cf664e5c65ecba
>> >> https://issues.apache.org/jira/browse/CLOUDSTACK-4329
>> >>
>> >> Thanks,
>> >> Marty
>> >
>> 
>> >>
>>
>>
>

Re: Review Request 15572: LDAP import users changes

2013-11-17 Thread Ian Duffy 

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


Rajani,

This introduces mixing of tabs and spaces within the javascript files. Can you 
please adjust to use spaces only?

Other than that it looks good.
I will ship once I see the above fixed.

Thanks,
Ian

- Ian Duffy


On Nov. 15, 2013, 11:50 a.m., Rajani Karuturi wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/15572/
> ---
> 
> (Updated Nov. 15, 2013, 11:50 a.m.)
> 
> 
> Review request for cloudstack, Abhinandan Prateek and Ian Duffy.
> 
> 
> Bugs: CLOUDSTACK-4866
> https://issues.apache.org/jira/browse/CLOUDSTACK-4866
> 
> 
> Repository: cloudstack-git
> 
> 
> Description
> ---
> 
> added LDAP group name label in add account wizard
> 
> changed the parameter for domain in api importLdapUser from name to UUID
> 
> improved error handling
> 
> 
> Diffs
> -
> 
>   client/WEB-INF/classes/resources/messages.properties 5885bd0 
>   
> plugins/user-authenticators/ldap/src/org/apache/cloudstack/api/command/LdapImportUsersCmd.java
>  063db0e 
>   
> plugins/user-authenticators/ldap/test/groovy/org/apache/cloudstack/ldap/LdapImportUsersCmdSpec.groovy
>  0455640 
>   ui/dictionary.jsp 0ccfc23 
>   ui/scripts/accountsWizard.js 70ef082 
>   ui/scripts/docs.js a3151b1 
>   ui/scripts/ui-custom/accountsWizard.js 358e29c 
> 
> Diff: https://reviews.apache.org/r/15572/diff/
> 
> 
> Testing
> ---
> 
> unit testing for all the java changes and manual testing for UI changes is 
> done.
> 
> 
> Thanks,
> 
> Rajani Karuturi
> 
>

Re: SDN compat matrix

2013-11-17 Thread Yoshikazu Nojima 
VXLAN supports VPC networks. It also supports L3 NAT, DHCP and
Firewall by utilizing CloudStack Virtual Router funtion for VLAN.

-Noji

2013/11/17 Chiradeep Vittal :
> Also BigSwitch VNS 4.2
>
> --
> Chiradeep
>
>> On Nov 17, 2013, at 2:40 AM, "Hugo Trippaers"  wrote:
>>
>> Hey guys,
>>
>> I’m building the compatibility matrix for our SDN plugins to use in my 
>> presentation for CCCEU13. I think i got everything in there, but would like 
>> to check it against your combined knowledge:
>>
>> GRE isolation
>>supports L2 isolation
>>XenServer supported since pre ACS
>>KVM supported since pre ACS
>>(not taking son extensions branch into account yet)
>> VXLAN
>>supports L2 isolation
>>KVM supported since master (4.3)
>> Nicira NVP
>>supports L2 isolation
>>supports L3 NAT function since 4.1
>>supports VPC networks
>>XenServer supported since 4.0
>>KVM supported since 4.1
>>VMware supported since 4.2
>> Midokura
>>supports L2 isolation
>>supports L3 NAT, DHCP, Firewall
>>supports VPC networks
>>KVM supported since 4.2
>> Stratosphere
>>supports L2 isolation
>>KVM supported since 4.2
>> Contrail
>>supports L2 isolation
>>supports L3 NAT, DHCP
>>Xenserver supported since master
>>KVM supported since master
>>
>>
>> Anything i forgot here?
>>
>> Cheers,
>>
>> Hugo

Re: CloudStack.next

2013-11-17 Thread Rohit Yadav 
Hi,

On Wed, Nov 13, 2013 at 5:11 AM, Steve Wilson wrote:

> Hi All,
>
> As we ramp towards freeze on 4.3 and start talking about 4.4, I thought it
> would be fun to queue up a discussion here on the list before Collab next
> week.
>
> What do you envision in the next MAJOR release of CloudStack?  Call it 5.0
> or whatever you like, but


If we're not changing/breaking APIs and since we had adopted semantic
versioning, we should not change the major version.


> what would you like to see there?  What would you change?


Few things I'm personally looking forward to is to have CloudStack have
better abilities and ease for controlling containers (lxc using docker or
what have you) and a being able to act as a container coordinator between
baremetal/virtual machines. I guess this is not a new request and we know
ACS already supports LXC but I would like to use ACS as a tool that works
for me to configure, deploy and manage containers using docker. In essence,
we can have something like a recipe, a DSL or infra-management-as-code to
automate infrastructure at a higher level just like we use Puppet or Chef,
we could have something for our infrastructure that just works.

 What would you enhance?


Probably next iteration of cloudmonkey and add tests (in my free time).


> Are there big bets we should be placing as a community?
>

There is a lot of architectural debt that CloudStack is paying for, maybe
we could introduce and implement cloud engine, new api services and the
other next gen stuff that we had discussed in that past; I would like to
contribute if that happens.

The cluster management service and the way agents and ACS mgmt server
communicate can be improved, things like Raft could be implemented as our
consensus problem is not solved (in case of network/io issue, the agents
and ACS mgmt server may have different view of the world, for example).

The codebase is monstrous, we can maybe bet of splitting every part as a
plugin and maybe move some code to other languages that are interoperable
and run on JVM like Scala. One motivation for this is the fact that a lot
of infrastructure code in the last one year has been written in Scala which
works perfectly with existing Java based ecosystem. Since I've some
experience of Scala and ACS's API layer, web services, plugin system, ACS's
ORM and build system I can think refactoring and rewriting stuff in Scala
would greatly reduce a lot of code while it would be still interoperable
with the rest of the components.

If you think about ACS from a top level bird's eye view, ACS is a big
resource consuming poorly written web app that takes in some request, spits
answers for read queries (sync commands) or enqueues in its job queue
(async jobs) and stores information what it knows about (from MySQL) and/or
cache (in/via DAOs). There are a lot of moving parts and SPOFs. If all
these components could be a ran as a separate service which could run on
different or same server, they could be cleanly separated and they can
become more testable, easier to understand, enhance and develop.

Just my views :)

Regards.



>
> Feel free to post any thoughts here and I'll look forward to talking to
> many of you in person at Collab next week.  You are coming to Collab, right?
>
> -Steve
>
> Steve Wilson
> VP, Cloud Engineering
> Citrix
> twitter: @virtualsteve
>

Re: SDN compat matrix

2013-11-17 Thread Sebastien Goasguen 

On Nov 17, 2013, at 12:24 PM, Yoshikazu Nojima  wrote:

> VXLAN supports VPC networks. It also supports L3 NAT, DHCP and
> Firewall by utilizing CloudStack Virtual Router funtion for VLAN.
> 
> -Noji
> 
> 2013/11/17 Chiradeep Vittal :
>> Also BigSwitch VNS 4.2
>> 
>> --
>> Chiradeep
>> 
>>> On Nov 17, 2013, at 2:40 AM, "Hugo Trippaers"  wrote:
>>> 
>>> Hey guys,
>>> 
>>> I’m building the compatibility matrix for our SDN plugins to use in my 
>>> presentation for CCCEU13. I think i got everything in there, but would like 
>>> to check it against your combined knowledge:
>>> 
>>> GRE isolation
>>>   supports L2 isolation
>>>   XenServer supported since pre ACS
>>>   KVM supported since pre ACS

Is that right ? I don't think KVM was supported pre ACS in GRE controller. 
Thought we only added it with Nguyen's work.

>>>   (not taking son extensions branch into account yet)
>>> VXLAN
>>>   supports L2 isolation
>>>   KVM supported since master (4.3)
>>> Nicira NVP
>>>   supports L2 isolation
>>>   supports L3 NAT function since 4.1
>>>   supports VPC networks
>>>   XenServer supported since 4.0
>>>   KVM supported since 4.1
>>>   VMware supported since 4.2
>>> Midokura
>>>   supports L2 isolation
>>>   supports L3 NAT, DHCP, Firewall
>>>   supports VPC networks
>>>   KVM supported since 4.2
>>> Stratosphere
>>>   supports L2 isolation
>>>   KVM supported since 4.2
>>> Contrail
>>>   supports L2 isolation
>>>   supports L3 NAT, DHCP
>>>   Xenserver supported since master
>>>   KVM supported since master
>>> 
>>> 
>>> Anything i forgot here?
>>> 
>>> Cheers,
>>> 
>>> Hugo

Review Request 15633: Bugfix CS-5079: Add guard against null pointer exception for listConfigurations API call, and set value to NULL if the pointer is null

2013-11-17 Thread Yichi Lu 

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

Review request for cloudstack.


Bugs: 5079
https://issues.apache.org/jira/browse/5079


Repository: cloudstack-git


Description
---

CLOUDSTACK-5079. When using api call, listConfigurations, and specifying 
clusterid, some keys may not have values. this causes a null pointer to be 
returned.
Add guard against null pointer in 
server/src/com/cloud/server/ConfigurationServerImpl.java::getConfigListByScope().
 If a null pointer is returned from 
framework/config/src/org/apache/cloudstack/framework/config/impl/ConfigDepotImpl.java::get(),
 set value to 'NULL'.


Diffs
-

  server/src/com/cloud/server/ConfigurationServerImpl.java 8459ada 

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


Testing
---

tested api calls for &listConfigurations, &listConfigurations&clusterid=xxx, 
&listConfigurations&zoneid=xxx,  &listConfigurations&category=Advanced


Thanks,

Yichi Lu

Re: CloudStack.next

2013-11-17 Thread Steve Wilson 
Lots of interesting ideas there.  Thanks for sharing!  BTW, I really share your 
interest in making CloudStack and Docker work really well together.

On Nov 17, 2013, at 9:57 AM, Rohit Yadav  wrote:

> Hi,
> 
> On Wed, Nov 13, 2013 at 5:11 AM, Steve Wilson wrote:
> 
>> Hi All,
>> 
>> As we ramp towards freeze on 4.3 and start talking about 4.4, I thought it
>> would be fun to queue up a discussion here on the list before Collab next
>> week.
>> 
>> What do you envision in the next MAJOR release of CloudStack?  Call it 5.0
>> or whatever you like, but
> 
> 
> If we're not changing/breaking APIs and since we had adopted semantic
> versioning, we should not change the major version.
> 
> 
>> what would you like to see there?  What would you change?
> 
> 
> Few things I'm personally looking forward to is to have CloudStack have
> better abilities and ease for controlling containers (lxc using docker or
> what have you) and a being able to act as a container coordinator between
> baremetal/virtual machines. I guess this is not a new request and we know
> ACS already supports LXC but I would like to use ACS as a tool that works
> for me to configure, deploy and manage containers using docker. In essence,
> we can have something like a recipe, a DSL or infra-management-as-code to
> automate infrastructure at a higher level just like we use Puppet or Chef,
> we could have something for our infrastructure that just works.
> 
> What would you enhance?
> 
> 
> Probably next iteration of cloudmonkey and add tests (in my free time).
> 
> 
>> Are there big bets we should be placing as a community?
>> 
> 
> There is a lot of architectural debt that CloudStack is paying for, maybe
> we could introduce and implement cloud engine, new api services and the
> other next gen stuff that we had discussed in that past; I would like to
> contribute if that happens.
> 
> The cluster management service and the way agents and ACS mgmt server
> communicate can be improved, things like Raft could be implemented as our
> consensus problem is not solved (in case of network/io issue, the agents
> and ACS mgmt server may have different view of the world, for example).
> 
> The codebase is monstrous, we can maybe bet of splitting every part as a
> plugin and maybe move some code to other languages that are interoperable
> and run on JVM like Scala. One motivation for this is the fact that a lot
> of infrastructure code in the last one year has been written in Scala which
> works perfectly with existing Java based ecosystem. Since I've some
> experience of Scala and ACS's API layer, web services, plugin system, ACS's
> ORM and build system I can think refactoring and rewriting stuff in Scala
> would greatly reduce a lot of code while it would be still interoperable
> with the rest of the components.
> 
> If you think about ACS from a top level bird's eye view, ACS is a big
> resource consuming poorly written web app that takes in some request, spits
> answers for read queries (sync commands) or enqueues in its job queue
> (async jobs) and stores information what it knows about (from MySQL) and/or
> cache (in/via DAOs). There are a lot of moving parts and SPOFs. If all
> these components could be a ran as a separate service which could run on
> different or same server, they could be cleanly separated and they can
> become more testable, easier to understand, enhance and develop.
> 
> Just my views :)
> 
> Regards.
> 
> 
> 
>> 
>> Feel free to post any thoughts here and I'll look forward to talking to
>> many of you in person at Collab next week.  You are coming to Collab, right?
>> 
>> -Steve
>> 
>> Steve Wilson
>> VP, Cloud Engineering
>> Citrix
>> twitter: @virtualsteve
>>

RE: CloudStack.next

2013-11-17 Thread Radhika Puthiyetath 
+ 1 to process improvements and ecosystems (advertising CloudStack, reaching 
out to the student community, which I always stand for)

-Original Message-
From: Sebastien Goasguen [mailto:run...@gmail.com] 
Sent: Friday, November 15, 2013 7:38 PM
To: dev@cloudstack.apache.org
Subject: Re: CloudStack.next

Hi, this is a bit of a brain dump:

I tend to see different types of buckets:

1-Processes
Involves getting better as a community in terms of release, bug fixing, 
committing code, documentation and user support. Some of these have already 
been discussed partially but we need to come to consensus and act.
For example:
-we should have no unanswered questions on the lists. Anyway to have an 
official volunteer support team ? With a 24/7 twilio number on the site that 
rings up someone out there :) ?
-we should catch up on bug fixing (and great job on 4.2.1 btw) -when we commit 
we cannot break master, and I also would argue for committing docs when it's a 
new feature, right now master is a catch all, instead of a super stable, high 
quality branch.
-we need much better docs
-we need to define standards for releases: RN, changes file, upgrade paths, 
testing etc.
-our testing infra needs to get much better, continuous testing for all 
branches, testing on commits etc...maybe we should find a way to get help from 
cloudbees to get us on the right tracks. Overall we need to be able to release 
at any instant with confidence.
-no feature should be un-documented and/or un-tested. for instance: there was a 
recent complaint about lack of F5 documentation, and right now I have no clue 
who is testing the F5 integration.

2-Ecosystem
We need to build up the ecosystem around cloudstack and advertize it.
We integrate with almost everything out there, yet people don't know it. I wish 
that:
2.1 we would improve on support in existing software: all configuration mgt 
systems, main cloud libraries, PaaS etc...
2.2 work with everyone in that ecosystem to advertize and demo CloudStack 
integration
2.3 work on extending that ecosystem (e.g Docker support, Cloudfoundry, Mesos, 
Spark, OpenDaylight controller) some of it is just a matter of writing a 
tutorial, some of it there is actual coding involved.
2.4 restart effort on AWS: as mentioned IAM is needed but there is more, we 
need to catch with euca and integrate with netflixOSS software. Bring EMR, ELB, 
CloudWatch etc...I have plans to work on this and hopefully propose a 
standalone AWS-ACS bridge with extended services.

3-Code (caveat, I am not a java developer) I still would love to see a lot of 
cleanup and review. For example I believe the KVM agent uses some python 
scripts in cloud-cli, those don't use Marvin. We should try to consolidate 
these. There is code in the tree that is unused, we should clean it up. In the 
UI when you add a cluster we still list 'OVM' yet it's broken, we need to 
clean. OStypes in image creation, we need to clean up...
Packaging and mavenization, we should finish that up and really make it super 
strong. We need to call out to maven and package experts for a hand.
We had a small thread on KVM agent and we will have a talk at the hackathon, 
here I will pick on Xen:
We need much better support for Xen_Project without using xapi (the xapi 
install on XP is a pain), without xapi we could easily have ARM / Ceph 
support... Overall I would like to see a strong core emerge with clean code 
separation with UI, DB abstraction,  backend drivers and plugins. ( A bit pie 
in the sky, but a non java guy should be able to keep the core and replace/add 
any other component, plug and play) Biggest item is probably a software 
architecture blueprint, right now we don't have that. No UML diagram, no 
sequence diagram, most people don't know how cloudstack actually works.

-seb (I will invest time on the ecosystem bucket)

On Nov 14, 2013, at 10:18 PM, Chiradeep Vittal  
wrote:

> +1 to IAM.
> 
> An Autoscale service independent of Netscaler.
> I'd like to see the built-in GRE controller fully fleshed out as a 
> distributed/cross-AZ virtual network provider. Make it the 
> out-of-the-box virtual network provider instead of VLAN.
> Easier service vm insertion into virtual networks.
> Better fidelity with AWS VPC APIs
> 
> 
> 
> 
> On 11/12/13 6:09 PM, "Simon Murphy"  wrote:
> 
>> As a CloudStack user, here are the ares that I feel need attention:
>> 
>> - improved IAM and implementation of a full RBAC security model. This 
>> is hurting us right now.
>> - improved VM import functionality (ie bulk import of VM's and import 
>> of running VM's from existing vSphere clusters)
>> - improved backup functionality and integration with 3rd party tools
>> - HA for VPC routers
>> 
>> Cheers,
>> Simon Murphy
>> Solutions Architect
>> 
>> ViFX | Cloud Infrastructure
>> Level 7, 57 Fort Street, Auckland, New Zealand 1010 PO Box 106700, 
>> Auckland, New Zealand 1143 M +64 21 285 4519 | S simon_a_murphy 
>> www.vifx.co.nz  follow u

edit access to cwiki

2013-11-17 Thread Shweta Agarwal 
I am unable to add test plans  for 4.3 release to wiki  as it seems the wiki 
edit access permissions are not there.
Can you somebody give edit access to cwiki for user 'shweta.agar...@citrix.com' 
?

Thanks
Shweta

Re: SDN compat matrix

2013-11-17 Thread Pedro Roque Marques 
Hugo,
Small correction bellow...

On Nov 17, 2013, at 2:40 AM, Hugo Trippaers  wrote:

> Hey guys,
> 
> I’m building the compatibility matrix for our SDN plugins to use in my 
> presentation for CCCEU13. I think i got everything in there, but would like 
> to check it against your combined knowledge:
> 
> GRE isolation
>   supports L2 isolation
>   XenServer supported since pre ACS
>   KVM supported since pre ACS
>   (not taking son extensions branch into account yet)
> VXLAN
>   supports L2 isolation
>   KVM supported since master (4.3)
> Nicira NVP
>   supports L2 isolation
>   supports L3 NAT function since 4.1
>   supports VPC networks
>   XenServer supported since 4.0
>   KVM supported since 4.1
>   VMware supported since 4.2
> Midokura
>   supports L2 isolation
>   supports L3 NAT, DHCP, Firewall
>   supports VPC networks
>   KVM supported since 4.2
> Stratosphere
>   supports L2 isolation
>   KVM supported since 4.2
> Contrail
>   supports L2 isolation
>   supports L3 NAT, DHCP
>   Xenserver supported since master
>   KVM supported since master

For Contrail KVM support is not there yet...; it does support a distributed 
router replacing the domain router for traffic that traverses guest networks.

> 
> 
> Anything i forgot here?
> 
> Cheers,
> 
> Hugo

Re: [MERGE] marvin-refactor to master

2013-11-17 Thread Prasanna Santhanam 
After some conversations it was decided to not merge this branch to
master. The gist - since factories introduce complexity into the
library and a learning curve for test case writers it was felt this
would be a burden to manage and maintain this work.

I've left the branch as-is for anyone to pickup if they feel it is
worth improving upon and then merging with these fixed.

Thanks,

-- 
Prasanna.,


Powered by BigRock.com