HackMD
  • Prime
    Prime  Full-text search on all paid plans
    Search anywhere and reach everything in a Workspace with Prime plan.
    Got it
      • Create new note
      • Create a note from template
    • Prime  Full-text search on all paid plans
      Prime  Full-text search on all paid plans
      Search anywhere and reach everything in a Workspace with Prime plan.
      Got it
      • Options
      • Versions and GitHub Sync
      • Transfer ownership
      • Delete this note
      • Template
      • Save as template
      • Insert from template
      • Export
      • Dropbox
      • Google Drive
      • Gist
      • Import
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
      • Download
      • Markdown
      • HTML
      • Raw HTML
      • Sharing Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Note Permission
      • Read
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Write
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • More (Comment, Invitee)
      • Publishing
        Everyone on the web can find and read all notes of this public team.
        After the note is published, everyone on the web can find and read this note.
        See all published notes on profile page.
      • Commenting Enable
        Disabled Forbidden Owners Signed-in users Everyone
      • Permission
        • Forbidden
        • Owners
        • Signed-in users
        • Everyone
      • Invitee
      • No invitee
    Menu Sharing Create Help
    Create Create new note Create a note from template
    Menu
    Options
    Versions and GitHub Sync Transfer ownership Delete this note
    Export
    Dropbox Google Drive Gist
    Import
    Dropbox Google Drive Gist Clipboard
    Download
    Markdown HTML Raw HTML
    Back
    Sharing
    Sharing Link copied
    /edit
    View mode
    • Edit mode
    • View mode
    • Book mode
    • Slide mode
    Edit mode View mode Book mode Slide mode
    Note Permission
    Read
    Owners
    • Owners
    • Signed-in users
    • Everyone
    Owners Signed-in users Everyone
    Write
    Owners
    • Owners
    • Signed-in users
    • Everyone
    Owners Signed-in users Everyone
    More (Comment, Invitee)
    Publishing
    Everyone on the web can find and read all notes of this public team.
    After the note is published, everyone on the web can find and read this note.
    See all published notes on profile page.
    More (Comment, Invitee)
    Commenting Enable
    Disabled Forbidden Owners Signed-in users Everyone
    Permission
    Owners
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Invitee
    No invitee
       owned this note    owned this note      
    Published Linked with GitHub
    Like BookmarkBookmarked
    Subscribed
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Subscribe
    ## Document Details - STATUS: - Point of Contact: Sayanchowdhury - Implementation Schedule: - Release Date: ## Goals To deploy plume as the tool to push Fedora Cloud images to cloud providers, and deprecate fedimg. ## Background and Strategic Fit fedimg has been the primary project uploading the cloud images and Atomic to AWS. fedimg did get a major revamp which gives us a control over the images but fedimg still uses a library which restricts us to do a lot of operation even scaling to other cloud providers. plume on other hand comes from CoreOS, which has been used to upload Container Linux to various cloud providers. Migrating from fedimg to plume, - give the project more set of eyes rather than just one. - benefit of scaling Fedora to more cloud providers. - Given both the project, do the same set of job it would be beneficial to have plume replacing fedimg. ## People Involved No one other than the point of Contact ## Assumptions and Questions Are there any assumptions to complete this work? - We plan to leverage Openshift for deploying the plume work. - We also plan to use fedora-messaging instead of fedmsg here. ## Initial Stories #### Personas - Plume maintainer: A maintainer of the Plume - Fedimg maintainer: A maintainer of Fedimg - Joystick maintainer: A maintainer of Joystick, the controller bridge of plume in fedora infrastructure - Fedora AWS user: A user of the Fedora AMIs on AWS - Fedora website maintainer: A person who updates fedora websites when there is new Fedora releases - Fedora 2WA release person: A person who does the 2-week Atomic releases. - Fedora Infrastructure person: A person from Fedora Infrastructure #### Story List - As a fedimg maintainer, I would like to have provision to add more system in plume so that it is easier to add more OS in the future and not just Container Linux. Acceptance criteria: Extension of plume code to add new system. - As a fedimg maintainer, I would like to add Fedora as a system so that we can push cloud images via plume. Acceptance criteria: Add Fedora as a system to plume code base - As a plume maintainer, I would like to see proper integration of new OS'ses so that we don't break our current Container Linux pipeline. Acceptance criteria: CL folks check that the container linux build flow does not break after adding new system. - As a Fedora website maintainer, I would like to see less change in the flow of the release process, so that during the next release everything works smoothly without much changes. Accpetance criteria: fedora-websites, get-amis script does not break or is update as per required. - As a Fedora 2WA release person, I would like to see the AMIs are properly uploaded, and not break like it does with fedimg, so that I don't need to go and manually upload or look why it did not upload. Acceptance criteria: Monitor couple of 2WA releases and seeing that they don't break. - As a joystick maintiner, I would like to see a script that would call plume with the appropriate parameters to upload the images to AWS. Acceptance criteria: A script is added into joystick repo that processes the messages and calls plume, and the appropriate channel. - As a joystick maintainer, I would like to see that we use fedora-messaging instead of fedmsg, because that would give use more realibility than fedmsg. Acceptance criteria: Fedora messaging both listening and publishing works in joystick script. - As a Fedora Infrastructure person, I would like to see the app deployed via openshift if possible so that it aligns with our goal to migrate more apps to Openshift. Acceptance criteria: Write a openshift config to deploy joystick as a openshift app - As a Fedora Infstructure person, I would like to see a RFR in place for the deployment of the project along with the playbooks in our ansible repo, so that we have ways to track the project and manage the boxes for it. Acceptance criteria: File RFR for plume and write the playbooks be it for openshift app or normal VM for both staging and prod. - As a Fedora AWS, I would like to know that the projects are changing so that I am aware where to report appropriate issues. Acceptance Criteria: Send a sunset email for fedimg. - As a fedimg maintainer, I would like to deprecate the fedimg project so that we move to use plume full time. Acceptance Criteria: Remove the fedimg boxes, and remove the playbooks after a couple of days, and finally put a deprecation notice on GH repo. ## Task breakdown #### Plume - [x] Add the provision in the code to add multiple system. - [x] Add Fedora as a system into plume - [x] Test the Container Linux release and build process before the integration of the PR. - [x] Build Plume RPM [1/2 day] #### Joystick - [x] Write a script to listen to pungi composes and trigger the plume AWS upload process - [x] Find the appropriate way to detect channels [1/2 day] - [x] Find the appropraite way to detect the image type [1/2 day] - [x] Write the integration with fedora-messaging - [x] Write the config file that would be consumed by joystick's fedora-messaging code [1/2 day] - [x] Write the listener consumer [trivial] - [x] Write the code that would query the regions to see if the images where uploaded [1 day] - [x] Push the appropriate messages for the regions, with as much similarity to earlier fedmsg messages [1 day] - [x] Write Openshift config to test the deployment as an Openshift App in fedora infrastructure [1 day] #### Fedora Infrastructure - [x] Write a RFR for the new resource for the deployment `Comments` * Smooge agreed to sponsor the RFR. - [ ] Security Audit of the application stack. `Comments` * This is stalling the deployment right now, 28/05, 29/05, 30/05. * - [x] Write the playbooks for the deployment: [1-2 days] - [MAJOR CATCH] We would try to deploy it using Openshift, if does not work we need to see how we can. - [ ] If fails, I would fail to quickly deploy using regular VM - [ ] Test the complete setup in stg [1-2 days] - [ ] Check on how fedimg sunset would be happening. Note the steps that needs to be followed [1/2 - 1 day] - [ ] Send email to Fedora announcements lists about the deprecation of fedimg [ 30 mins ] #### Fedora Websites - [ ] Test the compatibility of the get-amis.py or other neccessary scripts. With the new messages in place, we don't want the site generation to break [1 day] #### Fedora 2WA - [ ] Closely watch 2-3 releases. [3 weeks] #### Fedimg deprecation/Plume deployment - [ ] Deploy plume to production [1 day] - [ ] Follow the steps and deprecate fedimg [1/2 - 1 day] ## Phased Release #### Phase 1 Add the needed support for plume #### Phase 2 Write the script to control plume #### Phase 3 Test integration of everything #### Phase 4 Deployment and Deprecation.

    Import from clipboard

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lost their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template is not available.


    Upgrade

    All
    • All
    • Team
    No template found.

    Create custom template


    Upgrade

    Delete template

    Do you really want to delete this template?

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in via Google

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Tutorials

    Book Mode Tutorial

    Slide Mode Tutorial

    YAML Metadata

    Contacts

    Facebook

    Twitter

    Feedback

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions

    Versions and GitHub Sync

    Sign in to link this note to GitHub Learn more
    This note is not linked with GitHub Learn more
     
    Add badge Pull Push GitHub Link Settings
    Upgrade now

    Version named by    

    More Less
    • Edit
    • Delete

    Note content is identical to the latest version.
    Compare with
      Choose a version
      No search result
      Version not found

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub

        Please sign in to GitHub and install the HackMD app on your GitHub repo. Learn more

         Sign in to GitHub

        HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Available push count

        Upgrade

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Upgrade

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully