Hi,
I have been leveraging a wide range of open source projects in an
enterprise
environment for more then 10 years. During this time, I have
developed a
rich
understanding of both the positive and negative implications of
doing so.
I
am currently working at Merck and Co. Inc., with the
responsibility for
overseeing the engineering and operations of Merck's global
Internet/Intranet
web infrastructure. This infrastructure includes ~5000 Apache
virtual
hosts
and ~2700 Tomcat based applications with both test and production
environments.
To allow my team to manage an ever growing range of web assets, we
have
developed
a web based tool set to manage the entire web infrastructure.
Throughout
the
development of the tool set, the idea of releasing it back to the
community that
has provided me with so many wonderful tools has always been part
of the
project
plan. At this time I would like to propose the adoption of the
TMCg2 as
an
incubator project under the ASF.
Regards,
Neil Stein
####################
TMCg2 Proposal
0. Rationale
Organizations apply many styles to the management of open source
web and
application middle tier services, and although functional - it
can not be
considered to be a true enterprise means of middle tier service
management.
With the aim of solidifying the ease and control with which the
enterprise
manages the underlying Open Source web and application server
infrastructure, the TMCg2 was created. This solution brings the
promise
of
a single central tool that improves productivity, increases
control and
efficiencies in both horizontal and vertical scaling of services,
while
allowing for a proactive means in reducing and distributing the
complexities
of managing open source web and application server assets.
0.1 Criteria
Meritocracy:
The current committers have experience working with open source
projects
and
communities, and the leaders of this project have a career based
working
under normal meritocracy rules.
Community:
TMCg2 is not based on an existing open source community, but the
contributors involved have experience leveraging and building
upon many
open
source projects at Merck and Co., Inc. A primary objective of the
project
is to build a vibrant community of users and active contributors.
Core Developers:
The initial committers are not members of a computer technology
based
company, but rather a part of a Fortune 100 company focused on
bringing
efficiencies to its use of open source software.
FEATURES
** Please see White-Paper for specific details.
http://tmcg2.sourceforge.net/TMCg2_WhitePaper.pdf
<http://tmcg2.sourceforge.net/TMCg2_WhitePaper.pdf>
The TMCg2 is divided into two components, the console and agent.
Each
component is then broken down into smaller modules that perform the
specific
tasks.
TMCg2 Console
The TMCg2 Console is a browser based interface for both
administrators
and
application development teams, with access controls, rules, and web
application settings stored in a structured relational
database. A view
is
provided to development teams to focus on the configuration and
status of
their web application. Additional views are provided for the
enterprise
administrators to focus on the Apache and Tomcat configurations and
operating processes. Some types of requests for a developer would
include
application reloads/restarts and content deployments.
Administrators
would
make requests such as creating/modifying web applications,
virtual hosts,
starting or stopping the web application servers.
TMCg2 Agents
The TMCg2 Agent is responsible for brokering messages from the
console to
the appropriate module.
0.2 Warning signs
Management of an extensive web infrastructure is a very important
topic
for
Merck and Co., Inc., and has had limited attention from the ASF.
Continuing
and growing the TMCg2 will provide a continued benefit to Merck
and Co.,
Inc. There is no risk of any of the usual warning signs of
orphaned or
abandoned code.
The current committers have experience working with open source
projects
and
communities and the leaders of this project have a career based
working
under normal meritocracy rules.
Orphaned products:
3. Identify the ASF resources to be created
3.1 mailing list(s)
* tmcg2-ppmc
* tmcg2-dev
* tmcg2-commits
* tmcg2-user
3.2 Subversion repository
* [WWW] https://svn.apache.org/repos/asf/incubator/tmcg2
<https://svn.apache.org/repos/asf/incubator/tmcg2>
3.3 Jira
* tmcg2 (TMCg2)
4. Identify the initial set of committers:
* Neil Stein
* Steve Toback
5. Identify Apache sponsoring individual
We request that the Apache Incubator PMC sponsor TMCg2 as an
incubating
project, with the eventual goal of graduation as a TLP. The initial
contributors feel the scope of the project doesn't clearly
overlap with
any
existing TLP, and is broad enough to justify eventual TLP status.
Champion: Bill Rowe
Mentors: Bill Rowe
Jim Jagielski
Neil Stein
Merck & Co. Inc.
Enterprise Web Infrastructure
phone -- 908-423-4297
----------------------------------------------------------------------
--------
Notice: This e-mail message, together with any attachments,
contains information of Merck & Co., Inc. (One Merck Drive,
Whitehouse Station, New Jersey, USA 08889), and/or its affiliates
(which may be known outside the United States as Merck Frosst,
Merck Sharp & Dohme or MSD and in Japan, as Banyu) that may be
confidential, proprietary copyrighted and/or legally privileged. It
is intended solely for the use of the individual or entity named on
this message. If you are not the intended recipient, and have
received this message in error, please notify us immediately by
reply e-mail and then delete it from your system.
----------------------------------------------------------------------
--------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
