diff --git a/meta-romulus/conf/distro/openbmc-romulus.conf b/meta-romulus/conf/distro/openbmc-romulus.conf
new file mode 100644
index 0000000..9a5920a
--- /dev/null
+++ b/meta-romulus/conf/distro/openbmc-romulus.conf
@@ -0,0 +1,2 @@
+require conf/distro/openbmc-openpower.conf
+require conf/distro/include/phosphor-isolation.inc
diff --git a/meta-romulus/conf/local.conf.sample b/meta-romulus/conf/local.conf.sample
index 7bad7cd..83a3f9b 100644
--- a/meta-romulus/conf/local.conf.sample
+++ b/meta-romulus/conf/local.conf.sample
@@ -63,7 +63,7 @@
 # Ultimately when creating custom policy, people will likely end up subclassing
 # these defaults.
 #
-DISTRO ?= "openbmc-openpower"
+DISTRO ?= "openbmc-romulus"
 # As an example of a subclass there is a "bleeding" edge policy configuration
 # where many versions are set to the absolute latest code from the upstream 
 # source control systems. This is just mentioned here as an example, its not