There are this set of reviews: 6825, 6895, 6899 already open? There is still an outstanding issue that the Autoscale API should not refer to snmp counters but should use key value pairs instead. This has not been addressed. http://markmail.org/message/74sw3efn3mupfqc2
http://markmail.org/thread/nb262oyznlnkigkb On 9/10/12 12:03 PM, "Vijay Venkatachalam" <vijay.venkatacha...@citrix.com> wrote: >Ok thanks, so if I understand this right, I will be sending the patches >for review with the changes to source code but without the appropriate >jar files. > >For AutoScale branch, user downloads the right jar files to deps folder >and he can build. >For master, user still download to deps folder and runs >install-non-oss.sh (I can see the netscaler jar file entries already >present). > >I will upload the necessary jar files (for master and autoscale branch) >tomorrow to a public location and send out a separate mail. > >Thanks, >Vijay V. > >> -----Original Message----- >> From: Chip Childers [mailto:chip.child...@sungard.com] >> Sent: Tuesday, September 11, 2012 12:02 AM >> To: cloudstack-dev@incubator.apache.org >> Subject: Re: List of New Features in 4.0 >> >> Moved to the dev list: >> >> On Mon, Sep 10, 2012 at 2:22 PM, Vijay Venkatachalam >> <vijay.venkatacha...@citrix.com> wrote: >> > For Autoscale feature, the re-licensing of NetScaler SDK Jar is held >> > up in the Citrix legal :-( , and meanwhile, can I send patches with >>the latest >> NetScaler jar files (still without the new license) to the autoscale >>branch >> alone (not master)? We have about 10 pending patches waiting for >>inclusion. >> >> There are 2 issues with that. >> >> First, we are moving ALL jar / mar / war files out of the code repo, so >>please >> don't try to put one back in (even on a branch). >> >> The second issue is that we should not be moving backwards on the state >>of >> our licensing compliance. If the NetScaler jar is still a non-Apache 2 >> compatible license (per ASF standards on this), then it needs to be >>thought >> of as an optional build target. We need to be able have an optional >>build flag >> to include it after the user downloads the file manually somehow >>(probably >> the same way we do others like this: install-non-oss.sh ). >> >> -chip >> >> > I haven't checked the 4.0 code, but it seems that all NetScaler >>support is >> removed from 4.0 master (besides autoscale), Am I right here? Is this >> pending the NetScaler SDK jar re-licensing? >> > >> > Thanks, >> > Vijay V. >> > >> >> -----Original Message----- >> >> From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com] >> >> Sent: Monday, September 10, 2012 10:53 PM >> >> To: CloudStack Users >> >> Subject: Re: List of New Features in 4.0 >> >> >> >> Autoscaling is still pending a merge and is unlikely to make it into >>4.0. >> >> >> >> On 9/10/12 9:49 AM, "Shanker Balan" <m...@shankerbalan.net> wrote: >> >> >> >> >On 10-Sep-2012, at 8:10 PM, James Jeffrey <james.jeff...@cpp.co.uk> >> >> wrote: >> >> > >> >> >> Hello, >> >> >> >> >> >> Sorry if it already exists - I've looked but failed to find. Is >> >> >>there a list of new features in 4.0 please? >> >> >> >> >> > >> >> >AFAIK, the 2 significant features are VPC and autoscaling. Maybe the >> >> >release manager(s) can comment further. >> >> > >> >> >Hth >> >> >@shankerbalan >> >> > >> > >> >
