RSS

This Week in Flynn

The Flynn team is in London this week. CTO Jonathan Rudenberg will be at the London PaaS User Group (LOPUG) on Thursday, January 14th, 6:30PM at the Pivotal Labs London office to talk about Flynn. See the LOPUG Meetup page for more details.

If you are a Flynn user or would like to learn more about Flynn be sure to come by LOPUG on Thursday.

§ Changes

§ Enhancements

  • test/rootfs: Add redis-server to test infrastructure (#2354)
  • script: Refactor multi-node bootstrap. (#2340)

§ Bugfixes

  • router: Workaround currently broken test in Go 1.4.3 (#2356)
  • test/rootfs: Install go cover tool in rootfs (#2357)
  • slugbuilder: Only exclude ‘.git’ at the root of the slug (#2349)

§ Stay in Touch

§ How You Can Help

This Week in Flynn

The Flynn team continues to meet with users in Europe this month. Next week we’ll be in London, where Jonathan will be talking about Flynn at the London PaaS User Group (LOPUG) on Thursday, January 14th, 6:30PM at the Pivotal Labs London office. See the LOPUG Meetup page for more details. Come to learn about and discuss Flynn, stay for the free pizza and drinks.

A fix landed for a bug in which the deploy screen does not update after a deploy is completed.

§ Changes

§ Bugfixes

  • docs: Fixed email link (#2347)
  • dashboard: Fix deploy completion state transition (#2342)
  • host: Ensure new jobs are added to state when resurrecting (#2339)

§ Stay in Touch

§ How You Can Help

This Week in Flynn

We are hosting a meetup at 32c3 tomorrow, Tuesday 12/29, at 16:00 local time in hall C.1. Check 32c3’s calendar for more details.

We shipped a big new feature: Tag based scheduling. This enables jobs to be only run on hosts with specific tags. To set a tag on a host, use flynn-host tags set <hostid> <tag>=<value>. <hostid> can be retrieved with flynn-host list. To add tags to a job, use flynn scale <jobtype>=<processes>,<tag>=<value>. e.g.:

# On a flynn host
$ flynn-host tags set flynn1000000001 size=large

# From local codebase
$ flynn scale web=3,size=large

Members of the Flynn team are in Europe for the first half of January. If you’d like to meet up with us, email us at contact@flynn.io

§ Changes

§ Enhancements

  • Tag based scheduling (#2203)

§ Bugfixes

  • host: Only call state.SetContainerIP if the job has an IP (#2337)

§ Stay in Touch

§ How You Can Help

This Week in Flynn

We continued work on stability and performance this week.

Flynn developers now have the option of booting a cluster using a Flynn release with script/bootstrap-flynn by using the --version flag, e.g. script/bootstrap-flynn --version v20151214.1.

§ Changes

§ Enhancements

  • controller: Add “pending” job state (#2295)
  • host: Add version to status (#2302)
  • script: Support booting clusters using released versions (#2301)

§ Bugfixes

  • controller: Stop the formation listener on shutdown (#2335)
  • controller: Close database listeners on shutdown (#2329)
  • scheduler: Fix restarting jobs which failed to start (#2333)
  • test: Skip migrating cluster domain in TestExampleOutput (#2330)
  • scheduler: Prevent TestStopJob from blocking persisting jobs (#2331)
  • host: Buffer the containerinit state stream channel (#2328)
  • host: Perform explicit check for running containers (#2325)
  • controller: Deploy web processes using service events (#2326)
  • cli: Fix git config on Windows (#2324)
  • router: Only remove from routing tree if route matches (#2322)
  • installer: Fix CA Cert file extension (#2321)
  • Dashboard error handling improvements (#2320)
  • all: Use curl –fail whenever we pipe output with –silent (#2309)
  • dashboard: Fix app view UI from exceeding container bounds (#2318)
  • dashboard: Allow editing app env when no release (#2317)
  • test: Fix flynn cluster add command (#2319)
  • scheduler: Copy original processes in Formation.SetProcesses (#2305)
  • docs: Update “Routes” section of “Using Flynn” to mention path routes (#2312)
  • installer: Fix cert filename when downloading in Safari (#2314)
  • Update controller API docs (#2313)
  • controller: Migration listener (#2306)
  • router: Handle route deletions missed on reconnect (#2296)
  • controller: Make Job.HostError a pointer (#2303)
  • dashboard,pkg/cors: Fix CORS for dashboard ping endpoint (#2297)
  • host: Ensure log stream fds are closed (#2293)
  • Update controller API docs (#2292)
  • router: Add default to HTTP route path column (#2291)
  • Fix installer bugs (#2290)
  • updater: Fix MinVersion logic (#2289)

§ Stay in Touch

§ How You Can Help

Flynn Update: Online Meetup, 32c3, and more

We will host a Flynn online meetup this Thursday, December 17th at 9:00am EST. RSVP here.

§ Adoption

We’re thrilled to see so many users moving forward with Flynn deployments since the launch of the stable release channel last month.

We built Flynn to be a tool that delights developers and operators so meeting so many happy users is particularly exciting for our team.

We’re also very happy to be able to support a fast-growing number of production users and hope to be able to share some of their stories in a future newsletter.

§ Recent Changes

We’ve spent most of our time over the past month supporting new deployments and fixing small user-reported bugs, but feature development has also moved forward.

We just shipped HTTP path-based routing which has been a particularly popular request recently.

You can also find weekly development updates here on the Flynn Blog.

§ Online Events

This Thursday we’ll host an online meetup using Google Hangouts.

RSVP here

Although our team is spread out across three continents and we travel a lot, we still can’t see everyone in person. We’re going to try a series of online meetups to connect with users who we wouldn’t normally see.

This should work a lot like an in-person event, we’ll start with a short demo and then answer questions. Questions can be submitted in advance by email or using the Q&A button on Google Hangouts.

If these work well, we will stagger the timing in the future to make it easier for those in different time zones.

We’ll also make a video available for those who can’t join us synchronously.

§ In-person Events

We have a lot of travel planned in the next month. Most of our team will be at the 32nd Chaos Communication Congress in Hamburg, Germany 27-30 December.

We’ve scheduled a meetup on Tuesday 29 December at the conference and are also happy to meet with users individually while we’re there. Email us if you’d like to connect!

We are also planning to visit users in other cities in Europe, especially 11-14 January, 2016.

If you’re a current or prospective user and have an event or team you’d like us to speak at/with in Europe that week, let us know and we’ll try to make it happen.

We’re also looking for a venue to host a public meetup in London during that time as well. Contact us if you know of anywhere that’s available!

§ Connect

Wherever in the world you are, if you would like a Flynn team member to visit your local group for a Flynn talk, email us.

We can also help you put together your own presentation on Flynn if you’d like. Several users have already given successful talks on Flynn at conferences and community events.

§ Feedback

As always we want to thank our community and users for their support. We strongly encourage community contributions of code, documentation, and blog posts. We also try to send out T-shirts and stickers to everyone after their first commit or blog post. If you have already made a contribution, but haven’t received a package email us.

We want to hear about any problems, success, pain, or pleasure you’re having with Flynn.

If you have any feedback or questions about Flynn please stop by IRC (#flynn on Freenode), join the Google Group, file issues on GitHub, or email our team any time.

 RSS



Mailing List