Esempio n. 1
0
    def set_arch(self, arch):
        """
        The field is mainly relevant to PXE provisioning.

        Using an alternative distro type allows for dhcpd.conf templating
        to "do the right thing" with those systems -- this also relates to
        bootloader configuration files which have different syntax for different
        distro types (because of the bootloaders).

        This field is named "arch" because mainly on Linux, we only care about
        the architecture, though if (in the future) new provisioning types
        are added, an arch value might be something like "bsd_x86".

        """
        return utils.set_arch(self, arch)
Esempio n. 2
0
    def set_arch(self,arch):
        """
        The field is mainly relevant to PXE provisioning.

        Should someone have Itanium machines on a network, having
        syslinux (pxelinux.0) be the only option in the config file causes
        problems.

        Using an alternative distro type allows for dhcpd.conf templating
        to "do the right thing" with those systems -- this also relates to
        bootloader configuration files which have different syntax for different
        distro types (because of the bootloaders).

        This field is named "arch" because mainly on Linux, we only care about
        the architecture, though if (in the future) new provisioning types
        are added, an arch value might be something like "bsd_x86".

        Update: (7/2008) this is now used to build fake PXE trees for s390x also
        """
        return utils.set_arch(self,arch)
Esempio n. 3
0
    def set_arch(self,arch):
        """
        The field is mainly relevant to PXE provisioning.

        Should someone have Itanium machines on a network, having
        syslinux (pxelinux.0) be the only option in the config file causes
        problems.

        Using an alternative distro type allows for dhcpd.conf templating
        to "do the right thing" with those systems -- this also relates to
        bootloader configuration files which have different syntax for different
        distro types (because of the bootloaders).

        This field is named "arch" because mainly on Linux, we only care about
        the architecture, though if (in the future) new provisioning types
        are added, an arch value might be something like "bsd_x86".

        Update: (7/2008) this is now used to build fake PXE trees for s390x also
        """
        return utils.set_arch(self,arch)
Esempio n. 4
0
 def set_arch(self,arch):
     """
     The field is mainly relevant to PXE provisioning.
     see comments for set_arch in item_distro.py, this works the same.
     """
     return utils.set_arch(self,arch)
Esempio n. 5
0
 def set_arch(self, arch):
     """
     Override the arch used for reposync
     """
     return utils.set_arch(self, arch, repo=True)
Esempio n. 6
0
 def set_arch(self, arch):
     """
     The field is mainly relevant to PXE provisioning.
     see comments for set_arch in item_distro.py, this works the same.
     """
     return utils.set_arch(self, arch)
Esempio n. 7
0
 def set_arch(self,arch):
     """
     Override the arch used for reposync
     """
     return utils.set_arch(self,arch,repo=True)