Skip to content

Creating your first project

Setting up a new VDC project involves planning, creating AGS groups, and submitting a formal request. This guide walks you through the entire process step-by-step.

When do you need a new project?

Create a New Project When:

  • New team or initiative that doesn't fit in existing projects
  • Different silicon/platform with distinct validation needs
  • Separate organizational boundaries (different cost centers, security requirements)
  • Independent release cycles that don't align with existing projects
  • Distinct user groups that need separate access control

Consider Using Existing Project When:

  • Same team/organization with similar validation needs
  • Related work that benefits from shared ingredients or workflows

Pre-Requisites

Before starting the project creation process:

  • VDC-USERS Access - You must be a member of the VDC-USERS AGS group
  • Business Justification - Clear reason why a new project is needed
  • Team Planning - Know who needs access and at what levels
  • AGS Group Strategy - Decide whether to create groups yourself or get help

Step 1: Plan your project

Project Information Checklist

  • Project Name: Short, descriptive name (will be visible to all VDC users)
  • Project Purpose: 2-3 sentences explaining what the project will be used for
  • Team/Organization: Your organizational unit or team name
  • Silicon/Platform Association: If applicable, which silicon or platform this supports
  • Expected Users: Approximate number of people who will need access
  • Initial Admin: Who will be the primary project administrator

Access Planning

Determine who needs what level of access:

  • Project Admins: 2-3 people (include yourself and backup admins)
  • Project Users: Team members who will submit ingredient releases and run workflows
  • Project power users: Team members who will create ingredients and create workflows

Step 2: Create required AGS groups

Every VDC project requires three AGS groups for access control:

Required AGS Groups

  • [ProjectName]-Admins: Project administrators with full management permissions
  • [ProjectName]-Users: Standard users who can submit releases and run workflows
  • [ProjectName]-PowerUsers: advanced users with ingredient management and workflow creation permissions

AGS Group Creation Options

Option 1: Create Groups Yourself

Best for: Users familiar with AGS group creation process

Steps:

  1. Visit AGS Group Management - Create new AGS group
  2. Create three groups using the naming convention above
  3. Set yourself as group owner for all three groups
  4. Add initial members to appropriate groups
  5. Document group IDs for the HSD ticket

Option 2: Get Help from VDC Team

Best for: Users who need assistance with AGS group creation

Steps:

  1. Contact VDC team before submitting HSD ticket
  2. Provide project details and desired group names
  3. VDC team creates groups and assigns you as owner
  4. Receive group IDs to include in HSD ticket

Contact Information: Include this request in your HSD ticket and mention you need AGS group creation assistance.

Step 3: Submit HSD ticket

HSD Ticket Submission

URL: Submit HSD Ticket

service_type: tool Component: Select "tool.VDC"

HSD Ticket Template

Summary: Request new VDC project creation - [Your Project Name]

Description:
PROJECT INFORMATION:
- Project Name: [Proposed name]
- Project Purpose: [2-3 sentences describing business justification and use case]
- Team/Organization: [Your team/organization]
- Expected Users: [Approximate number of users]
- Silicon/Platform Association: [If applicable, which silicon/platform]

REQUIRED AGS GROUPS:
Please create the project with the following AGS groups:
- [ProjectName]-Admins: [AGS group ID or "Need VDC team to create"]
- [ProjectName]-Users: [AGS group ID or "Need VDC team to create"]  
- [ProjectName]-PowerUsers: [AGS group ID or "Need VDC team to create"]

INITIAL PROJECT SETUP:
- Initial Project Admin: [Your Intel email address]
- Additional Initial Admins: [List other admin users if any]

AGS GROUP ASSISTANCE:
[ ] I have created the required AGS groups (provide IDs above)
[ ] I need VDC team assistance to create AGS groups (please contact me)

Please create a new VDC project with the above specifications.

Required Information Details

Project Name Guidelines

  • Keep it descriptive but concise (e.g., "DMR-Validation", "NVL-Client-FV")
  • Avoid spaces - use hyphens or underscores %%todo: check%%
  • Make it recognizable to your team and organization
  • Consider future scope - don't make it too narrow

Project Purpose Examples

Good: "This project supports Diamond Rapids server validation activities for the Platform Integration & Validation team, including IFWI builds, BIOS testing, and automation workflows."

Poor: "We need a project for our team."

Step 4: wait for project creation

Timeline

  • Processing Time: 1 business days
  • AGS Group Creation: Additional 1-2 days if VDC team assistance is needed
  • Setup Completion: 1 day for initial project configuration

What Happens During Processing

  1. VDC team reviews your request and requirements
  2. AGS groups are created (if assistance was requested)
  3. Project is created in VDC with specified settings
  4. Initial permissions are set based on provided AGS groups
  5. Confirmation is sent with project details and next steps

You'll Receive

  • Project URL and access instructions
  • AGS group IDs (if created by VDC team)
  • Initial setup guidance for feeds and workflows

Step 5: Set up your new project

Initial Configuration

Once your project is created:

  1. Verify Access - Visit your new project in VDC Portal
  2. Add Team Members - Invite users to appropriate AGS groups
  3. Set Up Initial Ingredients - Create your first ingredients if ready
  4. Plan Workflows - Consider what automation you'll need

Managing AGS Groups

As the project admin, you're responsible for:

  • Adding new users to appropriate groups
  • Removing users who no longer need access
  • Managing group membership as your team evolves
  • Monitoring access for security and compliance

Best practices

Project Planning

  • Start small - begin with core team members and expand
  • Plan for growth - consider how your project might evolve
  • Document purpose - keep clear records of project goals and scope
  • Regular reviews - periodically assess project structure and membership

AGS Group Management

  • Use descriptive names - follow [ProjectName]-[Role] convention
  • Keep membership current - remove users promptly when they leave
  • Document processes - create team guidelines for requesting access
  • Regular audits - review group membership quarterly or semi-annually

Communication

  • Announce new project to your team and stakeholders
  • Document access process - make it easy for new users to join
  • Set expectations - clarify project scope and guidelines
  • Provide training - help team members learn VDC if needed

After project creation

Immediate Next Steps

  1. Test project access with your account
  2. Add initial team members to AGS groups
  3. Create your first feed for organizing ingredients
  4. Set up project documentation and guidelines

Continue Learning

Get Support

  • VDC Community - Connect with other project administrators
  • Documentation - Explore detailed guides for specific features
  • Training - Consider team training sessions for VDC adoption

Ready to create your project?

Follow the steps above and you'll have your VDC project up and running soon!