Thanks Sebastien. Here is list of what is in shape so far:
Additional VMX Settings - impacts only dev guide/ RN Persistent Networks without running a VM - Admin/Dev guide/RN AutoScale - Admin/RN Support SRX & F5 inline mode - Admin/RN Egress firewall rules for guest network - My patch is on Review board, waiting long for a reviewer ! Reset SSH Key to access VM (similar to reset password) Support for EC2 Query API (rest interface) Events framework to publish/subscribe to CloudStack events - Will finish this week, mostly! Jessica, please add if I have missed any of your features. I have started AWS-Style Regions, but I hear that is not yet in. Correct me Kishan. The case is still almost the same about VMware dvSwitch. Correct me Satish; I do not know yet the feature is merged, and ready to document. Status of the following features is in progress/ Open: health monitoring for load balanced instances Enhanced baremetal servers support on Cisco UCS Scaling up CPU and RAM for running VMs If you think I can pick up any of these features, let me know. We will get in touch with you tomorrow itself. Thanks -Radhika -----Original Message----- From: Sebastien Goasguen [mailto:run...@gmail.com] Sent: Tuesday, February 12, 2013 9:55 PM To: cloudstack-dev@incubator.apache.org Developers Subject: [DOCS][DISCUSS]Documentation for 4.1 Radhika, raise some questions about the documentation for 4.1, so I would like to move this discussion to a new thread. The 4.1 plan is at: https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.1+Release The feature freeze was 1/31 and the docs freeze is set for 2/28 To stick to a time based release that means (IMHO) that any docs that will not hit the docs freeze of 2/28 will not be part of the 4.1 release. The actual feature, if it met the 4.1 feature freeze will, but not the docs. Radhika prepared a documentation plan: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Apache+CloudStack+v+4.1+Documentation+Plan Feature owners need to double check this plan, make sure that it only lists 4.1 features and then work on their docs. We have 16 days left for docs freeze. After 2/28 we will just fix doc bugs, not add new docs, even if a feature is included in 4.1 if its docs are not in by 2/28 then too bad. That's a bit of tough love, but that's what will happen if we want to stick to the schedule. Thoughts, flames ? -Sebastien
