-
Notifications
You must be signed in to change notification settings - Fork 97
Create a new guide for provisioning virtual machines (2 of 3) #3608
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Changes from all commits
2d4b401
2baf401
2aa8b3d
8355b4c
f328a82
fde6f81
f570995
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,11 +1,9 @@ | ||
include::modules/con_security-settings.adoc[] | ||
|
||
ifndef::provisioning-virtual[] | ||
include::modules/proc_configuring-the-security-token-validity-duration.adoc[leveloffset=+1] | ||
endif::[] | ||
Comment on lines
+3
to
+5
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @stejskalleos The security token is not relevant for image-based provisioning, correct? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It is.
|
||
|
||
include::modules/proc_setting-a-default-encrypted-root-password.adoc[leveloffset=+1] | ||
|
||
ifdef::provisioning-cloud,provisioning-virtual[] | ||
include::modules/proc_removing-a-virtual-machine-upon-host-deletion.adoc[leveloffset=+1] | ||
endif::[] | ||
|
||
include::assembly_provisioning-fips-compliant-hosts.adoc[leveloffset=+1] |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -27,6 +27,4 @@ include::snip_prerequisites-common-compute-resource.adoc[] | |
Ensure that no other DHCP services run on this network to avoid conflicts with {SmartProxyServer}. | ||
For more information about network service configuration for {SmartProxyServers}, see {ProvisioningDocURL}preparing-networking[Preparing networking] in _{ProvisioningDocTitle}_. | ||
|
||
.Additional resources | ||
* For a list of permissions a non-admin user requires to provision hosts, see xref:permissions-required-to-provision-hosts_provisioning[]. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Note to myself: snip_prerequisites-common-compute-resource.adoc |
||
include::snip_resource-remove-vm.adoc[] | ||
include::snip_warning-destroy-vm-on-host-delete.adoc[] |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -13,8 +13,12 @@ A default installation of {ProjectName} contains three predefined profiles: | |
|
||
You can apply compute profiles to all supported compute resources: | ||
|
||
ifdef::provisioning,provisioning-cloud[] | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Are these flags used during the documentation generation? |
||
* xref:supported-cloud-providers[] | ||
endif::[] | ||
ifdef::provisioning,provisioning-virtual[] | ||
* xref:supported-virtualization-infrastructures[] | ||
endif::[] | ||
|
||
.Procedure | ||
. In the {ProjectWebUI}, navigate to *Infrastructure* > *Compute Profiles* and click *Create Compute Profile*. | ||
|
This file was deleted.
This file was deleted.
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,8 @@ | ||
[WARNING] | ||
==== | ||
By default, if a host entry that is associated with a virtual machine is deleted, the virtual machine will remain on the compute resource. | ||
|
||
If you want {Project} to destroy virtual machines on the compute resource when the associated host entry is deleted, navigate to *Administer* > *Settings* > *Provisioning* and set the *Destroy associated VM on host delete* setting to *Yes*. | ||
|
||
To avoid destroying virtual machines in this situation, disassociate the virtual machine from {Project} without removing it from the compute resource or keep the setting set to *No*. | ||
==== |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
include ../common/Makefile |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
../common |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
../common/docinfo.html |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
<title>{ProvisioningVirtualDocTitle}</title> | ||
<subtitle>Provision virtual machines on virtualization infrastructure by using images</subtitle> | ||
<productname>Red Hat Satellite</productname> | ||
<productnumber>{ProjectVersion}</productnumber> | ||
<abstract> | ||
<para> | ||
TODO | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Note to self: TODO "Overture is composed last." |
||
</para> | ||
</abstract> | ||
<authorgroup id="Author_Group"> | ||
<author> | ||
<firstname>Red Hat Satellite</firstname> | ||
<surname>Documentation Team</surname> | ||
<email>[email protected]</email> | ||
</author> | ||
</authorgroup> | ||
<xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
../common/images |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,51 @@ | ||
include::common/attributes.adoc[] | ||
include::common/header.adoc[] | ||
:context: provisioning-virtual | ||
:provisioning-virtual: | ||
|
||
= {ProvisioningVirtualDocTitle} | ||
|
||
// This guide is not ready for stable releases | ||
Comment on lines
+5
to
+8
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. question: Do you have reasons to believe that the guide would not work for unstable and/or foreman-el/foreman-deb? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It probably should work for all builds, since images are not part of Katello. However, right now I'm not sure it works at all and I would prefer to revisit this question later :)) There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I vote for making this guide "working" for all stable releases. I'll keep it in mind during the review |
||
ifdef::HideDocumentOnStable[] | ||
include::common/modules/snip_guide-not-ready.adoc[] | ||
endif::[] | ||
ifndef::HideDocumentOnStable[] | ||
|
||
ifdef::satellite[] | ||
include::common/modules/proc_providing-feedback-on-red-hat-documentation.adoc[leveloffset=+1] | ||
endif::[] | ||
|
||
include::common/assembly_introduction-to-provisioning.adoc[leveloffset=+1] | ||
|
||
include::common/assembly_preparing-client-platforms.adoc[leveloffset=+1] | ||
|
||
include::common/assembly_preparing-templates-for-provisioning.adoc[leveloffset=+1] | ||
|
||
include::common/assembly_preparing-networking.adoc[leveloffset=+1] | ||
|
||
include::common/assembly_security-settings.adoc[leveloffset=+1] | ||
|
||
include::common/modules/con_provisioning-contexts.adoc[leveloffset=+1] | ||
|
||
include::common/modules/proc_setting-the-provisioning-context.adoc[leveloffset=+2] | ||
|
||
include::common/modules/proc_using-novnc-to-access-virtual-machines.adoc[leveloffset=+1] | ||
|
||
include::common/assembly_provisioning-virtual-machines-kvm.adoc[leveloffset=+1] | ||
|
||
include::common/assembly_provisioning-virtual-machines-rhv.adoc[leveloffset=+1] | ||
apinnick marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
include::common/assembly_provisioning-virtual-machines-vmware.adoc[leveloffset=+1] | ||
|
||
ifndef::satellite[] | ||
include::common/assembly_provisioning-virtual-machines-proxmox.adoc[leveloffset=+1] | ||
endif::[] | ||
|
||
include::common/assembly_provisioning-virtual-machines-kubevirt.adoc[leveloffset=+1] | ||
|
||
[appendix] | ||
include::common/modules/ref_host-parameter-hierarchy.adoc[leveloffset=+1] | ||
|
||
[appendix] | ||
include::common/modules/ref_permissions-required-to-provision-hosts.adoc[leveloffset=+1] | ||
endif::[] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@stejskalleos What exactly are the networking requirements for image-based provisioning?
I thought that DHCP wasn't required, but the Prerequisites for image-based provisioning say that it is.
They still need at least one domain and one subnet, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's the thing, there are no exact requirements.
I'll describe it as best I can.
DHCP is always required. The host must have an IP address valid for its subnet and communication in the subnet.
Now, in Foreman, we have the terms managed and unmanaged DHCP, which, as far as I know, we came up with, rather than being an official tech buzzword.
Managed DHCP—Smart Proxy can add/update/remove DHCP records and leases and point the host to the bootloader file and boot configuration files. From the config files, it will get the path to the kernel and the init ramdisk and load them.
Unmanaged DHCP - Smart Proxy cannot do the stuff above, but that doesn't mean the host cannot obtain an IP from the DHCP.
In one sentence: The difference is whether or not the IP was assigned to the host by our smart-proxy, but the DHCP is still there.
So I would say that managed DHCP is preferred, but it is not required.