RE: Rework the Apache VCL website?
I agree, might as well use what Apache says. Just to provide alternatives, though, the current name for such things is "static site generator". Believe it or not, it's become one of the hot topics on many of the web design podcasts and blogs that I follow (perhaps a reaction to "heavy" solutions like WordPress, perhaps a reaction to the current popularity of Github). Here's a site which lists many such tools: http://iwantmyname.com/blog/2011/02/list-static-website-generators.html -- Tony Miller Technology Consultant, ITCS, East Carolina University mill...@ecu.edu /\ http://blog.ecu.edu/techtips -Original Message- From: Aaron Coburn [mailto:acob...@amherst.edu] Sent: Friday, May 04, 2012 2:10 PM To: Cc: Subject: Re: Rework the Apache VCL website? On May 4, 2012, at 1:00 PM, Andy Kurth wrote: > On Fri, May 4, 2012 at 10:46 AM, Aaron Coburn wrote: >> As for the website, I agree that some design work would be really >> useful. I am assuming that ASF would provide a hosting arrangement, >> i.e. a domain like vcl.apache.org? Would that also include server space to >> run any type of CMS? > > Yes, ASF hosts all project websites and provides server space. > If/when we graduate, the podling website will be moved to > vcl.apache.org. Apache provides a CMS but it is up to the community > whether to use it or something else as long as the content is static. > More info is here: > http://www.apache.org/dev/project-site.html > -and- > http://www.apache.org/dev/cms.html Thanks, I read about Apache's CMS, and I don't see any compelling reason not to use that. It supports both HTML and Markdown formats. Updates are managed by subversion, and it seems like it will be easy to use. Aaron Coburn >> Confluence is a nice all-in-one package, though if you are >> considering a complete overhaul of the site, I could also recommend a >> system like Drupal (MySQL + PHP). Drupal has a lot of bells and >> whistles that can make for a very nice, highly interactive site. The >> downside of drupal is that it is not specifically designed to handle >> software documentation. On the other hand, if we only need to serve >> static html pages that focus on documentation, etc, I can also >> recommend Sphinx. The downside of Sphinx is that it is really best >> for Python and C++ projects, and it doesn't support web-based updates >> -- it does create excellent sites, though. > > I also like Drupal but don't think it can be used due to the static > requirement. We actually use this for NCSU's VCL front page. > > I'm not familiar with Sphinx. It looks like at least one other > project is using Sphinx: > http://chemistry.apache.org/python/docs/docs.html > > -Andy > > > On Wed, Dec 7, 2011 at 7:54 AM, Aaron Peeler wrote: >> Yes, I agree the site needs to be updated. I'm fine to move to ASF >> CMS, especially if this the future direction. >> >> Aaron >> >> On Tue, Dec 6, 2011 at 3:58 PM, Andy Kurth wrote: >>> The Apache VCL project website (https://cwiki.apache.org/VCL) could >>> use some improving. It is automatically generated from the >>> Confluence wiki site >>> (https://cwiki.apache.org/confluence/display/VCL/Apache+VCL). >>> I'm not sure exactly how this works but some things have never >>> worked quite right... small details such as the left nav bar not showing up. >>> >>> I'd like to start reworking the site and would like ideas/help from >>> anyone interested. The first step would be to decide on an >>> underlying platform/CMS. I have nothing against Confluence but the >>> ASF is moving away from it in favor of the "ASF Content Management >>> System". More information is here: >>> http://www.apache.org/dev/cms.html >>> http://www.apache.org/dev/cmsref.html >>> >>> Tools have been written to assist in migrating from Confluence to >>> the ASF CMS. See the bottom of the wiki page: >>> http://wiki.apache.org/general/ApacheCms2010 >>> >>> At first glance this seems like a logical path to pursue. Thoughts? >>> >>> -Andy >>> >> >> >> >> -- >> Aaron Peeler >> Program Manager >> Virtual Computing Lab >> NC State University >> >> All electronic mail messages in connection with State business which >> are sent to or received by this account are subject to the NC Public >> Records Law and may be disclosed to third parties.
Re: [DISCUSS] Graduation
On May 1, 2012, at 12:44 PM, Andy Kurth wrote: > Status File: > (https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/vcl.xml) > This is not up to date and is missing information. Previous board > reports need to be added. News items need to be added containing the > string "new committer". Doing this will cause the numberCommittersNew > column on the "Status of the Clutch" page to turn green > (http://incubator.apache.org/clutch.html). > > Also, the list of commiters in the status file and project page hasn't > changed since Apache VCL started. The new committers obviously need > to be added. I'm not sure how the original list was decided upon, but > I feel several names should be removed since they have not contributed > any code and some have not been involved in the community at all. I > think the list should be Aaron Coburn, David Hutchins, Andy Kurth, > James O'Dell, Aaron Peeler, Josh Thompson. Also, Brian Bouterse > contributed some code a while ago. I'm not sure if he is still > interested in being a committer. I've added news items and updated the committers list for: David Hutchins, Aaron Coburn, and James O'dell. Andrew Kurth, Josh Thompson, and Aaron Peeler were all on the initial committers list. If you are implying that that list should be the current committers list -- as a podling graduates, the committers/PMC members of the podling are named in the graduation proposal. That list is not necessarily all of the committers on the podling committers list. It's not uncommon for initial committers to have very little/no participation in the podling. The podling should discuss this and propose the list of committers for the new project. If you feel Brian Bouterse's contributions merit consideration for committer, please bring this up on private@ and let's discuss… --kevan
Re: [DISCUSS] Graduation
So far, I've seen input from 4 committers and 4 community members (unless I have names mixed up). Would be great to hear from more people (especially committers). Even if it's "let's graduate, already!" --kevan
Re: [DISCUSS] Graduation
On Mon, May 7, 2012 at 3:40 PM, Kevan Miller wrote: > > So far, I've seen input from 4 committers and 4 community members (unless I > have names mixed up). Would be great to hear from more people (especially > committers). Even if it's "let's graduate, already!" > > --kevan "Let's graduate, already!" :-) Mark -- Mark Gardner --
Re: [DISCUSS] Graduation
I would love to see 2.3 to graduate :) I will enjoy many of the bug fixes -Alex CSUEB On Mon, May 7, 2012 at 12:51 PM, Mark Gardner wrote: > On Mon, May 7, 2012 at 3:40 PM, Kevan Miller > wrote: > > > > So far, I've seen input from 4 committers and 4 community members > (unless I have names mixed up). Would be great to hear from more people > (especially committers). Even if it's "let's graduate, already!" > > > > --kevan > > "Let's graduate, already!" :-) > > Mark > > -- > Mark Gardner > -- > -- Thanks, Alex Patterson User Support Services Operating System Analyst California State University, East Bay
Re: [DISCUSS] Graduation
Let's graduate. On Mon, May 7, 2012 at 3:40 PM, Kevan Miller wrote: > > So far, I've seen input from 4 committers and 4 community members (unless > I have names mixed up). Would be great to hear from more people (especially > committers). Even if it's "let's graduate, already!" > > --kevan -- regards, Karuna Karuna Pande Joshi PhD Candidate, CSEE Dept, UMBC kjos...@umbc.edu, karuna.jo...@umbc.edu
Re: [DISCUSS] Graduation
On May 7, 2012, at 3:53 PM, Alexander Patterson wrote: > I would love to see 2.3 to graduate :) I will enjoy many of the bug fixes Thanks Alexander. Minor point - a 2.3 release is orthogonal to the graduation process. A 2.3 release can happen before or after graduation… There's a 'status of 2.3 release' thread on the vcl-dev list. You're more than welcome to voice your 2.3 desires, there... --kevan
Re: Graduation
Hi, May I ask what are the benefits of "graduation" for VCL? How does graduation change the way the VCL is used? I apologize if these are trivial questions. Thanks. -- Dmitri Chebotarov Virtual Computing Lab Systems Engineer, TSD - Ent Servers & Messaging 223 Aquia Building, Ffx, MSN: 1B5 Phone: (703) 993-6175 Fax: (703) 993-3404 On Monday, May 7, 2012 at 16:39 , Kevan Miller wrote: > > On May 7, 2012, at 3:53 PM, Alexander Patterson wrote: > > > I would love to see 2.3 to graduate :) I will enjoy many of the bug fixes > > Thanks Alexander. Minor point - a 2.3 release is orthogonal to the graduation > process. A 2.3 release can happen before or after graduation… > > There's a 'status of 2.3 release' thread on the vcl-dev list. You're more > than welcome to voice your 2.3 desires, there... > > --kevan
Re: VCL Hardware
Hi, Pablo At the moment we have 10 VMs per ESXi host. We have a monitoring system which tracks memory and CPU usage on each ESXi host and we plan to use this data to review number of VMs per ESXi host later. There is some room to add more VMs per host. As for computers, each VM computer is configured with the same specs - 2 vCPU, 4GB memory. Then VCL has per image settings, which is what a VM will get when made available or during reservation. The per image setting will define how much resources you want to assign to this image, but it cannot be more that VM configuration (2 vCPU/4GB in my case). In VCL 2.2.1 per image default is 1 vCPU / 64MB (512MB). If you left it by default for all images, all your running VMs would use very little resources, which could affect performance … When you considering running large number of VMs per ESXi, make sure that you storage can handle it. VCL design is using shared storage, more ESXi servers you add, faster your storage should be. You could configure VM Host profile to use ESXi's local storage for running images. This would off-load shared storage, since you are only going to read from it (except when you create/update an image). Thanks. -- Dmitri Chebotarov Virtual Computing Lab Systems Engineer, TSD - Ent Servers & Messaging 223 Aquia Building, Ffx, MSN: 1B5 Phone: (703) 993-6175 Fax: (703) 993-3404 On Monday, May 7, 2012 at 15:59 , Pablo J. Rebollo-Sosa wrote: > Hi Dimitri, > > ¿How many virtual machines you can handle per blade? ¿What specs have the > virtual machines? > > Pablo > > On 4/9/12 3:50 PM, Dmitri Chebotarov wrote: > > Pablo > > > > I can tell what hardware we use for VCL - other people may have different > > setups. > > > > We use IBM's Blade Center H chassis with HS21/22 blades (7870 type): > > > > - 2xCPUs, from Xeon X5550 (older) to X5660 (newer), > > - 24GB to 48GB of memory, > > - 2x73GB RAID1 local storage (system only, can be replaced by embedded > > VMWare) > > > > CPU and memory per blade will depend on how many VMs you would like to have > > on a ESXi host, or what is an application's hardware requirement if you > > plan to use xCAT. > > > > Storage is N6040 (NetApp FAS3140 equivalent), using NFS - very flexibile > > and fast (NetApp works well with VMWARE). > > I would recommend to have de-duplication license, it saves a lot of space > > on the volume where you store images. > > > > You will need two separate networks - Private (to be used by VCL) and > > Public (users access to reservations). > > > > I hope it helps. > > Let me know if you want to know something else... > > > > Thanks. > > > > > > > > -- > > Dmitri Chebotarov > > Virtual Computing Lab Systems Engineer, TSD - Ent Servers & Messaging > > 223 Aquia Building, Ffx, MSN: 1B5 > > Phone: (703) 993-6175 > > Fax: (703) 993-3404 > > > > > > On Monday, April 9, 2012 at 15:00 , Pablo J. Rebollo-Sosa wrote: > > > > > Hi, > > > > > > I'm interested to know about the typical hardware used to implement the > > > VCL solution in terms of chassis, CPU/cores, memory, storage, etc. > > > > > > Thanks in advanced. > > > > > > Pablo J. Rebollo-Sosa
