The Apache Software Foundation Announces Apache® CloudMonkey® v6.0
Popular Open Source Command Line Interface tool that simplifies Apache CloudStack configuration and management now faster and easier to use.
Wakefield, MA —20 March 2019— The Apache Software Foundation (ASF), the all-volunteer developers, stewards, and incubators of more than 350 Open Source projects and initiatives, announced today Apache® CloudStack® CloudMonkey v6.0, the latest version of the turnkey enterprise Cloud orchestration platform's command line interface tool.
Apache CloudStack is the proven, highly scalable, and easy-to-deploy IaaS platform used for rapidly creating private, public, and hybrid Cloud environments. Thousands of large-scale public Cloud providers and enterprise organizations use Apache CloudStack to enable billions of dollars worth of business transactions annually across their clouds.
Apache CloudMonkey v6.0.0 is the latest major release since the previous major 5.x release in September 2013. CloudMonkey v6.0.0 is a rewrite of the original tool in Go programming language, and can be used both as an interactive shell and as a command line tool that simplifies CloudStack configuration and management.
Some of the new features and major changes include:
- Rewrite in Go, ships as single binary for Linux, Mac, and Windows
- Drop-in replacement for legacy Python-based cloudmonkey
- About 5-20x faster than legacy Python-based cloudmonkey
- Interactive UX for parameter and arg completion and selection
- JSON is the default output format
- New column based output
- Enable debug mode using set debug true option, file-based logging removed
- Per server profile based API cache
- New syntax arg=@/path/to/file to pass the content of file as API argument value similar to curl
- Improve help docs using -h argument
- Removed: XML output, coloured output, several set options
"This release is the work of over one year of effort and driven by the people operating CloudStack clouds," said Rohit Yadav, Apache CloudStack CloudMonkey v6.0 author, and release manager. "I would like to thank the contributors across all of these organizations for supporting this release, which reflects both the user-driven nature of our community and the Apache CloudStack project's commitment to continue to be the most stable, easily deployable, scalable Open Source platform for IaaS. Along with ease of installation, usage and availability of cross-platform dependency-free builds including Windows builds, v6.0 brings many changes and optimizations such as more interactive shell for parameter completion, faster API requests processing, server profile specific API caching, improved API help docs and a new syntax to pass content of files as API parameter argument." More on the background and story behind the CloudMonkey 6.0 effort can be found at https://blogs.apache.org/cloudstack/entry/what-s-coming-in-cloudmonkey
"Apache CloudStack is a significant part of our Cloud portfolio right now – we run large deployments all over the world, often supporting critical customer applications," said Robert van der Meulen, Product Strategy Lead at Leaseweb Global B.V. "CloudMonkey is an invaluable tool for interacting with CloudStack-based clouds, and it's the go-to tool that we recommend to our customers when they want to use command-line interaction with our CloudStack platforms."
"CloudMonkey is an effective tool for the operators of CloudStack environments and it becomes essential in large-scale CloudStack deployments," said Giles Sirett, CEO of ShapeBlue. "It's great to see this new version of CloudMonkey: having a CLI that can run on Windows desktops as well as Linux and Mac is important as we see more enterprise adoption of Apache CloudStack."
"CloudMonkey is now written in Golang, and with version v6.0 loading, speed has been drastically improved (accessing the CLI in under 0.5s)," said Pierre-Luc Dion, Cloud Architect at Cloud.ca. "This simplifies installation, deployments, updates, and operational efficiency."
"After many years of managing production Apache CloudStack deployments, I consider CloudMonkey a core tool in anyone's CloudStack toolkit, and now also being available for Windows makes me really happy," said Andrija Panic, Apache CloudStack Committer. "I can certainly see major speed improvements, but also having backward compatibility is what is so great with this new release."
Catch Apache CloudStack in action at ApacheCon 9-12 September 2019 in Las Vegas, Nevada, and at numerous Meetups worldwide, held throughout the year.
Downloads and Documentation
The official source code for CloudMonkey v6.0.0 can be downloaded from http://cloudstack.apache.org/downloads.html. The community-maintained builds are available at the project's Github release page at https://github.com/apache/cloudstack-cloudmonkey/releases . CloudMonkey's usage is documented at https://github.com/apache/cloudstack-cloudmonkey/wiki
Availability and Oversight
Apache CloudStack software is released under the Apache License v2.0 and is overseen by a self-selected team of active contributors to the project. A Project Management Committee (PMC) guides the Project's day-to-day operations, including community development and product releases. For downloads, documentation, and ways to become involved with Apache CloudStack, visit http://cloudstack.apache.org/
About The Apache Software Foundation (ASF)
Established in 1999, the all-volunteer Foundation oversees more than 350 leading Open Source projects, including Apache HTTP Server —the world's most popular Web server software. Through the ASF's meritocratic process known as "The Apache Way," more than 730 individual Members and 7,000 Committers across six continents successfully collaborate to develop freely available enterprise-grade software, benefiting millions of users worldwide: thousands of software solutions are distributed under the Apache License; and the community actively participates in ASF mailing lists, mentoring initiatives, and ApacheCon, the Foundation's official user conference, trainings, and expo. The ASF is a US 501(c)(3) charitable organization, funded by individual donations and corporate sponsors including Aetna, Alibaba Cloud Computing, Anonymous, ARM, Baidu, Bloomberg, Budget Direct, Capital One, Cerner, Cloudera, Comcast, Facebook, Google, Handshake, Hortonworks, Huawei, IBM, Indeed, Inspur, Leaseweb, Microsoft, ODPi, Pineapple Fund, Pivotal, Private Internet Access, Red Hat, Target, Tencent, Union Investment, Workday, and Verizon Media. For more information, visit http://apache.org/
© The Apache Software Foundation. "Apache", "CloudStack", "Apache CloudStack", and "ApacheCon" are registered trademarks or trademarks of the Apache Software Foundation in the United States and/or other countries. All other brands and trademarks are the property of their respective owners.
# # #
Posted at 10:00AM Mar 20, 2019
by Sally in General |
Project Perspectives: Apache RocketMQ and The Apache Way
Last year, I wrote a blog about how communities from a non-English-speaking country understand and use Apache way for open innovation
. In that article, I mainly expressed the desire to be open as a developer, to be good at using mailing lists, listening to community voices and making decisions. In addition, project communities can also organize more programming activities like Google Summer of Code ("GSoC"; applications are now open for the 2019 program) to help developers learn how to become involved in the community-led development process as well as provide greater help and encouragement for developers to join the community. After that, I have been thinking about sharing some Apache RocketMQ community building and collaborative innovation stories through some real-life examples. It is my great honor to share some stories with community at the upcoming ASF anniversary celebration. IMO, The Apache Way has greatly helped Apache RocketMQ to grow its community since entering the Apache Incubator in 2016.
Apache RocketMQ was originally created and used as a distributed messaging engine for online e-commerce transaction processing. It could undertake billions, even trillions of message transmissions in many companies’ production environments. RocketMQ has been proven to be suitable for high-throughput, low-latency messaging systems in the large-scale distributed scenarios. A standard OpenMessaging project on the Linux Foundation provides a common benchmarking platform for distributed messaging systems in the cloud including Apache RocketMQ. Of course, as a widely used messaging engine, the functional level, RocketMQ provides both pull and push models, supporting scheduled message, ordered message, batch message, broadcast message, message filtering, dead-letter queue and so on, almost sustaining all classic event driven or streaming scenarios. Even so, there are still a few core features not included from an enterprise perspective. Last year, the RocketMQ community announced three attractive features: transactional message, message tracing, authentication and authorization. The transactional message implements the transaction consistency guarantee between the sender and the local business operation. This feature is a very valuable feature which was initiated and contributed by several individuals from the financial industry. While based on transactional messages, we could build a full-stack distributed transaction platform, which is suitable for long-running microservice.
In the enterprise application for messaging, there has always been a troubling problem. Where did my message send to? How can I find message accumulation if the consumer has failed or not? That’s a very difficult task especially when we are providing cloud pub/sub service, because messaging is an asynchronous decoupling process, the natural upstream and downstream are not aware of each other. Fortunately, some guys from the China Mobile Research Institute found some of the pmc members at Apache RocketMQ Meetup and mentioned their troubles. So, we showed them the latest RIP plan from the community, which is a very challenging optimization and improvement for Apache RocketMQ intra code. Under the help of a Project Management Committee (PMC) member, RIP were proposed, discussed and accepted. After the necessary time planning, we started to design, coding and discuss, exchange code implementation details, which includes several meetups to gather together to discuss and review the code until the later online verification and released. More interesting, in the following review process, another cloud vendor from the community has joined. After simple video communication, the original implementation was optimized to be compatible with its implementation. Finally, in the community, we are happy to see that the new version has been verified in production by two cloud vendors. The ACL feature is also a process in which the PMC and the community continue to collaborate, and the final version of the RIP is finally published. Through the meetup we collected the requirements, through open discussion, coupled with the video communication using Zoom, the RocketMQ community completed the several important releases in the last year. At the same time, in order to better promote ecological flourishing, several projects residing under the Apache RocketMQ external repository were reorganized (80% above projects contributed by community during incubation). In addition to setting milestones, this time we added similar incubations and graduation mechanism further reduces the difficulty of community participation while better guarantee product quality. Today, several different language sdk projects that have graduated are from a large number of users in use and maintenance. The enthusiasm of the community completely surpasses thoughts. It also verifies that the future cloud architecture is language-independent, even serverless. Under this general trend, the community's guys actively participated in the RocketMQ multi-language ecological construction. RocketMQ now supports java, cpp, python, go, nodejs and other languages are planning and on the way. Even, the current CPP client can support up to 8 platforms, like CentOS, MacOS, Ubuntu and Windows.
Not only that, more and more community enthusiasts are also spontaneously self-organizing: they are also actively planning similar activities in the city station, but also need to give some attention and encouragement by PMCs. At the same time, this also provoked us to think about whether the Apache community should have a developer-oriented role like release manager, such as developer-relationship maintainer, project manager, to let more users understand, and become more involved in the product. The community development in recent years has also brought many new signs to the RocketMQ community. There are more and more active developers in the community. In roughly three months, nearly 2,000 emails were sent from the dev email list. Research has shown that 70% of top banks in China use Apache RocketMQ on the core business link, approximately 60% of Internet finance and insurance customers use RocketMQ in their production environments, and 75% of top 20 Internet companies in China widely use classic pub/sub scenarios.
Recently, the RocketMQ community has been discussing the development of the next-generation messaging platform. We hope it is a unified messaging engine with lightweight data processing platform, and welcome everyone to become involved and tell the PMC what features you are most looking forward to seeing in future versions of RocketMQ.
Many thanks to The Apache Software Foundation for its open and inclusive community culture that helps RocketMQ build a broader community. It will soon be 20th anniversary. I am pleased to represent the RocketMQ community in wishing the ASF a happy 20th anniversary, hoping for many more and continuing to thrive.
# # #
Part of the "Success at Apache" series, Project Perspectives chronicles how projects and their communities have benefited from The Apache Way.
Posted at 02:17AM Mar 20, 2019
by Sally in SuccessAtApache |