Uploaded image for project: 'Infrastructure'
  1. Infrastructure
  2. INFRA-698

Infra team sign off of new plugin site architecture

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: www
    • Labels:
      None
    • Similar Issues:

      Description

      We need to get the infra team to sign off this new addition.

      One of the earlier sticking point was the requirement to have a persistent volume on disk, but this requirement has been removed since then according to Thorsten Scherler.

      Perhaps this requires a quick meeting with Thorsten Scherler and R. Tyler Croy

        Attachments

          Issue Links

            Activity

            Hide
            kohsuke Kohsuke Kawaguchi added a comment -

            I talked to Tyler and I consider this effort complete. Quoting his response of this below that outlines the infra work that has to happen:

            With the MongoDB component killdozed (yay) I think /architecturally/
            things are in a good space as far as my operational concerns go.

            The plugin site, similar to the accounts-app suffers from a
            header/footer mismatch (and different CSS) to what is on jenkins.io. I
            don't think this is a deal breaker, but this guarantees that the three
            applications are going to diverge painfully as different people
            contribute to each (filed ages ago to address
            https://issues.jenkins-ci.org/browse/WEBSITE-88)

            Outside of that:

            • Update jenkins.io top nav (this might require some re-organization,
              gettin' busy up there)
            • Update wiki to direct people to plugins.jenkins.io
            • Update plugin-site README and documentation to be accurate on
              current architecture and contribution guidelines

            I believe from an infrastructure standpoint there remains:

            • Provision appropriately sized instance
            • Write Puppet manifest which would be responsible for:
            • managing Docker container
            • Setting up Apache with a vhost for SSL termination
            • Setup letsencrypt for plugins.jenkins.io
            • Setup monitoring to ensure that http is responsive, etc
            Show
            kohsuke Kohsuke Kawaguchi added a comment - I talked to Tyler and I consider this effort complete. Quoting his response of this below that outlines the infra work that has to happen: With the MongoDB component killdozed (yay) I think /architecturally/ things are in a good space as far as my operational concerns go. The plugin site, similar to the accounts-app suffers from a header/footer mismatch (and different CSS) to what is on jenkins.io. I don't think this is a deal breaker, but this guarantees that the three applications are going to diverge painfully as different people contribute to each (filed ages ago to address https://issues.jenkins-ci.org/browse/WEBSITE-88 ) Outside of that: Update jenkins.io top nav (this might require some re-organization, gettin' busy up there) Update wiki to direct people to plugins.jenkins.io Update plugin-site README and documentation to be accurate on current architecture and contribution guidelines I believe from an infrastructure standpoint there remains: Provision appropriately sized instance Write Puppet manifest which would be responsible for: managing Docker container Setting up Apache with a vhost for SSL termination Setup letsencrypt for plugins.jenkins.io Setup monitoring to ensure that http is responsive, etc
            Hide
            rtyler R. Tyler Croy added a comment -

            Kohsuke Kawaguchi I'm not sure how a definition of requirements means that this ticket is closed. I would expect that this ticket would be dependent on all the other tickets that enumerate those requirements and only once they're all met should we close this ticket

            Show
            rtyler R. Tyler Croy added a comment - Kohsuke Kawaguchi I'm not sure how a definition of requirements means that this ticket is closed. I would expect that this ticket would be dependent on all the other tickets that enumerate those requirements and only once they're all met should we close this ticket
            Hide
            kohsuke Kohsuke Kawaguchi added a comment -

            I originally meant to use this ticket to make sure the architecture and operational footprint of the new plugin site is within the acceptable boundaries, before the implementation is considered complete, which I consider achieved by your listed requirements. This preliminary sign-off needed to happen sooner because otherwise sizable engineering work was required.

            I think you are saying we should turn those requirements into actionable tickets now, which is fine. I'll do that.

            Show
            kohsuke Kohsuke Kawaguchi added a comment - I originally meant to use this ticket to make sure the architecture and operational footprint of the new plugin site is within the acceptable boundaries, before the implementation is considered complete, which I consider achieved by your listed requirements. This preliminary sign-off needed to happen sooner because otherwise sizable engineering work was required. I think you are saying we should turn those requirements into actionable tickets now, which is fine. I'll do that.

              People

              Assignee:
              rtyler R. Tyler Croy
              Reporter:
              kohsuke Kohsuke Kawaguchi
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: