RSS

This Week in Flynn

The big news from this past week is that we shipped a complete rewrite of the scheduler. While this will not have any noticeable immediate impact beyond clearing up a few lingering bugs, it includes a number of enhancements under the hood that will enable future features.

The dashboard’s app history view now supports rolling back to previously deployed releases.

We also continued our focus on cleaning up bugs, with several more bugfixes shipped.

§ Changes

§ Enhancements

  • dashboard: Make app history items actionable (#1913)
  • bootstrap: Default min-hosts to len(peer-ips) when appropriate (#1930)
  • host: Update containerinit stream logging (#1928)
  • scheduler: Added issue numbers to TODO comments (#1923)
  • Implement Scheduler V2 (#1914)

§ Bugfixes

  • host: Fixed log fallback command in collect-debug-info (#1925)
  • cli: Fixed panic when force-adding cluster that conflicts with multiple clusters (#1926)
  • slugbuilder: Allow buildpack build to access client SSH keys (#1918)
  • dashboard: Fixed scale app (#1910)
  • schema: Fixed app JSON (#1909)

§ Stay in Touch

§ How You Can Help

This Week in Flynn

This past week we shipped a new addition to the dashboard: A view of the history of an app’s deploys and scale changes.

A number of fixes were also shipped, including a fix for the DigitalOcean installer.

§ Changes

§ Enhancements

  • dashboard: List app history (release and scale) (#1898)
  • all: Update Go to 1.4.3 (#1903)

§ Bugfixes

  • Fixed #1887 - Hanging DigitalOcean installer (#1908)
  • worker: Cancel deployments when worker shuts down (#1907)
  • updater: Increase timeout when deploying postgres (#1902)
  • script: Fixed duplicate flag name (#1896)

§ Stay in Touch

§ How You Can Help

This Week in Flynn

We shipped a long-awaited feature this week: the ability to run multi-node Flynn clusters on one machine, e.g. on a local Vagrant instance. This means that developers can test multi-node cluster functionality locally, rather than having to spin up multiple cloud instances.

We also shipped a number of browser compatibility fixes and usability enhancements as we work towards a polished 1.0 release.

§ Changes

§ Enhancements

  • Support running Flynn clusters on a single machine (#1891)
  • updater: Update status app (#1889)
  • installer,dashboard: Updated OSX cert install instructions (#1874)
  • test: Added failure count to GitHub CI hook failure notice (#1869)

§ Bugfixes

  • dashboard: Copy env from previous release when deploying commit (#1888)
  • dashboard: Fix install cert flow with security exception (#1886)
  • dashboard: Ensure event stream is connected (#1883)
  • util/assetbuilder: Install npm deps in Dockerfile (#1879)
  • test: Fixed SchedulerSuite.TestOmniJobs (#1857)
  • dashboard: Fixed issue causing blank page instead of login view (#1878)
  • dashboard: Fixed github auth (#1873)

§ Stay in Touch

§ How You Can Help

This Week in Flynn

This week brought two significant changes to Flynn.

The component that powers service discovery in Flynn, discoverd, now includes Raft in-process. This was the final component that required etcd, which had been a source of instability in Flynn clusters for some time. Etcd is no longer shipped with Flynn. This change had increased cluster stability substantially.

This is the first of several expected changes to our use of consensus algorithms. In the future we will only depend on Raft for leader election and consistent service state and instead use gossip for discovering service instances (which do not require consistency).

The installer can now install on arbitrary hosts via SSH. Until now the installer could only target public clouds like AWS, Azure, and Digital Ocean. Now you can install Flynn on any machine to which you have access by running flynn install.

§ Changes

§ Enhancements

  • Added failure count to IRC CI notifications (#1859)
  • Implemented generic SSH support in installer (#1830)
  • Added list of failures to CI list UI (#1858)
  • Updated pgx package (#1852)
  • Added logging to router startup (#1849)
  • Moved host removal tracking in integration tests (#1848)
  • Replaced etcd with discoverd in-process Raft (#1612, #1844, #1845, #1856)

§ Bugfixes

  • Fixed local git configuration when using installer (#1853)
  • Fixed adding hosts in CI (#1851)
  • Added vagrant user to libvirtd group (#1841)

§ Stay in Touch

§ How You Can Help

This Week in Flynn

Our focus this week was on a series of incremental improvements that increase stability and usability including a number of additions to the CLI.

§ Changes

§ Enhancements

  • Changed hstore usage to jsonb in controller (#1833)
  • Migrated blobstore from pq to pgx (#1832)
  • Updated pgx package (#1828)
  • Added support for choosing the port for a TCP route (#1813)
  • Added CLI command to list deployments (#1747)
  • Added CLI command to configure app git remote (#1786)
  • Updated dashboard to use SSE streams for sync (#1768)
  • Standardized on hyphenated UUIDs throughout Flynn (#1784, #1802, #1805)
  • Added logging to discoverd events (#1801)
  • Added job log tailing to flynn-host CLI (#1779)
  • Implemented support for custom git and controller URLs in CLI (#1795)
  • Removed unused container image storage drivers (#1788)
  • Added --quiet flag to flynn release (#1785)

§ Bugfixes

  • Fixed corrupt gitreceive caching (#1814)
  • Added error message for duplicate route (#1812)
  • Fixed app import with no git remote available (#1810)
  • Fixed gitreceive test configuration race (#1807)
  • Added cleanup for failed deployment queuing (#1798)
  • Added delay to racing deploy test (#1794)
  • Fixed adding/removing hosts in scheduler (#1793)
  • Fixed postgres deployment failures (#1792)
  • Fixed CI fallback logging (#1790)

§ Stay in Touch

§ How You Can Help

 RSS



Mailing List