"Couldn't automatically load credentials" about classicswarm

[fermayo]

The go-tutum library version in #87 does not have that anymore. It should be fixed once that PR is merged. Sorry about that!

[shykes]

Sounds good, thanks!

On Wednesday, June 18, 2014, Fernando Mayo [email protected] wrote:

The go-tutum library version in #87
moby/swarmkit#87 does not have that anymore.
It should be fixed once that PR is merged. Sorry about that!

—
Reply to this email directly or view it on GitHub
moby/swarmkit#89 (comment).

[aluzzardi]

Hi there. I've got good news and bad news :)

The bad news is that I am closing this pull request - not because we don't like it, but because we are rebooting the project with a narrowed scope and a cleaned up codebase. As a result, your patch will probably not merge cleanly, and depending on which area it targeted (clustering, machine management or abstract service composition) you might need to open your PR on a different repo. Read below for details. We're really sorry for the inconvenience, as we know some of you put a lot of effort in these contributions. We really appreciate any contribution and promise that your experience will be very different if you choose to continue the work - we hope you do!

The good news is, Swarm is back! It now has a simpler and narrowed down focus, a fresh codebase, and a full-time team of maintainers hacking away day and night, and eager to review your contributions.

We just announced the details at Dockercon. Here's the summary:

• The project is now just called "Swarm". It is a simple clustering system which speaks the Docker API
• It includes a full-featured "batteries included" scheduler with bin packing and resource management
• We plan on bringing back pluggable backends once the user experience is awesome
• We are announcing a partnership with Mesosphere, to contribute a Mesos backend. There will be a live session soon, if you're interested
• The primary form factor is the command-line, not a library (although it will still be possible to import it as a Go package)
• Depending on user feedback we will aim for tighter integration with the Docker core, but it is not a short-term priority: thanks to API compatibility we already have a seamless way to drop Swarm into a Docker deployment.
• We announced a new project, [Docker Machine|https://github.com/docker/machine] which takes over the machine management aspect. If your work is related to Rackspace, Azure, EC2, SSH, Openstack etc, you should go check out that repo. We hope you will join the effort! It's a really awesome project.
• We are moving the libchan-based service composition abstraction into the libchan repo. This will help iterate on the best interface, without interfering with the immediate implementation of machine and swarm.

TLDR: more focus, new code, new team, ship real things early and often.

Swarm is back!

Sincerely,
Andrea, Victor and Solomon