Sorry I'm getting to this thread a little late. Our priorities for 2.4
would be NAT and OpenStack support.
Everett Toews | Senior Developer
http://twitter.com/#%21/cybera_everettCybera Inc. http://www.cybera.ca/
@everett_toews http://twitter.com/#!/everett_toews
On Wed, May 23, 2012 at 3:30
I would commit to helping scripted installation into 2.4. I believe the
focus should be on a basic, entry-level VCL that is automatic from bare
metal to working system for those who are no so familiar with Linux.
Larry
Josh Thompson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris,
Oops, Sorry - it's already listed.
Aaron
On Wed, May 23, 2012 at 10:46 AM, Aaron Peeler fapee...@ncsu.edu wrote:
I agree. Definitely need to add the automated/scripted install to the
published roadmap.
Aaron
On Wed, May 23, 2012 at 7:51 AM, Larry Burton
larry_bur...@runningcedar.com
Hi Josh,
I found that php requires gettext for multilingualization (or usually,
internationalization or i18n). Is it possible to check gettext support
by using testsetup.php?
Shoji
At Mon, 21 May 2012 15:53:40 -0400,
Josh Thompson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
That ends up making the list of feature for 2.4 pretty long. How about
splitting them up into two releases as follows:
VCL 2.3 (this release)
* Service deployments
* Allow for additional access methods for environments (port, other
Looks good to me.
Anyone else? This is a community decision :)
Aaron
On Tue, May 22, 2012 at 9:30 AM, Josh Thompson josh_thomp...@ncsu.edu wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
That ends up making the list of feature for 2.4 pretty long. How about
splitting them up into two
Aaron,
At some point I would like to put IPv6 and NAPT on the list but I am
still working on the code. (I would prefer to follow in the footsteps
of the others and have something working to back it up so maybe we
don't want to put it on the schedule yet.)
Mark
On Tue, May 22, 2012 at 9:50 AM,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
NOTE - I changed access methods to connect methods in this thread since we
ended up naming it connect methods previously.
Mark,
We can just add IPv6 in whatever release is next after you finish it. For
NAPT, I was thinking to include that as part
Mark,
Please start a discussion thread on the vcl-dev list regarding IPv6
support. Others may be interested in participating, the current
status, problems encountered, etc.
Thanks,
Andy
On Tue, May 22, 2012 at 11:21 AM, Josh Thompson josh_thomp...@ncsu.edu wrote:
-BEGIN PGP SIGNED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I like the idea of prioritizing items that are preventing people from using
VCL. I'll move power management and Libcloud to 2.5. I think Spice will be
taken care of with the work needed for NAT. Having Spice makes us more
competitive with
It would be nice to see IPv6 included for sure. We at Clemson are
definitely wanting that.
Hopefully this wasn't mentioned before and I missed it, but is there a spot
to vote on what features are important to the community? Like a survey or
something for interested parties?
Thanks for the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris,
We don't have any surveys or anything like that. Things really just happen
through discussion on this list.
Josh
On Tuesday, May 22, 2012 1:13:01 PM Chris Jones wrote:
It would be nice to see IPv6 included for sure. We at Clemson are
Works for me. You can put Clemson down for wanting IPv6. :)
-ChrisJ
On Tue, May 22, 2012 at 2:01 PM, Josh Thompson josh_thomp...@ncsu.eduwrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris,
We don't have any surveys or anything like that. Things really just happen
through
Looks good.
I would also like to see added to 2.4:
* support for ESX OS for end users - the work that Dmitri has done
* initial support for EC2 api, openstack, this could likely include
the code that Cameron and Young have are working on
* initial support for libcloud
Aaron
On Mon, May 21,
14 matches
Mail list logo
