Dec 3rd: Open TOC Nominations
Jan 7th: Close TOC Nominations
TOC Evaluation Period
Jan 8th: Open TOC Evaluation
Jan 22nd: Close TOC Voting
Open TOC Voting (3 days)
Jan 25th: Open Voting
Jan 28th: Close Voting
Jan 29th: Announce TOC Results
Dear CNCF Community,
As a GM and principal technical leader of cloud architecture at AT&T I have the fortune of enjoying a unique perspective through which I can observe and influence technology and its impact on our business markets, government and education sectors and on the individual consumer. My team and I are entrusted with the care and feeding of our architecture efforts toward Cloud Computing, Big Data and the consumption and providing of content and capabilities via scalable and reusable platform APIs.
My current perspective combined with many years of driving innovation and standards through collaboration across open source and corporate and start-up initiatives has forged a strong commitment to the importance of the Cloud Native Computing Foundation. It is from that commitment that I seek your support for a TOC nomination.
While cloud computing has held out the promise of reducing cost, complexity and time to market we have only scratched the surface of realizing these goals. In my opinion our current challenges will include not just the definition and realization of technical standards but will include the need to keep the market energized in the belief that cloud computing is still a worthy end game. With that in mind I believe our technical leadership will need to possess peripheral visionary skills and the technical grounding, historical understanding and determination to foster collaboration, prioritization and a steady cadence of accomplishments among our contributors and stakeholders.
The community tends to focus on specific technologies, tools and projects and look to understand the “either-or” value proposition of selecting one over the other. My intent would be to offer a unique and diverse perspective which recognizes our establishment of a patchwork quilt, derived from the contributions of providers, open source projects and thought leadership from a broad base of stakeholders. I would also offer a view which looks at both the provider and customer aspects of the equation and the view that innovation and change is a primary constant in our equation.
In the spirit of keeping this brief but useful I would close with the following perspective. Our ultimate business challenge is to reduce the time, cost and complexity associated with the deployment and management of software defined business and technical functions which run our lives. Our biggest technical challenge is to “right-size” the IT resources supporting today’s software enablers to point in time demand for specific functions as opposed to entire infrastructure deployments. We must accomplish this while reducing cost, complexity and time to market while offering abstraction, flexibility and choice - a tall order.
Lastly, our biggest scope challenge is in realizing software workload deployments in loosely coupled, geographically diverse architectures involving multiple providers, virtualization technologies and locations. Providing a level of visibility and control to both consumers and providers unprecedented in our technology history is imperative to maintaining comfort, confidence and adoption of the solutions we will inevitably define for the Cloud Native Computing Ecosystem.
I look forward to working with all of you in defining the direction, strategy, problem set and ultimate standards to which the industry will evolve. I would be honored to play a leadership role in this effort with the intent of uniting a diverse group of super-smart contributors to a common goal that will stand the test of time by assuring constant innovation and evolution. I appreciate your consideration.
With kind regards,
Doug
Douglas Nassaur
Lead Principal – Technical Architect
Cloud Native Computing - Architecture and Platforms
Domain 2.0 Architecture and Design
770.331.6823
The main value I bring is an understanding of how all the moving parts come together to make a project succeed, from idea to product, and from community to customer.
- CEO Weaveworks, which I co-founded. Weave is approaching 5M downloads from DockerHub and Github, and as a team we have influenced the container community and CNCF.
- CEO RabbitMQ, which I co-founded. Rabbit is widely used in cloud native software.
- Head of products for Spring and vFabric (commercial) at Pivotal where I reorganised Spring and introduced the cloud native generation of Spring products that is now doing so well (eg Boot)
- As part of the above, I was also responsible for our product effort around Redis, Apache Tomcat and Apache Web Server. I had previously convinced Salvatore (Redis) to join us. Vert.x was born in my team too.
- At VMware I was instrumental in convincing the exec team to join OpenStack. That took a while, but we got there in the end… And between VMware and Pivotal I had a proximal although never hands on role in Cloud Foundry and its journey to the current Foundation model.
- I have experience with interoperable open standards - I co-chaired and successfully brought an open cloud API standard to market - OCCI, in the OGF. I also played a leading role in AMQP through my work on RabbitMQ.
- I helped to create the MPL2 updated Mozilla open source license. And, for more info on me, please see my linkedin bio.
|
|||||||||||||
Think before you print.
CNCF members,
I would like to nominate Doug Davis (from IBM) for consideration for the TOC.
Doug has been working on open-source and software standards for over 15 years for IBM with his most recent focus being on Docker and other container related technologies. In Docker, Doug was IBM's first maintainer and leads IBM's open-source Docker development efforts. With the creation of OCI and CNCF, Doug now also leads IBM's development efforts in those spaces as well. Looking at the broader Cloud space, Doug was in-charge of developing IBM's proposal for IaaS API standardization to the DMTF, and took a lead role in the DMTF's Cloud Infrastructure Management Interface standardization efforts by helping to coordinate the work efforts by being the lead editor on the specification - helping guide the discussions to quick resolution. Beyond the DMTF's work, Doug has also worked on OpenStack and Cloud Foundry as part of the team to integrate and launch IBM's Bluemix Cloud environment. Leading the effort to stand-up and manage the Bluemix development pipeline, Doug has first-hand experience in managing a PaaS infrastructure.
During his time with open-source and standards work, Doug has had the opportunity to work on all aspects of what it takes to make these efforts successful. While working on the development of the SOAP/WS-* specifications he, personally, implemented most of the specifications during their development to ensure what was being written in the specs would actually work in practice. These implementations would then be used for interop testing with other vendors as well as within IBM itself. Often design decisions are not simply coding matters but need to take into account issues that are of broader concern. Issues such as: enterprise needs, end-user interactions, customer requirements and, of course, business needs all need to be considered. And it goes beyond what IBM views as important for these - each participant of these open-source/standards projects have their own view as well. Doug understands this and was successful in collaborating with people from across the industry (vendors as well as customers/end-users) to ensure all voices were heard and taken into account. So much so, that he founded and setup a new consortium of WS-* vendors and customers with the sole purpose of ensuring interoperability of the WS-* specifications.
All of this comes back to IBM's goal with the CNCF, we did not join the CNCF with the goal of trying to promote one particular (or our own) implementation over another. Rather, IBM is looking to harmonize the various implementations available today in the community. This is exactly the type of activity that Doug has been working on during his time in IBM's open-source and standards organization and will continue to do within the CNCF.
Todd M. Moore
Vice President IBM Open Technology
11501 Burnet Rd. MS 9035H014
Austin, TX , 78758. (512) 286-7643 (tie-line 363)
tmmoore@...
President and CEO
Joyent, Inc.
(o)415-800-0872
(c)650-906-0740
CNCF Community,
I would like to nominate myself for the TOC.
I have had a long history in both academic and industry research in computer security. I started my career as a professor at Carnegie Mellon University teaching computer security, and was a founding faculty member of Carnegie Mellon’s Cyber Security Center. During that time, I led many cross industry/academia research efforts and spearheaded many research projects including one that led to the “chenxification” code-level obfuscation technique that is still used in high-security DoD projects and to the best of my knowledge, some underground malware kits.
My post academia work included a VP of research position at Forrester Research, where I covered many segments of the security market and published many hard-hitting research papers on security technologies. My advocacy for application security and privacy led to keynotes at SANS developer conference, RSA Asia, and OWASP. During my Forrester stint, I contributed to the specification of the privacy markup language, sat on the RSA conference’s technical review committee, and served on many National Science Foundation research grant review boards.
At RSA 2016, I’ll be running a featured encryption privacy panel with the former Cyber Security advisor for President Obama, Director of Privacy for Homeland Security and noted privacy experts from EPIC. I recently keynoted ACM’s Cloud Security Workshop on the topic of intersection of cloud security and privacy.
At Twistlock, we are advocating that container security should be platform neutral and cloud native. That means portable, interoperable technologies that do not require anchoring to a specific OS, server architecture, or runtime environment. This is the overriding principle that influences our product strategies, roadmap, and also our open source work. Because of this, we are selected as the first security partner for Google Container Engine. We also recently committed authorization framework code to Docker, which allows third party authorization plugins to be integrated with Docker. For those efforts, I work very closely with R&D to craft product and technology roadmap. Our mission is to engineer a platform-neutral layer of security controls that are open, standards-based, and can benefit a large part of the ecosystem. This mission fits extremely well with the CNCF vision.
Prior to Twistlock, I spent two years leading the innovation strategy at Intel security, focusing primarily on deriving unique value from a software-hardware combined strategy. I led the ubiquity research and developed the technical roadmap and specification for embedding identity-based encryption engine in Intel hardware, which led to the integration roadmap for Cloud-to-chip technologies for Intel Security.
The industry is going through a sea change presently when DevOps initiatives are taking hold in organizations large and small. Security must adapt accordingly or risk jeopardizing the pace of innovation. For those reasons, we contend that it is important for the TOC to have a designated representative on security technologies.
Twistlock’s market position – an early mover in container security – and my experience in deep technical work, privacy, as well as big-picture strategy research, allow me to bring unique insights to the technical committee. I believe that I can make significant and valuable contribution to the technical work of CNCF and therefore would like to nominate myself to be a member of the technical committee.
Sincerely,
Ken Owens, CTO Cisco Cloud Solution Engineering
Technical executive with 20+ years’ experience in architecture, analysis, design, research, and implementation of cloud computing infrastructures consisting of Cloud Native development, Microservices, SOA software design, virtualization, server, network, security, storage, automation, management layers, and deployment methodologies. Experience in system engineering functions, such as system architecture development, system requirements synthesis, performance modeling, behavior modeling, feasibility analysis, and validation of multi-layered communication systems.
Currently responsible for Cisco Cloud Engineering technology and strategy including innovations and cloud native capabilities. Architected, designed, developed, and deployed microservices architecture called MANTL (http://mantl.io) and the Cloud Native developer UX called Shipped (http://ciscoshipped.io). Cisco Shipped is the first of its kind platform in the industry built to implement the DevOps process for Continuous Integration and Deployment. Shipped is designed to help develop and deploy micro services in a containerized environment (mantl.io). This project is designed for cloud native and transformation from existing development to cloud native. Developers can deploy code to target cloud environment within minutes, familiarize themselves with the latest technologies in CI/CD, and help their business rapidly test cloud native capabilities without any vendor lock in.
As CTO of Savvis Cloud Business previously, Responsible for the overall cloud technology roadmap including key strategic innovations relating to the product development process and creating a platform that all cloud products and services will innovate on. Created and incorporated new Service Design Methodology into the product development process resulting in creating services that delight and connect to our customers. Drove the adaption of the Service Design Methodology across the Hosting and Cloud Business Units. Architected, engineered, and designed new Openstack Platform Strategy that is integral to transformation to a new cloud architecture that is less reliant on VMWare and mutli-cloud federation capable. Lead the creation and implementation of an Innovation Framework and Research & Development methodologies to drive disruptive technologies and services into market rapidly. Lead creation and implementation of a Competitive Intelligence process that established an innovation landscape and competitive SWOT analysis. Created eco-system partner certification methodology, process, and automated test suite. Supported Sales and Sales Engineers on strategic customer accounts resulting in 40$ Million in revenue
|
|||||||||||||
Think before you print.
Yaron Haviv, Founder & CTO, iguaz.io
In the past two decades my direct reports and I have been involved in multiple standard organization bodies and have made significant contributions to variety of very relevant Cloud and Infrastructure related open source projects (see list below), I have been engaged in hands on development and architecture, and awarded more than a dozen patents in the fields of service orchestration, network virtualization, storage, databases, high-performance, and security. I have my own Blog (SDSBlog.com) in which I cover various technical topics including Cloud, BigData, Storage, and advocate for Cloud-Native approaches. My positions as CTO and VP included all aspects of community and partner related activities, and I fully understand the role which is to find the most pragmatic path to consensus, combined with industry evangelism.
I believe I can provide significant value and guidance to the CNCF technical committee, bringing deep and wide knowledge, and experience in architecting complex systems and engaging with various communities. In my new company we plan on making active spec & code contribution to CNCF and not be a bystander.
Previous standard activities:
- IEEE (DCB), IETF (IPS/iSCSI, RDMA), IBTA (Steering, LWG), iWarp, OFA, OGF
- ONF (OpenFlow), OCP (OpenCompute), Open Network Linux
Open Source projects my team members (under my guidance) and I contributed to:
- Linux core: netdev (networking), OpenFabric (RDMA), SCSI/Block, KVM
- Networking: Open vSwitch, VxLAN
- OpenStack: Nova-volume, Nova-networking, Neutron, Cinder
- Storage: Ceph, iSCSI (Linux client, TGTD, SCST, LIO), NVMe
- Hadoop: MapReduce, HDFS
- Messaging: OpenMPI, Accelio
More information:
LinkedIn: https://il.linkedin.com/in/yaronh
Twitter: @yaronhaviv
Email: yaronh@...
Yaron Haviv
Founder and CTO, iguaz.io
Personal Blog: SDSBlog.com
Mobile: +972 (54) 4522300
Dear CNCF members,
I would like to nominate Dr. Ying Xiong (from Huawei) to participate the TOC election.
Ying is the Chief Architect of Cloud Platform at Huawei, where he has been leading the architecture, design and development of Huawei PaaS platform that supports cloud native distributed system and micro services. He is guiding Huawei’s open source development in container related projects such as Docker, Kubernetes, OCI, Cloud Foundry, Mesos and Cloudify, and made the company a vital contributor in the communities. Ying has been working on software industry over 20+ years, he is a very hands-on technology leader and has been instrumental in building the cloud platform architecture that not only integrates various open source technologies, but also significantly improves the technologies in terms of reliability, scalability and performance to meet customer requirements. In addition to delivering PaaS, Ying is responsible for driving strategy and technology innovation for hyper-scale, heterogeneous and cross-DC cloud-native infrastructure, where he is currently driving projects such as large scale container cluster management, advanced container networking, container Devops and next generation micro service architecture. He believes these technologies will not only benefit Huawei’s telco and enterprise customers, but also the open source communities.
Ying has extensive experience in cloud computing. Prior to Huawei, he worked at Microsoft over 8 years and was a principal architect in Azure core team since 2009, where he led designing and developing a few core components (resource scheduling, app deployment, monitoring and auto scaling) of Azure, one of largest public cloud platforms in the world, and deploying and monitoring hundreds and thousands of applications per day. He received Architecture Metal Award and Gold Excellence Award during his stay at Microsoft.
Last but not least, I think Ying has another advantage. China is a vivid battle field for cloud native infrastructure, it is not only due to the massive customer base, but also due to the pace that new technologies and number of developers are emerging there. I believe Ying’s connections with these technical circles along with his culture background would make him play an ideal role to align the technical direction in CNCF.
So in summary, with his deep experience in cloud computing and immersed interest in building next generation cloud native open source technologies, and interoperability, I believe Ying would bring an invaluable perspective and experience to the CNCF technical committee. He sees CNCF as a home for building next generation interoperable cloud computing platform that can drive mass adoption with public cloud reliability and scalability.
Ying attends and speaks in industry and open source conferences. He promotes platform openness through blogs, quotes and interviews. Here are a few recent examples about his talks, quotes and interviews.
https://www.youtube.com/watch?v=reKsg7xpSFw
https://www.youtube.com/watch?v=EMRbhBNI3DM
http://finance.yahoo.com/news/cloud-native-computing-foundation-drive-130000670.html
http://blog.kubernetes.io/2015/11/Kubernetes-as-Foundation-for-Cloud-Native-PaaS.html
http://finance.yahoo.com/news/huawei-mesosphere-announce-integration-huaweis-160000265.html
http://blog.altoros.com/top-qoutes-from-the-cloud-foundry-summit-2015.html
https://www.linkedin.com/pulse/cfsummit-keynotes-huawei-chief-architect-notes-steve-chambers
You can reach him at Ying.Xiong1@....
Peixin Hou
Huawei Technology
I would like to nominate Fritz Ferstl from Univa (formerly of Sun/Oracle) whom I believe would be an excellent member and contributor to the CNCF's TOC.
- 23 years as a leading expert in distributed workload and resource management
- As the CTO of Univa Corporation defining product and technology direction for servicing several hundreds of large enterprise customers across all industry verticals on behalf of their workload management requirements. Among these customers are many of the largest computing environments that exist in large enterprises
- In that role having helped to address the challenges created by workloads and operational models of all kinds, ranging from high throughput scenarios to persistent service environments and to extreme-scale, long-running, parallel computations
- Having initiated, shepherded and helped grow the most widely used workload management systems in the world
- Having led the open sourcing of Sun Grid Engine and acting 10 years as 'benevolent dictator' for it
- Having participated in standards bodies such as GGF/OGF leading to sanctioned and widely adopted industry standards
- evolve from early adopter solutions to solutions for a maturing market
- can be implemented by ISVs and integrated into their products
- provide best-in-class solutions for all use cases and workload types required by the various market verticals
- can be integrated into standard enterprise IT environments
----------------------------------------------------
I would like to nominate Steven Borrelli
Current: Founder, Asteris (http://aster.is)
Steven Borrelli is the founder of Asteris (https://aster.is) and is one of the
architects and core comitters for the Mantl project (http://mantl.io).
Mantl is a open-source project that spans many of the technology domains in the CNCF: multiple cloud providers, schedulers, network and logging backends, service discovery, and security. As part of this project he has gained tremendous knowledge on interoperability of the various technologies and integrating them to create a cohesive platform.
In prior roles, Steven was a developer for Savvis Cloud R&D team, where he worked on emerging technologies including containers and distributed systems.
Previous to Savvis Steven Managed for Unix and Storage Engineering within Citi North America IT.
Steven was also a Sr. Developer for Citi Alpha Analytics, where he built HPC infrastructure and applications to analyze Mortgage portfolios in parallel. He was an SME for security, audit, distributed systems and storage.
|
|||||||||||||
Think before you print.
On Tue, Jan 5, 2016 at 6:32 PM, Aaron Bell via cncf-toc
<cncf-toc@...> wrote:
I would like to nominate Benjamin Hindman—a leader in the movement toward
cloud-native application architectures—as a member of the Technical
Oversight Committee for the CNCF. Ben was one of the original members of the
AMPLab [1] at the University of California, Berkeley, where he co-created of
Apache Mesos [2] (he is now a vice president at the Apache Software
Foundation, where he oversees the Mesos project). He led the Mesos team at
Twitter, overseeing the replatforming of Twitter on Mesos. Since 2012, Ben
has been the co-founder and chief scientist at Mesosphere.
Apache Mesos is considered a key technology in cloud-native computing [3].
In addition to Twitter, it runs some of the largest cloud-native clusters in
the world at companies such as Apple (with which Ben worked closely as a
consultant), Airbnb, Verizon, Samsung and many more. Mesos has been
integrated as the core technology is Microsoft’s Azure Container Service,
and has helped usher in a coming mass adoption of microservices in
containers.
Under Ben’s guidance, both Apache Mesos and Mesosphere have embraced and
expanded the ecosystem of open source technologies required for building
next-generation applications. The list of projects currently integrated with
Mesos and Mesosphere’s commercial Datacenter Operating System includes
Kubernetes, Docker, Marathon (developed by Mesosphere), Apache Spark, Apache
Cassandra and Apache Kafka.
Prior to the creation of Mesos in 2010, Ben conducted advanced distributed
computing and software programming research at various institutions,
including the University of Washington, Microsoft Research, Google, and the
UC-Berkeley. At UC-Berkeley, Ben also worked on a precursor to Mesos called
Lithe; was a member of its RAD Lab and Par Lab programs (predecessors to the
AMPLab); and helped develop the Dominant Resource Fairness algorithm [4].
Along with its eventual creators (and UC-Berkeley peers), Ben helped
conceive of Apache Spark as a sample framework for data-processing on Mesos.
Ben’s deep knowledge of distributed computing, as well as his experience
building production cloud-native environments and packaging open source
software for commercial use, make him an excellent candidate for the CNCF
Technical Oversight Committee.
[1] https://amplab.cs.berkeley.edu/
[2] https://www.usenix.org/legacy/event/nsdi11/tech/full_papers/Hindman.pdf
[3]
http://radar.oreilly.com/2014/12/why-the-data-center-needs-an-operating-system.html
[4] https://www.cs.berkeley.edu/~alig/papers/drf.pdf
Thanks,
Aaron Bell
Engineering Manager, Mesosphere
_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
On Tue, Jan 5, 2016 at 10:57 AM, Alexis Richardson via cncf-toc
<cncf-toc@...> wrote:
+1
On Tue, Jan 5, 2016 at 6:32 PM, Aaron Bell via cncf-toc
<cncf-toc@...> wrote:I would like to nominate Benjamin Hindman—a leader in the movement toward_______________________________________________
cloud-native application architectures—as a member of the Technical
Oversight Committee for the CNCF. Ben was one of the original members of the
AMPLab [1] at the University of California, Berkeley, where he co-created of
Apache Mesos [2] (he is now a vice president at the Apache Software
Foundation, where he oversees the Mesos project). He led the Mesos team at
Twitter, overseeing the replatforming of Twitter on Mesos. Since 2012, Ben
has been the co-founder and chief scientist at Mesosphere.
Apache Mesos is considered a key technology in cloud-native computing [3].
In addition to Twitter, it runs some of the largest cloud-native clusters in
the world at companies such as Apple (with which Ben worked closely as a
consultant), Airbnb, Verizon, Samsung and many more. Mesos has been
integrated as the core technology is Microsoft’s Azure Container Service,
and has helped usher in a coming mass adoption of microservices in
containers.
Under Ben’s guidance, both Apache Mesos and Mesosphere have embraced and
expanded the ecosystem of open source technologies required for building
next-generation applications. The list of projects currently integrated with
Mesos and Mesosphere’s commercial Datacenter Operating System includes
Kubernetes, Docker, Marathon (developed by Mesosphere), Apache Spark, Apache
Cassandra and Apache Kafka.
Prior to the creation of Mesos in 2010, Ben conducted advanced distributed
computing and software programming research at various institutions,
including the University of Washington, Microsoft Research, Google, and the
UC-Berkeley. At UC-Berkeley, Ben also worked on a precursor to Mesos called
Lithe; was a member of its RAD Lab and Par Lab programs (predecessors to the
AMPLab); and helped develop the Dominant Resource Fairness algorithm [4].
Along with its eventual creators (and UC-Berkeley peers), Ben helped
conceive of Apache Spark as a sample framework for data-processing on Mesos.
Ben’s deep knowledge of distributed computing, as well as his experience
building production cloud-native environments and packaging open source
software for commercial use, make him an excellent candidate for the CNCF
Technical Oversight Committee.
[1] https://amplab.cs.berkeley.edu/
[2] https://www.usenix.org/legacy/event/nsdi11/tech/full_papers/Hindman.pdf
[3]
http://radar.oreilly.com/2014/12/why-the-data-center-needs-an-operating-system.html
[4] https://www.cs.berkeley.edu/~alig/papers/drf.pdf
Thanks,
Aaron Bell
Engineering Manager, Mesosphere
_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc
John Lawler
VP of Marketing and Product Management
Virtuozzo
e: jlawler@... c: 425.829.5962
w: 425.282.1755 skype: jlawler.odin
TOC.
If I had to sum up, in one phrase, my strength (and weakness) is that I
am a Jack of all trades (how many I master could be, and is, debated).
I've been an operator of large infrastructure as chief architect at iMCI /
Cable & Wireless (one of the two largest Internet backbones in the late
1990's early 2000's - responsible for everything from physical
infrastructure through to applications and hosting across 5 continents)
and at Telstra, the incumbent combined fixed-line, wireless, and cable
operator in Australia. There, I started championing distributed storage,
a unified cloud infrastructure with containers for application
delivery, and exposing telco APIs to developers from 2009-2011.
I've been a small operator, building one of the first OpenStack
Bioinformatics clusters for genomic computation at Annai Systems in the
early 2010's. I've also operated R&E infrastructure as the lead
engineer for networking and computing at the US Antarctic Program.
I've also been a vendor, with a few start-ups under my belt (Big Switch
and Woven Systems) and a few largish ones (Alcatel as the CTO for a
business unit in Asia) and Metaswitch.
Before coming to Metaswitch, I had become convinced that we (the
industry) were making networking (as well as other things in the "cloud"
world) much too complex. That led to Project Calico, which I instigated and
did much of the initial high-level design when I started at Metaswitch, very
specifically focusing on Containers and the new data-model driven world (as
well as OpenStack - but knowing that the big shift was going to come in this
new model).
I understand how the pieces fit together, and I am pretty good at
figuring out the "right" place to solve a hard problem. I firmly
believe that less is more, and if it isn't simple, it should be suspect,
while recognizing that some genuinely hard problems do ultimately require
complex solutions.
I've also done my time at cat herding, serving as a working group chair
in two IETF working groups (OPS and PGP), and co-managing the Internet
Area Directorate. In that role, I’ve seen both what great things can be
achieved in a multi-vendor group motivated to push in the same direction,
as well as the issues that occur when standards are created for their own
sake, not for solving actual, real-world problems.
I believe that I would bring a good mix of both the User/Operator and
Developer/Vendor side to the role.
Christopher Liljenstolpe
Project Calico Architect
--
李柯睿
Avt tace, avt loqvere meliora silentio
Check my PGP key here: http://www.asgaard.org/cdl/cdl.asc
Current vCard here: http://www.asgaard.org/cdl/cdl.vcf
keybase: https://keybase.io/liljenstolpe
Thanks for your consideration.
President and CEO
Joyent, Inc.
(o)415-800-0872
(c)650-906-0740