---
# System prepended metadata

title: Untitled

---

Demo Scenario

Day 1 (ops)
    1. create a single cluster (TKG on the provider of your choice)
        * 2 namespaces (non-prod, prod)
    2. TKG+ components (Ivy already has these)
    3. TAC service catalog
    4. Jenkins in the TKG cluster pipeline connected to TKG cluster
        * build story via buildpacks... 
        * application hosted in github
        * harbor in TKG (Ivy is already installing it)
            * scanning
            * signing (notary)
        * demonstrate a secure software supply chain with buildpacks
    5.Wavefront integration
    
Day 2 story: 
   - onboard TKG cluster into TMC
    we've outgrown a single cluster...
       - ingest *this cluster* into TMC and create a fleet...
       - speak to lifecycle and policy management across the fleet
    - then include TSM to push app to another cluster. 
    - Demonstrate Wavefront integration IRL


Action Items
1. Talk to Dustin about possibly relying on Antrea for Ivy instead of calico (because support is going away in next release) (Matyas)
A: Beijing is a month away and antrea is not ready for prime time at this time. Calico support is not going away next release, customers will have a choice. For the interim this should be solved by the art of story telling "the customer has choice". 
3. Reach out to Wavefront team for account for this 
    * https://confluence.eng.vmware.com/display/CNA/Wavefront+Demos 
5. Reach out to Grant about "FUN" sample apps for CI (David)
    * we'll focus on pacman-js or whack-a-mole apps (on github)
7. Fork Ivy gitlab repo for the project (Matyas)
  * structure should be 2 directories
  * TBD:
    * day1
        * sets up ivy with namespaces
        * jenkins, etc. APJ team is working on this
        * 
    * day2
        * git based stand-up for TKG instance
        * APJ team is working on this

Outcomes:
- Have an AWS environment
- infra code in engineering gitlab that sets up stuff
- Demo video
- CNR content -> Blog
