Nova Healthcare Administrators, Inc., a wholly owned subsidiary of Independent Health Association, brings greater value to self-funded benefit management needs. Podnova reaches out to meet your podcasting needs It's a place where you can: manage your podcast subscriptions; discover new podcasts; find new podcasting software for Windows and for your mobile device.

NOVA’s online catalog is the official catalog of the College. The Catalog includes information about admission to the College, enrollment, degrees and certificates and academic policies.

Programs of Study & Course Descriptions

Programs of Study refer to an associate degree with its own curriculum code and all related specializations, certificates and career studies certificates.

PDF Edition

Looking for a Previous Catalog Year

Click here to view archieved catalogs from 2007-2008 to 2018-2019.

Archieved online Catalog from 2019-2020 can be accessed via the drop-down menu in the upper right corner.

NOVA is committed to preparing students for today’s workforce and recognizes computers to be an extension of the learning tools needed to be globally competitive. To attend NOVA, students are expected to have a laptop (or a desktop with webcam and microphone) that meets the minimum requirements for their major and internet access at home or through a mobile device hot spot. (NOTE: Chromebooks and iPads are useful but insufficient to replace a laptop. They will not run all the software typically needed at NOVA). Students can find the required specifications for their computers Student Computer Specifications document.

It is the policy of both Northern Virginia Community College (NOVA) and the Virginia Community College System (VCCS) to maintain and promote equal employment and educational opportunities without regard to race, color, sex or age (except where sex or age is a bona fide occupational qualification), religion, disability, national origin, marital status, veteran status, political affiliation, sexual orientation, or other non-merit factors. Inquiries concerning affirmative action and equal opportunity policies should be addressed to the College’s Office of the Assistant Attorney General, 4001 Wakefield Chapel Road, Annandale, Virginia 22003 (703-323-3266). Statement of Non-Discrimination: Equal Opportunity/Affirmative Action Institution

Catalog Policy

Northern Virginia Community College provides its Catalog, handbooks, website, and any other printed materials or electronic media for general guidance. The College does not guarantee that the information contained within them, including, but not limited to, the contents of any page that resides under the Domain Name System (DNS) registration of www.nvcc.edu is up-to-date, complete, and accurate, and individuals assume any risks associated with relying upon information without checking other credible sources, such as a student’s academic advisor. In addition, a student’s or prospective student’s reliance upon information contained within these sources, or individual program catalogs or handbooks, when making academic decisions does not constitute, and should not be construed as, a contract with the College. Further, the College reserves the right to make changes to any provision or requirement within these sources, as well as changes to any curriculum or program, whether during a student’s enrollment or otherwise.

Links or references to other materials or websites provided in the above-referenced sources are also for information purposes only and do not constitute the College’s endorsement of products or services referenced.

• 1Projects
• 3General Resources
• 4Resources for Contributors
  • 4.2Nova subteams
    • 4.2.2Sub-team Meetings

Projects

Nova

We align with what was the integrated release schedule, with three milestones.

But we do have some Nova specific process deadlines, please see Nova/Stein_Release_Schedule and Nova Process

Python Nova client

People

• PTL
  • Balazs Gibizer (gibi)
• Feature Drivers
• Code Reviewers
• Blueprint Czar (responsible for maintenance of Nova's blueprint lists)
  • Same as PTL.
• Bug Czar (responsible for organizing Nova's bug team that maintains Nova's bug list)
  • n/a
• Stable Branch Czar (works with stable maintenance team around Nova things)
  • Lee Yarwood(lyarwood)
• Security Czar (responsible for working with VMT and leading nova-coresec)
  • n/a
• Gate Czar (on top of the status of Nova in the CI gate)
  • n/a
• API Working Group Liaisons
  • Alex Xu (alex_xu)
• Ironic Liaison
  • Jim Rollenhagen (jroll)
• python-novaclient Czar
  • Andrey Kurilin (andreykurilin)
• Mentoring Czar
  • n/a
• Answers (ask.openstack.org) Czar
  • n/a
• Release Czar
  • Sylvain Bauza (bauzas)
• Docs Czar
• Notifications
  • Balazs Gibizer (gibi)
• Catering Czar
  • Chet Burgess (cburgess)

For bug tag owners, please see: Nova Bug Triage

For other folks, please see: Cross Project Liaisons (CPLs)

General Resources

Documentation

Release Process

• nova (and other projects under the compute program in governance) are released through the standard openstack release process: https://github.com/openstack/releases/blob/master/README.rst
• Server side release checklist is found in Nova/ReleaseChecklist

Code Review Dashboards

• Many Nova reviewers use dashboards to help them decide what to review. Nova/GerritDashboards tracks some of our favorites.

Other resources

• Details about the hypervisor support matrix

Resources for Contributors

Novak Djokovic

Contributor Documentation

Nova subteams

The Nova team meets weekly: Meetings/Nova.

In addition to a project-wide Nova gathering each week, there are some sub-teams. These sub-teams get together to discuss work going on in a focused area of Nova.

Code Review Subteam

Sub-teams don't need permission. They can be around for short or long periods of time.

A common pattern is an ad-hoc group of people, focusing on a sub set of reviews. They generally co-ordinate on here:https://etherpad.openstack.org/p/stein-nova-subteam-tracking

For each sub-team, the etherpad usually includes:

• list of people in the group (IRC nicks)
• list of patches the sub-team have reviewed, and think are ready for nova-core to approve
• list of patches the sub-team are focusing their reviews on
• May link to a regular meeting, but that is strictly optional

Over time, it is hoped, some sub-teams may become trusted enough to count as a +2. Even without counting as a +2, the review focus and implied prioritisation is still very valuable.

Sub-team Meetings

Some subteams are more formal, with a regular meeting and a wiki page.

• The linked wiki page should include:
  • The mission of the team
  • A regular meeting time
  • A coordinator / point of contact
  • Meeting Agenda
  • Links to logs from previous meetings
• A sub-team representative should regularly attend the main Nova meeting to provide a sub-team status report.
• A sub-team is *not* exclusively responsible for an area of code. Anyone is welcome to contribute anywhere. However, you are encouraged to communicate regularly with others working in the same area as you and sub-teams help encourage that.
• A sub-team is about organizing development efforts, but not necessarily setting direction for the project in a given area. Approval of patches is still done by the nova-core team and it is beneficial to publish designs to the openstack-dev mailing list for vetting in advance.

Active Sub-teams

TODO - this list can get out-of-date, need a better approach.

History

• Previous PTLs
  • Vish Ishaya (vishy), project beginning until Grizzly release
  • Russell Bryant (russellb), Havana and Icehouse releases
  • Michael Still (mikal), Juno and Kilo releases
  • John Garbutt (johnthetubaguy), Liberty and Mitaka releases
  • Matt Riedemann (mriedem), Newton, Ocata, Pike, and Queens releases
  • Melanie Witt (melwitt), Rocky and Stein releases
  • Eric Fried (efried), Train release

• Previous or current core reviewers:
  • Alex Xu
  • Andrew Laski
  • Balazs Gibizer
  • Brian D. Elliott
  • Brian Lamar
  • Brian Waldon
  • Chris Behrens
  • Chris Yeoh
  • Dan Prince
  • Dan Smith
  • Daniel Berrange
  • Devananda van der Veen
  • Eric Fried
  • Jay Pipes
  • Joe Gordon
  • Johannes Erdfelt
  • John Garbutt
  • Ken'ichi Ohmichi
  • Kevin L. Mitchell
  • Lorin Hochstein
  • Mark McLoughlin
  • Matt Dietz
  • Matt Riedemann
  • Melanie Witt
  • Michael Still
  • Nikola Dipanov
  • Pádraig Brady
  • Paul Voccio
  • Rick Harris
  • Russell Bryant
  • Sandy Walsh
  • Sean Dague
  • Soren Hansen
  • Stephen Finucane
  • Sylvain Bauza
  • Trey Morris
  • Vishvananda Ishaya
  • Yun Mao

Developer Contacts

The following is a list of major subsystems within Nova and people that youcan approach on IRC or email if you have questions about that particularsubsystem. IRC nicks are in parentheses.

Nova Objects Framework

libvirt virt driver

Hyper-V virt driver

VMWare/vCenter virt driver

XenAPI virt driver

Ironic/bare metal

Scheduling and resource tracking

Block device mapping and volume attachments

REST API

Database

Cells (v1 and v2)

nova-network

Neutron

RPC

Notification system

PCI Devices / SRIOV

Placement / Resource Providers

So, you want to learn more about Nova?

To learn more about Nova, please read out about Nova Mentoring

Nova Southeastern University