Merge pull request #30 from cloud-gov/chore-news-migration

migrated news

content/news/articles/2015-05-29-week-update.md

@@ -0,0 +1,18 @@
+---
+layout: layouts/post
+tags: news
+date: 2015-05-29
+title: "Updates for the week of 5/29/2015"
+redirect_from:
+  - /updates/2015-05-29-week-update/
+---
+
+Platform:
+
+- Upgraded to release [210](https://github.com/cloudfoundry/cf-release/releases/tag/v210)
+- Binary and Static buildpacks are now built in the deployment
+- Added Newrelic Insights and Plugins for platform monitoring data
+
+Services:
+
+- The rds service now encrypts the passwords

content/news/articles/2015-09-01-sprint-4-update.md

@@ -0,0 +1,45 @@
+---
+layout: layouts/post
+tags: news
+date: 2015-09-01
+title: "Status page and console additions"
+redirect_from:
+  - /updates/2015-09-01-sprint-4-update/
+---
+
+We've added a new status page to show you the state of the cloud.gov platform, and we've made significant upgrades in your ability to manage your apps via the web.
+<!--more-->
+
+### Status Page
+As production use of cloud.gov ramps up, it's important that you have a constant picture of the platform's status, which may affect your product's operations and availability.
+
+We're now providing this visibility via the [cloud.gov Status Page](https://cloudgov.statuspage.io/), where you'll be able to see at a glance:
+
+- When there are any ongoing or recent degradations in service
+- When any maintenance is planned or recently completed
+
+We've proactively subscribed existing users to that page, so there's no need for any action on your part... You'll be notified via e-mail whenever problems are identified, or when planned maintenance is expected to impact your application's availability. However, you can also use the subscription control at the upper-right of the page to subscribe to updates via texts or Atom/RSS feed if you so choose.
+
+### Console Improvements
+In addition to the command-line client, the [cloud.gov web-based console](https://console.cloud.gov/) has now entered an alpha state. You can use the console to **review your organizations and spaces**, and **manage the state of your applications, services, and routes**. Creation of accounts, orgs, and spaces is still managed [via GitHub request]({{ site.baseurl }}/getting-started/setup/).
+
+Here are examples of actions now possible via the magic of your Interweb-capable browsing apparatus:
+
+- Traverse the layout of your accessible organizations and spaces
+- Control access to your owned orgs and spaces for other accounts
+- Browse a list of available services and provision new instances
+- Bind service instances with specific applications
+- Edit the routes that will bring user traffic to an application
+- Inspect the live resource utilization of a running application
+- Restart stopped or misbehaving applications
+
+If you've not taken a look in a while, please [check it out](https://console.cloud.gov/)!
+
+Note I said above the console is in "alpha" state, and really it's more of an MVP. Please [report problems or feature requests](https://github.com/18F/cf-deck/issues) or better yet, [make pull-requests](https://github.com/18F/cf-deck/pulls) via GitHub. (Side note: **We are short-handed on front-end/design/UI resources**, so any quick help anyone can offer, even if it's just some help with our IA, would be very **VERY** welcome!)
+
+### Other stuff
+We're now publishing our [roadmap](https://18f.storiesonboard.com/m/gov-dev) in [story-map form](http://jpattonassociates.com/wp-content/uploads/2015/03/story_mapping.pdf) in case anyone wants to get a peek at what we're focused on now and what we're juggling for the future. Our focus right now is: **Buttoning up loose ends that prevent us from offering cloud.gov to other agencies.**
+
+Our [intra-sprint kanban board](https://trello.com/b/ChGzyepo/gov-dev) is also visible, as is the [calendar of cloud.gov team rituals](https://www.google.com/calendar/embed?src=gsa.gov_0samf7guodi7o2jhdp0ec99aks%40group.calendar.google.com&ctz=America/Los_Angeles) for anyone who would like to attend.
+
+That's all for now...

content/news/articles/2015-09-14-sprint-5-update.md

@@ -0,0 +1,42 @@
+---
+layout: layouts/post
+tags: news
+date: 2015-09-14
+title: "Even more console features and a new home for updates"
+redirect_from:
+  - /updates/2015-09-14-sprint-5-update/
+---
+
+Now you can view log and event data for your apps and adjust permissions for your org and spaces via the web. We're also publishing these updates via [cloud.gov](http://cloud.gov/updates/).
+<!--more-->
+
+### View log and event data for your apps in the console
+When you take a look at the details for an application via the [cloud.gov console](http://console.cloud.gov), you'll now be able to see any recent logs generated by your application, as well as a list of recent deployment events from cloud.gov itself.
+
+<!--
+![Viewing logs for an app]({{site.baseurl}}/img/view-app-logs.png)
+
+![Viewing events for an app]({{site.baseurl}}/img/view-app-events.png)
+-->
+
+### Adjust permissions for your orgs and spaces in the console
+It's now possible to inspect and adjust the permissions for the individual orgs and spaces you control.
+
+<!--
+![Managing users for a space]({{site.baseurl}}/img/manage-space-users.png)
+
+![Adjusting a single user's permissions]({{site.baseurl}}/img/adjust-a-single-user.png)
+-->
+
+### Updates now published via the cloud.gov website
+We've also started consolidating announcement about updates to cloud.gov, like this one, on cloud.gov! [Check it out.](http://cloud.gov/updates/)
+
+### Want to know more?
+Follow our team:
+
+- Our [roadmap](https://18f.storiesonboard.com/m/gov-dev) in [story-map form](http://jpattonassociates.com/wp-content/uploads/2015/03/story_mapping.pdf)
+  - Current milestone: M2: Buttoning up loose ends that prevent us from offering cloud.gov to other agencies.
+- Our [kanban board for the current sprint](https://trello.com/b/ChGzyepo/gov-dev)
+- Our [calendar of team rituals](https://www.google.com/calendar/embed?src=gsa.gov_0samf7guodi7o2jhdp0ec99aks%40group.calendar.google.com&ctz=America/Los_Angeles)
+
+That’s all for now...

content/news/articles/2016-02-12-logs-update.md

@@ -0,0 +1,19 @@
+---
+layout: layouts/post
+tags: news
+date: 2016-02-12
+title: "Logging service"
+redirect_from:
+  - /updates/2016-02-12-logs-update/
+---
+
+New feature: Zero-setup persistent logs.
+<!--more-->
+
+Given the universal need for compliant logging, we've recently added a common logging facility to cloud.gov. Now, logs and events for every cloud.gov application are stored and indexed automatically, with zero setup required. 
+
+For more information about this feature, please see [our documentation about logging]({{ site.baseurl }}/apps/logs/#historic-logs:6d6e87c8985e9c9e781f22ee066f5a45).
+
+Now that cloud.gov provides platform-level logging, the ELK service we previously provided will be deprecated. If you are still using it, we recommend you delete the instance whenever is convenient to reduce your resource usage (and hence costs).
+
+If you have feedback about this service, please don't hesitate to [contact us](mailto:[email protected]).

content/news/articles/2016-06-15-auth-ssh-changes.md

@@ -0,0 +1,32 @@
+---
+layout: layouts/post
+tags: news
+date: 2016-06-15
+title: "Changes to login and cf-ssh"
+redirect_from:
+  - /updates/2016-06-15-auth-ssh-changes/
+---
+
+Earlier this month we updated **cloud.gov login** and **`cf-ssh`** in ways that mean most cloud.gov users need to change how they use them. You've probably already made these changes if you need to (we sent email notifications to people who should log in using the new system), but here are the details as a handy reference.
+<!--more-->
+
+### For GSA and EPA, your cloud.gov login is now your agency login
+
+We updated how @gsa.gov and @epa.gov accounts authenticate with cloud.gov. When you log in, use your official agency credentials instead of your old cloud.gov-specific username and password. Here's how:
+
+* **On the web:** At [https://login.cloud.gov/](https://login.cloud.gov/), select the button for your agency and enter your agency credentials (the same credentials you use for your agency's own services).
+* **On the command line:** Use the new command listed at [Setting up the command line]({{ site.baseurl }}/getting-started/setup/) for agency accounts: `cf login -a api.cloud.gov --sso`
+
+This update improves the security of these accounts because you're now using your agency's existing multi-factor authentication system. This is a step in our progress toward FedRAMP compliance and certification for cloud.gov.
+
+### Use the new version of `cf-ssh`
+
+If you use [`cf-ssh` for running one-off commands](https://cloud.gov/docs/management/using-ssh/), we released [version 3 on June 2](https://github.com/18F/cf-ssh/releases/). Please download and use that latest version.
+
+If you haven't updated `cf-ssh`, you may get this error when you try to use it:
+```shell
+Initiating tmate connection...success
+ssh: Could not resolve hostname tmate.18f.us: nodename nor servname provided, or not known
+```
+
+That usually means you need to update `cf-ssh` to our latest version.

content/news/articles/2016-07-07-deck-update.md

@@ -0,0 +1,42 @@
+---
+layout: layouts/post
+tags: news
+date: 2016-07-07
+title: "Today’s Dashboard update (formerly the “Deck”)"
+redirect_from:
+  - /updates/2016-07-07-deck-update/
+---
+
+Today we released a new version of the [cloud.gov Deck (now Dashboard)](https://dashboard.cloud.gov/). The best part is invisible: we refactored the codebase so we can improve it much faster than we could with the old version. But it has visible changes too, so here’s what’s new, what we have in mind, and how to tell us what you think.
+<!--more-->
+
+We'll keep the [old Deck](https://console.cloud.gov/) around for about a week and then will redirect it to this new version. Let us know if this would cause problems for you.
+
+### What's new and different
+
+* **Name:** We took this opportunity to rename it from the “Deck” to the “Dashboard”, since that’s what people usually call it.
+* **Style:** It fits into the overall cloud.gov style and navigation! So for example, when you’re in the Dashboard troubleshooting something, you can easily go look at [documentation]({{ site.baseurl }}/docs/) and [status](https://cloudgov.statuspage.io/).
+* **Navigation:** Navigating to your orgs, spaces, and apps is simpler: the sidebar displays a straightforward list of the orgs and spaces in your account, along with the marketplaces available for your orgs. You won’t have to click as many menus to do common tasks.
+* **Labels:** Data about your apps has unit labels to identify whether numbers are in GB or MB.
+* **Code:** The Dashboard's refactored codebase has better tests and less repetition.
+* **More potential for open source collaboration:** This improved codebase will help us encourage reuse and contributions by outside-18F teams that are also building tools on top of Cloud Foundry.
+
+### What’s missing in this version
+
+* **App management options:** This version doesn’t include all the earlier Deck’s options for managing apps (such as starting/stopping them, binding services, and updating routes). Instead, it links to documentation for those tasks on the command line. These web options weren’t used much, and we’re researching whether we should prioritize rebuilding them. (We’re curious what you think.)
+* **App logs and events:** The Dashboard now points to [logs.cloud.gov](https://login.cloud.gov/) for viewing app logs and events, instead of duplicating it.
+* **Quota meter:** We didn’t re-implement the small quota indicator from the old Deck, since it was mostly mysterious to people. We’re researching how to helpfully explain your quota usage.
+* **Perfectly bug-free experience:** We have a list of [known bugs](https://github.com/18F/cg-deck/issues?q=is%3Aopen+is%3Aissue+label%3Abug) — please feel free to file more if you notice something weird or broken.
+
+### What we’ve heard that people want
+
+As we figure out next steps, we know that people want the Dashboard to help them:
+
+* Understand how to use cloud.gov
+* Troubleshoot apps that are having problems
+* Do more tasks that are only available on the command line
+* Get insight into quotas and billing
+
+### We’d like your thoughts
+
+Everyone can [file issues](https://github.com/18F/cg-deck/issues) for bugs and suggestions. If you're in 18F, come talk to us about the Dashboard in [#cloud-gov-navigator](https://gsa-tts.slack.com/messages/cloud-gov-navigator/). If you're a cloud.gov user outside 18F, you can send thoughts and questions to us at [[email protected]](mailto:[email protected]).

content/news/articles/2016-07-19-fedramp-ready.md

@@ -0,0 +1,10 @@
+---
+layout: layouts/post
+tags: news
+date: 2016-07-19
+title: "Full steam ahead on FedRAMP assessment"
+redirect_from:
+  - /updates/2016-07-19-fedramp-ready/
+---
+
+Over on the 18F team blog, [we've posted an update on cloud.gov's FedRAMP assessment progress](https://18f.gsa.gov/2016/07/18/cloud-gov-full-steam-ahead-fedramp-assessment-process/). In short: we've passed the FedRAMP Ready milestone, and we expect to receive FedRAMP Joint Authorization Board (JAB) Provisional Authority to Operate (P-ATO) in November. [More details in the post!](https://18f.gsa.gov/2016/07/18/cloud-gov-full-steam-ahead-fedramp-assessment-process/)

content/news/articles/2016-11-18-release-notes.md

@@ -0,0 +1,27 @@
+---
+layout: layouts/post
+tags: news
+date: 2016-11-18
+title: "Platform Release Notes"
+redirect_from:
+  - /updates/2016-11-18-release-notes/
+---
+
+Curious what’s new that you might find helpful as a cloud.gov application developer? Here are highlights from our platform updates over the past four weeks.
+<!--more-->
+
+### Added
+- cloud.gov supports the [.NET Core buildpack](https://docs.cloudfoundry.org/buildpacks/dotnet-core/index.html) ([learn about buildpacks]({{ site.baseurl }}/docs/getting-started/concepts#buildpacks)).
+- You can [invite](https://account.fr.cloud.gov/invite) teammates who aren’t in agencies with supported single-sign-on authentication (GSA, EPA, FDIC). After you invite them, they can log in by creating a cloud.gov account with multi-factor authentication.
+- The [dashboard](https://dashboard.fr.cloud.gov) shows the current memory, disk usage and quota limits for apps.
+- You can create [deployer accounts]({{ site.baseurl }}/docs/apps/continuous-deployment#govcloud-environment-deployer-account-broker) programmatically.
+- For FDIC users: you can log into cloud.gov using your agency single-sign-on credentials.
+
+### Changed
+- We upgraded Cloud Foundry (the underlying open source project that powers cloud.gov) to [Release v246](https://github.com/cloudfoundry/cf-release/releases/tag/v246), which includes updates to buildpacks and improvements for internal components.
+
+### Security
+You can [restage](https://docs.cloudfoundry.org/devguide/deploy-apps/start-restart-restage.html#restage) your application to incorporate the latest security fixes and ensure you’re running the most recent language version supported.
+
+- The PHP buildpack update addresses [USN-3095-1](https://www.ubuntu.com/usn/usn-3095-1/) (assorted PHP vulnerabilities) with PHP 5.6.27 and 7.0.12. The associated CVEs are [CVE-2016-7124](https://ubuntu.com/security/CVE-2016-7124), [CVE-2016-7125](https://ubuntu.com/security/CVE-2016-7125), [CVE-2016-7127](https://ubuntu.com/security/CVE-2016-7127), [CVE-2016-7128](https://ubuntu.com/security/CVE-2016-7128), [CVE-2016-7129](https://ubuntu.com/security/CVE-2016-7129), [CVE-2016-7130](https://ubuntu.com/security/CVE-2016-7130), [CVE-2016-7131](https://ubuntu.com/security/CVE-2016-7131), [CVE-2016-7132](https://ubuntu.com/security/CVE-2016-7132), [CVE-2016-7133](https://ubuntu.com/security/CVE-2016-7133), [CVE-2016-7134](https://ubuntu.com/security/CVE-2016-7134), [CVE-2016-7411](https://ubuntu.com/security/CVE-2016-7411), [CVE-2016-7412](https://ubuntu.com/security/CVE-2016-7412), [CVE-2016-7413](https://ubuntu.com/security/CVE-2016-7413), [CVE-2016-7414](https://ubuntu.com/security/CVE-2016-7414), [CVE-2016-7416](https://ubuntu.com/security/CVE-2016-7416), [CVE-2016-7417](https://ubuntu.com/security/CVE-2016-7418), [CVE-2016-7418](https://ubuntu.com/security/CVE-2016-7418)
+- The Node buildpack update addresses [USN-3087-1](https://www.ubuntu.com/usn/usn-3087-1/) (assorted OpenSSL vulnerabilities) with node 6.8.1 and 6.9.0. The associated CVEs are [CVE-2016-2177](https://ubuntu.com/security/CVE-2016-2177), [CVE-2016-2178](https://ubuntu.com/security/CVE-2016-2178), [CVE-2016-2179](https://ubuntu.com/security/CVE-2016-2179), [CVE-2016-2180](https://ubuntu.com/security/CVE-2016-2180), [CVE-2016-2181](https://ubuntu.com/security/CVE-2016-2181), [CVE-2016-2182](https://ubuntu.com/security/CVE-2016-2182), [CVE-2016-2183](https://ubuntu.com/security/CVE-2016-2183), [CVE-2016-6302](https://ubuntu.com/security/CVE-2016-6302), [CVE-2016-6303](https://ubuntu.com/security/CVE-2016-6303), [CVE-2016-6304](https://ubuntu.com/security/CVE-2016-6304), [CVE-2016-6306](https://ubuntu.com/security/CVE-2016-6306)

content/news/articles/2016-11-30-release-notes.md

@@ -0,0 +1,28 @@
+---
+layout: layouts/post
+tags: news
+date: 2016-11-30
+title: "Platform Release Notes"
+redirect_from:
+  - /updates/2016-11-30-release-notes/
+---
+
+Curious what’s new that you might find helpful as a cloud.gov application developer? Here are highlights from our platform updates over the past two weeks.
+<!--more-->
+
+### Added
+- The [dashboard](https://dashboard.fr.cloud.gov) now allows restarting of apps from the app page.
+
+### Changed
+- We upgraded Cloud Foundry (the underlying open source project that powers cloud.gov) to [Release v247](https://github.com/cloudfoundry/cf-release/releases/tag/v247), which includes updates to buildpacks and improvements for internal components. 
+
+### Fixed
+- **Dashboard**: We fixed an [issue](https://github.com/18F/cg-dashboard/issues/672) that prevented creating service instances on the marketplace page.
+
+### Security
+The base filesystem used for running your application has been updated to address several security vulnerabilities. You can [restage your application](http://cli.cloudfoundry.org/en-US/cf/restage.html) to ensure you [incorporate fixes in the base filesystem](https://docs.cloudfoundry.org/devguide/deploy-apps/stacks.html#cli-commands) and are running the most recent language version supported by your [buildpack](https://docs.cloudfoundry.org/buildpacks/).
+
+- [USN-3116-1: DBus vulnerabilities](https://www.ubuntu.com/usn/usn-3116-1/). The associated CVE is [CVE-2015-0245](https://ubuntu.com/security/CVE-2015-0245)
+- [USN-3117-1: GD library vulnerabilities](https://www.ubuntu.com/usn/usn-3117-1/). The associated CVEs are [CVE-2016-6911](https://ubuntu.com/security/CVE-2016-6911), [CVE-2016-7568](https://ubuntu.com/security/CVE-2016-7568), [CVE-2016-8670](https://ubuntu.com/security/CVE-2016-8670)
+- [USN-3119-1: Bind vulnerability](https://www.ubuntu.com/usn/usn-3119-1/). The associated CVE is [CVE-2016-8864](https://ubuntu.com/security/CVE-2016-8864)
+- [USN-3123-1: curl vulnerabilities](https://www.ubuntu.com/usn/usn-3123-1/). The associated CVEs are [CVE-2016-7141](https://ubuntu.com/security/CVE-2016-7141), [CVE-2016-7167](https://ubuntu.com/security/CVE-2016-7167), [CVE-2016-8615](https://ubuntu.com/security/CVE-2016-8615), [CVE-2016-8616](https://ubuntu.com/security/CVE-2016-8616), [CVE-2016-8617](https://ubuntu.com/security/CVE-2016-8617), [CVE-2016-8618](https://ubuntu.com/security/CVE-2016-8618), [CVE-2016-8619](https://ubuntu.com/security/CVE-2016-8619), [CVE-2016-8620](https://ubuntu.com/security/CVE-2016-8620), [CVE-2016-8621](https://ubuntu.com/security/CVE-2016-8621), [CVE-2016-8622](https://ubuntu.com/security/CVE-2016-8622), [CVE-2016-8623](https://ubuntu.com/security/CVE-2016-8623), [CVE-2016-8624](https://ubuntu.com/security/CVE-2016-8624)