cf-dev@lists.cloudfoundry.org | MEGA team mitosis

Home Messages Hashtags Subgroups

Date Date 1 - 6 of 6

MEGA team mitosis

Amit Kumar Gupta #2886 Hey all, The CF Release Integration team (also known as "MEGA") will be splitting into two smaller teams. The current team's responsibilities included: - splitting out, maintaining, and adding features to an etcd-release - splitting out, maintaining, and adding features to a consul-release - splitting out and maintaining a NATS-release - splitting out and maintaining a "pre-diego-runtime"-release (DEA, Warden, HM9k) - splitting out and maintaining a postgres-release - owning the CATS and cf-smoke-tests - managing the main integration pipelines that take all the bits and create a usable, well-tested distribution of the CF components - managing the cf-release repo, and the final release process - building tooling to generate manifests that compose all the split-out releases - building tooling to automate bootstrapping environments for Concourse and CF (no more snowflakes) - canary apps used to monitor integration and production environments - providing other common functionality, e.g. route registration This is a lot of context for a small team of two pairs to juggle, and it could arguably be the work of several teams, but we will start with two one-pair teams for now. CF Release Integration (no longer referred to as MEGA?) - splitting out and maintaining a "pre-diego-runtime"-release (DEA, Warden, HM9k) - owning the CATS and cf-smoke-tests - managing the main integration pipelines that take all the bits and create a usable, well-tested distribution of the CF components - managing the cf-release repo, and the final release process - building tooling to generate manifests that compose all the split-out releases - canary apps used to monitor integration and production environments - providing other common functionality, e.g. route registration Product Manager: Amit Gupta, Pivotal Lead Engineer: Rob Dimsdale, Pivotal Engineer: Zachary Auerbach, Pivotal CF Infrastructure - splitting out, maintaining, and adding features to an etcd-release - splitting out, maintaining, and adding features to a consul-release - splitting out and maintaining a NATS-release - splitting out and maintaining a postgres-release - building tooling to generate manifests that compose all the split-out releases Product Manager: Amit Gupta, Pivotal Lead Engineer: Ryan Moran, Pivotal Engineer: Adrian Zankich, Pivotal We look forward to collaborating with all of you, we're still on the usual communication channels -- the cf-dev mailing list, and issues and PR on GitHub -- no changes there! Cheers, Amit attachment.html attachment.html
More All Messages By This Member
Amit Kumar Gupta #2887 One more thing to add, we're also keeping an eye on the "cloudfoundry" tag on StackOverflow, so feel free to ask questions there as well. Best, Amit toggle quoted message Show quoted text On Wed, Nov 25, 2015 at 8:04 PM, Amit Gupta <agupta(a)pivotal.io> wrote: Hey all, The CF Release Integration team (also known as "MEGA") will be splitting into two smaller teams. The current team's responsibilities included: - splitting out, maintaining, and adding features to an etcd-release - splitting out, maintaining, and adding features to a consul-release - splitting out and maintaining a NATS-release - splitting out and maintaining a "pre-diego-runtime"-release (DEA, Warden, HM9k) - splitting out and maintaining a postgres-release - owning the CATS and cf-smoke-tests - managing the main integration pipelines that take all the bits and create a usable, well-tested distribution of the CF components - managing the cf-release repo, and the final release process - building tooling to generate manifests that compose all the split-out releases - building tooling to automate bootstrapping environments for Concourse and CF (no more snowflakes) - canary apps used to monitor integration and production environments - providing other common functionality, e.g. route registration This is a lot of context for a small team of two pairs to juggle, and it could arguably be the work of several teams, but we will start with two one-pair teams for now. CF Release Integration (no longer referred to as MEGA?) - splitting out and maintaining a "pre-diego-runtime"-release (DEA, Warden, HM9k) - owning the CATS and cf-smoke-tests - managing the main integration pipelines that take all the bits and create a usable, well-tested distribution of the CF components - managing the cf-release repo, and the final release process - building tooling to generate manifests that compose all the split-out releases - canary apps used to monitor integration and production environments - providing other common functionality, e.g. route registration Product Manager: Amit Gupta, Pivotal Lead Engineer: Rob Dimsdale, Pivotal Engineer: Zachary Auerbach, Pivotal CF Infrastructure - splitting out, maintaining, and adding features to an etcd-release - splitting out, maintaining, and adding features to a consul-release - splitting out and maintaining a NATS-release - splitting out and maintaining a postgres-release - building tooling to generate manifests that compose all the split-out releases Product Manager: Amit Gupta, Pivotal Lead Engineer: Ryan Moran, Pivotal Engineer: Adrian Zankich, Pivotal We look forward to collaborating with all of you, we're still on the usual communication channels -- the cf-dev mailing list, and issues and PR on GitHub -- no changes there! Cheers, Amit attachment.html attachment.html
More All Messages By This Member
John Feminella #2889 How will the #mega Slack channel on CF split and/or be renamed as a result of the reorganization? (Or will it?) -- John Feminella Advisory Platform Architect ✉ · jfeminella(a)pivotal.io t · @jxxf <https://twitter.com/jxxf> toggle quoted message Show quoted text On Wed, Nov 25, 2015 at 11:14 PM, Amit Gupta <agupta(a)pivotal.io> wrote: One more thing to add, we're also keeping an eye on the "cloudfoundry" tag on StackOverflow, so feel free to ask questions there as well. Best, Amit On Wed, Nov 25, 2015 at 8:04 PM, Amit Gupta <agupta(a)pivotal.io> wrote: Hey all, The CF Release Integration team (also known as "MEGA") will be splitting into two smaller teams. The current team's responsibilities included: - splitting out, maintaining, and adding features to an etcd-release - splitting out, maintaining, and adding features to a consul-release - splitting out and maintaining a NATS-release - splitting out and maintaining a "pre-diego-runtime"-release (DEA, Warden, HM9k) - splitting out and maintaining a postgres-release - owning the CATS and cf-smoke-tests - managing the main integration pipelines that take all the bits and create a usable, well-tested distribution of the CF components - managing the cf-release repo, and the final release process - building tooling to generate manifests that compose all the split-out releases - building tooling to automate bootstrapping environments for Concourse and CF (no more snowflakes) - canary apps used to monitor integration and production environments - providing other common functionality, e.g. route registration This is a lot of context for a small team of two pairs to juggle, and it could arguably be the work of several teams, but we will start with two one-pair teams for now. CF Release Integration (no longer referred to as MEGA?) - splitting out and maintaining a "pre-diego-runtime"-release (DEA, Warden, HM9k) - owning the CATS and cf-smoke-tests - managing the main integration pipelines that take all the bits and create a usable, well-tested distribution of the CF components - managing the cf-release repo, and the final release process - building tooling to generate manifests that compose all the split-out releases - canary apps used to monitor integration and production environments - providing other common functionality, e.g. route registration Product Manager: Amit Gupta, Pivotal Lead Engineer: Rob Dimsdale, Pivotal Engineer: Zachary Auerbach, Pivotal CF Infrastructure - splitting out, maintaining, and adding features to an etcd-release - splitting out, maintaining, and adding features to a consul-release - splitting out and maintaining a NATS-release - splitting out and maintaining a postgres-release - building tooling to generate manifests that compose all the split-out releases Product Manager: Amit Gupta, Pivotal Lead Engineer: Ryan Moran, Pivotal Engineer: Adrian Zankich, Pivotal We look forward to collaborating with all of you, we're still on the usual communication channels -- the cf-dev mailing list, and issues and PR on GitHub -- no changes there! Cheers, Amit attachment.html attachment.html
More All Messages By This Member
Amit Kumar Gupta #2890 Good question. We have two new slack channels: #infrastructure and #release-integration. The #mega channel's "purpose" tagline is updated to redirect people to the other two, and I've also configured a daily reminder that Slackbot will post to the #mega channel redirecting folks to the other two. I will also monitor the #mega channel and 301 people to the new channels until it dies down enough, and will then archive the channel. Best, Amit On Wed, Nov 25, 2015 at 9:14 PM, John Feminella <jfeminella(a)pivotal.io> wrote: How will the #mega Slack channel on CF split and/or be renamed as a result of the reorganization? (Or will it?) -- John Feminella Advisory Platform Architect ✉ · jfeminella(a)pivotal.io t · @jxxf <https://twitter.com/jxxf> On Wed, Nov 25, 2015 at 11:14 PM, Amit Gupta <agupta(a)pivotal.io> wrote: One more thing to add, we're also keeping an eye on the "cloudfoundry" tag on StackOverflow, so feel free to ask questions there as well. Best, Amit On Wed, Nov 25, 2015 at 8:04 PM, Amit Gupta <agupta(a)pivotal.io> wrote: Hey all, The CF Release Integration team (also known as "MEGA") will be splitting into two smaller teams. The current team's responsibilities included: - splitting out, maintaining, and adding features to an etcd-release - splitting out, maintaining, and adding features to a consul-release - splitting out and maintaining a NATS-release - splitting out and maintaining a "pre-diego-runtime"-release (DEA, Warden, HM9k) - splitting out and maintaining a postgres-release - owning the CATS and cf-smoke-tests - managing the main integration pipelines that take all the bits and create a usable, well-tested distribution of the CF components - managing the cf-release repo, and the final release process - building tooling to generate manifests that compose all the split-out releases - building tooling to automate bootstrapping environments for Concourse and CF (no more snowflakes) - canary apps used to monitor integration and production environments - providing other common functionality, e.g. route registration This is a lot of context for a small team of two pairs to juggle, and it could arguably be the work of several teams, but we will start with two one-pair teams for now. CF Release Integration (no longer referred to as MEGA?) - splitting out and maintaining a "pre-diego-runtime"-release (DEA, Warden, HM9k) - owning the CATS and cf-smoke-tests - managing the main integration pipelines that take all the bits and create a usable, well-tested distribution of the CF components - managing the cf-release repo, and the final release process - building tooling to generate manifests that compose all the split-out releases - canary apps used to monitor integration and production environments - providing other common functionality, e.g. route registration Product Manager: Amit Gupta, Pivotal Lead Engineer: Rob Dimsdale, Pivotal Engineer: Zachary Auerbach, Pivotal CF Infrastructure - splitting out, maintaining, and adding features to an etcd-release - splitting out, maintaining, and adding features to a consul-release - splitting out and maintaining a NATS-release - splitting out and maintaining a postgres-release - building tooling to generate manifests that compose all the split-out releases Product Manager: Amit Gupta, Pivotal Lead Engineer: Ryan Moran, Pivotal Engineer: Adrian Zankich, Pivotal We look forward to collaborating with all of you, we're still on the usual communication channels -- the cf-dev mailing list, and issues and PR on GitHub -- no changes there! Cheers, Amit attachment.html attachment.html
More All Messages By This Member
John Feminella #2891 Awesome! Thanks Amit. -- John Feminella Advisory Platform Architect ✉ · jfeminella(a)pivotal.io t · @jxxf <https://twitter.com/jxxf> toggle quoted message Show quoted text On Thu, Nov 26, 2015 at 12:40 AM, Amit Gupta <agupta(a)pivotal.io> wrote: Good question. We have two new slack channels: #infrastructure and #release-integration. The #mega channel's "purpose" tagline is updated to redirect people to the other two, and I've also configured a daily reminder that Slackbot will post to the #mega channel redirecting folks to the other two. I will also monitor the #mega channel and 301 people to the new channels until it dies down enough, and will then archive the channel. Best, Amit On Wed, Nov 25, 2015 at 9:14 PM, John Feminella <jfeminella(a)pivotal.io> wrote: How will the #mega Slack channel on CF split and/or be renamed as a result of the reorganization? (Or will it?) -- John Feminella Advisory Platform Architect ✉ · jfeminella(a)pivotal.io t · @jxxf <https://twitter.com/jxxf> On Wed, Nov 25, 2015 at 11:14 PM, Amit Gupta <agupta(a)pivotal.io> wrote: One more thing to add, we're also keeping an eye on the "cloudfoundry" tag on StackOverflow, so feel free to ask questions there as well. Best, Amit On Wed, Nov 25, 2015 at 8:04 PM, Amit Gupta <agupta(a)pivotal.io> wrote: Hey all, The CF Release Integration team (also known as "MEGA") will be splitting into two smaller teams. The current team's responsibilities included: - splitting out, maintaining, and adding features to an etcd-release - splitting out, maintaining, and adding features to a consul-release - splitting out and maintaining a NATS-release - splitting out and maintaining a "pre-diego-runtime"-release (DEA, Warden, HM9k) - splitting out and maintaining a postgres-release - owning the CATS and cf-smoke-tests - managing the main integration pipelines that take all the bits and create a usable, well-tested distribution of the CF components - managing the cf-release repo, and the final release process - building tooling to generate manifests that compose all the split-out releases - building tooling to automate bootstrapping environments for Concourse and CF (no more snowflakes) - canary apps used to monitor integration and production environments - providing other common functionality, e.g. route registration This is a lot of context for a small team of two pairs to juggle, and it could arguably be the work of several teams, but we will start with two one-pair teams for now. CF Release Integration (no longer referred to as MEGA?) - splitting out and maintaining a "pre-diego-runtime"-release (DEA, Warden, HM9k) - owning the CATS and cf-smoke-tests - managing the main integration pipelines that take all the bits and create a usable, well-tested distribution of the CF components - managing the cf-release repo, and the final release process - building tooling to generate manifests that compose all the split-out releases - canary apps used to monitor integration and production environments - providing other common functionality, e.g. route registration Product Manager: Amit Gupta, Pivotal Lead Engineer: Rob Dimsdale, Pivotal Engineer: Zachary Auerbach, Pivotal CF Infrastructure - splitting out, maintaining, and adding features to an etcd-release - splitting out, maintaining, and adding features to a consul-release - splitting out and maintaining a NATS-release - splitting out and maintaining a postgres-release - building tooling to generate manifests that compose all the split-out releases Product Manager: Amit Gupta, Pivotal Lead Engineer: Ryan Moran, Pivotal Engineer: Adrian Zankich, Pivotal We look forward to collaborating with all of you, we're still on the usual communication channels -- the cf-dev mailing list, and issues and PR on GitHub -- no changes there! Cheers, Amit attachment.html attachment.html
More All Messages By This Member
Amit Kumar Gupta #2930 Correction to the original email: CF Infrastructure will work on "building tooling to automate bootstrapping environments for Concourse and CF (no more snowflakes)", not "building tooling to generate manifests that compose all the split-out releases" -- the Release Integration team will work on the latter. Thanks to Caleb Miles for the catch. Best, Amit On Wed, Nov 25, 2015 at 9:51 PM, John Feminella <jfeminella(a)pivotal.io> wrote: Awesome! Thanks Amit. -- John Feminella Advisory Platform Architect ✉ · jfeminella(a)pivotal.io t · @jxxf <https://twitter.com/jxxf> On Thu, Nov 26, 2015 at 12:40 AM, Amit Gupta <agupta(a)pivotal.io> wrote: Good question. We have two new slack channels: #infrastructure and #release-integration. The #mega channel's "purpose" tagline is updated to redirect people to the other two, and I've also configured a daily reminder that Slackbot will post to the #mega channel redirecting folks to the other two. I will also monitor the #mega channel and 301 people to the new channels until it dies down enough, and will then archive the channel. Best, Amit On Wed, Nov 25, 2015 at 9:14 PM, John Feminella <jfeminella(a)pivotal.io> wrote: How will the #mega Slack channel on CF split and/or be renamed as a result of the reorganization? (Or will it?) -- John Feminella Advisory Platform Architect ✉ · jfeminella(a)pivotal.io t · @jxxf <https://twitter.com/jxxf> On Wed, Nov 25, 2015 at 11:14 PM, Amit Gupta <agupta(a)pivotal.io> wrote: One more thing to add, we're also keeping an eye on the "cloudfoundry" tag on StackOverflow, so feel free to ask questions there as well. Best, Amit On Wed, Nov 25, 2015 at 8:04 PM, Amit Gupta <agupta(a)pivotal.io> wrote: Hey all, The CF Release Integration team (also known as "MEGA") will be splitting into two smaller teams. The current team's responsibilities included: - splitting out, maintaining, and adding features to an etcd-release - splitting out, maintaining, and adding features to a consul-release - splitting out and maintaining a NATS-release - splitting out and maintaining a "pre-diego-runtime"-release (DEA, Warden, HM9k) - splitting out and maintaining a postgres-release - owning the CATS and cf-smoke-tests - managing the main integration pipelines that take all the bits and create a usable, well-tested distribution of the CF components - managing the cf-release repo, and the final release process - building tooling to generate manifests that compose all the split-out releases - building tooling to automate bootstrapping environments for Concourse and CF (no more snowflakes) - canary apps used to monitor integration and production environments - providing other common functionality, e.g. route registration This is a lot of context for a small team of two pairs to juggle, and it could arguably be the work of several teams, but we will start with two one-pair teams for now. CF Release Integration (no longer referred to as MEGA?) - splitting out and maintaining a "pre-diego-runtime"-release (DEA, Warden, HM9k) - owning the CATS and cf-smoke-tests - managing the main integration pipelines that take all the bits and create a usable, well-tested distribution of the CF components - managing the cf-release repo, and the final release process - building tooling to generate manifests that compose all the split-out releases - canary apps used to monitor integration and production environments - providing other common functionality, e.g. route registration Product Manager: Amit Gupta, Pivotal Lead Engineer: Rob Dimsdale, Pivotal Engineer: Zachary Auerbach, Pivotal CF Infrastructure - splitting out, maintaining, and adding features to an etcd-release - splitting out, maintaining, and adding features to a consul-release - splitting out and maintaining a NATS-release - splitting out and maintaining a postgres-release - building tooling to generate manifests that compose all the split-out releases Product Manager: Amit Gupta, Pivotal Lead Engineer: Ryan Moran, Pivotal Engineer: Adrian Zankich, Pivotal We look forward to collaborating with all of you, we're still on the usual communication channels -- the cf-dev mailing list, and issues and PR on GitHub -- no changes there! Cheers, Amit attachment.html attachment.html
More All Messages By This Member

1 - 6 of 6

1

Previous Topic Next Topic

Home Hashtags Subgroups Terms